Merge pull request #210 from internetofwater/new-ref

Separate Reference Features Repository

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.
 

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. 
 
 

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.

demo/index.Rmd

@@ -139,7 +139,7 @@ What is geoconnex.us? It is a framework for providers of water data to publish s
 
 ## Beginning our journey -- community reference features
 
-The geoconnex.us framework includes a large and growing catalog of "community reference features" -- neutral internet representations of real-world locations and areas that can be used by water data providers to describe what their published data is about. Many of these reference features are available from the website https://reference.geoconnex.us, which is powered by [PyGeoAPI](https://pygeoapi.io), a python implementation of [OGC API-Features](https://www.ogc.org/standards/ogcapi-features). This API enables programmatic interaction with spatial features on the web. 
+The geoconnex.us framework includes a large and growing catalog of "community reference features" -- neutral internet representations of real-world locations and areas that can be used by water data providers to describe what their published data is about. Many of these reference features are available from the website https://reference.geoconnex.us, which is powered by [pygeoapi](https://pygeoapi.io), a python implementation of [OGC API-Features](https://www.ogc.org/standards/ogcapi-features). This API enables programmatic interaction with spatial features on the web. 
 
 
 What's available from https://reference.geoconnex.us? We have collated a variety of common hydrologic and administrative locations and boundaries, and will continue to add more.
@@ -343,9 +343,9 @@ It looks like, in addition to the HUC8 and the PWS, we also have data from:
 
 A key part of the philosophy of geoconnex is that metadata is published independently by organizations and harvested automatically. Hovering around these various features on the map, we can that all sites have a `uri` (`@id`) that begins with "https://geoconnex.us/". However, if one follows these links, one is taken to different websites hosted on different servers by different organizations that are not aware of each other. 
 
-For example, https://geoconnex.us/nmwdi/nmbgmr/wells/WL-0183 redirects to http://wells.newmexicowaterdata.org/collections/nmbgmr_wells/items/WL-0183 , a PyGeoAPI instance operated by the [New Mexico Water Data Initiative](https://newmexicowaterdata.org/).
+For example, https://geoconnex.us/nmwdi/nmbgmr/wells/WL-0183 redirects to http://wells.newmexicowaterdata.org/collections/nmbgmr_wells/items/WL-0183 , a pygeoapi instance operated by the [New Mexico Water Data Initiative](https://newmexicowaterdata.org/).
 
-Meanwhile 	https://geoconnex.us/wade/sites/NM_146344 redirects to https://wade-test.geoconnex.us/collections/WaDE/items/NM_146344, a separate PyGeoAPI instance operated by the [Water Data Exchange](https://www.westernstateswater.org/wade/).
+Meanwhile 	https://geoconnex.us/wade/sites/NM_146344 redirects to https://wade-test.geoconnex.us/collections/WaDE/items/NM_146344, a separate pygeoapi instance operated by the [Water Data Exchange](https://www.westernstateswater.org/wade/).
 
 However, since both data systems provide JSON-LD markup, their metadata can be harvested automatically to create the data discovery workflow visualized here. This allows us to browse through the metadata. For example, perhaps we are only interested the SDWIS points and the NPDES permit for the Las Vegas drinking water system:
 

demo/index.html

@@ -7558,7 +7558,7 @@ <h2>Introduction</h2>
 </div>
 <div id="beginning-our-journey-community-reference-features" class="section level2">
 <h2>Beginning our journey – community reference features</h2>
-<p>The geoconnex.us framework includes a large and growing catalog of “community reference features” – neutral internet representations of real-world locations and areas that can be used by water data providers to describe what their published data is about. Many of these reference features are available from the website <a href="https://reference.geoconnex.us" class="uri">https://reference.geoconnex.us</a>, which is powered by <a href="https://pygeoapi.io">PyGeoAPI</a>, a python implementation of <a href="https://www.ogc.org/standards/ogcapi-features">OGC API-Features</a>. This API enables programmatic interaction with spatial features on the web.</p>
+<p>The geoconnex.us framework includes a large and growing catalog of “community reference features” – neutral internet representations of real-world locations and areas that can be used by water data providers to describe what their published data is about. Many of these reference features are available from the website <a href="https://reference.geoconnex.us" class="uri">https://reference.geoconnex.us</a>, which is powered by <a href="https://pygeoapi.io">pygeoapi</a>, a python implementation of <a href="https://www.ogc.org/standards/ogcapi-features">OGC API-Features</a>. This API enables programmatic interaction with spatial features on the web.</p>
 <p>What’s available from <a href="https://reference.geoconnex.us" class="uri">https://reference.geoconnex.us</a>? We have collated a variety of common hydrologic and administrative locations and boundaries, and will continue to add more.</p>
 <pre class="r"><code>collection_url &lt;- &quot;https://reference.geoconnex.us/collections&quot;
 collections &lt;- jsonlite::fromJSON(collection_url)
@@ -7938,8 +7938,8 @@ <h2>Beyond reference features - organizational data</h2>
 <li>points of diversion with data managed by the Western States Water Council <a href="https://www.westernstateswater.org/wade/">Water Data Exchange (WaDE)</a></li>
 </ul>
 <p>A key part of the philosophy of geoconnex is that metadata is published independently by organizations and harvested automatically. Hovering around these various features on the map, we can that all sites have a <code>uri</code> (<code>@id</code>) that begins with “<a href="https://geoconnex.us/" class="uri">https://geoconnex.us/</a>”. However, if one follows these links, one is taken to different websites hosted on different servers by different organizations that are not aware of each other.</p>
-<p>For example, <a href="https://geoconnex.us/nmwdi/nmbgmr/wells/WL-0183" class="uri">https://geoconnex.us/nmwdi/nmbgmr/wells/WL-0183</a> redirects to <a href="http://wells.newmexicowaterdata.org/collections/nmbgmr_wells/items/WL-0183" class="uri">http://wells.newmexicowaterdata.org/collections/nmbgmr_wells/items/WL-0183</a> , a PyGeoAPI instance operated by the <a href="https://newmexicowaterdata.org/">New Mexico Water Data Initiative</a>.</p>
-<p>Meanwhile <a href="https://geoconnex.us/wade/sites/NM_146344" class="uri">https://geoconnex.us/wade/sites/NM_146344</a> redirects to <a href="https://wade-test.geoconnex.us/collections/WaDE/items/NM_146344" class="uri">https://wade-test.geoconnex.us/collections/WaDE/items/NM_146344</a>, a separate PyGeoAPI instance operated by the <a href="https://www.westernstateswater.org/wade/">Water Data Exchange</a>.</p>
+<p>For example, <a href="https://geoconnex.us/nmwdi/nmbgmr/wells/WL-0183" class="uri">https://geoconnex.us/nmwdi/nmbgmr/wells/WL-0183</a> redirects to <a href="http://wells.newmexicowaterdata.org/collections/nmbgmr_wells/items/WL-0183" class="uri">http://wells.newmexicowaterdata.org/collections/nmbgmr_wells/items/WL-0183</a> , a pygeoapi instance operated by the <a href="https://newmexicowaterdata.org/">New Mexico Water Data Initiative</a>.</p>
+<p>Meanwhile <a href="https://geoconnex.us/wade/sites/NM_146344" class="uri">https://geoconnex.us/wade/sites/NM_146344</a> redirects to <a href="https://wade-test.geoconnex.us/collections/WaDE/items/NM_146344" class="uri">https://wade-test.geoconnex.us/collections/WaDE/items/NM_146344</a>, a separate pygeoapi instance operated by the <a href="https://www.westernstateswater.org/wade/">Water Data Exchange</a>.</p>
 <p>However, since both data systems provide JSON-LD markup, their metadata can be harvested automatically to create the data discovery workflow visualized here. This allows us to browse through the metadata. For example, perhaps we are only interested the SDWIS points and the NPDES permit for the Las Vegas drinking water system:</p>
 <!-- (I'm just filtering by variables that include the PWSID here, but it should really be filtering over a predicate like schema:about or is) -->
 <pre class="r"><code>npdes &lt;- within_hu08_13060001$`NMED-NPDES`

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. 

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

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

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