Appendix F Documentation & Metadata Standards.docx
DOCX document 10 KB Posted
- Attached to
- Carbon Management Zones Consulting
- Solicitation number
- DQ1 EFAA 2027000170 1
- Issued by
- Denver County, Denver City, Colorado
About this file
This document is Appendix F of a state or local contract opportunity, establishing Documentation & Metadata Standards that contractors must follow when delivering spatial datasets. The appendix specifies comprehensive documentation requirements including a Data Dictionary with detailed attribute definitions formatted in accessible file types such as Microsoft Excel, Google Sheets, Word, or PDF. Contractors must document every field within spatial datasets, including source field names, user-friendly field aliases, data types and lengths, detailed descriptions of attribute representations, units of measurement, and coded value lookup tables. Additionally, contractors must provide a Data Lineage & Processing Methodology Log that outlines data creation processes, including source URLs, original data providers, access timestamps, data transformation rules, spatial joins, data cleaning logic, known data anomalies, missing value flags, spatial limitations, and estimated dataset size.
The appendix further requires that embedded metadata comply with FGDC/ISO standards within File Geodatabase item properties or Shapefile XML files, minimally including title, summary/abstract, description, credits/data sources, and use constraints. If the deliverable dataset includes predetermined symbology requirements, contractors must document specifications in a document or spreadsheet detailing attribute field values, visual properties including RGB or HEX color codes, symbol shapes, size/scale thresholds, line weights and fill patterns, cartographic guidance such as legend labels and display order, and background transparency settings. All symbology must meet WCAG 2.1AA contrast standards to ensure accessibility for all users.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Appendix B_ Vendor Disclosure Statement.pdf | ||
| Appendix D Artificial Intelligence (AI) Disclosure and Use Requirements.docx | DOCX document | |
| DQ EFAA 27-170 Carbon Managment Zones Consulting.docx | DOCX document | |
| Appendix E Required Data Formats.docx | DOCX document | |
| Appendix C_Vendor Accessibility Checklist.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 .