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
Investigating further into HasZ shows some inconsistencies between types. These are expected:
forgeom_typein POINT LINESTRING LINEARRING POLYGON;do
geom="$geom_type Z EMPTY"echo"$geom"echo -n " copy: "
./bin/geosop -a "$geom" -f wkt
echo -n " hasZ: "
./bin/geosop -a "$geom" -f txt hasZ
done
outputs
POINT Z EMPTY
copy: POINT Z EMPTY
hasZ: true
LINESTRING Z EMPTY
copy: LINESTRING Z EMPTY
hasZ: true
LINEARRING Z EMPTY
copy: LINEARRING Z EMPTY
hasZ: true
POLYGON Z EMPTY
copy: POLYGON Z EMPTY
hasZ: true
and similar expected behaviour with M/ZM coordinate types.
However, these are not expected:
forgeom_typein GEOMETRYCOLLECTION MULTIPOINT MULTILINESTRING MULTIPOLYGON;do
geom="$geom_type Z EMPTY"echo"$geom"echo -n " copy: "
./bin/geosop -a "$geom" -f wkt
echo -n " hasZ: "
./bin/geosop -a "$geom" -f txt hasZ
done
outputs
GEOMETRYCOLLECTION Z EMPTY
copy: GEOMETRYCOLLECTION EMPTY
hasZ: false
MULTIPOINT Z EMPTY
copy: MULTIPOINT EMPTY
hasZ: false
MULTILINESTRING Z EMPTY
copy: MULTILINESTRING EMPTY
hasZ: false
MULTIPOLYGON Z EMPTY
copy: MULTIPOLYGON EMPTY
hasZ: false
and similar behaviour with M/ZM coordinate types. The expected behaviour should mimic the non-multi empty geometries, similar to PostGIS:
postgis=# select st_astext('POINT Z EMPTY');
st_astext
---------------
POINT Z EMPTY
(1 row)
postgis=# select st_astext('MULTIPOINT Z EMPTY');
st_astext
--------------------
MULTIPOINT Z EMPTY
(1 row)
postgis=# select st_astext('GEOMETRYCOLLECTION Z EMPTY');
st_astext
----------------------------
GEOMETRYCOLLECTION Z EMPTY
(1 row)
The text was updated successfully, but these errors were encountered:
Investigating further into HasZ shows some inconsistencies between types. These are expected:
outputs
and similar expected behaviour with
M
/ZM
coordinate types.However, these are not expected:
outputs
and similar behaviour with
M
/ZM
coordinate types. The expected behaviour should mimic the non-multi empty geometries, similar to PostGIS:The text was updated successfully, but these errors were encountered: