Text · page 51 of 67
Read the whole document on one page (all 67 pages, each with its own heading)
d. Documentation 1) A data dictionary must be included along with the map files describing file contents, file names along with the name, description, data type and length for each attribute in a data table. Metadata must be provided for each file and shall include: 1. Title- In plain language; 2. Summary- One or two sentences of information describing what the data is showing 3. Thumbnail- image of data on map; 4. Description- A paragraph giving a more in-depth description as to the background of the data, the provider of the data, when the data was last updated. The who, what, why of the data; 5. Tags/ Descriptive Words- key descriptive words that help focus a user’s search; 6. Bounds of data- Bounding coordinates (N, E, S, W), usage limitation/ general constraints; 7. Publication Dates: When was the data first published. If it has never been published, we will give a published date when it is published on the Gateway; 8. Citation Contact- Who produced the data: Organization name and phone number, email, website of the organization and or individual should be provided; 9. Lineage- information describing the revision history of the data. Start with date of creation, any following update or review dates; and, 10. Use limitations: Please provide any use limitation for the data and creation methodology. It is important to understand that deliverables are not considered complete without metadata. Data provided under federal funds must be provided in a manner which meets Digital Geospatial Federal Geographic Data Committee Metadata Standard as executed by Executive Order 12906, April 11,1994, "Coordinating Geographic Data Acquisition and Access: the National Spatial Data Infrastructure". 2) Datums and Coordinate Systems – All vector data and map products should be submitted in geographic coordinate system, decimal degree units, and either NAD83 or WGS84. Raster data, such as aerial photographs, may be submitted in their native projection, and maps should be in the appropriate projection/coordinate system for the area depicted. Where applicable, the National Geodetic Vertical Datum of 1988 (NGVD88) shall be used as the preferred vertical datum. e. Map Accuracy -- All deliverable map products must conform to National Map Accuracy Standards for horizontal and vertical accuracy as established by the United States Bureau of the Budget, June 10, 1941, revised June 17, 1947. For example, for Contract Number: C1003337 Page 9 of 11, Attachment A-2 – Program Specific Terms and Conditions