Upload File

the best practices data model – governmental units march 1 ... · the best practices data model...

  • Home
  • Documents
  • 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
1
March 1, 2006 The Best Practices Data Model – Governmental Units The Catalog View Coded value domain IncorporatedPlace FCode Description Field type Split policy Merge policy Long integer Duplicate Default value Description Code 61400 Incorporated Place 61401 Borough 61403 City 61404 City and Borough 61405 Communidad 61407 Consolidated City 61410 Independent City 61412 Municipality 61414 Town 61415 Village 61416 Zone Urbana Coded value domain NativeAmericanReservation FCode Description Field type Split policy Merge policy Long integer Default value Default value Description Code 64000 Native American Reservation 64080 Tribal Designated Statistic Area 64081 Colony 64082 Community 64083 Joint Use Area 64084 Pueblo 64085 Rancheria 64086 Reservation 64087 Reserve 64088 Oklahoma Tribal Statistical Area 64089 American Indian Trust Land 64090 Joint Use OK Trib Stat Area 64091 Ranch 64092 State Desig Amer Indian Stat Area 64093 Indian Village 64094 Village 64095 Indian Community 64096 Amer Indian Off-Res Trust Land Native American Area Domains Regulated Use Domains Zoning Domains Boundary Point Domain Jurisdictional Domains Reserve Domains Coded value domain MinorCivilDivision FCode Description Field type Split policy Merge policy Long integer Duplicate Default value Description Code 61300 Minor Civil Division 61302 Barrio 61304 Barrio - Pueblo 61306 Borough 61308 Census County Division 61310 Census Sub Area 61312 Census Sub District 61314 Charter Township 61316 City 61318 County 61320 District 61322 Gore 61324 Grant 61326 Incorporated Town 61328 Independent City 61330 Island 61332 Location 61334 Municipality 61336 Plantation 61338 Precinct 61340 Purchase 61342 Reservation 61344 Subbarrio 61346 Town 61348 Township 61350 Unorganized Territory 61352 Village Governmental Units includes administrative areas, census units, and management jurisdictions for local governments, states, federal agencies, and Native American organizations. Domains Geodatabase Feature dataset Foundation Point feature class GU_BoundaryPoint Polygon feature class GU_Country Polygon feature class GU_StateOrTerritory Polygon feature class GU_CountyOrEquivalent Polygon feature class GU_IncorporatedPlace Polygon feature class GU_MinorCivilDivision Polygon feature class GU_NativeAmericanArea Polygon feature class GU_CensusBlock Polygon feature class GU_CensusBlockGroup Polygon feature class GU_CensusTract Polygon feature class GU_Reserve Polygon feature class GU_Jurisdicational Polygon feature class GU_Zoning Polygon feature class GU_RegulatedUse Polygon feature class GU_UnincorporatedPlace Simple feature class GU_Zoning Contains Z values Contains M values Geometry Polygon No No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls OBJECTID Object ID Shape Geometry Yes Permanent_Identifier String Yes 40 Source_FeatureID String Yes 40 Source_DatasetID String Yes 40 Source_DataDesc String Yes 100 Source_Originator String Yes 130 Data_Security Short integer Yes 0 Sec_Classification Domain 0 Distribution_Policy String Yes E4 Distribution_Policy Domain 4 LoadDate Date Yes 0 0 8 GNIS_ID String Yes 10 Name String Yes 100 AreaSqM Double Yes 0 0 FType Long integer Yes 680 0 FCode Long integer Yes 68000 0 Use_Status String Yes UseStatus Domain 10 Shape_Length Double Yes 0 0 Shape_Area Double Yes 0 0 Default value List of defined default values and domains for subtypes in this class Domain Field name Subtype Description Default subtype Subtype field Subtype Code Subtypes of GU_Zoning FType 680 681 Commercial Data_Security 0 Sec_Classification Domain Distribution_Policy E4 Distribution_Policy Domain FCode 68100 Commercial FCode Use_Status UseStatus Domain 682 Industrial Data_Security 0 Sec_Classification Domain Distribution_Policy E4 Distribution_Policy Domain FCode 68200 Industrial FCode Use_Status UseStatus Domain 680 Residential Data_Security 0 Sec_Classification Domain Distribution_Policy E4 Distribution_Policy Domain FCode 68000 Residential FCode Use_Status UseStatus Domain FEATURE CLASSES Feature Metadata Simple feature class GU_CensusBlock Contains Z values Contains M values Geometry Polygon No No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Shape Geometry Yes OBJECTID Object ID Permanent_Identifier String Yes 40 Source_FeatureID String Yes 40 Source_DatasetID String Yes 40 Source_DataDesc String Yes 100 Source_Originator String Yes 130 Data_Security Short integer Yes 0 Sec_Classification Domain 0 Distribution_Policy String Yes E4 Distribution_Policy Domain 4 LoadDate Date Yes 0 0 8 FCode Long integer Yes 60000 CensusBlock FCode 0 StCo_FIPSCode String Yes 5 State_Name String Yes 60 County_Name String Yes 60 CensusTract String Yes 6 CensusBlockGroup String Yes 1 CensusBlock String Yes 4 Population2000 Long integer Yes 0 AreaSqM Double Yes 0 0 GNIS_ID String Yes 10 Shape_Length Double Yes 0 0 Shape_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 metadata fields 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 et a 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 information template to accommodate local, state, tribal, and national data needs. Permanent_Identifiers

Upload: others

Post on 24-Aug-2020

1 views

Category:

Documents


0 download

Report

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

The Best Practices Data Model - Transportation … Best Practices Data Model - Transportation March 1, 2006 Feature Detail Tables Coded value domain Junction FCode Description Field

Foresight Maturity Model (FMM): Achieving Best Practices

Firefighter Best Practices Model Program

Best Practices of a School Based Behavioral Health Model

A Best Practices Model for Streamlined Local Permitting

A Best Practices Model for Streamlined Local … Best Practices Model for Streamlined Local Permitting ... A Best Practices Model for Streamlined Local Permitting ... to implement

Recruitment Retention Best Practices Model

SAS6485-2016 Best Practices for Effective Model …support.sas.com/resources/papers/proceedings16/SAS6485...1 SAS6485-2016 Best Practices for Effective Model Risk Management Satish

IBM Tivoli Common Data Model: Guide to Best Practices

120530-1 CMDB Best Practices and Service Model

Shader Model 3.0, Best Practicesdeveloper.download.nvidia.com/.../docs/6800_Leagues_SM3_Best_Pr… · Shader Model 3.0, Best Practices Phil Scott Technical Developer Relations, EMEA

Best Practices for Model-Driven Development - · PDF file3 MDSD Best Practices Model-Driven Software Development • Model-Driven Software Development is about making software development

Best Practices for DSLs and Model- Driven Development · BEST PRACTICES FOR DSLS AND MODEL-DRIVEN DEVELOPMENT 80 JOURNAL OF OBJECT TECHNOLOGY VOL. 8, NO. 6. Each of the best practices

THE BEST PRACTICES (BPs) MODEL FOR UPGRADING RANKING …

Academic talent development programs: a best practices model · Academic talent development programs: a best practices model ... called gifted programs, mainly exemplified by pullout

Model Risk Management : Best Practices

BEST PRACTICES - SportsEngine...BEST PRACTICES The Minnesota Development Model (MDM) is based on the principles of USA Hockey’s American Development Model (ADM). This involves the

Comply and Compete: Model Management Best Practices

The Oncology Care Model: Evolving Best Practices ·  · 2017-09-07The Oncology Care Model Evolving Best Practices •Diana Verrilli, ... The Oncology Care Model Evolving Best Practices

A model of Best Practices for a Sourcing Process

Best Practices for Model Based Design v3

A COLLABORATIVE MODEL OF JOB DEVELOPMENT FIVE BEST PRACTICES

The Best Practices Data Model – Structures March 1, 2006 ......The Best Practices Data Model accommodates structure locations, building footprints, complexes, and 3D representations

Best Practices for System Dynamics Model Design and ... · PDF fileSANDIA REPORT SAND2011-4108 . Unlimited Release . Printed June 2011 . Best Practices for System Dynamics Model Design

Model Runway: Design Best Practices at BlueCross BlueShield

SCOR Model - GS1 Taiwan · 42 Best Practices SCOR ModeBest Practices D1.12 Ship Product Metrics (see Appendix A for metrics attributes): Best Practices: SCOR Model (SCM)

HR Shared Services: Best Practices, Business Model and Technology

Best Practices In Automated Valuation Model (AVM) Validation

Best Modeling Practices: Model Evaluation · 2015-09-18 · 1 Best Modeling Practices: Model Evaluation Web-based Training on Best Modeling Practices and Technical Modeling Issues

Developing a Metadata Best Practices Model

Model Wind Turbine Provisions and Best Practices for New ... · REPORT Model Wind Turbine Provisions and Best Practices for New Brunswick Municipalities, Rural Communities and Unincorporated

A best practices discussion Transform your bank's operations model

Application of Development "Best Practices" Model

SAS® Modeling Best Practices › kntur85557 › attachments...SAS® Modeling Best Practices Agenda •Problem definition •Supervised vs. unsupervised learning •Best model for

Best Practices for Irregular Warfare (IW) Data …ismor.cds.cranfield.ac.uk/29th-symposium-2012/best...References • Irregular Warfare (IW) Model Validation Best Practices Guide (TRAC,