Metropolitan Planning Organization

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics
Publication_Date: 2003
Title: Metropolitan Planning Organization
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: <http://www.bts.gov/gis/>
Larger_Work_Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics
Publication_Date: 2003
Title: National Transportation Atlas Database (NTAD) 2003
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washington, DC
Publisher: Bureau of Transportation Statistics
Online_Linkage: <http://www.bts.gov/gis/>
Description:
Abstract:
The United States Metropolitan Planning Organization database is a geographic database of Metropolitan Planning Organization political boundaries.
Purpose:
The data provides users with information about the locations, names and sizes of Metropolitan Planning Organizations and is intended for use primarily with national planning applications.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2003
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -158.280941
East_Bounding_Coordinate: -65.739195
North_Bounding_Coordinate: 61.479960
South_Bounding_Coordinate: 17.930901
Keywords:
Theme:
Theme_Keyword_Thesaurus: None.
Theme_Keyword: municipal
Theme_Keyword: planning
Theme_Keyword: organization
Theme_Keyword: region
Theme_Keyword: regional
Theme_Keyword: polygon
Theme_Keyword: transportation
Theme_Keyword: MPO
Theme_Keyword: Agency
Theme_Keyword: COG
Theme_Keyword: Council of Governments
Theme_Keyword: metropolitan
Theme_Keyword: study area
Theme_Keyword: planning commission
Theme_Keyword: planning agency
Temporal:
Temporal_Keyword: 2003
Access_Constraints: None.
Use_Constraints:
Acknowledgement of the Bureau of Transportation Statistics (BTS) National Transportation Atlas Databases (NTAD) 2003 would be appreciated in products derived from these data.
Point_of_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Transportation Statistics
Contact_Address:
Address_Type: mailing and physical address
Address: 400 7th St. SW
City: Washington
State_or_Province: DC
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 1 202 366 DATA
Contact_Facsimile_Telephone: 1 202 366 3640
Contact_Electronic_Mail_Address: answers@bts.gov
Data_Set_Credit:
The Bureau of Transportation Statistics and the Federal Highway Administration.
Native_Data_Set_Environment:
Microsoft Windows NT Version 4.0 (Build 1381) Service Pack 6; ESRI ArcCatalog 8.3.0.800
Cross_Reference:
Citation_Information:
Originator: Bureau of Transportation Statistics
Publication_Date: 2003
Title: National Transportation Atlas Database (NTAD) 2003
Geospatial_Data_Presentation_Form: vector digital data
Publication_Information:
Publication_Place: Washinton, DC
Publisher: Bureau of Transportation Statistics

Data_Quality_Information:
Logical_Consistency_Report:
All node-link and polygon topological relationships were created and verified using ESRI ArcGIS 8.2.
Completeness_Report: Complete.
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics
Publication_Date: 2001
Title: US Counties
Geospatial_Data_Presentation_Form: vector digital data
Larger_Work_Citation:
Citation_Information:
Originator: Bureau of Transportation Statistics
Publication_Date: 2001
Title: North American Transportation Atlas Databases
Publication_Information:
Publication_Place: Washington, DC
Publisher: Bureau of Transportation Statistics
Process_Step:
Process_Description:
Various types of processing were used for the data that arrived from many different sources. The sources mostly include individual MPOs and state DOTs. An attempt to summarize the various types of processing that occurred with the data will follow. For the specific processing on each MPO, please refer to notes submitted to BTS when the data was delivered (Appendix E - MPO Listing, Project ID Code and Processing Notes). ESRI ArcGIS 8.2 was used for the processing environment.

- Some MPOs were entirely defined by county units. The NTAD county layer served as the basis for bringing in the county(s) and merging several counties if necessary into the MPO shapefile. - Some MPOs sent shapefiles or other digital files with the boundary. The projection needed to be defined before inclusion into the dataset. As the projection information was not included in many cases, some errors could have been introduced and calls or email were required to the contact person for the data. NAD83 datum was assumed and tested for agreement on occasions where the datum could not be verified. - Some digital files had multiple polygons that were merged to form a single multipart polygon in ESRI format. - Some digital files were converted using ESRI and other proprietary tools to ESRI readable formats and then added to the MPO shapefile. Others were converted to ESRI readable files with request to the MPOs themselves or BTS. - Some digital files arrived as line features and built using ESRI tools to form polygons. On some occasions small connectors were added to complete the topology of the polygon (usually not more than a few meters). - On occasions where the boundaries received were significantly out-of-alignment with the NTAD county layer, but clearly intending to follow a county boundary in a particular boundary region, part of the received boundary would be snapped to the NTAD county boundary layer. This snapping occured frequently along shorelines or rivers. These adjustments were an attempt to create uniformity with the NTAD county boundaries. - In the few digital sources that were not referenced to a coordinate system, ESRI affine transformation tool and manual creation of reference points were used to bring the data into a known coordinate system. - In the few text descriptions of boundaries received from MPOs (rather than digital files), geographies were used from several sources to manually create the boundaries. The sources are noted in the Source Information section of this document. - For MPOs with no boundary information, 5 mile radius circular placeholders were created using a North American Lambert Conformal Conic Projection with Incorporated Places/Census Designated Places, 2000, for placement reference.

Process_Date: 2003
Process_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Transportation Statistics
Contact_Address:
Address_Type: mailing and physical address
Address: Bureau of Transportation Statistics (BTS)
Address: Room 3430
Address: 400 Seventh Street, S.W.
City: Washington
State_or_Province: DC
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 202-366-DATA
Contact_Facsimile_Telephone: 202-366-3640
Contact_Electronic_Mail_Address: answers@bts.gov

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: G-polygon
Point_and_Vector_Object_Count: 342

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Geographic:
Latitude_Resolution: 0.000001
Longitude_Resolution: 0.000001
Geographic_Coordinate_Units: Decimal degrees
Geodetic_Model:
Horizontal_Datum_Name: D_WGS_1984
Ellipsoid_Name: WGS_1984
Semi-major_Axis: 6378137.000000
Denominator_of_Flattening_Ratio: 298.257224

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: mpo
Entity_Type_Definition: Metropolitan Planning Organization Boundaries
Entity_Type_Definition_Source: BTS
Attribute:
Attribute_Label: FID
Attribute_Definition: Internal feature number.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain:
Sequential unique whole numbers that are automatically generated.
Attribute:
Attribute_Label: Shape
Attribute_Definition: Feature geometry.
Attribute_Definition_Source: ESRI
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: ID
Attribute_Definition: Unique Identifier
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Numeric Value
Codeset_Source: BTS
Attribute:
Attribute_Label: AREA
Attribute_Definition: The area size of the polygon that was system generated
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Numeric Value
Codeset_Source: BTS
Attribute:
Attribute_Label: INITIAL_ID
Attribute_Definition: Initial Data Processing ID
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Numeric Value
Codeset_Source: BTS
Attribute:
Attribute_Label: MPO_ID
Attribute_Definition:
A unique identifier for all MPOs. This development ID is not an official identifier such as a FIPS code.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Numeric Value
Codeset_Source: BTS
Attribute:
Attribute_Label: AGENCY_NAM
Attribute_Definition: The name of the Metropolitan Planning Organization.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: NUMBER_OF_
Attribute_Definition: The number of Primary urbanized area associated with the MPO.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Numeric Value
Attribute:
Attribute_Label: PRIMARY_UR
Attribute_Definition: Primary urbanized area associated with the MPO.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: INCLUDED_U
Attribute_Definition: Urbanized areas included in MPO.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: INCLUDED_1
Attribute_Definition: Partial urbanized areas included in MPO area.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: INCLUDED_2
Attribute_Definition: Partial urbanized areas included in MPO area.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: INCLUDED_3
Attribute_Definition: Partial urbanized areas included in MPO area.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: ADDRESS1
Attribute_Definition: Mailing address.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: ADDRESS2
Attribute_Definition: Mailing address.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: PO_BOX
Attribute_Definition: Post office box number.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Numeric Value
Attribute:
Attribute_Label: CITY
Attribute_Definition: Mailing address city.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: STATE
Attribute_Definition: Mailing address state.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: ZIP_CODE
Attribute_Definition: Mailing address zip code.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Numeric Value
Attribute:
Attribute_Label: PHONE
Attribute_Definition: Contact telephone number.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Numeric Value
Attribute:
Attribute_Label: AGENCY_WEB
Attribute_Definition: URL for MPO internet site.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Unrepresentable_Domain: Character String
Attribute:
Attribute_Label: MPO_POPULA
Attribute_Definition: Total population served by MPO.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Codeset_Domain:
Codeset_Name: Numeric Value
Codeset_Source: BTS
Attribute:
Attribute_Label: VERSION
Attribute_Definition:
The VERSION is a 2-digit number that will be incremented for all records in the database whenever a new release is distributed.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 00
Range_Domain_Maximum: 99
Attribute:
Attribute_Label: REVISION
Attribute_Definition:
REVISION is a 2-digit number that will be incremented individually for each record whenever a change is made to one of its fields.
Attribute_Definition_Source: BTS
Attribute_Domain_Values:
Range_Domain:
Range_Domain_Minimum: 00
Range_Domain_Maximum: 99

Distribution_Information:
Distributor:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Transportation Statistics (BTS)
Contact_Address:
Address_Type: mailing and physical address
Address: 400 Seventh Street, S.W.
City: Washington
State_or_Province: DC
Postal_Code: 20950
Country: USA
Contact_Voice_Telephone: 202-366-DATA
Contact_Facsimile_Telephone: 202-366-3640
Contact_Electronic_Mail_Address: answers@bts.gov
Resource_Description:
Downloadable Data National Transportation Atlas Database (NTAD) 2003
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Shapefile
Format_Version_Number: 2003
Transfer_Size: 7.256
Digital_Transfer_Option:
Online_Option:
Access_Instructions:
Anyone with access to the World Wide Web may connect to the BTS server. To access a specific database, go to the address listed above in the Network Resource Name. The visitor can create a package of the dataset for download in a .zip format (i.e. MS-DOS zip archive). This archived package is stored in a temporary file that can then be copied to the visitor's home directory.
Offline_Option:
Offline_Media: CD-ROM
Fees: None
Ordering_Instructions:
Call 202-366-DATA, fax 202-366-3640, or E-mail (answers@bts.gov) BTS to request the National Transportation Atlas Databases 2003 CD-ROM. This and other BTS products may be ordered from the BTS Internet website (<http://www.bts.gov/gis/>).
Technical_Prerequisites:
Must have access to GIS software such as ESRI's ArcView or ArcINFO, or other compatible software to view the data
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: 2003

Metadata_Reference_Information:
Metadata_Date: 20030506
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Bureau of Transportation Statistics
Contact_Address:
Address_Type: 400 7th St. SW
City: Washington
State_or_Province: DC
Postal_Code: 20590
Country: USA
Contact_Voice_Telephone: 1 202 366 DATA
Contact_Facsimile_Telephone: 1 202 366 3640
Contact_Electronic_Mail_Address: answers@bts.gov
Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time
Metadata_Extensions:
Online_Linkage: <http://www.esri.com/metadata/esriprof80.html>
Profile_Name: ESRI Metadata Profile

Generated by mp version 2.7.33 on Tue May 06 10:13:29 2003