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
Calling Geo.JSON.decode! on this data will result in a %Geo.GeometryCollection{} to be returned. The properties are preserved in the Geo structs – which is great – but won't be interpreted by other GeoJSON consumers (unless I'm misunderstanding here) because they're not technically part of the spec.
Is there a reason why there isn't first class FeatureCollection support in Geo?
The text was updated successfully, but these errors were encountered:
Hiya!
I started using this library to transform results from GDAL
ogr2ogr
CLI executions into structured GeoJSON.I noticed that if a
FeatureCollection
is passed intoGeo.JSON.decode!/1
, it is returned as a%Geo.GeometryCollection{}
.As an example, consider the following GeoJSON:
Calling
Geo.JSON.decode!
on this data will result in a%Geo.GeometryCollection{}
to be returned. Theproperties
are preserved in theGeo
structs – which is great – but won't be interpreted by other GeoJSON consumers (unless I'm misunderstanding here) because they're not technically part of the spec.Is there a reason why there isn't first class
FeatureCollection
support in Geo?The text was updated successfully, but these errors were encountered: