diff --git a/docs/source/configuration.rst b/docs/source/configuration.rst index 14956d9f0..9dff49a17 100644 --- a/docs/source/configuration.rst +++ b/docs/source/configuration.rst @@ -131,7 +131,7 @@ The ``metadata`` section provides settings for overall service metadata and desc - api keywords_type: theme # keyword type as per the ISO 19115 MD_KeywordTypeCode codelist. Accepted values are discipline, temporal, place, theme, stratum terms_of_service: https://creativecommons.org/licenses/by/4.0/ # terms of service - url: http://example.org # informative URL about the service + url: https://example.org # informative URL about the service license: # licensing details name: CC-BY 4.0 license url: https://creativecommons.org/licenses/by/4.0/ @@ -648,5 +648,5 @@ At this point, you have the configuration ready to administer the server. .. _`JSON-LD`: https://json-ld.org .. _`Google Structured Data Testing Tool`: https://search.google.com/structured-data/testing-tool#url=https%3A%2F%2Fdemo.pygeoapi.io%2Fmaster .. _`Google Dataset Search`: https://developers.google.com/search/docs/appearance/structured-data/dataset -.. _RotatingFileHandler: http://docs.python.org/3/library/logging.handlers.html#rotatingfilehandler -.. _TimedRotatingFileHandler: http://docs.python.org/3/library/logging.handlers.html#timedrotatingfilehandler +.. _RotatingFileHandler: https://docs.python.org/3/library/logging.handlers.html#rotatingfilehandler +.. _TimedRotatingFileHandler: https://docs.python.org/3/library/logging.handlers.html#timedrotatingfilehandler diff --git a/docs/source/data-publishing/ogcapi-coverages.rst b/docs/source/data-publishing/ogcapi-coverages.rst index 76ed0de39..8c486ab4e 100644 --- a/docs/source/data-publishing/ogcapi-coverages.rst +++ b/docs/source/data-publishing/ogcapi-coverages.rst @@ -148,7 +148,7 @@ Data access examples ``.../coverage`` queries which return an alternative representation to CoverageJSON (which prompt a download) will have the response filename matching the collection name and appropriate file extension (e.g. ``my-dataset.nc``) -.. _`OGC API - Coverages`: https://github.com/opengeospatial/ogcapi-coverages +.. _`OGC API - Coverages`: https://ogcapi.ogc.org/coverages .. _`Rasterio`: https://rasterio.readthedocs.io .. _`Xarray`: https://docs.xarray.dev/en/stable .. _`NetCDF`: https://en.wikipedia.org/wiki/NetCDF diff --git a/docs/source/data-publishing/ogcapi-edr.rst b/docs/source/data-publishing/ogcapi-edr.rst index 83a2a76bd..641a20b5d 100644 --- a/docs/source/data-publishing/ogcapi-edr.rst +++ b/docs/source/data-publishing/ogcapi-edr.rst @@ -114,6 +114,4 @@ Data access examples .. _`NetCDF`: https://en.wikipedia.org/wiki/NetCDF .. _`Zarr`: https://zarr.readthedocs.io/en/stable .. _`pyproj.CRS.from_user_input`: https://pyproj4.github.io/pyproj/stable/api/crs/coordinate_system.html#pyproj.crs.CoordinateSystem.from_user_input - - -.. _`OGC Environmental Data Retrieval (EDR) (API)`: https://github.com/opengeospatial/ogcapi-coverages +.. _`OGC Environmental Data Retrieval (EDR) (API)`: https://ogcapi.ogc.org/edr diff --git a/docs/source/data-publishing/ogcapi-features.rst b/docs/source/data-publishing/ogcapi-features.rst index 2a1f87d54..2b598d649 100644 --- a/docs/source/data-publishing/ogcapi-features.rst +++ b/docs/source/data-publishing/ogcapi-features.rst @@ -813,7 +813,7 @@ Data access examples .. _`Feature Service`: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/what-is-a-feature-service-.htm .. _`Map Service`: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/what-is-a-map-service.htm .. _`Google Cloud SQL`: https://cloud.google.com/sql -.. _`OGC API - Features`: https://www.ogc.org/standards/ogcapi-features +.. _`OGC API - Features`: https://ogcapi.ogc.org/features .. _`Socrata Open Data API (SODA)`: https://dev.socrata.com .. _`sodapy`: https://github.com/xmunoz/sodapy .. _`Tabledap`: https://coastwatch.pfeg.noaa.gov/erddap/tabledap/documentation.html diff --git a/docs/source/data-publishing/ogcapi-tiles.rst b/docs/source/data-publishing/ogcapi-tiles.rst index 0074f3bec..3f669061a 100644 --- a/docs/source/data-publishing/ogcapi-tiles.rst +++ b/docs/source/data-publishing/ogcapi-tiles.rst @@ -120,11 +120,11 @@ Following code block shows how to configure pygeoapi to read Mapbox vector tiles - type: tile name: MVT-proxy data: http://localhost:3000/ne_50m_admin_0_countries/{z}/{x}/{y} - options: - zoom: - min: 0 - max: 15 - schemes: + options: + zoom: + min: 0 + max: 15 + schemes: - WebMercatorQuad format: name: pbf @@ -183,7 +183,7 @@ Data access examples -.. _`OGC API - Tiles`: https://github.com/opengeospatial/ogcapi-tiles +.. _`OGC API - Tiles`: https://ogcapi.ogc.org/tiles .. _`tippecanoe`: https://github.com/mapbox/tippecanoe .. _`Elasticsearch`: https://www.elastic.co/ .. _`Mapbox Vector Tiles`: https://docs.mapbox.com/data/tilesets/guides/vector-tiles-introduction/ diff --git a/docs/source/data-publishing/stac.rst b/docs/source/data-publishing/stac.rst index 84f0c7436..97a23c965 100644 --- a/docs/source/data-publishing/stac.rst +++ b/docs/source/data-publishing/stac.rst @@ -334,7 +334,7 @@ The example below shows the content of a file named *arcticdem-frontiere-0.json* ], "assets": { "image": { - "href": "http://absolute/path/to/the/ressource/arcticdem-frontiere-0.tif", + "href": "https://example.com/path/to/resource/arcticdem-frontiere-0.tif", "type": "image/tiff; application=geotiff; profile=cloud-optimized", "roles": [] } diff --git a/docs/source/language.rst b/docs/source/language.rst index 594f8ce7b..26f0740ec 100644 --- a/docs/source/language.rst +++ b/docs/source/language.rst @@ -15,9 +15,9 @@ End user guide There are 2 ways to affect the language of the results returned by pygeoapi, both for the HTML and JSON(-LD) formats: 1. After the requested pygeoapi URL, append a ``lang=`` query parameter, where ```` should be replaced by a well-known language code. - This can be an ISO 639-1 code (e.g. `de` for German), optionally accompanied by an ISO 3166-1 alpha-2 country code (e.g. `de-CH` for Swiss-German). - Please refer to this `W3C article `_ for more information or - this `list of language codes `_ for more examples. + This can be an `ISO 639-1 code `_ (e.g. `de` for German), optionally accompanied by an `ISO 3166-1 alpha-2 country code `_ (e.g. `de-CH` for Swiss-German). + + Please refer to this `W3C article `_ for more information. Another option is to send a complex definition with quality weights (e.g. `de-CH, de;q=0.9, en;q=0.8, fr;q=0.7, \*;q=0.5`). pygeoapi will then figure out the best match for the requested language.