UGB_2011_DAS

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Title: UGB_2011_DAS
Geospatial_Data_Presentation_Form: vector digital data
Description:
Abstract:
This theme delineates Urban Growth Boundaries (UGBs) in the state of Oregon. Oregon land use laws limit development outside of urban growth boundaries. The line work was created by various sources including the Oregon Department of Land Conservation and Development (DLCD), the Oregon Department of Transportation (ODOT), Metro Regional Council of Governments (Metro), county and city GIS departments, and the Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO).Urban growth boundaries (UGBs) are lines drawn on planning and zoning maps to show where a city expects to experience growth for the next 20 years. UGBs were established under Oregon Statewide Planning Goals in 1973 by the Oregon State Legislature (Senate Bill 100). Goal 14 specifically deals with UGBs (OAR 660-15-0000(4)). Other specific ORS that relate to the designation and delineation of UGBs are: 197.626 Expanding urban growth boundary and designating urban reserve area subject to periodic review.A city with a population of 2,500 or more within its urban growth boundary that amends the urban growth boundary to include more than 50 acres or that designates urban reserve areas under ORS 195.145 shall submit the amendment or designation to the Land Conservation and Development Commission in the manner provided for periodic review under ORS 197.628 to 197.650. [1999 c.622 §14; 2001 c.672 §10]and 197.628 Periodic review; policy; conditions that indicate need for periodic review.(1) It is the policy of the State of Oregon to require the periodic review of comprehensive plans and land use regulations in order to respond to changes in local, regional and state conditions to ensure that the plans and regulations remain in compliance with the statewide planning goals adopted pursuant to ORS 197.230, and to ensure that the plans and regulations make adequate provision for needed housing, employment, transportation and public facilities and services.Determining UGBs in Oregon is done based on input from city and county governments. Such special districts as public safety and utilities also participate because they provide important services. Local citizens and other interested people also provide input at public hearings, and by voting. After local governments determine the UGB, the state Department of Land Conservation and Development (DLCD) reviews it for consistency with Goal 14. One of the major tasks in initially creating the UGB layer was to create an effective process for identifying, determining and documenting data sources for the layer. This included examining numerous existing data sources prepared and compiled by local and state jurisdictional bodies. Maps of boundaries were forwarded to several stakeholders for review, data requests were made directly to the GIS coordinators, planners, or senior administrators. Overall, local contacts had a high response rate. The initial assumption was that the local files were more accurate than DCLDs so a map was made of each respective UGB on file in 2006 and sent to the corresponding jurisdiction and county. This conclusion was based on the local files being: 1) typically linked to such official and legal boundary as city limits, or cadastral data, 2) the locals are the originators of the data which was submitted to DLCD, and 3) local planning agencies and county assessors typically maintain these data in high-resolution digital GIS data files. Where local authorities provided data, we revised boundaries to reflect a combination of DLCD files and local data. Differences were noted, documented and corrected based on mutual agreement from both DLCD acknowledged files and local authorities. If the county/local planning authority did not provide any data, it is assumed that the boundary on file was correct and the legal definition of UGBs for their respective areas were the attached digital file, until the local jurisdiction re-submits data to DLCD for approval, or to provide justification that DCLD information is incomplete (i.e,. other DLCD approved amendments).
Purpose:
The theme was created to delineate UGBs and document amendments to these boundaries since their original designations. As of September 2008 DLCD has taken over maintaining the data so a process was established obtaining data on the UGB Coverage layer for the state. To obtain as much precise data as possible to digitize the boundary layer for accuracy statewide, every city/metro UGB was assessed and updated based on DLCD, county and city records. Under the Oregon Geographic Information Council, the Framework Implementation Team has delegated the development of an Administrative Boundaries Implementation Plan and an Administrative Boundary Data Content Standard. The Administrative Boundaries Framework is a collection of prioritized, spatially referenced digital representation of broadly defined feature sets for Oregon; of which one was identified as UGBs with a Very High priority and DLCD tasked as being the steward of the data. This feature set will be detailed in the Oregon Framework database posted on the website maintained by the Geospatial Enterprise Office and updated annually.
DLCD’s Urban Planner position stewards the UGB Framework in an ESRI geodatabase and shares it as a shapefile. All UGB expansions after 2008 were processed with digital data provided by the local jurisdiction, Council of Governments, or the County. Annual versions are available at the Oregon Geospatial Data Clearinghouse for download or as a Web service. The 2010 version is also available through Oregon Explorer as a download or as a Web map service combined with other administrative boundaries. The 2011 version has been submitted to the Geospatial Enterprise Office (GEO) in the Department of Administrative Services for publication as Framework. Since the data is now routinely updated, this process will serve as a long term planning tool.
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -124.761210
East_Bounding_Coordinate: -116.799106
North_Bounding_Coordinate: 46.260271
South_Bounding_Coordinate: 41.938313
Keywords:
Theme:
Theme_Keyword_Thesaurus: ISO 19115 Topic Categories
Theme_Keyword: boundaries
Theme_Keyword: planningCadastre
Theme:
Theme_Keyword_Thesaurus: None
Theme_Keyword: UGBs
Theme_Keyword: Urban Growth Boundary
Theme_Keyword: Boundary
Access_Constraints: None
Use_Constraints:
None. The Oregon Department of Land Conservation and Development makes no warranty as to the accuracy of these data. Questions regarding the legal ownership and boundaries of real property should be directed to individual counties. This product is for informational purposes and may not have been prepared for or be suitable for legal, engineering, or surveying purposes. Users of this information should review or consult the primary data and information sources to ascertain the usability of the information.
Data_Set_Credit:
This dataset was originally created in 2004 at the Oregon Department of Employment under a grant from the Oregon Geographic Information Council (OGIC). In 2006, DLCD partnered with the University of Oregon's Infographics Lab and ODOT for another comprehensive update to the data following as closely as possible the methodology followed in the 2004 project. In 2008 DLCD took stewardship of the data and began a refined methodology necessary to bring the UGB data in line with other statewide framework elements through the OGIC data standards process. UGBs were optimized with reliance on cadastral tax lot data acquired through the Oregon Department of Revenue ORMAP project. Every jurisdiction's entire UGB was reviewed against County records, City records and DLCD records. Discrepancies were verified against acknowledged plan amendments and/or City Ordinances.
Native_Data_Set_Environment:
Microsoft Windows 7 Version 6.1 (Build 7601) Service Pack 1; Esri ArcGIS 10.1.0.3035

Spatial_Data_Organization_Information:
Direct_Spatial_Reference_Method: Vector
Point_and_Vector_Object_Information:
SDTS_Terms_Description:
SDTS_Point_and_Vector_Object_Type: GT-polygon composed of chains
Point_and_Vector_Object_Count: 217

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Lambert Conformal Conic
Lambert_Conformal_Conic:
Standard_Parallel: 43.0
Standard_Parallel: 45.5
Longitude_of_Central_Meridian: -120.5
Latitude_of_Projection_Origin: 41.75
False_Easting: 1312335.958005249
False_Northing: 0.0
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.0000000266012656346959
Ordinate_Resolution: 0.0000000266012656346959
Planar_Distance_Units:
Geodetic_Model:
Horizontal_Datum_Name: D North American 1983
Ellipsoid_Name: GRS 1980
Semi-major_Axis: 6378137.0
Denominator_of_Flattening_Ratio: 298.257222101

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: UGB_2011_DAS
Entity_Type_Definition: Urban Growth Boundries around cities
Entity_Type_Definition_Source: State governmental units
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: Geographic area feature geometry.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Coordinates defining the features.
Attribute:
Attribute_Label: OBJECTID
Attribute_Definition: Feature ID generated Internally
Attribute_Definition_Source: Internallly generated
Attribute:
Attribute_Label: instName
Attribute_Definition: Name of the specific instance of the geographic area
Attribute_Definition_Source: Admin Boundaries Standards
Attribute:
Attribute_Label: Shape_Leng
Attribute:
Attribute_Label: Shape_Area
Attribute_Definition: Area of feature in internal units squared.
Attribute_Definition_Source: Esri
Attribute_Domain_Values:
Unrepresentable_Domain: Positive real numbers that are automatically generated.
Attribute:
Attribute_Label: unitID
Attribute_Definition:
Framework unique identifier (formed from concatenating unitOwner and instCode)
Attribute_Definition_Source: Admin Boundaries Standard
Attribute:
Attribute_Label: descriptn
Attribute_Definition: Description of the geographic area or a reference to it
Attribute_Definition_Source: Admin Boundaries Standard
Attribute:
Attribute_Label: instCode
Attribute_Definition:
Instance code for geographic area (generated by boundary authority)
Attribute_Definition_Source: Admin Boundary Standard
Attribute:
Attribute_Label: codeRef
Attribute_Definition: Coding system reference (e.g., ANSI, FIPS)
Attribute_Definition_Source: Admin Boundary Standard
Attribute:
Attribute_Label: effDate
Attribute_Definition: Effective date in the form YYYYMMDD, date of latest UGB update
Attribute_Definition_Source: Admin Boundary Standard
Attribute:
Attribute_Label: unitOwner
Attribute_Definition:
Organization to which the unit belongs (GNIS code preferred; FIPS code if GNIS code not established)
Attribute_Definition_Source: Admin Boundary Standard
Attribute:
Attribute_Label: cSteward
Attribute_Definition: Organization responsible for maintaining the geospatial feature
Attribute_Definition_Source: Admin Boundary Standard

Metadata_Reference_Information:
Metadata_Date: 20121008
Metadata_Future_Review_Date: 20130131
Metadata_Standard_Name: FGDC Content Standard for Digital Geospatial Metadata
Metadata_Standard_Version: FGDC-STD-001-1998
Metadata_Time_Convention: local time

Generated by mp version 2.9.12 on Mon Oct 08 15:17:24 2012