diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5aecdae2..36aeb30f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -34,7 +34,7 @@ If you have a collection of >300,000 features that cannot be easily and consiste ### Adding geospatial reference features to reference.geoconnex.us -[https://reference.geoconnex.us](https://reference.geoconnex.us) is available to host community reference features. See the readme in the [pygeoapi](pygeoapi) folder for more info. +[https://reference.geoconnex.us](https://reference.geoconnex.us) is available to host community reference features. See the readme in the [reference features repository](https://github.com/internetofwater/reference.geoconnex.us) for more info. ## Licensing of geoconnex.us contributions. diff --git a/README.md b/README.md index 87ea0e74..e8824594 100644 --- a/README.md +++ b/README.md @@ -20,7 +20,7 @@ See [https://geoconnex.us/demo](https://geoconnex.us/demo) for a mockup of data Architecturally, Geoconnex involves: -1. A set of community-curated web resources about hydrologic *reference features* (e.g. watersheds, monitoring locations, dams, bridges, etc.) about which many organizations may collect and publish data. +1. A set of community-curated web resources about hydrologic [Reference features](https://github.com/internetofwater/reference.geoconnex.us) (e.g. watersheds, monitoring locations, dams, bridges, etc.) about which many organizations may collect and publish data. 1. Web resources about hydrologic features that organizations publish on the web, including embedded JSON-LD metadata, using common ontologies such as [schema.org](https://schema.org), and domain-specific ontologies such as [HY-Features](https://www.opengis.net/def/schema/hy_features/hyf) for hydrology and [SOSA/SSN](https://www.w3.org/TR/vocab-ssn/) for sensor data. Guidance for embedded JSON-LD is under development at [docs.geoconnex.us](https://github.com/internetofwater/docs.geoconnex.us) 1. A registry of persistent identifiers (PIDs) that point to the above resources. The PIDs in the geoconnex system have the base URI `https://geoconnex.us/`. Learn how to submit identifiers for the registry here: [CONTRIBUTING](CONTRIBUTING.md). PIDs are important to maintain so that data publishers can change the URLs of their web resources while the knowledge graph and any search engine remain functional (preventing [link rot](https://en.wikipedia.org/wiki/Link_rot)). 1. A harvester that collects the JSON-LD published above, and publishes the resulting knowledge graph as both a public domain data product and an open API, allowing for the building of search interfaces. The harvester codebase is under development at [harvest.geoconnex.us](https://github.com/internetofwater/harvest.geoconnex.us), and the knowledge graph itself will be available from [graph.geoconnex.us](https://graph.geoconnex.us) @@ -31,9 +31,9 @@ See the figure below: ## What is in graph.geoconnex.us? -The features registered in `https://geoconnex.us` are automatically harvested and included in [graph.geoconnex.us](https://graph.geoconnex.us) are either community reference features or associated with a particular organization or database. +The features registered in `https://geoconnex.us` are automatically harvested and included in [graph.geoconnex.us](https://graph.geoconnex.us) are either community reference features or associated with a particular organization or database. See [Geoconnex Features App](https://geoconnex.us/iow/map) for a simple map-based search interface for features in geoconnex. -1. community reference features: monitoring and environmental features collated by a person or group in the interest of the community. These features are available via OGC API Features at [reference.geoconnex.us](https://reference.geoconnex.us/collections). See this [R Shiny application](https://internetofwater.shinyapps.io/geoconnex-reference-features) for a simple map-based search interface for reference features. +1. community reference features: monitoring and environmental features collated by a person or group in the interest of the community. These features are available via OGC API Features at [reference.geoconnex.us](https://reference.geoconnex.us/collections). 1. organization specific features: features owned by a particular organizational entity or from a specific dataset. diff --git a/about-the-registry.md b/about-the-registry.md index 8b0ba4f4..86e79ab2 100644 --- a/about-the-registry.md +++ b/about-the-registry.md @@ -34,7 +34,7 @@ These use cases imply requirements that `https://geoconnex.us` helps satisfy: The features registered in `https://geoconnex.us` are either community reference features or associated with a particular organization or database. -1. community reference features: monitoring and environmental features collated by a person or group in the interest of the community +1. community reference features: Hosted at [reference.geoconnex.us](https://github.com/internetofwater/reference.geoconnex.us), these monitoring and environmental features are collated by a person or group in the interest of the community. 1. organization specific features: features owned by a particular organizational entity or from a specific dataset These features can also be described using their role in the linked-data system. diff --git a/namespaces/ref/README.md b/namespaces/ref/README.md index 46576f81..9b8a6e30 100644 --- a/namespaces/ref/README.md +++ b/namespaces/ref/README.md @@ -2,7 +2,9 @@ This is a community identifier namespace. It is to be used for shared identifiers for thematic collections of features. -PIDs in this namespace will follow the pattern: +Deployment for reference features is at [this repository](https://github.com/internetofwater/reference.geoconnex.us) + +PIDs in this namespace follow the pattern: `/ref/{featuretype}/{id}` Where {featuretype} is the thematic type. diff --git a/namespaces/ref/nat_aq/README.md b/namespaces/ref/nat_aq/README.md index 5a66ea5a..50dd8884 100644 --- a/namespaces/ref/nat_aq/README.md +++ b/namespaces/ref/nat_aq/README.md @@ -9,7 +9,7 @@ This is a reference collection of National Aquifers as described by the National These aquifers have a 1:1 correspondence with the [principal aquifers of the united states.](https://github.com/internetofwater/geoconnex.us/tree/master/namespaces/ref/princi_aq) -The current implementation creating these ids and landing-content is in: https://github.com/internetofwater/geoconnex_prep and hosted on https://reference.geoconnex.us/collections/nat_aq geojson source for the landing content is available in [this repository here.](https://github.com/internetofwater/geoconnex.us/blob/master/pygeoapi/ext_data/nat_aq.geojson) +The current implementation creating these ids and landing-content is in: https://github.com/internetofwater/geoconnex_prep and hosted on https://reference.geoconnex.us/collections/nat_aq. The file source for the content is available in [this repository here.](https://github.com/internetofwater/reference.geoconnex.us) Example: https://geoconnex.us/ref/nat_aq/N100BSNRGB diff --git a/namespaces/ref/princi_aq/README.md b/namespaces/ref/princi_aq/README.md index 21eda8c5..e9fb30ed 100644 --- a/namespaces/ref/princi_aq/README.md +++ b/namespaces/ref/princi_aq/README.md @@ -8,7 +8,7 @@ This map layer contains the shallowest principal aquifers of the conterminous Un These aquifers have a 1:1 correspondence with the [National Aquifers of the United States.](https://github.com/internetofwater/geoconnex.us/tree/master/namespaces/ref/nat_aq) -The current implementation creating these ids and landing-content is in: https://github.com/internetofwater/geoconnex_prep and hosted on https://reference.geoconnex.us/collections/nat_aq geojson source for the landing content is available in [this repository here.](https://github.com/internetofwater/geoconnex.us/blob/master/pygeoapi/ext_data/nat_aq.geojson) +The current implementation creating these ids and landing-content is in: https://github.com/internetofwater/geoconnex_prep and hosted on https://reference.geoconnex.us/collections/nat_aq. The file source for the content is available in [this repository here.](https://github.com/internetofwater/reference.geoconnex.us) Example: * https://geoconnex.us/ref/principal_aq/108 diff --git a/namespaces/ref/sec_hydrg_reg/README.md b/namespaces/ref/sec_hydrg_reg/README.md index 7ecfedca..9196f59c 100644 --- a/namespaces/ref/sec_hydrg_reg/README.md +++ b/namespaces/ref/sec_hydrg_reg/README.md @@ -8,7 +8,7 @@ The U.S. Geological Survey (USGS) previously identified 62 [Principal Aquifers]( Belitz, K., Watson, E., Johnson, T.D., and Sharpe, J.B., 2018, Data release for secondary hydrogeologic regions of the conterminous United States: U.S. Geological Survey data release, https://doi.org/10.5066/F7F76BSS. -The current implementation creating these ids and landing-content is in: https://github.com/internetofwater/geoconnex_prep and hosted on https://reference.geoconnex.us/collections/sec_hydrg_reg geojson source for the landing content is available in [this repository here.](https://github.com/internetofwater/geoconnex.us/blob/master/pygeoapi/ext_data/sec_hydrg_reg.geojson) +The current implementation creating these ids and landing-content is in: https://github.com/internetofwater/geoconnex_prep and hosted on https://reference.geoconnex.us/collections/sec_hydrg_reg. The file source for the content is available in [this repository here.](https://github.com/internetofwater/reference.geoconnex.us) Example: https://geoconnex.us/ref/sec_hydrg_reg/S47