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
The easiest way to handle this is just to hard-code the geometry column type as GEOMETRY which is what I already do for GeoJSON files.
You could try and work out up-front if all the features are of the same type (but this could take a long time). You could also allow the user to manually specify the type of the geom column as a param. This is basically the same problem you already anticipated with GeometryCollection in #8 so you might as well apply the same solution for both.
The text was updated successfully, but these errors were encountered:
shp_to_spatialite()
attempts to be "clever" and detect a suitable geometry type based on the first recordgeometry-to-spatialite/geometry_to_spatialite/shapefile.py
Line 62 in f4011e9
This falls apart once you have a shapefile that has multiple geometry types in it. Here's an example of a shapefile input that reproduces this problem
two_things.zip
The easiest way to handle this is just to hard-code the geometry column type as
GEOMETRY
which is what I already do for GeoJSON files.You could try and work out up-front if all the features are of the same type (but this could take a long time). You could also allow the user to manually specify the type of the geom column as a param. This is basically the same problem you already anticipated with
GeometryCollection
in #8 so you might as well apply the same solution for both.The text was updated successfully, but these errors were encountered: