Appendix F Documentation & Metadata Standards.docx
DOCX document 10 KB Posted
- Attached to
- Thermal Opportunity Mapping
- Solicitation number
- DQ1 EFAA 2027000087 1
- Issued by
- Denver County, Denver City, Colorado
About this file
This is a Documentation and Metadata Standards appendix document for Colorado's Thermal Opportunity Mapping state and local contract opportunity. The document establishes comprehensive technical requirements and standards for data submission, documentation practices, and metadata specifications that contractors must follow throughout the project execution and deliverable submission phases. The standards cover data formatting requirements, file naming conventions, documentation protocols, quality assurance procedures, and metadata tagging systems designed to ensure consistency, interoperability, and accessibility of all project outputs. Contractors are required to adhere to these standards for all thermal mapping data, supporting documentation, analytical reports, and associated metadata to facilitate integration with existing state systems and enable future data utilization by multiple stakeholders.
The appendix specifies technical validation procedures, data quality metrics, and documentation review processes that contractors must implement to verify compliance with the established standards before final submission. These standards ensure that deliverables meet state requirements for data accuracy, completeness, and usability while establishing clear protocols for version control, revision tracking, and documentation archiving. The requirements apply to all phases of the thermal opportunity mapping project, including data collection, analysis, visualization, and reporting, with particular emphasis on maintaining detailed metadata that documents data sources, processing methodologies, assumptions, and limitations to support transparency and reproducibility of all project findings and deliverables.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Appendix E Required Data Formats.docx | DOCX document | |
| DQ EFAA 27-87 Thermal Opportunity Mapping.docx | DOCX document | |
| Appendix C_Vendor Accessibility Checklist.docx | DOCX document | |
| Appendix B_ Vendor Disclosure Statement.pdf | ||
| Appendix D AI Contracting Language.docx | DOCX document |
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 .