Timeline for Trying to show an OSM/Nominatim relation on an OpenLayers 3 map
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2016 at 10:28 | comment | added | mmd | You could check how this is done in overpass turbo: overpass-turbo.eu/s/hNU ... the respective library osmtogeojson already has this implemented. Maybe you could delegate the coversion from osm to geojson to such a library and only display geojson in your openlayers3 app. Otherwise you would need to implemente some logic similar to this code snippet in osmtogeojson. | |
| Aug 11, 2016 at 10:20 | comment | added | Adam Baranyai |
Yes, this did the trick. But what abbout inner rings? For example, relation id 7382, when viewed on nominatim.openstreetmap.org has one inner ring. When fetched with Overpass API, it returns multiple ways which are marked by role->inner. I can connect those ways also, as I am doing right now with the outer ring, but what if a relation has multiple inner rings? How can I be sure that I am connecting the ways correctly?
|
|
| Aug 11, 2016 at 10:16 | vote | accept | Adam Baranyai | ||
| Aug 10, 2016 at 13:24 | history | edited | mmd | CC BY-SA 3.0 |
deleted 55 characters in body
|
| Aug 10, 2016 at 13:19 | history | answered | mmd | CC BY-SA 3.0 |