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.68685&lng=-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
