-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace nominatim with something more lightweight #5
Comments
Possibly https://github.com/digidem/osm-p2p-server ? |
Isn't Nominatim a requirement for the Photon geocoder? Otherwise, how do you import the Photon Elastic Search data? Thanks for your great work! I'm trying to set up a planet vector tile and geocoder server and what you're doing is very inspiring :) |
Nominatim would still be a necessary part of photon index generation, yeah. The idea is just to save resources at runtime. I went to go check on my demo server though and while both GraphHopper and photon are using a fair bit of memory I don't see anything in |
I was speaking with a friend about this over brunch and realized that nominatim supports queries that could be used to implement categorical search, which would be very useful so I'm inclined to keep it for now. |
I only used Photon with a pre-generated search index dump. I don't know if Nominatim runs in the background. I'm still learning how to configure all these tools. |
If you've used Photon with the pre-generated index then you probably didn't have Nominatim running in the background, but Headway is currently configured to use both. |
I think I'm closing this for now, because categorical search is pretty important for a maps app and nomimatim is probably the easiest way to get implement it. Photon supports query filtering by OSM tag, but it doesn't support only querying by OSM tag. It also requires text. |
Right now nominatim is just used as a source of truth for OSM data. Only the lookup endpoint is exposed. There's no reason we couldn't replace it with something more lightweight built on top of postgis. That could drastically reduce the memory requirements for the full Headway stack, potentially even to the point that the whole planet could be hosted with 64GB of RAM which is about the point where it becomes feasible to do.
The text was updated successfully, but these errors were encountered: