Oregon City Limits and City Annexations - 1999

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
Geographic Information Services Unit, Oregon Department of Transportation
Publication_Date: Unpublished Material
Publication_Time: Unknown
Title: Oregon City Limits and City Annexations - 1999
Geospatial_Data_Presentation_Form: vector digital data
Online_Linkage: <http://navigator.state.or.us/sdl/data/shapefile/k24/citylimits.zip>
Description:
Abstract:
A continuous area within the statutory boundary of an incorporated city, which is the smallest subdivision of an annexed area. It is represented as spatial data (polygon with label point).
Purpose:
The use of city limits information was identified as a need for general planning purposes within ODOT. It was determined that this would be a frequently used data set that needed to be both spatially referenced and attributed in a GIS base layer. The decision was made to create a statewide coverage of the boundary outlining the city limits for each of the 240 incorporated cities. An incorporated city may have multiple areas that are not contiguous. Each such area is represented separately with its own polygon. The area of the city limits will be calculated from the polygons created. The city limits base layer will be updated and maintained to include approximately 1000 new annexations per year
Supplemental_Information:
An area may be annexed into a city from an unincorporated area or from another incorporated city. Each annexation may have multiple parts, which are not necessarily contiguous. When an area is annexed from another city, this may create one or more fragments, which are subdivisions of one or more existing parts.
Time_Period_of_Content:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: unknown
Currentness_Reference: publication date
Status:
Progress: Complete
Maintenance_and_Update_Frequency: Quarterly
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -124.756250
East_Bounding_Coordinate: -116.799127
North_Bounding_Coordinate: 46.259944
South_Bounding_Coordinate: 41.940807
Keywords:
Theme:
Theme_Keyword_Thesaurus: Municipality
Theme_Keyword: City Liimits
Place:
Place_Keyword: Oregon
Place_Keyword: OR
Place_Keyword: Pacific Northwest
Temporal:
Temporal_Keyword: 1999
Access_Constraints: None.
Use_Constraints: None.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chad W. Brady
Contact_Organization:
Geographic Information Services Unit, Oregon Department of Transportation
Contact_Position: Spatial Data Administrator
Contact_Address:
Address_Type: mailing and physical address
Address: 555 13th St. NE, Suite 2
City: Salem
State_or_Province: Oregon
Postal_Code: 97301
Contact_Voice_Telephone: (503) 986-3164
Contact_Facsimile_Telephone: (503) 986-4249
Contact_Electronic_Mail_Address: chad.w.brady@odot.state.or.us
Hours_of_Service: Monday thru Friday 8:00 AM - 5:00 PM
Browse_Graphic:
Browse_Graphic_File_Name: <http://navigator.state.or.us/sdl/data/image/k100/citylimits.html>
Browse_Graphic_File_Description: Oregon City Limits and City Annexations
Browse_Graphic_File_Type: JPEG
Data_Set_Credit:
Oregon Department of Transportaton, Geographic Information Services Unit
Security_Information:
Security_Classification: Unclassified
Native_Data_Set_Environment:
Bentley Microstation SE, Intergraph Modular GIS Environment (MGE) 7.0, Windows NT 4.0
Cross_Reference:
Citation_Information:
Originator:
Geographic Information Services Unit, Oregon Department of Transportation
Publication_Date: Unpublished Material
Publication_Time: Unknown
Title: Oregon City Limits and City Annexations
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details: Urban Growth Boundaries in Oregon
Online_Linkage: <http://www.oregon.gov/ODOT/TD/TDATA/gis/odotgis.shtml>

Data_Quality_Information:
Attribute_Accuracy:
Attribute_Accuracy_Report:
Attributes that have derived values have not been tested to determine the accuracy of said. Attributes with software assigned values are assumed to be accurate. Attributes with keyed in values are filtered by database design to accept only certain formats of information. This does not preclude errors, it does, however, minimize them. Additional, in-house, review is conducted to identify errors.
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: Digitizing Accuracy
Attribute_Accuracy_Explanation:
One of the main considerations we have when placing new line-work is the probable inclusion of the line-work into a GIS base layer. For this reason we need to take extra measures to assure that newly placed lines are snapped to end-points, and that every intersection is broken and no overlaps or open intersections exist. Duplicate line-work is also a problem. What do we do to resolve anomalous line-work? Perhaps we find an overlap or a gap exists between existing line-work and the new parcel, or maybe a given legal description shows that one leg of a parcel adjoins a highway right-of-way for which a readily available description does not exist. One method for resolving this is to obtain a copy of the county property assessment map from the DOR. If existing records don’t resolve the anomaly, an estimated resolution is employed. This method is not ideal, but experience and an informed idea of what the city intends, helps to minimize error (Educated guesswork).

If an obvious overlap occurs with a new annexation and the existing city limits, we assume (guess) that the overlapped area is intended to be included in the revised boundary. It doesn't matter that it overlaps, the intent of the city is to include it. If a sliver or gap between parcels becomes apparent to us, we call the city planning dept. and ask for a clarification. Many of these anomalies occur by mistake, and aren't supposed to exist. We ask for what the city intends. We have found that these types of problems occur more often in communities that have limited resources. The number of occurances varies from year to year, but a figure of 5% is probably close to the average.

For clarity, unless the boundary follows the centerline of a street or highway, an offset is employed to an estimated right of way. This offset averages 10 feet, and merely indicates that the line follows a right of way. Rights of way are seldom an even number of feet. Exceptions to the 10’ offset placement will occur when the placed line is between two converging or parallel highways or roads. and it seems reasonable to split the difference which may be less than or more than 10’. Another exception may occur when the line parallels a feature that has many vertices and it’s reasonable to use fewer to place the boundary.

As annexations are entered, we print out scale plots of newly annexed areas and transfer that information onto our counter maps. Printed records of the annexations are placed in Current City Map Corrections file drawers.

Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: Software Derived Data Accuracy
Attribute_Accuracy_Explanation:
Beginning in 1990, Oregon surveyors initiated the Partition Plat Law to allow for simplified legal descriptions. New land partitions of three or fewer parcels are now described by partition plat and parcel numbers, similar to the lot and block descriptions of subdivisions. This process makes parcel descriptions increasingly difficult to track and plot unless the original plat is available to verify the dimensions of that parcel, or copies of the county map showing bearings and distances can be used for verification. The DOR is responsible for reviewing and approving annexations for assessment purposes as per O.R.S. 308.225. Occasionally annexations do not contain a correct description or accompanying maps. DOR works with the annexing body to resolve the issues. Annexations are also recorded in the Secretary of State’s Office as per O.R.S.198.780.The Secretary of State’s Office catalogs but does not review the annexations for accuracy. Prior to a cooperative effort between the ODOT and the Oregon Department of Revenue, the information in the Secretary of State’s Office was used by ODOT to determine new city limits.

Unfortunately, not all cities have consistently complied with O.R.S.198.70. Traditionally, the only annexations available to ODOT are those that have been received by the Sec. Of State’s office. Currently, information from the DOR can be cross-referenced with information from the Secretary of State’s Office to solve discrepancies.

Our maps are a graphic representation of the sum of information available to us. Our maps are not an exact replica of the real world due to the amount of information collected, the number of places it was collected from, and due to the fact that no map (digital or hand drawn) paints a perfect picture.

Logical_Consistency_Report:
All linestrings intersect, wiith no overlaps or gaps and form clean bounding linework for the city limits and city annexations. All linework is feature tagged and all centroids are feature tagged and attributed. Every centroid is bounded by the feature tagged linestring. If a bounding linestring does not contain a centroid then the linestring belongs to a larger bounding linestring of an original city limits attributed centroid.
Completeness_Report:
This file is complete at the time of posting and is dependent upon receipt of current city annexations at time of posting.
Positional_Accuracy:
Horizontal_Positional_Accuracy:
Horizontal_Positional_Accuracy_Report: Horizontal accuracy is 1:24,000 or better.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: 6.096
Horizontal_Positional_Accuracy_Explanation: (+/-) Digitizing from county plat maps.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: 6.096
Horizontal_Positional_Accuracy_Explanation: (+/-) Precision imput from meets and bounds description.
Quantitative_Horizontal_Positional_Accuracy_Assessment:
Horizontal_Positional_Accuracy_Value: 12.192
Horizontal_Positional_Accuracy_Explanation: (+/-) When digitized from USGS quads.
Vertical_Positional_Accuracy:
Vertical_Positional_Accuracy_Report: No vertical positional accuracy has been determined
Lineage:
Source_Information:
Source_Citation:
Citation_Information:
Originator:
United States Geologic Survey Denver, Colorado 80225 or Reston, Virginia 22092
Publication_Date: Unknown
Publication_Time: Unknown
Title: :100,000 United States Geologic Survey Digital Line Graphs
Geospatial_Data_Presentation_Form: digital tape media

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: 240

Spatial_Reference_Information:
Horizontal_Coordinate_System_Definition:
Planar:
Map_Projection:
Map_Projection_Name: Lambert Conformal Conic
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.958000
False_Northing: 0.000000
Planar_Coordinate_Information:
Planar_Coordinate_Encoding_Method: coordinate pair
Coordinate_Representation:
Abscissa_Resolution: 0.004096
Ordinate_Resolution: 0.004096
Planar_Distance_Units: international feet
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

Entity_and_Attribute_Information:
Detailed_Description:
Entity_Type:
Entity_Type_Label: citylimits
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: ENTITY
Attribute:
Attribute_Label: COLOR
Attribute:
Attribute_Label: MSLINK_DMR
Attribute:
Attribute_Label: NAME
Attribute:
Attribute_Label: AREA
Attribute:
Attribute_Label: PERIMETER
Attribute:
Attribute_Label: ACRES
Attribute:
Attribute_Label: REGION

Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Chad W. Brady
Contact_Organization:
Geographic Information Services Unit, Oregon Department of Transportation
Contact_Position: Spatial Data Administrator
Contact_Address:
Address_Type: mailing and physical address
Address: 555 13th St. NE, Suite 2
City: Salem
State_or_Province: Oregon
Postal_Code: 97301
Country: USA
Contact_Voice_Telephone: (503) 986-3164
Contact_Facsimile_Telephone: (503) 986-4249
Contact_Electronic_Mail_Address: chad.w.brady@odot.state.or.us
Hours_of_Service: Monday thru Friday 8:00 AM - 5:00 PM
Contact_Instructions:
Call, email or write for spatial data sets. If unable to contact or have Arcview related questions contact Jan Shearer (503) 986-3163
Resource_Description: Downloadable Data
Distribution_Liability:
The Oregon Department of Transportation shall not be liable for any activity involving these data with regard to lost profits or savings or any other consequential damages; or the fitness for use of the data for a particular purpose; or the installation of the data, its use, or the results obtained.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Transfer_Size: 0.767
Available_Time_Period:
Time_Period_Information:
Single_Date/Time:
Calendar_Date: unknown

Metadata_Reference_Information:
Metadata_Date: 20051021
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization:
Geographic Information Services Unit, Oregon Department of Transportation
Contact_Person: Chad W. Brady
Contact_Position: Spatial Data Administrator
Contact_Address:
Address_Type: mailing and physical address
Address: 555 13th St. NE, Suite 2
City: Salem
State_or_Province: Oregon
Postal_Code: 97301
Country: USA
Contact_Voice_Telephone: (503) 986-3164
Contact_Facsimile_Telephone: (503) 986-4249
Contact_Electronic_Mail_Address: chad.w.brady@odot.state.or.us
Hours_of_Service: Monday thru Friday 8:00 AM thru 5:00 PM
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.8.6 on Fri Oct 21 08:16:37 2005