The following is an example of a gml:Curve that was loaded into Postgres using FME.
379352.97 580000 379387.02 580022.77 379392.7 580028.98 379412 580031 379419.11 580023.97 379420 580016.95 379446.92 580000379446.92 580000 379508 580004.5 379521 580016.5 379529.14 580047.36 379531.91 580057.92 379552.03 580087.79 379559.12 580095.84 379606.5 580115.5 379618 580112.5 379630.79 580097.79 379636.51 580091.2 379667.5 580050 379717.24 580096.52 379729.15 580088.65
Postgres accepted the geometry but all attempts to do anything with it yield the error:
SELECT id FROM water WHERE ST_IsValid(geom) = 'f' returns this error rather than the id.
Is there anyway round this? As a related question is there any reason why ST_IsValid returns an error, rather than regarding an error as valid = false.
Fortunately, I have a shape file of the same area, in which the geometry is encoded as a MultiLinestring, but I would like to avoid having to reload the entire table if possible.
أكثر...
379352.97 580000 379387.02 580022.77 379392.7 580028.98 379412 580031 379419.11 580023.97 379420 580016.95 379446.92 580000379446.92 580000 379508 580004.5 379521 580016.5 379529.14 580047.36 379531.91 580057.92 379552.03 580087.79 379559.12 580095.84 379606.5 580115.5 379618 580112.5 379630.79 580097.79 379636.51 580091.2 379667.5 580050 379717.24 580096.52 379729.15 580088.65
Postgres accepted the geometry but all attempts to do anything with it yield the error:
ERROR: Unknown geometry type: 9 - CompoundCurve
including ST_IsValid(geom). Therefore, there is no way to even find out the unique id of the offending geometry, as
SELECT id FROM water WHERE ST_IsValid(geom) = 'f' returns this error rather than the id.
Is there anyway round this? As a related question is there any reason why ST_IsValid returns an error, rather than regarding an error as valid = false.
Fortunately, I have a shape file of the same area, in which the geometry is encoded as a MultiLinestring, but I would like to avoid having to reload the entire table if possible.
أكثر...