{"action":"created","issue":{"url":"https://api.github.com/repos/opengeospatial/geopackage/issues/137","labels_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/137/labels{/name}","comments_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/137/comments","events_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/137/events","html_url":"https://github.com/opengeospatial/geopackage/issues/137","id":103282379,"number":137,"title":"Update CRS reference","user":{"login":"jyutzler","id":3401345,"avatar_url":"https://avatars.githubusercontent.com/u/3401345?v=3","gravatar_id":"","url":"https://api.github.com/users/jyutzler","html_url":"https://github.com/jyutzler","followers_url":"https://api.github.com/users/jyutzler/followers","following_url":"https://api.github.com/users/jyutzler/following{/other_user}","gists_url":"https://api.github.com/users/jyutzler/gists{/gist_id}","starred_url":"https://api.github.com/users/jyutzler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jyutzler/subscriptions","organizations_url":"https://api.github.com/users/jyutzler/orgs","repos_url":"https://api.github.com/users/jyutzler/repos","events_url":"https://api.github.com/users/jyutzler/events{/privacy}","received_events_url":"https://api.github.com/users/jyutzler/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/opengeospatial/geopackage/milestones/7","html_url":"https://github.com/opengeospatial/geopackage/milestones/tiles-corrigendum","labels_url":"https://api.github.com/repos/opengeospatial/geopackage/milestones/7/labels","id":1167002,"number":7,"title":"tiles-corrigendum","description":null,"creator":{"login":"jyutzler","id":3401345,"avatar_url":"https://avatars.githubusercontent.com/u/3401345?v=3","gravatar_id":"","url":"https://api.github.com/users/jyutzler","html_url":"https://github.com/jyutzler","followers_url":"https://api.github.com/users/jyutzler/followers","following_url":"https://api.github.com/users/jyutzler/following{/other_user}","gists_url":"https://api.github.com/users/jyutzler/gists{/gist_id}","starred_url":"https://api.github.com/users/jyutzler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jyutzler/subscriptions","organizations_url":"https://api.github.com/users/jyutzler/orgs","repos_url":"https://api.github.com/users/jyutzler/repos","events_url":"https://api.github.com/users/jyutzler/events{/privacy}","received_events_url":"https://api.github.com/users/jyutzler/received_events","type":"User","site_admin":false},"open_issues":6,"closed_issues":11,"state":"open","created_at":"2015-06-16T16:01:39Z","updated_at":"2015-08-26T15:32:42Z","due_on":null,"closed_at":null},"comments":4,"created_at":"2015-08-26T14:25:33Z","updated_at":"2015-08-26T15:44:18Z","closed_at":null,"body":"From @kryden\r\nThe original OGC Geopackage specification was adopted prior to the adoption of the updated SRS WKT Specification OGC Well known text representation of coordinate reference systems. As a result, the original OGC Geopackage specification references older documents that should be superseded by the final version of OGC Well known text representation of coordinate reference systems, OGC 12-063r5, approved 13 August, 2014. Changes are required in the Geopackage specification document to adopt OGC 12-063r5, and eliminate ambiguities being encountered in the field from the older specification reference."},"comment":{"url":"https://api.github.com/repos/opengeospatial/geopackage/issues/comments/135072742","html_url":"https://github.com/opengeospatial/geopackage/issues/137#issuecomment-135072742","issue_url":"https://api.github.com/repos/opengeospatial/geopackage/issues/137","id":135072742,"user":{"login":"KRyden","id":2131460,"avatar_url":"https://avatars.githubusercontent.com/u/2131460?v=3","gravatar_id":"","url":"https://api.github.com/users/KRyden","html_url":"https://github.com/KRyden","followers_url":"https://api.github.com/users/KRyden/followers","following_url":"https://api.github.com/users/KRyden/following{/other_user}","gists_url":"https://api.github.com/users/KRyden/gists{/gist_id}","starred_url":"https://api.github.com/users/KRyden/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/KRyden/subscriptions","organizations_url":"https://api.github.com/users/KRyden/orgs","repos_url":"https://api.github.com/users/KRyden/repos","events_url":"https://api.github.com/users/KRyden/events{/privacy}","received_events_url":"https://api.github.com/users/KRyden/received_events","type":"User","site_admin":false},"created_at":"2015-08-26T15:44:18Z","updated_at":"2015-08-26T15:44:18Z","body":"Pepijn is correct that there are multiple OGC specifications that need to update references to the CRS Well Known Text specification (12-063r5 adopted August 13, 2014).  OGC management will need to help move that effort, and with all of these documents on different revision cycles (some stretching out years), timing becomes a real problem when you need to fix things and get it right.  We need to get this moving, and Geopackage is in a good position to start driving it forward as it is directly impacted.  We should update Simple Features ASAP.\r\n\r\nRegarding compatibility, section 6.7 of 12-063r5 addresses the expectations for compatibility - \"Backward compatibility means that an implementation of the text strings in this International Standard would be able to read CRS WKT strings conforming to the old (ISO 19125-1:2004) syntax\" - so newer parser implementations should be handling older strings.  This is not just an issue for existing geopackages - all software supporting interpretation of CRS WKT strings needs to make this move.  What's going to be an issue in the field is older software that does not know how to process newer CRS WKT strings - each software provider will need to address that issue in their own way.  At some point, we have to move on.\r\n\r\nJeff - Any valid CRS WKT should be sufficient - the following statement is probably a result of referencing 01-009 which is superseded, and should be removed:\r\n\r\n\"Values SHALL include optional <authority> EBNF entities. Values for SRS other than WGS-84 SHOULD include optional <to wgs84> EBNF entities. Values MAY omit optional <to wgs84> and <twin axes> EBNF entities.\"\r\n\r\nAnd the braces \"<>\" should be removed from around <authority> in this sentence:\r\nEBNF name and number values MAY be obtained from any specified <authority>, e.g. <<13>><<14>>. \r\n\r\nSo the final paragraph would read:\r\nDefinition column WKT values in the `gpkg_spatial_ref_sys` table SHALL define the Spatial Reference Systems used by feature geometries and tile images, unless these SRS are unknown and therefore undefined as specified in <<_requirement-11>>. Values SHALL be constructed and applications SHALL interpret the EBNF using rules in <<32>>.  EBNF name and number values MAY be obtained from any specified authority, e.g. <<13>><<14>>. For example, see the return value in <<spatial_ref_sys_data_values_default>> Test Method step (3) used to test the definition for WGS-84 per <<_requirement-11>>: "}}