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/db-wg@ripe.net/

[db-wg] Future of "geoloc:"

• Previous message (by thread): [db-wg] Role of RIPE NCC in geofeed, abuse-c checks, etc
• Next message (by thread): [db-wg] Future of "geoloc:"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

denis walker ripedenis at gmail.com
Tue Apr 12 21:17:00 CEST 2022

Colleagues

Now we have the "geofeed:" attribute, what should we do with
"geoloc:"? Right now far more people are using "geoloc:" than
"geofeed:".

denis$ zgrep "^geofeed:" ~/Desktop/ripe.db.inetnum.gz  | wc -l
     289
denis$ zgrep "^remarks:\s*geofeed" ~/Desktop/ripe.db.inetnum.gz  | wc -l
      13

Although from the 289 there are only 161 unique organisations.

denis$ zgrep "^geoloc:" ~/Desktop/ripe.db.inetnum.gz  | wc -l
   35453

cheers
denis
co-chair DB-WG

• Previous message (by thread): [db-wg] Role of RIPE NCC in geofeed, abuse-c checks, etc
• Next message (by thread): [db-wg] Future of "geoloc:"

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ db-wg Archives ]