-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Multipolygons are breaking geojson convertion #135
Comments
UPD: I did this patch for me, it works, but it definitely need to be slightly improved before merge:
|
Thanks for spotting and fixing! |
I'm wondering if it might be best to import another lib for converting OSM format to geojson and let this lib focus on the API stuff, rather than maintain a homegrown converter. Something like osm2geojson, perhaps? |
I had a quick look at replacing the built-in geojson method with osm2geojson, found that osm2geojson uses 7 decimal points of precision for coordinates, while this library has been using 6 (default from the geojson library) and osm2geojson nests the |
I think the best way to go about supporting GeoJSON properly is not to roll our own but instead support |
This is fixed on the main branch now with #140 merged in. Looking to get 0.7.1 out soon with this fix. |
When trying to fetch multipolygons (e.g. 11038555), I get error:
It seems that happens because outer and inner members are not always closed: they may be just ways.
Are you planning to improve this?
The text was updated successfully, but these errors were encountered: