On Tue, 25 May 2021 14:39:32 -0700 (PDT), David Anderson wrote:
> My assumption is that it is the same st_geometry encoding that ESRI
> has been using with Postgres and Oracle and SQLite in the ArcMap
a long story lasting from many years summarized in just few lines:
step #1) SpatiaLite is the first full-fledged Spatial DBMS based
on the top of SQLite, and is almost fully compliant with OGC
SFS and ISO SQL-MM standard specifications.
step #2) when OGC and the US Army Geospatial Center start working
on a new standard for a lightwheight spatial database mainly
intended for mobiles SpatiaLite is adopted as the initial
step #3) when the first OGC Geopackage specification has been
finally published any reference to SpatiaLite has been removed
and a brand new binary encoding for Geometries has been introduced.
the main and most authoritative supporter for such a solution
was ESRI, advocating the supposed advantages of the new
binary Geometries for ensuring a robust interoperability
between the implementations of different vendors.
step #4) now we discover that the optimal perfect solution
for a spatial database well tailored for mobiles (at least
accordingly to ESRI) is to deploy their own proprietary
(and undocumented) binary format for Geometries on the
top of SQLite.
If in all this history there is any trace of rational progress
I personally am not able to understand it.