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
Though this may not be the right thing to do, the fact is most geojson generating libraries (i.e. GDAL OGR) do generate "type": "FeatureCollection" root element, even if there is only one polygon or multipolygon in features array.
Could be great if osmium extract accepts this geojson format, so there won't be any effort to reformat geojson (extract the feature element) to fit the expected osmium format.
It could simply use the first object in features array ignoring all the others, if there are more than one feature. @joto What do you think of it?
The text was updated successfully, but these errors were encountered:
It could simply use the first object in features array ignoring all the others, if there are more than one feature.
I have just started using osmium-tool in my projects. Curious to understand why we don't want to do all features (more than 1 feature) in a FeatureCollection?
@bkowshik Because to use all features we'd have to merge them somehow first. That's a potentially complex geometry operation with possibly overlapping polygons. This is outside the scope of Osmium.
Though this may not be the right thing to do, the fact is most geojson generating libraries (i.e. GDAL OGR) do generate
"type": "FeatureCollection"
root element, even if there is only one polygon or multipolygon infeatures
array.Could be great if osmium extract accepts this geojson format, so there won't be any effort to reformat geojson (extract the feature element) to fit the expected osmium format.
It could simply use the first object in
features
array ignoring all the others, if there are more than one feature.@joto What do you think of it?
The text was updated successfully, but these errors were encountered: