Add support for nodes and relations?
Thank you for building this neat tool! It inspired me to add some etymology information to places in my area. I had been hoping that this tool would work with boundary relations and natural=peak nodes as I added etymology details to a funny local case where the Town of Lincoln, VT is named after a Revolutionary War general with surname “Lincoln”, while the biggest mountain in the town was named after the US president with the same surname. I also added etymology tags to waterfall nodes and a few non-way POIs.
I see that e30ae33f removes node and relations from the query "to make the query faster". How much of a difference does dropping nodes and relations make? I wonder if there might be other techniques to speed up the site while still show all types of OSM objects? For example, only re-fetching after a short delay (e.g. 2 seconds) so that a zoom and pan operation allows the user to set their view first and then trigger a single query rather than trigger many queries during zoom and pan. Another option might be to only re-query if the zoom or center have changed by a significant amount, allowing slight tweaks to the viewport to use already-loaded data.
A more difficult and comprehensive option would be to do client-side caching of data for different granular zoom ranges and viewports. From CONTRIBUTING.md I see that there is server-side caching involved in CachedBBoxGeoJSONQuery.php, but it seems like every slight zoom and move may be triggering another live query. I wonder if doing zoom-dependent rounding on the BBOX coords would greatly increase cache hits? Or is the client already doing some rounding in the query being sent to the server?
I'm happy to brain storm further if that's of interest or maybe try out some patches in a few weeks when I get some free time. :-) Thanks again for making this neat tool and inspiring entry of etymology information!