[Talk-us] new geocoder
I'm working on an app that requires a forward geocoder with autocomplete, so I've been experimenting with putting OSM data (US only for now) into Elasticsearch. There's still a lot to do, but it's ready to play with, so I figured I'd share the demo: http://mapzen.com/pelias/ This uses Quattroshapes Geonames for the admin hierarchy. OSM streets, addresses, and POIs get reverse geocoded into the hierarchy. There are three endpoints which we'd like to make widely available in the future, but for now these are for testing only might break/change/vanish at any moment: Suggestions (works pretty well) http://api-pelias-test.mapzen.com/suggest?query=brook Reverse (works okay) http://api-pelias-test.mapzen.com/reverse?lat=40.68685lng=-73.9885 Search (needs work!) http://api-pelias-test.mapzen.com/search?query=1369%20coffee%20house%20cambridge Would love feedback, suggestions, help, etc! -Randy ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] new geocoder
This is awesome, Randy. Can you point to the code if it's available? I'd love to look at how you're pulling together the ElasticSearch documents. How much disk space does the US index use? On Sun, Jan 12, 2014 at 8:47 AM, Randy Meech randy.me...@gmail.com wrote: I'm working on an app that requires a forward geocoder with autocomplete, so I've been experimenting with putting OSM data (US only for now) into Elasticsearch. There's still a lot to do, but it's ready to play with, so I figured I'd share the demo: http://mapzen.com/pelias/ This uses Quattroshapes Geonames for the admin hierarchy. OSM streets, addresses, and POIs get reverse geocoded into the hierarchy. There are three endpoints which we'd like to make widely available in the future, but for now these are for testing only might break/change/vanish at any moment: Suggestions (works pretty well) http://api-pelias-test.mapzen.com/suggest?query=brook Reverse (works okay) http://api-pelias-test.mapzen.com/reverse?lat=40.68685lng=-73.9885 Search (needs work!) http://api-pelias-test.mapzen.com/search?query=1369%20coffee%20house%20cambridge Would love feedback, suggestions, help, etc! -Randy ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] new geocoder
On Sun, Jan 12, 2014 at 10:20 AM, Ian Dees ian.d...@gmail.com wrote: Can you point to the code if it's available? I'd love to look at how you're pulling together the ElasticSearch documents. Sure -- definitely available: https://github.com/mapzen/pelias Here's the address class: https://github.com/mapzen/pelias/blob/master/lib/pelias/address.rb How much disk space does the US index use? Just under 60GB currently. Much of that is Quattroshapes, which are stored as GeoJSON polygons. I'm currently indexing all named streets, most addresses (haven't done interpolations yet), and the POIs I think someone might possibly search for. -Randy ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] new geocoder
On 1/12/2014 9:47 AM, Randy Meech wrote: so I've been experimenting with putting OSM data (US only for now) into Elasticsearch. Looks fantastic! One corner case that would be nice to handle is searching for a street with directional without the directional. Example: North Laurens Street Search: Laurens St - returns North Laurens Street as one of the suggestions. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
