Proper CSV Formatting for Geoconnex
For a tutorial on how to submit your CSV data see the contribution tutorial
Geoconnex expects a standard format for the CSVs which maps a persistent identifier in Geoconnex to a single data resource. You must include at least the following 4 columns:
| Column Title | Description |
|---|---|
id | The ID within geoconnex that your data should map to. These are unique, will redirect to the associated target, and are meant for individual monitoring locations. View the identification scheme section for more info. |
target | The URL pointing to a JSON-LD landing page for a single feature in your data. |
creator | A contact email for someone associated with the resource. |
description | A natural language description of the data. |
1:1 vs 1:N Redirects
- 1:1 Redirects
- 1:N Regex Redirects
There is a strong preference for creating 1:1 redirects. That is, specifying an exact redirect from a geoconnex.us-based PID to the URI of the hydrologic feature you have a web resource about, for each and every individual feature. This enables the resolution of features such as https://geoconnex.us/usgs/monitoring-location/01010000 to https://waterdata.usgs.gov/monitoring-location/01010000
An example 1:1 mapping
| Source: demo.csv |
|---|
Unless you have more than 300,000 features and cannot use 1:1 redirects, you should avoid using regex redirects as they are harder to resolve and maintain if endpoints change
If you need to create PIDs and redirects for a large number of features (more than 300,000), and cannot use 1:1 redirects, we will require a regular expression matching redirect.
-
For example, redirecting from https://geoconnex.us/example-namespace/*wildcard-string to https://example.org/features?query=*wildcard-string.
-
If you have more than 300,000 features, but these features can be split in a consistent way into sub-collections, all of which number less than 300,000 features (as might be the case for features that can be divided by geography, jurisdiction, theme, or type), then you might consider submitting multiple collections of 1:1 redirects.
To submit a request to submit this data, you can create an issue of type "Request regex redirect" and fill out the template.
An example 1:N mapping that uses a regular expression
| Source: monitoring-location.csv |
|---|