Added geospatial functions implemented in PostGIS, Spatialite and H2GIS.

[ar-chad]

#609

[situx]

@ar-chad The table looks good. But why does it only include alignments for functions that already exist in GeoSPARQL? Would it not be interesting also to see functions that are missing in GeoSPARQL but which are present in the other databases?

[ar-chad]

@situx sure, I can add anything else from ttl that does not match any of the GeoSPARQL functions. No problem.

[ar-chad]

@situx sure, I can add anything else from ttl that does not match any of the GeoSPARQL functions. No problem.

done now ✅ and ready for review 👀

[situx]

I addded prefixes and camelCase for the GeoSPARQL functions

[mperry455]

I have not had time for a detailed review yet, but some GeoSPARQL functions are missing, for example geof:is3D, geof:isMeasured, geof:coordinateDimension, and some like geof:within are not in the spec - should be geof:sfWithin instead.

Should this include functions in GeoSPARQL that do not exist in other spatial databases, for example geof:geometryType?

[ar-chad]

I have not had time for a detailed review yet, but some GeoSPARQL functions are missing, for example geof:is3D, geof:isMeasured, geof:coordinateDimension, and some like geof:within are not in the spec - should be geof:sfWithin instead.

Should this include functions in GeoSPARQL that do not exist in other spatial databases, for example geof:geometryType?

is3D, isMeasured and coordinateDimension did not match because they are not in functions.ttl which was used to do the matching.

geof:sfWithin has skos:prefLabel "within" and this is how it was matched.

I am not voting to include all GeoSPARQL functions in this table, because it will be a duplication of already existing information. But I will be able to add them, if others vote for it.

[mperry455]

Per 4/30/2025 SWG Meeting, we need to:

1. Replace preferred name with function URI (@situx to look at this one)
2. Create two versions of the table:
   a) Whitepaper version: also contains GeoSPARQL functions that do not appear in any 3D Spatial DB
   b) GeoSPARQL spec version: does not contain GeoSPARQL functions that do not appear in any 3D Spatial DB