Pima County Geographic Information Systems logo

Pima County Geographic Information Systems

GIS Library Data Layers

Metadata Field Descriptions

This table describes the fields used in the data layer metadata. As such it's meta-metadata!

 Metadata FieldField DescriptionAcceptable Values
 Descriptive name Full name of dataset Up to 75 characters
 File name Shapefile name (also used as GDB feature class name and coverage name, if any) Up to 8 characters
 Spatial domain Area included in the data Pima County, Eastern Pima County, downtown, etc. - up to 20 characters
 Abstract Short, descriptive paragraph and explanation. The abstract may also include the data's history and the purpose of the data. Include the main features of the data and whatever makes it unique.  Up to 2000 characters
 Known errors or qualifications Assessment of known errors and problems. Optional. Up to 2000 characters
 Feature type Geospatial data type point, line, polygon, or raster
 Feature count Number of features in the dataset. For instance, the number reported by describe for a coverage. If this number is inflated by artifacts such as interior polygons, explain under "Known errors or qualifications". Optional. An integer number
 Thumbnail Map Link to layer thumbnail in PDF format. Automatically updated. 
 Projection Common nomenclature for the projection in the GIS Library NAD83 HPGN, NAD83 UTM, NAD83 2011, NAD83, or WGS84. See parameters
 Rectification Other dataset used to rectify or align this dataset  COT basemaps, orthophoto, orthophoto90, orthophoto98, parcel, quads, source map, TIGER, FIRM panels, N/A, or unknown. When different areas of the layer are rectified differently, the rectification field may contain more than one value such as "parcel,ortho98". This may occur when the metro area is rectified to parcel and the outlying areas are rectified to the orthophotos.
 Source organization Name of organization from which the data originated to make or enter the GIS Library layer. This should be where the data originated, not necessarily where we got it which can be included under lineage.  Up to 35 characters
 Source contact Name of contact in the organization from which the data originated, possibly including phone number. Optional. Up to 35 characters
 Source document or file name Name of document or file name from which the data originated. Optional. Up to 50 characters
 Source date Date of source map or source data creation Up to 8 characters in form 19990728 (yyyymmdd)
 Source scale Scale of source map. Optional. 24000, etc.
 Source format Format of source data. Unknown, Coverage, Shape, Geodatabase, Esri Layer Pkg, GPS, Grid, MapInfo, BIL, DLG, DGN, DWG, SDE, TIFF, JPG, ECW, SID, Database, Paper, Verbal or Email text
 Second source organization Name of organization for additional data used in the layer. This should be where the data originated, not necessarily where we got it which can be included under lineage. Optional. Up to 35 characters
 Second source contact Name of contact in second organization from which data originated, possibly including phone number. Optional. Up to 35 characters
 Second source document or file name Name of document or file name from which data originated. Optional. Up to 50 characters
 Second source date Date of second source map or source data creation. Optional. Up to 8 characters in form 19990728 (yyyymmdd)
 Second source scale Scale of second source map. Optional. 24000, etc.
 Second source format Format of second source data. Unknown, Coverage, Shape, Geodatabase, Esri Layer Pkg, Grid, MapInfo, BIL, DLG, DGN, DWG, SDE, TIFF, JPG, ECW, SID, Database, Paper, Verbal or Email text
 Date of last data update Date that the layer was last updated with new or significantly altered features or "Daily" for layers with daily maintenance. Up to 8 characters in form 19990728 (yyyymmdd) or "Daily"
 Last data update by Name of person who did the last data update (If unknown, then organization name.) Up to 25 characters
 Date/time last touched Date/time last touched. See more. Automatically updated.
 Lineage Lineage may be the "hands" the data passed through to get to our library. Lineage may also include a description of how the data was derived or descended from one or more sources.  Up to 2000 characters
 On maintenance? Is the dataset being maintained/updated? Yes, No, or Not required
 Maintenance organization Name of organization that maintains the data. The maintenance organization may or may not be the organization that determines content. Content or update requests come from the source organization. Optional.  Up to 35 characters
 Maintenance frequency If on maintenance, then this field describes how often it is updated. Daily, Weekly, Monthly, Quarterly, Annually, Varies, or N/A
 Maintenance description A brief description of who does what and when to maintain the data. Should include how we get the updated info or data, who does the update, when it is updated - particularly for those layers where the update frequency is "Varies". The Maintenance description may also include the formats being converted and the organizations involved, etc.

Optional.

 Up to 2000 characters.
 Original conversion by Point of contact name or organization that did the original conversion to electronic form. Up to 25 characters
 Pima County ITD GIS contact Name of point of contact person in the Pima County ITD GIS area. This is generally whoever knows the most about the layer content or the contact for edits. Up to 25 characters
 On Pima County Geospatial Data Portal? Is the dataset available on the Pima County Geospatial Data Portal?  No, Yes