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!

Date/time last touched
 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, 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, NAD83 UTM or NAD83 2011. 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, DGN, DWG, SDE, TIFF, Paper or Verbal
 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 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 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. 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.

A layer may specify "Shape" as the Maintenance format in our library when a unique job or process is used to generate the shapefile from sources other than the GDBMAINT geodatabase (as opposed to editing the shapefile directly). In these cases, the Maintenance description field is the appropriate place to enter (1) the name of the scheduled job (2) the name of the machine it runs on and (3) the name of the process owner.

   Job Name: pa_hcsbs
   Machine: SPGISPROC1
   Process Owner: John Dickinson

Optional.

 Up to 2000 characters.
 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 Pima County ITD GIS contact to write the data to the GIS library, for example PAG, or COT Planning.  Not maintained, Pima County ITD GIS, 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 GIS library, typically Shape, Coverage, GDB Std Export, GDB Spec Export or GDB No Export.

The method used to export GDBMAINT Enterprise Geodatabase feature classes to the file-based library determines how the this field should be set:

  • If the layer is maintained in the GDBMAINT Enterprise Geodatabase, but does not have a special process unique to the layer for export, then the Maintenance format should be set to "GDB Std Export" (standard export). Setting the Maintenance format to "GDB Std Export" triggers standardized nightly "GDB to Shape" processing to export the layer's Shapefile format in the library.

  • If the layer is maintained in the GDBMAINT Enterprise Geodatabase and exported to the file-based library by a special process unique to that layer, then this Maintenance format field should indicate "GDB Spec Export" (special export). When the Maintenance Format is set to "GDB Spec Export" then the "GDBMAINT Special Export Process" field should be filled in to identify or explain the process.
 Coverage, Shape, GDB No Export, GDB Std Export, GDB Spec Export, Grid, DWG, TIFF, JPG, ECW, SID
 GIS library path to file maintenance format or GDB maintenance published export format  Path to the file maintenance format or GDB maintenance published export 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
 Pima County ITD GIS contact Name of point of contact person in the Pima County ITD GIS area Up to 25 characters
 Pima County ITD GIS contact initials Point of contact initials Up to 9 characters
 On FTP Server? When "Yes" automatically makes the dataset available on the Pima County GIS Data FTP Server, provided Shapefiles are in the library.  Yes, No
 Available from PC ITD GIS for commercial purpose? Available from PC ITD GIS for commercial purpose? Yes, No
 Available from PC ITD GIS for commercial use data exchange? Available from PC ITD 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. Optional. 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. Optional. 24000, etc.
 MapGuide scale - high If on MapGuide, then this field is the furthest (largest or zoomed out) scale the layer is visible. Optional. 400000, etc.
 Primary Geocortex layer name The full name of this layer as defined in the Geocortex. By our convention this is generally the same as the ArcGIS Server layer name and becomes the PimaMaps layer name. Optional. For example: Streets - All  Up to 100 characters