[db-wg] Geolocation data prototype in the RIPE Database

At 15:29 05/10/2011 +0200, Denis Walker wrote:

Rather than make new toys, sure would have been nice if RIPE saw the 
justification of fixing up and correcting the country code listing for ERX 
prefixes (from 2004) in delegated-ripencc-latest, that list all ERX objects 
as country code=EU.  Team Cymru, among others, use that for 
geolocation.   But alas, the answer I received from RIPE was basically - No.

-Hank

>Dear colleagues,
>
>At the RIPE 62 Meeting in Amsterdam the RIPE NCC Database Group was
>asked to investigate handling geolocation data in the RIPE Database. We
>now have a proof of concept prototype for discussion by the community.
>
>Based on input from a number of community sources and the subsequent
>presentation at RIPE 62, this prototype has two new optional attributes
>for storing geolocation data and language details.
>
>We have written an article about the design approach on RIPE Labs
>https://labs.ripe.net/Members/denis/geolocation-prototype-for-ripe-database
>
>This prototype references a sand-boxed TEST Database and does not have
>any pre-loaded geolocation or language data. But you can create your own
>data to see how easy it is to manage this new, optional information. We
>also have a prototype Geolocation Finder tool to search for this data.
>
>Another article on RIPE Labs shows how to create the new optional
>attributes and use the Geolocation Finder tool to search for this data.
>No changes in this sand-boxed TEST Database will affect the production
>RIPE or TEST Database services.
>
>The article is available at:
>https://labs.ripe.net/Members/denis/example-usage-of-ripe-database-geolocation-prototype
>
>We invite comments or feedback on this design and suggestions for how to
>move forward if it is seen as a useful addition to the RIPE Database by
>the community.
>
>Regards
>
>Denis Walker
>Business Analyst
>RIPE NCC Database Group