Oregon City Limits and City Annexations - 2003

Metadata also available as

Metadata:


Identification_Information:
Citation:
Citation_Information:
Originator:
Oregon Department of Transportaton, Geographic Information Services Unit.
Publication_Date: 2003
Title: Oregon City Limits and City Annexations - 2003
Geospatial_Data_Presentation_Form: vector digital data
Other_Citation_Details: Scale 1:24000
Online_Linkage: <http://www.oregon.gov/DAS/IRMD/GEO/sdlibrary.shtml>
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.
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: August 8, 2003
Currentness_Reference: August 8, 2003
Status:
Progress: Complete
Maintenance_and_Update_Frequency: As needed
Spatial_Domain:
Bounding_Coordinates:
West_Bounding_Coordinate: -124.756312
East_Bounding_Coordinate: -116.799127
North_Bounding_Coordinate: 46.259944
South_Bounding_Coordinate: 41.940806
Keywords:
Theme:
Theme_Keyword_Thesaurus: municipality
Theme_Keyword: city limits
Theme_Keyword: limit
Theme_Keyword: limits
Theme_Keyword: city
Theme_Keyword: 1:24,0000
Theme_Keyword: boundary
Theme_Keyword: incorporated
Theme_Keyword: municipaility
Place:
Place_Keyword: Oregon
Place_Keyword: OR
Place_Keyword: US
Place_Keyword: United States
Temporal:
Temporal_Keyword: 2003
Access_Constraints: None.
Use_Constraints: None.
Point_of_Contact:
Contact_Information:
Contact_Person_Primary:
Contact_Organization:
Geographic Information Services Unit, Oregon Department of Transportation (ODOT).
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.3154
Contact_Facsimile_Telephone: 503.986.4249
Contact_Electronic_Mail_Address: odot.maps@odot.state.or.us
Hours_of_Service: 8:00AM - 5:00PM M-F
Browse_Graphic:
Browse_Graphic_File_Name: <http://navigator.state.or.us/sdl/data/image/k100/citylimits.html>
Browse_Graphic_File_Description: Oregon City Limits 2003
Browse_Graphic_File_Type: JPEG
Native_Data_Set_Environment: Windows NT 4.0, GeoMedia Professional v5.0
Cross_Reference:
Citation_Information:
Originator: Oregon Department of Transportaation (ODOT)
Publication_Date: Unknown
Publication_Time: Unknown
Title: Oregon City Limits
Geospatial_Data_Presentation_Form: vector digital data
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:
Several attribute values are derived from software needs. These attributes are defined in the Entity and Attribute section and are identified by "Maintained by MGE software" or "Calculated by MGE software" descriptions. These attributes may be dependent on digitizing accuracy, precision input or the source data accuracy. There has been no attempt to verify items like measured areas within polygons to determine attribute accuracy.
Quantitative_Attribute_Accuracy_Assessment:
Attribute_Accuracy_Value: Source 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. As a matter of record, maps are not legal documents. Text (survey) descriptions of a property is the legal definition of a property.

Logical_Consistency_Report:
All polygons close, with no overlaps or gaps and form clean bounding polygons 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.
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: 1:100,000 United States Geologic Survey Digital Line Graphs
Source_Scale_Denominator: 100000
Type_of_Source_Media: digital tape media
Source_Citation_Abbreviation: city_lim.dgn
Source_Information:
Source_Citation:
Citation_Information:
Originator: Dept. of Revenue
Publication_Date: Unknown
Publication_Time: Unknown
Title: Dept. of Revenue Annexaton Approval Packet
Geospatial_Data_Presentation_Form: map
Other_Citation_Details:
map and legal description need to be submitted, and both must match for approval
Source_Citation_Abbreviation: DOR Annexation Packet
Process_Step:
Process_Description:
Calculations for Area (Ac) was done in Geomedia. Calculations are rounded to nearest 1/100th. Contact individual cities or county offices in which cities reside for more accurate dimensions. Annexations are entered into our city limit base layer. A hard copy of the annexation is filed in house and a scanned .tif image is placed on our ftp site. The ftp address is <ftp://ftp.odot.state.or.us/tdb/trandata/maps/cl_tiffs>.

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.958005
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: citylim_2003
Entity_Type_Definition:
An unbroken area within the statutory boundary of an incorporated city, which was annexed at a known time, or which represents the extent of the city before annexations were recorded in this database. It is represented as spatial data (polygon and label point). An area may be annexed into a city from unincorporated area or from another incorporated city. Note: this is a logical entity that represents the spatial City Annexation Polygon information contained within Geomedia Pro v 5.0.
Entity_Type_Definition_Source:
Geographic Information Services Unit, Oregon Department of Transportation, Oregon Transportation Management
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: CITY_NAME
Attribute_Definition: City Name
Attribute_Definition_Source: Oregon Department of Transportation
Attribute:
Attribute_Label: FIPS_CODE
Attribute_Definition: FIPS Code
Attribute_Definition_Source: Department of Transportation
Attribute:
Attribute_Label: ACRES
Attribute_Definition: GeoMedia generated acres
Attribute_Definition_Source:
Geographic Information Services Unit, Oregon Department of Transportation
Overview_Description:
Entity_and_Attribute_Overview: City Limits contains acres, fips, name, seat, shape
Entity_and_Attribute_Detail_Citation:
\\Scdata\otms\System Documentation (100-920)\_1Program-Level Documentation\02 Conceptual Data Model\3 Approved\180S GIS01 Conceptual Data Model v01.doc

Distribution_Information:
Distributor:
Contact_Information:
Contact_Person_Primary:
Contact_Person: Data Administrator
Contact_Organization: Oregon Geospatial Enterprise Office (GEO)
Contact_Address:
Address_Type: mailing and physical address
Address: 955 Center St. NE Room 470
City: Salem
State_or_Province: Oregon
Postal_Code: 97301
Country: USA
Contact_Voice_Telephone: (503) 378-2166
Contact_Electronic_Mail_Address: gis at gis.state.or.us
Hours_of_Service: Monday through Friday, 8:00 AM to 5:00 PM.
Resource_Description: Downloadable Data
Distribution_Liability:
The Oregon Geospatial Data Clearinghouse (OGDC), the State of Oregon or any of the data providers cannot accept any responsibility for errors, omissions, or positional accuracy in the digital data or underlying records. There are no warranties, expressed or implied, including the warranty of merchantability or fitness for a particular purpose, accompanying any of these products.
Standard_Order_Process:
Digital_Form:
Digital_Transfer_Information:
Format_Name: ESRI Shapefile
Format_Specification: ESRI Shapefile Format
File_Decompression_Technique:
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.
Transfer_Size: 1.155
Digital_Transfer_Option:
Online_Option:
Computer_Contact_Information:
Network_Address:
Network_Resource_Name: <http://navigator.state.or.us/sdl/data/shapefile/k24/citylim_2003.zip>
Access_Instructions: Open via anonymous ftp
Offline_Option:
Offline_Media: CD-ROM

Metadata_Reference_Information:
Metadata_Date: 20051021
Metadata_Review_Date: September 30, 2002
Metadata_Contact:
Contact_Information:
Contact_Organization_Primary:
Contact_Organization: Oregon Geospatial Enterprise Office (GEO)
Contact_Person: Data Administrator
Contact_Position: GIS 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) 378-2166
Contact_Electronic_Mail_Address: gis at gis.state.or.us
Hours_of_Service: Monday thru Firday 8:00 AM - 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 10:31:37 2005