Keywords
Theme:
Boundaries, Urban growth boundaries, Zoning
Place:
Oregon
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).
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.
Supplementary Information
Technical and Operation Context
The data environment is a vector model, comprised of area (polygons) and boundaries (lines) and spatial and maintenance relationships between areas. The exchange medium for administrative boundary data files is the ESRI shapefile, which is a public domain data structure relating feature geometry and feature attributes.
_________________
Status of the data
Complete
Data update frequency:
Annually
Time period for which the data is relevant
Date and time:
2009
Description:
publication date
Publication Information
Who created the data: Oregon Department of Land Conservation and Development (DLCD), Oregon Department of Transportation (ODOT), Oregon Department of Administrative Services - Geospatial Enterprise Office (DAS-GEO), Metro,
Date and time:
2009
_________________
Data storage and access information
File name: UGB_Coverage
Type of data: vector digital data
Data processing environment: Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ESRI ArcCatalog 9.3.0.1770
Accessing the data
Data format: ESRI Shapefile
Data transfer size: 0.546 MB
How to decompress the file: The files were subsequently compressed using Info-Zip's free version of Zip. This archiving method is compatable with the familiar PKZip. You can download compiled Unzip binaries for many systems from the uunet archive.
Network location:
http://navigator.state.or.us/sdl/data/shapefile/k24/UGB_2009.zip
Access instructions: Access via HTTP with web browser
Constraints on accessing and using the data
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.
Details about this document
Contents last updated: 20091201
at time 11051200
Who completed this document
Angela Lazarean
Department of Land Conservation and Development
mailing and physical address:
635 NE Capitol St, Suite 150
Salem, OR 97301
(503) 373-0050 X.286 (voice)
angela.lazarean@state.or.us
Hours of service:
M-TH 7:30 AM - 5:30 PM
Standards used to create this document
Horizontal coordinate system
Projected coordinate system name: NAD_1983_Oregon_Statewide_Lambert_Feet_Intl
Geographic coordinate system name: GCS_North_American_1983
Details
Map Projection Name: Lambert Conformal Conic
Standard Parallel: 43.000000
Standard Parallel: 45.500000
Longitude of Central Meridian: -120.500000
Latitude of Projection Origin: 41.750000
False Easting: 1312335.958005
False Northing: 0.000000
Planar Coordinate Information
Planar Distance Units: international feet
Coordinate Encoding Method: coordinate pair
Coordinate Representation
Abscissa Resolution: 0.000328
Ordinate Resolution: 0.000328
Geodetic Model
Horizontal Datum Name: North American Datum of 1983
Ellipsoid Name: Geodetic Reference System 80
Semi-major Axis: 6378137.000000
Denominator of Flattening Ratio: 298.257222
Altitude System Definition
Resolution: 0.000100
Encoding Method: Explicit elevation coordinate included with horizontal coordinates
_________________
Bounding coordinates
Horizontal
In decimal degrees
West:
-124.761213
East:
-116.799106
North:
46.260271
South:
41.938313
In projected or local coordinates
Left: 233080.577756
Right: 2249469.998360
Top: 1644229.740814
Bottom: 94736.609580
_________________
Lineage
FGDC lineage
Process step 1
Process description: DLCD Plan Amendments and Periodic Review files were used to modify the historically compiled UGB coverage. Theme was originally created by OR Dept of Transportation (ODOT) and other cooperators. ODOT asked cities and counties to send them maps of the delineated UGBs, which, in turn were digitized and traced onto a 1:24,000 base map.. 2004 update performed by OR Employment Department in cooperation with ODOT and OR Geospatial Data Clearinghouse (OGDC). 2007 updates were developed under contract with ODOT in partnership with Dept of Land Conservation and Univeristy of Oregon InfoGraphics department.
Process step 2
Process description: In 2008, DLCD took stewardship over UGB coverage and the following process was established: plan amendment files were reviewed thoroughly and those that were missing from jurisdiction's UGBs were digitized into the database. DLCD does not require a map of amendments to be submitted and often only qualitative descriptions existed for an amendment. The revised database was redesigned to:
include all additions and removals,
identify data source used for creating lines,
specify accuracy, precision and reliability of data source(s),
include links to attributes in DLCD amendment and UGB databases,
build into new database model, i.e., shape files and a geo-database
Source used: S:\UGB 2008 Update\Metadata\2004 metadata.xml
Process date: 20090929
at time 07195900
Process step 3
Process description: 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. It is critical to effectively include all potential stakeholders into the framework process since it will improve the quality and resolution of the spatial data, increase the potential attributes associated with the GIS data, and provide potential methods for establishing longterm maintenance of the data. Emails were sent to all primary local jurisdictional authorities with maps of boundaries for review.
Data requests were made directly to the GIS Coordinators or Senior Planning staff. Overall, local contacts had a high response rate. Data stewards contacted during this project are available at DLCD.
Source used: C:\DOCUME~1\danar\LOCALS~1\Temp\xml11.tmp
Process date: 20090929
at time 08330700
Process step 4
Process description: UGB lines were digitized using ArcView and ArcMap. Data sources were used to define line, reliability of the data source in feet, and the cadastral data used for verification were all entered into a GIS database. Amendments and original UGBs were identified as points with the related jurisdiction name and DCLD amendment number. Topology errors, dangle nodes and label errors were determined in ArcCatalog/ArcMap and were re-digitized to ensure all line networks were complete and each amendment and original UGB existed. Line work, in combination with point coverage, was used to create a comprehensive polygon coverage for all UGBs and their amendments.
Source used: S:\UGB 2008 Update\Metadata\2009 metadata.xml
Process date: 20091005
at time 07483000
Process step 5
Process description: Metadata imported.
Source used: S:\UGB 2008 Update\Metadata\2009 metadata.xml
Process date: 20091005
at time 10383200
Process step 6
Process description: Metadata imported.
Source used: S:\UGB 2008 Update\Metadata\2009 metadata.xml
Process date: 20091020
at time 08362100
Process step 7
Process description: Metadata imported.
Source used: S:\UGB 2008 Update\Metadata\2009 metadata.xml
Process date: 20091118
at time 08344300
Process step 8
Process description: Dataset copied.
Source used: \\dlcdsfil01\share\UGB 2008 Update\UGB Geodatabase\UGB.gdb
Process date: 20091118
at time 08370500
_________________
Spatial data quality
Horizontal positional accuracy
Horizontal_Positional_Accuracy_Report Unknown
Vertical positional accuracy
Vertical_Positional_Accuracy_Report N/A
_________________
Spatial data description
Vector data information
ESRI description
UGB_Coverage
ESRI feature type: Simple
Geometry type: Polygon
Topology: FALSE
Feature count: 216
Spatial Index: TRUE
Linear referencing: FALSE
SDTS description
Feature class: SDTS feature type, feature count
UGB_Coverage:
G-polygon, 216
Feature class:
String, 400
Feature class:
GT-polygon composed of chains, 262