5-3. Attachment A - Data Specifications.pdf
PDF 170 KB Posted
- Attached to
- On Call Water Resources Engineering Services State and local contract opportunity
- Solicitation number
- RFP-209-25
- Issued by
- Boulder County, Colorado
About this file
This document is a set of Data Solutions Specifications for Spatial & Nonspatial Data Deliverables from Boulder County Parks & Open Space (BCPOS), outlining comprehensive requirements for contractors providing Geographic Information System (GIS) data. The specifications detail precise technical standards for both spatial and non-spatial data deliverables, focusing on ensuring high-quality, compatible, and accurately formatted geographic information. The document mandates specific technical requirements such as using ArcGIS compatible formats (shapefiles or file geodatabases), requiring complete metadata, maintaining unique identifiers across datasets, and specifying a precise coordinate system (NAD 1983 HARN State Plane Colorado North).
The technical specifications provide granular guidance for data submission, including rules for spatial data accuracy, georeferencing, and coordinate system parameters, as well as detailed non-spatial data formatting instructions. Key non-spatial data requirements include aggregating data into larger files, using only alphanumeric characters in column headers, maintaining consistent date formats, avoiding special formatting, and properly representing missing data. The document also requires that tabular data linking to geospatial data must contain foreign keys or identifiers for spatial features, and metadata must accompany all data files, either as a separate document or as an additional spreadsheet tab in Excel.
View the file
Other files for this state and local contract opportunity
| File | Type | Posted |
|---|---|---|
| 7-6. Attachment D - Boulder County Services Sample Contract.docx | DOCX document | |
| 1-Vendor Information for Bonfire - Fillable.pdf | ||
| 6-5. Attachment C - Purchase Order Terms and Conditions.pdf | ||
| 8-7. Evaluation Criteria.pdf | ||
| 2-1. RFP-209-25 Specifications and Information.pdf | ||
| 3-4. Attachment B - Confidential and Sensitive Information Sharing Agreement.pdf | ||
| 4-2. Exhibit A - Insurance Requirements.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Data Solutions Specifications for Spatial & Nonspatial Data Deliverables
Last Updated: June 2025
Summary If the contractor will be delivering GIS data to Boulder County Parks & Open Space (“BCPOS”), then BCPOS requires GIS specifications be met before delivering that GIS data.
Specifications Spatial Data
1. The contractor will provide, to the best of their ability, high-accuracy locations of GIS features. Accuracy must be noted.
2. The GIS data being delivered by the contractor must be ArcGIS compatible as either a shapefile or file geodatabase feature class with complete metadata.
3. At a minimum, the spatial data must contain an attribute field to hold a unique identifier for each feature. This unique identifier must also be reflected in any non-spatial data (see below).
4. All static maps (e.g. PDF/JPG maps) being provided by the contractor must be georeferenced, when applicable.
5. All spatial or georeferenced data is required to be provided, by the contractor, in the following coordinate system:
Name: NAD 1983 HARN State Plane Colorado North FIPS 0501 Feet Unit: Foot US Projection: Lambert Conformal Conic Horizontal Datum: North American Datum 1983 HARN Vertical Datum: North American Vertical Datum 1988 Spheroid: GRS 1980
Non-Spatial Data
1. Only include data in a data file; do not include figures or analyses.
2. Aggregate like data into fewer large files, rather than many small ones or separate tabs within a spreadsheet.
3. Column headers only use alphanumeric characters or underscores. Column headers do not include spaces. Use only the first row to identify a column header.
4. All cell data format type is formatted properly. Date fields should be in a consistent date format throughout the dataset.
5. Do not rely on special formatting for tables.
6. Do no hide columns or rows.
7. Do not use zeros or blanks to represent missing data. Common alternative conventions include: -9999, NA, or NULL.
8. Table must contain a unique identifier for each record in the table.
ATTACHMENT A
Data Solutions Specifications for Spatial & Nonspatial Data Deliverables
9. Tabular data linking to geospatial data must contain the foreign key or identifier for the spatial feature.
10. Metadata (information that includes data about the data) will accompany data file(s). It will be in a separate, associated word or text document, except in the case of Excel, where it should be included in an additional sheet within the workbook.
| Summary |
| Specifications |
| Spatial Data |
| Non-Spatial Data |
File details come from the government source that posted it. Updated .