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
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem you would like to solve.
It would be nice to be able to check that a GeoSeries (and at the libcuspatial level, a geometry column) contains valid data. For example if there are unclosed geometries, etc.
Also, we should provide GeoSeries APIs/attributes is_valid and is_simple (also possibly is_ring) a la GeoPandas, as well as the equivalent at the libcuspatial C++ level.
We do not introspect data to validate it at construction time or at the point of calling algorithms. This is because doing so is an expense users are not likely willing to pay at all times (especially if their data has been validated already). It is up to the user to validate data, so we should provide APIs to do so.
Describe any alternatives you have considered
Validation on the host using GeoPandas, Shapely or other libraries is possible but the round trip and memory overhead is too expensive.
Not providing validation APIs makes our software potentially harder to use.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is this a new feature, an improvement, or a change to existing functionality?
New Feature
How would you describe the priority of this feature request
Medium
Please provide a clear description of problem you would like to solve.
It would be nice to be able to check that a GeoSeries (and at the libcuspatial level, a geometry column) contains valid data. For example if there are unclosed geometries, etc.
This should follow the definitions here: https://postgis.net/docs/using_postgis_dbmanagement.html#OGC_Validity
Also, we should provide GeoSeries APIs/attributes
is_valid
andis_simple
(also possiblyis_ring
) a la GeoPandas, as well as the equivalent at the libcuspatial C++ level.We do not introspect data to validate it at construction time or at the point of calling algorithms. This is because doing so is an expense users are not likely willing to pay at all times (especially if their data has been validated already). It is up to the user to validate data, so we should provide APIs to do so.
Describe any alternatives you have considered
Validation on the host using GeoPandas, Shapely or other libraries is possible but the round trip and memory overhead is too expensive.
Not providing validation APIs makes our software potentially harder to use.
Additional context
No response
The text was updated successfully, but these errors were encountered: