The following applies to data in the internal SGID database.
Adding New Tables
When adding a new table to the SGID, a corresponding record will be added to the Data Stewardship spreadsheet and a data page will be added to the AGRC website. The data stewardship spreadsheet will contain at a minimum:
- The authoritative access from location
- The table name
- A description
- The data steward
- The steward contact name and email
- A link the the data page on the AGRC website
- A link to the SGID Open Data page
The ArcGIS Online item will contain a curated summary, description, and tags while residing in its ISO category folder. If the data is authoritative, it will be marked as
authoritative. If the data does not receive updates, it will be tagged as
static. If the data has historical relevance but is not the most recent data it will be tagged as
If the data is shared with the SGID Open Data, it will have the enable multiple formats download option selected to allow for File Geodatabases and other non default downloads.
The minimum metadata content will be populated.
- Purpose of data
- Owner of the data
- Contact person
- Date loaded
- Last update date
All empty geometries and duplicate records will be removed, with Sweeper or some other form of automation.
The ESRI default Resolution and Tolerance will be used.
- XY Resolution: 0.0001 Meter
- XY Tolerance: 0.001 Meter
Dates in Table Names
Dates are acceptable in table names when content is related to either
tax ISO categories. For all other categories, dates should only be used for tables that are no longer effective/active or soon-to-be effective/active. This implies that the most current and relevant data contains no date suffix. Historical or future data will contain a date suffix to help identification at a glance. The best way to learn about a dataset is to view the data page metadata.
Updating and Editing Existing Tables
No edits will be made to the internal SGID from 7:00PM to 10:00AM MST to allow for automated scripts to push accurate updates to ArcGIS Online and ArcGIS Server. AGRC will ensure that data is production-ready before the editing windows ends.
All database updates will be done during the editing window using swapper or some other automated process to reduce the amount of time with incomplete data.
All data updates being pushed into the SGID will have removed empty geometries and duplicate records with Sweeper or another automated process.
All edits made to the internal SGID will be captured in
Last update date in the metadata, in the SGID Update log, and as an update on the AGRC website data page.
Removing SGID Products
When data or services are deprecated, the Cemetery project is used.