I have noticed that there seems to be a portion of the ESRI SQL implementation that is undocumented. The geometry related functions such as ST_Area, etc are well documented in the help. What is not documented are the various functions for the setup, administration and maintenance of the data. One such function is the AddGeometryColumn function as described in the 10.2 help here:ArcGIS Help (10.2, 10.2.1, and 10.2.2)
There are other calls such as CreateSpatialIndex or DropGeometryMetadata that are shown in examples but I can not find the function documention. Much less a list of what other functions are available in the ST_Geometry library.
Does anyone know where I might find the full documentation of the ST_Geometry library?
I already know about that section of the help files that documents the various ST_ functions. What I can not find is the documentation for functions such as AddGeometryColumn.
A quick tour of SQL functions used with ST_Geometry has been reformatted at 10.3.x. Although the content is much the same as earlier versions, the improved presentation is helpful in understanding some of the information.
Regarding AddGeometryColumn, CreateSpatialIndex, DropGeometryMetadata, etc..., Esri doesn't document those SQL functions because they are not part of the ST_Geometry data type. Since Esri didn't create/develop those functions and they aren't part of the ST_Geometry data type, they assume users will use the relevant DBMS documentation to read up on how those functions work.
Thanks Josh. That makes sense.
As I read your reply and think about what I want to know I realize that my real question is what is the full documentation for the stgeometry_sqlite.dll. That implements both the ST_Geometry functions and the utility functions on SQLite databases. Now that is the library that lacks documentation about functions other than the ST_ series. I found the reference to the ones like AddGeometryColumn in the help files which got me to wondering what other functions are under the hood. So far as I can tell the ESRI documentation does not list them. Just a few examples of using them.
Contrast this with Spatialite which has a plethora of documented functions, including ones to handle Geopackages.
Hacking ArcSDE describes some of the cool things you can to with georgraphy, and the little to no modification required to do the same things in geometry. The MSDN documentation on the Geometry and Geography functions is pretty basic, if you're willing to roll up your sleeves on SQL coding you can do some pretty advanced spatial logic, all outside of the SDE stack but transparent to users.
The OP is/was asking about ST_Geometry, and ST_Geometry in SQLite specifically. I agree that a lot of spatial can be done with SQL outside of the SDE stack, but MSDN documentation has limited value in this case since ST_Geometry isn't implemented on SQL Server.