5 ms·
It seems to be somewhat particular about relation IDs. I have it working for Palo Alto, with relation ID 1544955. If you want to try this for your city, I recom
by arctux 8y ago
It seems to be somewhat particular about relation IDs. I have it working for Palo Alto, with relation ID 1544955. If you want to try this for your city, I recommend zooming in the city on openstreetmap.org, clicking the "Query features" button on the right side of the map (it's the cursor with a question mark icon), and clicking within the boundaries of you city. On the left side, a list of features will appear. Scroll down to enclosing features, and click on the appropriate entry. A relation name and number will be displayed at the top, with the OSM data below.
I hope this stays within the Overpass API server's usage limits. Processing Palo Alto caused the page to download ~85 MB from overpass-api.de, which asks users to stay below 10k queries and 5 GB per day. The OSM wiki lists other servers, some of which allow heavier usage.[0]
[0]: https://wiki.openstreetmap.org/wiki/Overpass_API https://wiki.openstreetmap.org/wiki/Overpass_API
- mvexel 8y agoThat is a good way to find the boundary relation and one I had not thought of. As for the Overpass API limits -- yes, if folks start to actually use this on any kind of scale, this will croak. I should perhaps do some logging, https://github.com/mvexel/meetyourmappers/issues/3 https://github.com/mvexel/meetyourmappers/issues/3
- incompatible 8y agoMy city boundaries were not available, only a state level, which was too big for this tool.