Skip to content
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.

Sign up for GitHub

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

Update verticalextent.asciidoc #157

Merged
merged 1 commit into from
Jul 31, 2024
Merged

Update verticalextent.asciidoc #157

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/partials/verticalextent.asciidoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ specified coordinate reference system
for the vertical extent measurements. This should be recorded as a name
or as a code, for example as provided in the EPSG Geodetic Parameter
Registry produced by The International Association of Oil & Gas
Producers (see http://www.epsg-registry.org/)
Producers (see https://epsg.org/)

|Comment |This element should be used only where vertical extent is
significant, e.g. in geology, mining, meteorology etc.
Expand All @@ -60,7 +60,7 @@ significant, e.g. in geology, mining, meteorology etc.
* Maximum value: 0.0
* Coordinate reference system: height in metres above Newlyn Datum

|Revision date |March 2019
|Revision date |July 2024
|===

.Corresponding element in other standards...
Expand Down Expand Up @@ -131,7 +131,7 @@ the zero reference) and the units of the coordinate values.
(Example One) or by value (Example Two). These examples express the same
information: that the vertical extent coordinates are referenced to
Ordnance Datum (Newlyn). Codes and GML CRS data are from the
http://www.epsg-registry.org/[EPSG Registry].
https://epsg.org/[EPSG Registry].
. Additionally, the gco:nilReason attribute can be used if the vertical
CRS is unknown (Example Three) but this renders the vertical extent
information ambiguous at best. Consequently it would be better to
Expand Down Expand Up @@ -178,4 +178,4 @@ include::../snippets/extent-verticalcrs-unknown.xml[]
[%collapsible]
====
No error information available
====
====