Taxlots

Metro Data Resource Center 1990 Taxlots County tax assessors tax lots with associated property data. Selected items from each county assessor's file are included and standardized for all three counties. The tax lot spatial features and data associated with the tax lot are compiled by Metro from existing records created and maintained by the local county assessment and taxation offices. For mapping, property analysis, and planning. Care should be taken in the use and interpretation of these data. Not all columns are fully populated by the assessor and the data are standardized for consistency across the data layer. Tax lots, right-of-way outlines and tax account numbers as represented on county tax assessor hard copy maps. Each tax lot is a polygon with an associated tax lot number which is the "hook" to the county tax assessor's tabular data base. Selected items from each County Assessor's file are included. The tax lot spatial features are maintained by each county and delivered to Metro quarterly. All data associated with the taxlot shape files are compiled by Metro from existing records created and maintained by county Assessment and Taxation offices. Care should be taken in the use and interpretation of these data. Not all columns are fully populated by the assessor. For example, the landuse and prop_code columns are useful for producing generalized land-use maps, but are not considered reliable for parcel specific applications. Field verification has not been done. 20121017 Ground condition Complete Quarterly -123.47121656 -121.65053671 45.82618832 44.85462409 None Taxlots tax lots parcels assessor cadastral None Portland Clackamas County Multnomah County Washington County Oregon None For product terms and conditions, please see http://www.oregonmetro.gov/index.cfm/go/by.web/id=505 Please review the State of oregon Cadastral Data Exchange Standard, v2 (pdf) and the Oregon Map Goals and contact the Surveyors office for Washington, Clackamas, or Multnomah Counties. Portland General Electric (PGE) purchased aerial orthophotography with 10 foot horizontal control and digitized street center lines, tax lots and street names. This layer was produced on a CAD system as a visual background to their electrical system. 1980 Metro converted the PGE line work to polygons and added tax account numbers. David Evans and Associates was contractor. Beaverton, Oregon City and Tigard planning areas were improved to +/- 5 feet accuracy. Oregon Dept. of Revenue and Multnomah County Assessor provided CAD drawings of the area east of 42nd Ave. which had been entered using coordinate geometry and existing control from the cities and county. This original RLIS dataset contained 553 sections. 1990 Metro converted 436 rural sections to polygon coverages and added tax account numbers. David Evans and Associates was contractor. Tax assessor hard copy maps were scanned and registered to PGE base maps. 1991 Washington Co. rural taxlot linework created by Washington Co. using assessor maps. 199301 Washington County began maintaining this layer within their boundaries. 199301 Metro converted the coverage from NAD27 to NAD83 and from single to double precision. 199401 Clackamas County began maintaining this layer within their boundaries. 1995 Multnomah Co. rural taxlot linework created by Metro using 1:24000 USGS quad for control. 199507 Oregon Dept. of Revenue and Multnomah County Assessor provided tax lot CAD drawings of the remaining areas of the city of Portland. This data was entered using coordinate geometry and existing control. The city of Portland converted the CAD drawings to ARC/INFO format and furnished the information to Metro. 199706 A major upgrade was completed in Multnomah County. The taxlots for Portland were re-mapped and updated. The horizontal positional accuracy was spatially corrected. Columns storing X and Y coordinates of each taxlot were added, mainly for use by programmers. 199710 Clackamas County is gradually improving the horizontal ground control of the map by registering the map to the 1996 Spencer B. Gross digital orthophotography. The photography has ground control of +/- 5 feet. 1998 In Multnomah County, the "TLID" field was changed to be the "state ID number" instead of the account number (R number). This made Multnomah County consistent with the other two counties. In cases where the state ID number was not available, the R number was supplied. Since the state ID number is wider in Multnomah County, the TLID field was changed to 15 characters wide instead of 12. The Multnomah County portion was projected to NAD83/91 projection (also known as HPGN). 199801 A field called "Rno" was added to the taxlots shapefile. Earlier the Multnomah County "R number" was used in the "Tlid" field. The "R number" is now in its own field for those users who still need it. 199804 In Washington County, the technique used to populate OWNER2, OWNER3 and OWNERADDR was improved. Previously the address could appear in OWNER2, OWNER3 or OWNERADDR (depending on the first available field). Now all the address information is in OWNERADDR. 199807 This layer was reprojected to the NAD83/91 projection (also known as HPGN) as part of a conversion of all RLIS map layers. 199807 Multnomah County Assessment and Taxation updated their computer system and are now using a new format for the tax lot identifier (TLID). Since the beginning of RLIS Lite, Metro has used the county's format for taxlot number, so we converted to the new 16-character number used by the county. EXAMPLE: (^ represents a space). 1S2E06AB^^^00100. If the quarter section or quarter-quarter section letters are not used, a space is used as a place holder. There are three additional spaces following the quarter-quarter section letter. The 5-digit tax lot number uses leading zeros as place holders if the number is less than 10000. Landuse data for Multnomah County was extracted from a new field, and may look slightly different than previous releases. 200001 The TLID format for Multnomah County was changed to be consistent with the format used by the Assessor. The 3 spaces between township, range, section and the taxlot id number was changed to 2 spaces and a hyphen. Y2K issues required that the SALEDATE field be changed from a numeric field formatted YYMM to a character field formatted YYYYMM. 200011 Projection information (.prj file), compatible with ArcGIS 8.1, was added to the layer. 20010715 Add XML metadata compatible with ArcCatalog 8.1 20011031 Incorporated Clackamas County COGO-ed taxlot data for Lake Oswego and West Linn. 20011031 Clackamas County replaced data with COGO'ed areas in Lake Oswego and West Linn to Willamette River. 2002 Positional adjusts to taxlots per COGO data by County Surveyor in portions of Urban Washington County - (primarily Northern Hillsboro/Beaverton, SW Tigard and Sherwood). 2002 ongoing Clackamas County replaced data in Oregon City with COGO'ed sections. 20021101 Multnomah County began maintaining taxlots within their boundaries. In the past, Multnomah County's taxlots were maintained by the city of Portland and Metro (Metro maintained land outside the city). The taxlots will be more accurate since this layer will be maintained by the cartographers in the Assessment and Taxation office. This quarter, the county provided taxlots for the rural portion of the county. 200302 Tax Lots, multi-part features - The tax lot layer now supports multi-part features, a feature that is composed of more than one physical part but only references one set of attributes in the database. Previously two or more polygons could represent one tax lot, e.g. tax lots that cross roads. When you select a multi-part tax lot, both parts of the tax lot will be selected, but only one row in the attribute table. Tax Lots, multiple database records - Multiple county assessor database records for a single tax lot are now included as a separate point data layer. These records previously were not included in RLIS Lite. The primary record is included as a row in the taxlot database and all the records are included in a new point data layer called TL_MANY. TL_MANY includes all attributes that are on the taxlot data layer and an additional attribute called TLID_LONG. TLID_LONG, also known as the state_id or map tax lot number, uniquely identifies each multiple record. 200304 Over the past eighteen months, Multnomah County gradually took over maintenance of taxlots for Multnomah County. Metro now receives all taxlot shapes and Assessment and Taxation data directly from the county. 200407 Multnomah County discontinued using supplemental map sheets for condos and dropped the supplemental map number from the TLID (e.g. 1N1E33AD26-40001 is now shown as 1N1E33AD -40001). The county no longer maps condo footprints, but provides representational GIS polygons. Condos which were originally drawn as building footprints will not change unless they are updated. 20060331 Counties began providing source data to Metro as shapefile or geodatabase (rather than coverage). Metro began using ArcGIS Python scripts to merge shapes and calculate attributes. County-supplied shapes were used without generalizing vertices, resulting in larger file size. 20070331 Added OWNERSTATE and SITEZIP fields and added ArcGIS attribute indexes. Damascus is in processes of being COGOed. Gaps and overlaps may appear during this process. 20070331 To improve address data, the following fields were standardized using AccuMail software: OWNERADDR, OWNERCITY, OWNERZIP, SITEADDR, SITECITY, SITEZIP. More ZIP4 and fewer "null" entries appear in the OWNERZIP and SITEZIP fields. Also, a JURIS_CITY field was added to show the city that has jurisdiction over each tax lot. SITECITY is the post office mailing city of the site, which does not necessarily match the city boundaries. 20091115 OWNERADDR is no longer standardized by third party address software and is the original value produced by county assessors. STATECLASS was added and represents the State of Oregon land use class code. The lookup table stateclass.dbf contians the description of the codes provided by the local assessors offices. GIS_ACRES was added and is the area in acres calculated from the feature polygon using GIS software. 20100726 Fields that are indexed for RLISlite are OWNERSORT, OWNER1, TLIS, and SITEADDR 20100805 OWNADDR and SITEADDR are no longer standardized using third party address software. They contain the same values as in local assessors databases. Methods used to create TLID and multipart taxlots in Clackamas County have been modified to ensure that the item only contains 12 characters. As a result more records have full attributes. 20101015 Vector NA Simple FALSE 0 TRUE FALSE International feet North American Datum of 1983/1991 (HPGN) Taxlots.dbf Tax lot attributes provided by the three county assessors. Feature Class 0 OBJECTID OBJECTID OID 4 10 0 Internal feature number. ESRI Sequential unique whole numbers that are automatically generated. Shape Column containing the shape geometry Coordinates defining the features. Shape Geometry 4 0 0 ESRI TLID Tax lot account number, also known as state_id or map tax lot number. Text 16 TLID 0 0 Shape.STArea() Shape.STArea() Double 0 0 0 Shape.STLength() Shape.STLength() Double 0 0 0 Metro Data Resource Center

600 NE Grand Ave.

Portland OR 97232 503 797-1742 503 797-1909 drc@oregonmetro.gov The information in this file was derived from digital databases on Metro's GIS. Care was taken in the creation of this file. Metro cannot accept any responsibility for errors, omissions, or positional accuracy. There are no warranties, expressed or implied. Shapefile or ESRI geodatabase format. Hourly fee will be charged for conversion Approx. 350 MB (199709) CD-ROM or DVD ISO9660 (DOS, Unix, or Macintosh) http://www.oregonmetro.gov/rlisdiscovery Most RLIS layers are available on the RLIS Discovery site. Email drc@oregonmetro.gov or call 503 797-1742 for further instructions. RLIS subscription required 20121017 Metro Data Resource Center Steve Erickson mailing and physical address

600 NE Grand Ave.

Portland OR 97232 503 797-1595 503 797-1909 steve.erickson@oregonmetro.gov FGDC Content Standards for Digital Geospatial Metadata 19940608 Version 6.2 (Build 9200) ; Esri ArcGIS 10.8.1.14362 URA_TIF_Taxlots 002 URA_TIF_Taxlots 002 Projected GCS_North_American_1983_HARN NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.8'><WKT>PROJCS["NAD_1983_HARN_StatePlane_Oregon_North_FIPS_3601_Feet_Intl",GEOGCS["GCS_North_American_1983_HARN",DATUM["D_North_American_1983_HARN",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",8202099.737532808],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-120.5],PARAMETER["Standard_Parallel_1",44.33333333333334],PARAMETER["Standard_Parallel_2",46.0],PARAMETER["Latitude_Of_Origin",43.66666666666666],UNIT["Foot",0.3048],AUTHORITY["EPSG",2913]]</WKT><XOrigin>-111333600</XOrigin><YOrigin>-98152500</YOrigin><XYScale>3048</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808398950131233</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2913</WKID><LatestWKID>2913</LatestWKID></ProjectedCoordinateSystem> Linear Unit: Foot (0.304800) 20210513 21502600 20210513 21502600 20240109 15350200 1.0 FGDC CSDGM Metadata FALSE Feature Class dataset EPSG 6.13(9.0.0) 0 20210513