Opened 10 years ago
Closed 7 years ago
#3112 closed enhancement (wontfix)
Add a new function to determine if a geometry will be accepted by routines not handling curve geometries
Reported by: | aaime | Owned by: | pramsey |
---|---|---|---|
Priority: | low | Milestone: | PostGIS 2.4.0 |
Component: | postgis | Version: | 2.1.x |
Keywords: | Cc: |
Description
ST_HasArc almost does the job, but will return "false" on a curve geometry that does not contain any circular segment (e.g., a compound curve that only contains straight segments).
Please add a new function to determine if a geometry is safe to use with "non curve aware" functions (regardless of its circular segment contents)
Change History (6)
comment:1 by , 10 years ago
comment:2 by , 10 years ago
Milestone: | PostGIS 2.1.8 → PostGIS 2.2.0 |
---|---|
Priority: | medium → low |
comment:3 by , 9 years ago
The problem is not so much in categorizing whether a geometry has curves in them as in categorizing which functions do or do not handle curved geometries. It might be better just to do a run through the whole functional set and pushing all arc's through stroking so that we have no functions that do not "support" curved geometry. If that results in a little weirdness (the first stop in running simplify on an arced object would be adding a bunch of vertices to it) at least we'd have 100% functional coverage for those types.
comment:4 by , 9 years ago
Milestone: | PostGIS 2.2.0 → PostGIS 2.3.0 |
---|
I think I'd rather move to more universally stroking all arc features and just feeding them through rather than trying to flag/error them.
comment:5 by , 8 years ago
Milestone: | PostGIS 2.3.0 → PostGIS 2.4.0 |
---|
comment:6 by , 7 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
could be done by only looking at GeometryType output (recursively checking within GEOMETRYCOLLECTION, which does allow for internal curves)