ForcePolygonCCW and others missing?

Skip to first unread message

Jukka Rahkonen

Feb 26, 2021, 2:24:11 PMFeb 26
to SpatiaLite Users


I tried to use function ST_ForcePolygonCCW with two spatialite-gui versions, one with spatialite 4.3.0a and another with version 5.0.0-beta0. Both versions claim that there is no such function even it is documented in Same applies to other functions that deal with orientation of polygons. Are they dropped intentionally or by accident?

-Jukka Rahkonen-

Feb 26, 2021, 4:07:28 PMFeb 26
Hi Jukka,

please note: the spatialite-sql-latest.html documentations
corresponds to the latest 5.0.1

the first implementation of ST_ForcePolygonCCW() and related was
committed during October 2017, so for sure it couldn't be supported
by 4.3.0a that was released on June 2015.
it should be probably supported by 5.0.0-beta0 that was released
on August 2018, but I'm not really sure if your GUI tool was
based on the released package or on some earlier development

just for the sake of my personal curiosity, why you are still
using obsolete versions ?

if you are looking for a reasonably fresh pre-compiled spatialite_gui
for Windows you can download the most recent version based on 5.0.0

bye Sandro

Jukka Rahkonen

Feb 26, 2021, 5:51:15 PMFeb 26
to SpatiaLite Users

I was having a look at this GDAL ticket and experimenting with the same Spatialite versions that most GDAL Windows users have. My OSGeo4W installation, updated 2021-01-19, has still 4.3.0 and the binaries from come with 5.0.0.  But I was indeed all too lazy with my trials, the gisinternals package with released version 5.0.0. does have ForcePolygonCCW and I could have checked that the previous 4.3a version was published long before this conversation

I will probably keep the older spatialite-gui available also in the future just because it allows to update the attributes of GeoPackage tables and the tool is sometimes more handy than DB Browser for SQLite. The new spatialite-gui seems to open GeoPackage tables as read only. I know, user must be careful.

Everything fine now.

Reply all
Reply to author
0 new messages