This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] Future of "geoloc:"
- Previous message (by thread): [db-wg] Future of "geoloc:"
- Next message (by thread): [db-wg] NWI-2 historical queries
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Massimo Candela
massimo at ntt.net
Wed Apr 13 02:27:00 CEST 2022
Hi Denis, You have an interesting question. Possibly, as Laurent suggested, we could inform the users to use geofeed instead of geoloc. On 12/04/2022 21:17, denis walker via db-wg wrote: > Right now far more people are using "geoloc:" than > "geofeed:". This is definitely true. However, in this comparison keep in mind that while geoloc is a lat,long specified for each inetnum, a geofeed can be associated to a parent inetnum and contain definitions valid for multiple more-specific inetnums (and prefixes). > > denis$ zgrep "^geofeed:" ~/Desktop/ripe.db.inetnum.gz | wc -l > 289 including inet6num they are 352 > denis$ zgrep "^remarks:\s*geofeed" ~/Desktop/ripe.db.inetnum.gz | wc -l > 13 There are 537 inet(6)nums with "Geofeed" remarks (uppercase G) and 19 with "geofeed". Ciao, Massimo
- Previous message (by thread): [db-wg] Future of "geoloc:"
- Next message (by thread): [db-wg] NWI-2 historical queries
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]