Open situx opened 3 weeks ago
I think doing 1. is fine, as for prior art we have e.g. MySQL: https://dev.mysql.com/doc/refman/8.4/en/gis-point-property-functions.html#function_st-latitude
if the user desires the outcome of 2., they can call geof:centroid manually
I think doing 1. is fine, as for prior art we have e.g. MySQL: https://dev.mysql.com/doc/refman/8.4/en/gis-point-property-functions.html#function_st-latitude
if the user desires the outcome of 2., they can call geof:centroid manually
Makes sense to me. I will take this to the next GeoSPARQL meeting on Wednesday and we will form an opinion in the group.
Discussion in the group:
Should this be for points only? Options presented were:
Option 1 was selected as there is already a function provided to get the centroid of a shape other than a point. We don't want to make assumptions over how to chain this together to produce a result for non-Points given the functions required for the user to decide that are available.
How should the centroid be returned? Options presented:
Option 2 was selected as it is aligned with how Simple Features functions work.
Meeting 26th June: We decided to rename the functions to geof:easting and geof:northing so that values in meter may be returned
The pull request is, therefore, again ready for review and I notify @SimonBin that he can follow the discussions we had in this pull request.
As suggested in #160 I am proposing the inclusion of a latitude and a longitude function for GeoSPARQL.
We may have two possibilities for definition here:
@nicholascar and @SimonBin any opinions?