You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wrote a couple of requests that sum up the bicycle parking capacity for a number of cities. One produces polygons and uses the make statement (https://overpass-turbo.eu/s/1VAs), the other produces points and uses the convert statement (https://overpass-turbo.eu/s/1VAt). Exporting the result to GeoJSON using Turbo produces a file with no data (maybe this is an issue for Turbo rather than the API ?).
The irony is that the result is very close to the GeoJSON format. Using the clause [out:json], the geometries are output in GeoJson. The only bits missing to produce GeoJSON is to rename elements to features, wrap them up in a FeatureCollection, and rename tags to properties.
My use case is to output the result of those request in GeoJSON format, then import this data in a uMap map. That would be very handy.
The text was updated successfully, but these errors were encountered:
I wrote a couple of requests that sum up the bicycle parking capacity for a number of cities. One produces polygons and uses the
make
statement (https://overpass-turbo.eu/s/1VAs), the other produces points and uses theconvert
statement (https://overpass-turbo.eu/s/1VAt). Exporting the result to GeoJSON using Turbo produces a file with no data (maybe this is an issue for Turbo rather than the API ?).The irony is that the result is very close to the GeoJSON format. Using the clause
[out:json]
, the geometries are output in GeoJson. The only bits missing to produce GeoJSON is to renameelements
tofeatures
, wrap them up in aFeatureCollection
, and renametags
toproperties
.My use case is to output the result of those request in GeoJSON format, then import this data in a uMap map. That would be very handy.
The text was updated successfully, but these errors were encountered: