-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid WKT CRS in Annex B - GEOPOSE LOCAL FRAME OF REFERENCE SPECIFICATIONS #83
Comments
question asked to http://lists.ogc.org/pipermail/coordtran.wg/2024-June/002767.html |
Very comprehensive answer from Roger Lott in http://lists.ogc.org/pipermail/coordtran.wg/2024-June/002768.html that I would sum up along the lines "Presenting a topocentric CRS either as derived geodetic CRS or a projected CRS is fine, with the later being probably more practical for most software implementation" |
@rouault Thank you. I agree with your analysis. Your corrected example should replace the current one. |
yes I am |
Document update per comments above. Will close when new version appears on .OGC link |
There are errors. See my comments in 804f828. (I'd suggest using pull requests instead of direct commits) |
Examples at https://docs.ogc.org/is/21-056r11/21-056r11.html#toc47 are invalid WKT.
A valid WKT CRS cannot just start with BASEGEOGCRS. I assume here the top node should be a PROJCRS (not totally sure. I'm hesitating with a GEODCRS[], in which case CONVERSION should be DERIVINGCONVERSION). There was also a missing closing bracket to end DATUM.
A more valid example would be:
The text was updated successfully, but these errors were encountered: