Transcript
Page 1: The Best Practices Data Model – Governmental Units March 1 ... · The Best Practices Data model was developed as a collaborative effort between ESRI and the U.S. Geological Survey

March 1, 2006The Best Practices Data Model – Governmental Units

The Catalog ViewCoded value domainIncorporatedPlace FCodeDescription

Field typeSplit policy

Merge policy

Long integerDuplicateDefault value

DescriptionCode61400 Incorporated Place61401 Borough61403 City61404 City and Borough61405 Communidad61407 Consolidated City61410 Independent City61412 Municipality61414 Town61415 Village61416 Zone Urbana

Coded value domainNativeAmericanReservation FCodeDescription

Field typeSplit policy

Merge policy

Long integerDefault valueDefault value

DescriptionCode64000 Native American Reservation64080 Tribal Designated Statistic Area64081 Colony64082 Community64083 Joint Use Area64084 Pueblo64085 Rancheria64086 Reservation64087 Reserve64088 Oklahoma Tribal Statistical Area64089 American Indian Trust Land64090 Joint Use OK Trib Stat Area64091 Ranch64092 State Desig Amer Indian Stat Area64093 Indian Village64094 Village64095 Indian Community64096 Amer Indian Off-Res Trust Land

Native American Area Domains

Regulated Use Domains Zoning Domains

Boundary Point Domain

Jurisdictional DomainsReserve Domains

Coded value domainMinorCivilDivision FCodeDescription

Field typeSplit policy

Merge policy

Long integerDuplicateDefault value

DescriptionCode61300 Minor Civil Division61302 Barrio61304 Barrio - Pueblo61306 Borough61308 Census County Division61310 Census Sub Area61312 Census Sub District61314 Charter Township61316 City61318 County61320 District61322 Gore61324 Grant61326 Incorporated Town61328 Independent City61330 Island61332 Location61334 Municipality61336 Plantation61338 Precinct61340 Purchase61342 Reservation61344 Subbarrio61346 Town61348 Township61350 Unorganized Territory61352 Village

Governmental Units includes administrative areas, census units, and management jurisdictions for local governments, states, federal agencies, and Native American organizations.

Domains

GeodatabaseFeature datasetFoundation

Point feature classGU_BoundaryPoint

Polygon feature classGU_Country

Polygon feature classGU_StateOrTerritory

Polygon feature classGU_CountyOrEquivalent

Polygon feature classGU_IncorporatedPlace

Polygon feature classGU_MinorCivilDivision

Polygon feature classGU_NativeAmericanArea

Polygon feature classGU_CensusBlock

Polygon feature classGU_CensusBlockGroup

Polygon feature classGU_CensusTract

Polygon feature classGU_Reserve

Polygon feature classGU_Jurisdicational

Polygon feature classGU_Zoning

Polygon feature classGU_RegulatedUse

Polygon feature classGU_UnincorporatedPlace

Simple feature classGU_Zoning Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allow nulls

OBJECTID Object IDShape Geometry Yes

Permanent_Identifier String Yes 40Source_FeatureID String Yes 40Source_DatasetID String Yes 40Source_DataDesc String Yes 100Source_Originator String Yes 130

Data_Security Short integer Yes 0 Sec_Classification Domain 0Distribution_Policy String Yes E4 Distribution_Policy Domain 4

LoadDate Date Yes 0 0 8GNIS_ID String Yes 10

Name String Yes 100AreaSqM Double Yes 0 0

FType Long integer Yes 680 0FCode Long integer Yes 68000 0

Use_Status String Yes UseStatus Domain 10Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0

Default value

List of defined default values and domains for subtypes in this class

DomainField nameSubtype

Description

Default subtypeSubtype field

SubtypeCode

Subtypes of GU_ZoningFType680

681 Commercial

Data_Security 0 Sec_Classification DomainDistribution_Policy E4 Distribution_Policy Domain

FCode 68100 Commercial FCodeUse_Status UseStatus Domain

682 Industrial

Data_Security 0 Sec_Classification DomainDistribution_Policy E4 Distribution_Policy Domain

FCode 68200 Industrial FCodeUse_Status UseStatus Domain

680 Residential

Data_Security 0 Sec_Classification DomainDistribution_Policy E4 Distribution_Policy Domain

FCode 68000 Residential FCodeUse_Status UseStatus Domain

FEATURE CLASSES

Feature Metadata

Simple feature classGU_CensusBlock Contains Z values

Contains M valuesGeometry Polygon

NoNo

Data typeField namePrec-ision Scale LengthDomainDefault value

Allow nulls

Shape Geometry YesOBJECTID Object ID

Permanent_Identifier String Yes 40Source_FeatureID String Yes 40Source_DatasetID String Yes 40Source_DataDesc String Yes 100Source_Originator String Yes 130

Data_Security Short integer Yes 0 Sec_Classification Domain 0Distribution_Policy String Yes E4 Distribution_Policy Domain 4

LoadDate Date Yes 0 0 8FCode Long integer Yes 60000 CensusBlock FCode 0

StCo_FIPSCode String Yes 5State_Name String Yes 60

County_Name String Yes 60CensusTract String Yes 6

CensusBlockGroup String Yes 1CensusBlock String Yes 4

Population2000 Long integer Yes 0AreaSqM Double Yes 0 0GNIS_ID String Yes 10

Shape_Length Double Yes 0 0Shape_Area Double Yes 0 0

Metadata is stored in the model in three related tables. The Meta_DatasetDetail table holds information specific to the source of the data, i.e.; originator name, data accuracy

and currency, data source url, etc.

The Meta_ProcessDetail table holds fields specific to the processor (contact information) and the process used in loading or updating the dataset features or objects.

The BPFeatureToMetadata table links the features and objects to one or more processes and their sources. This table gives the model the capability of lineage,

i.e.; tracking the history of changes for a given feature.

Each feature and object in the model is linked to the Meta_DatasetDetail table through the Source_DatasetID field

included in every feature class and object table. Certain metadatafields in the Meta_DatasetDetail and Meta_ProcessDetail tables

are included on the features and objects themselves to give the user quick access to key metadata

information. (See fields outlined in red).

For field definitions, please refer to the document Standard Content Standard for Digital Geospatial Metadata (FGDC-STD-001-1998). http://www.fgdc.gov/metadata/contstan.html

To M

eta

This poster depicts the Best Practices model, version 1.1 and was created by the U. S. Geological Survey ,National Geospatial Technical Operations Center,

Denver, Colorado, 80225

The Best Practices Data model was developed as a collaborative effort between ESRI and the U.S. Geological Survey.

A “GIS for the Nation,” the Best Practices Data Model offers a data sharing informationtemplate to accommodate local, state, tribal, and national data needs.

Permanent_Identifiers

Top Related