Pima County Department of Transportation

Geographic Information Services Division

GIS Library Data Layers

Metadata Field Descriptions

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

Date/time last touched

Metadata Field Field Description Acceptable Values

Descriptive name Full name of dataset Up to 75 characters

File name Coverage and shapefile name 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, raster, or tics

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 Link to layer thumbnail in PDF format. Automatically updated.

Projection Common nomenclature for the projection. NAD83 HPGN, NAD27, UTM or LAT/LON. See parameters

Rectification Other dataset used to rectify or align this dataset COT basemaps, 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 data originated. 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 organization from which data originated, possibly including phone number. Optional. Up to 35 characters

Source document or file name Name of document or file name from which 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, Geodatabase, Grid, Shape, BIL, DLG, DWG, SDE, TIFF, or Paper

Source path with layer name (data as received) Path to the original source data as received. Optional. Use backslashes, complete with machine name. Unlike the GIS Library path, do include the layer name (i.e. shapefile, coverage directory, etc). Up to 100 characters

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, Geodatabase, Grid, Shape, BIL, DLG, DWG, SDE, TIFF, or Paper

Date of last 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 update by Name of person who did the last 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 in the specified maintenance format. It is not the organization that determines content. That would be 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. Optional. Includes how we get the updated info or data, who does the update, and when it is updated - particularly for those layers where the update frequency is "Varies". May also include the formats being converted and the organizations involved, etc. - up to 2000 characters. Optional.

Generate lat/lon shapefile? Should a shapefile in latitude/longitude unit be automatically generated in the library? Yes, No

Skip conversion to coverage? Should the normal shapefile automatic conversion to coverage format in the library be skipped?
Typically, the default "No" value is correct. Skipping conversion to coverage is necessary or appropriate in rare cases that include data that can't be properly expressed in a coverage such as:

A shapefile with overlapping data (usually polygon, but also applies to points and lines).
A shapefile that can't be converted to a coverage for technical reasons, such as attribute field types that won't convert, or conversions that fail due to coverage limitations (complexity, number and length of fields, etc).
Yes, No (Always 'No' for Coverage maintenance format layers)

Library write access Describes the maintenance organization's access to the GIS data library. "External organization direct" means they have direct write access to the GIS library, for example PC Development Services or COT DOT. "External organization via import" means the maintaining organization gives the data to the PC DOT GIS Division contact to write the data to the GIS library, for example PAG, or COT Planning. Not maintained, PC DOT GIS Division, External organization direct, External organization via import

Maintenance format in our library. This field describes the format that is used to enter and maintain the data in our Geographic Information Services Division GIS library, typically Shape, Coverage or Enterprise GDB,
The method used to export Enterprise Geodatabase layers to the file-based library determines how the metadata Maintenance format field should be set:

If the layer is maintained in the Enterprise Geodatabase and exported to the file-based library by a special process unique to that layer, then this Maintenance format field should indicate the "file" maintenance format exported by the layer's special process, usually "Shape".

If the layer is maintained in the Enterprise Geodatabase, but does not have a special process unique to the layer for export, then the Maintenance format should be set to "Enterprise GDB". Setting the Maintenance format to "Enterprise GDB" triggers nightly processing to export the layer's Shapefile format in the library.
Coverage, Shape, Enterprise GDB, Grid, BIL, DWG, SDE, TIFF

GIS library path to file maintenance format Path to the file maintenance format, shapefile or coverage. Optional. Use backslashes, complete with machine name but not layer file name. Use trailing backslash. Up to 100 characters

Original conversion by Point of contact name or organization that did the original conversion to electronic form. Up to 25 characters

PC DOT GIS Division contact Name of point of contact person in the PC DOT GIS Division Up to 25 characters

PC DOT GIS Division contact initials Point of contact initials Up to 9 characters

On FTP Server and PCLAYERS DVD? When "Yes" automatically makes the dataset available on the Pima County GIS Data FTP Server and the Pima County GIS Layers (PCLAYERS) DVD (If it's on one, the system adds it to the other.), provided Shapefiles are in the library. Yes, No

Available from PC DOT GIS for commercial purpose? Available from PC DOT GIS for commercial purpose? Yes, No

Available from PC DOT GIS for commercial use data exchange? Available from PC DOT GIS for commercial use data exchange? Yes, No

On main MapGuide map? Is the dataset displayed on the Main MapGuide Map? See John Dickinson or Vernon Woods for additions or changes. Yes, No

On SDCP MapGuide map? Is the dataset displayed on the SDCP MapGuide Map? See John Dickinson or Vernon Woods for additions or changes. Yes, No

On Other MapGuide map? Is the dataset displayed on a MapGuide map other than the Main MapGuide Map and the SDCP MapGuide Map? See John Dickinson or Vernon Woods for additions or changes. Yes, No

MapGuide layer name If on MapGuide, then this field is the layer name as used in the MapGuide legend. Up to 100 characters

MapGuide scale - low If on MapGuide, then this field is the closest (smallest or zoomed in) scale the layer is visible. 24000, etc.

MapGuide scale - high If on MapGuide, then this field is the furthest (largest or zoomed out) scale the layer is visible. 400,000, etc.

Metadata Field	Field Description	Acceptable Values
Descriptive name	Full name of dataset	Up to 75 characters
File name	Coverage and shapefile name	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, raster, or tics
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	Link to layer thumbnail in PDF format.	Automatically updated.
Projection	Common nomenclature for the projection.	NAD83 HPGN, NAD27, UTM or LAT/LON. See parameters
Rectification	Other dataset used to rectify or align this dataset	COT basemaps, 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 data originated. 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 organization from which data originated, possibly including phone number. Optional.	Up to 35 characters
Source document or file name	Name of document or file name from which 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, Geodatabase, Grid, Shape, BIL, DLG, DWG, SDE, TIFF, or Paper
Source path with layer name (data as received)	Path to the original source data as received. Optional. Use backslashes, complete with machine name. Unlike the GIS Library path, do include the layer name (i.e. shapefile, coverage directory, etc).	Up to 100 characters
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, Geodatabase, Grid, Shape, BIL, DLG, DWG, SDE, TIFF, or Paper
Date of last 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 update by	Name of person who did the last 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 in the specified maintenance format. It is not the organization that determines content. That would be 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. Optional.	Includes how we get the updated info or data, who does the update, and when it is updated - particularly for those layers where the update frequency is "Varies". May also include the formats being converted and the organizations involved, etc. - up to 2000 characters. Optional.
Generate lat/lon shapefile?	Should a shapefile in latitude/longitude unit be automatically generated in the library?	Yes, No
Skip conversion to coverage?	Should the normal shapefile automatic conversion to coverage format in the library be skipped? Typically, the default "No" value is correct. Skipping conversion to coverage is necessary or appropriate in rare cases that include data that can't be properly expressed in a coverage such as: A shapefile with overlapping data (usually polygon, but also applies to points and lines). A shapefile that can't be converted to a coverage for technical reasons, such as attribute field types that won't convert, or conversions that fail due to coverage limitations (complexity, number and length of fields, etc).	Yes, No (Always 'No' for Coverage maintenance format layers)
Library write access	Describes the maintenance organization's access to the GIS data library. "External organization direct" means they have direct write access to the GIS library, for example PC Development Services or COT DOT. "External organization via import" means the maintaining organization gives the data to the PC DOT GIS Division contact to write the data to the GIS library, for example PAG, or COT Planning.	Not maintained, PC DOT GIS Division, External organization direct, External organization via import
Maintenance format in our library.	This field describes the format that is used to enter and maintain the data in our Geographic Information Services Division GIS library, typically Shape, Coverage or Enterprise GDB, The method used to export Enterprise Geodatabase layers to the file-based library determines how the metadata Maintenance format field should be set: If the layer is maintained in the Enterprise Geodatabase and exported to the file-based library by a special process unique to that layer, then this Maintenance format field should indicate the "file" maintenance format exported by the layer's special process, usually "Shape". If the layer is maintained in the Enterprise Geodatabase, but does not have a special process unique to the layer for export, then the Maintenance format should be set to "Enterprise GDB". Setting the Maintenance format to "Enterprise GDB" triggers nightly processing to export the layer's Shapefile format in the library.	Coverage, Shape, Enterprise GDB, Grid, BIL, DWG, SDE, TIFF
GIS library path to file maintenance format	Path to the file maintenance format, shapefile or coverage. Optional. Use backslashes, complete with machine name but not layer file name. Use trailing backslash.	Up to 100 characters
Original conversion by	Point of contact name or organization that did the original conversion to electronic form.	Up to 25 characters
PC DOT GIS Division contact	Name of point of contact person in the PC DOT GIS Division	Up to 25 characters
PC DOT GIS Division contact initials	Point of contact initials	Up to 9 characters
On FTP Server and PCLAYERS DVD?	When "Yes" automatically makes the dataset available on the Pima County GIS Data FTP Server and the Pima County GIS Layers (PCLAYERS) DVD (If it's on one, the system adds it to the other.), provided Shapefiles are in the library.	Yes, No
Available from PC DOT GIS for commercial purpose?	Available from PC DOT GIS for commercial purpose?	Yes, No
Available from PC DOT GIS for commercial use data exchange?	Available from PC DOT GIS for commercial use data exchange?	Yes, No
On main MapGuide map?	Is the dataset displayed on the Main MapGuide Map? See John Dickinson or Vernon Woods for additions or changes.	Yes, No
On SDCP MapGuide map?	Is the dataset displayed on the SDCP MapGuide Map? See John Dickinson or Vernon Woods for additions or changes.	Yes, No
On Other MapGuide map?	Is the dataset displayed on a MapGuide map other than the Main MapGuide Map and the SDCP MapGuide Map? See John Dickinson or Vernon Woods for additions or changes.	Yes, No
MapGuide layer name	If on MapGuide, then this field is the layer name as used in the MapGuide legend.	Up to 100 characters
MapGuide scale - low	If on MapGuide, then this field is the closest (smallest or zoomed in) scale the layer is visible.	24000, etc.
MapGuide scale - high	If on MapGuide, then this field is the furthest (largest or zoomed out) scale the layer is visible.	400,000, etc.