Appendix F Documentation & Metadata Standards.docx
DOCX document 10 KB Posted
- Attached to
- Thermal Opportunity Mapping
- Solicitation number
- DQ1 EFAA 2027000087 2
- Issued by
- Denver County, Denver City, Colorado
About this file
Appendix F Documentation & Metadata Standards
This document is an appendix establishing documentation and metadata standards for the Thermal Opportunity Mapping project in Colorado. The appendix provides technical specifications and requirements for data collection, organization, and reporting throughout the project lifecycle. The standards establish protocols for how all project deliverables, datasets, and supporting documentation must be formatted, labeled, and maintained to ensure consistency, interoperability, and accessibility across all project phases. These standards apply to all contractors and subcontractors involved in the thermal mapping initiative and serve as binding technical requirements for contract performance.
The metadata standards detailed in this appendix ensure that all thermal imaging data, geographic information systems (GIS) files, reports, and supporting documentation meet Colorado's data management requirements and are compatible with existing state systems. The standards address file naming conventions, data structure requirements, quality assurance protocols, and documentation procedures that contractors must follow when submitting deliverables. Adherence to these specifications is mandatory for contract acceptance and payment, and non-compliant submissions may be rejected or require resubmission at the contractor's expense. These standards enable seamless integration of thermal opportunity mapping data into Colorado's broader environmental and energy planning frameworks.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Appendix C_Vendor Accessibility Checklist.docx | DOCX document | |
| Appendix D AI Contracting Language.docx | DOCX document | |
| Appendix E Required Data Formats.docx | DOCX document | |
| DQ EFAA 27-87 Thermal Opportunity Mapping.docx | DOCX document | |
| Amend # 1 Vendor Q&A DQ EFAA 2027-87 Thermal Opportunity Mapping.pdf | ||
| Appendix B_ Vendor Disclosure Statement.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Appendix F: Documentation & Metadata Standards The Contractor must provide extensive documentation accompanying the spatial data.
Data Dictionary & Attribute Definitions If the deliverable datasets are custom-made with a unique attribute schema, the Contractor shall provide a standalone Data Dictionary (formatted as a Microsoft Excel workbook, Google Sheet, Word Doc, Google Doc, PDF, or other easily consumable file format) detailing every field within the spatial dataset, including:
· Source Field Name: Exact column header/attribute name in the database.
· Field Alias: User-friendly display name (suitable for web app pop-ups and legends).
· Data Type & Length: (e.g., Text(50), Short Integer, Double, Date).
· Detailed Description: A clear, written definition explaining what the attribute represents and how it was derived.
· Units of Measurement: Explicitly stating units where applicable (e.g., kWh, Megawatts, Square Feet, USD).
· Coded Values & Domains: A complete lookup table for any coded fields, acronyms, or numeric flags (e.g., 0 = Inactive, 1 = Active, 99 = Unknown / Not Reported).
Data Lineage & Processing Methodology Log
The Contractor must supply a technical summary outlining how the data was created, including:
· Source URLs, original data providers, and access timestamps.
· Summary of data transformation rules, spatial joins, or data cleaning logic applied.
· Known data anomalies, missing value flags, or spatial limitations.
· Estimated dataset size.
Embedded Metadata
Standard FGDC/ISO-compliant metadata must be embedded directly within the File Geodatabase item properties or Shapefile XML, filling out at a minimum: Title, Summary/Abstract, Description, Credits/Data Sources, and Use Constraints.
Symbology
If the deliverable dataset includes predetermined or required symbology rules, classification schemes, or color standards, the Contractor must document these specifications in a document or spreadsheet. This documentation must clearly detail:
Attribute Field Values: The specific fields and coded values driving the symbology.
Visual Properties: Color codes (RGB or HEX values), symbol shapes, size/scale thresholds, line weights, and fill patterns corresponding to each value or category.
Cartographic Guidance: Legend labels, display order, and any required background transparency settings.
Symbology must meet WCAG 2.1AA contrast standards to ensure accessibility.
File details come from the government source that posted it. Updated .