- From: Timo via GitHub <sysbot+gh@w3.org>
- Date: Thu, 24 Feb 2022 17:30:02 +0000
- To: public-sdwig@w3.org
In GeoSPARQL 1.0 the situation is as follows: - WKT Literals without a CRS definition are assumed to use the CRS84 CRS - GML Literals without a CRS definition are allowed but would probably fail the test of a GML parser (not sure though) In GeoSPARQL 1.1 the situation will be as follows: - GeoJSON literals and KML literals have a fixed CRS by definition of the literal format - DGGS literals without a CRS definition are to my knowledge not defined correctly, so they should not parse correctly The specification (GeoSPARQL 1.0 and 1.1) only says that the CRS of the geometry literal is to be returned. How to treat errors is up to the implementers to a certain extent. I believe that the triple store would return a general error message here. -- GitHub Notification of comment by situx Please view or discuss this issue at https://github.com/w3c/sdw/pull/1334#issuecomment-1050089191 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 24 February 2022 17:30:05 UTC