From 230dbca11734ea0015ca8973d50cbded58a7ca55 Mon Sep 17 00:00:00 2001 From: James Passmore Date: Tue, 16 Jul 2024 09:41:56 +0100 Subject: [PATCH 1/4] Update verticalextent.asciidoc Correcting link to the EPSG registry, as per issue https://github.com/agiorguk/gemini/issues/87 --- docs/partials/verticalextent.asciidoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/partials/verticalextent.asciidoc b/docs/partials/verticalextent.asciidoc index 995da98..978bfae 100644 --- a/docs/partials/verticalextent.asciidoc +++ b/docs/partials/verticalextent.asciidoc @@ -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. @@ -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... @@ -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 @@ -178,4 +178,4 @@ include::../snippets/extent-verticalcrs-unknown.xml[] [%collapsible] ==== No error information available -==== \ No newline at end of file +==== From 7562ea8629f8f37b5b6adb08aab4c8dffed2ed4b Mon Sep 17 00:00:00 2001 From: James Passmore Date: Tue, 16 Jul 2024 09:47:46 +0100 Subject: [PATCH 2/4] Update verticalextent.asciidoc Fixing broken EPSG references as per https://github.com/agiorguk/gemini/issues/87 --- docs/partials/verticalextent.asciidoc | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/partials/verticalextent.asciidoc b/docs/partials/verticalextent.asciidoc index 995da98..978bfae 100644 --- a/docs/partials/verticalextent.asciidoc +++ b/docs/partials/verticalextent.asciidoc @@ -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. @@ -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... @@ -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 @@ -178,4 +178,4 @@ include::../snippets/extent-verticalcrs-unknown.xml[] [%collapsible] ==== No error information available -==== \ No newline at end of file +==== From 76dfbbd6ea0fdfdf53ff74716e9e973e5e459643 Mon Sep 17 00:00:00 2001 From: Jo Cook Date: Wed, 31 Jul 2024 12:41:25 +0100 Subject: [PATCH 3/4] Update dev-build.yml Corrected external_repository parameter in main:dev_build.yml to agiorguk --- .github/workflows/dev-build.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/dev-build.yml b/.github/workflows/dev-build.yml index b91dfcc..5c14e74 100644 --- a/.github/workflows/dev-build.yml +++ b/.github/workflows/dev-build.yml @@ -23,7 +23,7 @@ jobs: uses: peaceiris/actions-gh-pages@v3 with: personal_token: ${{ secrets.API_TOKEN_GITHUB }} - external_repository: archaeogeek/gemini-dev + external_repository: agiorguk/gemini-dev publish_branch: gh-pages publish_dir: ./docs/ enable_jekyll: true From 9bd136d875bf6c76df56b5aea843c44482dfb97e Mon Sep 17 00:00:00 2001 From: Peter Parslow Date: Wed, 4 Sep 2024 14:46:19 +0100 Subject: [PATCH 4/4] Update 1037-uk-gemini-introduction.asciidoc Changed link to Schematron files, so that it links to the current repository. --- docs/1037-uk-gemini-introduction.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/1037-uk-gemini-introduction.asciidoc b/docs/1037-uk-gemini-introduction.asciidoc index ca8f8af..05e75c2 100644 --- a/docs/1037-uk-gemini-introduction.asciidoc +++ b/docs/1037-uk-gemini-introduction.asciidoc @@ -13,7 +13,7 @@ entry points to the guidance: ** link:1051-uk-gemini-v2-2-specification-for-discovery-metadata-for-geospatial-resources.html[General introduction to GEMINI] ** link:1049-metadata-guidelines-for-geospatial-data-resources-part-2.html[General guidance for GEMINI] ** link:1048-uk-gemini-encoding-guidance.html[General guidance on the XML encoding of GEMINI] -** https://github.com/AGIGemini/Schematron[Schematron rules for validating GEMINI records (GitHub link)] +** https://github.com/agiorguk/gemini-schematron[Schematron rules for validating GEMINI records (GitHub link)] ** link:1056-glossary.html[Glossary of terms] ** link:1047-metadata-guidelines-for-geospatial-data-resources-part-3.html[List of references] ** link:1053-common-metadata-errors-uk-location-discovery-metadata-service.html[Common errors]