Taxlots

1990-01-01 00:00:00.0 Taxlots 52065 EGH_PUBLIC_WGS STAND-ALONE taxlots_pdx Taxlots 50009 Tax lots, right-of-way outlines and tax account numbers as represented on county tax assessor hard copy maps. Each Taxlot carries as an attribute the county "Property ID" for that parcel which can be used to associate the taxlot with the information in the County Assessor's database for the county in which the parcels lies. Selected items from each County Assessor's file are included in the attribute table for each taxlot. The tax lot spatial features inside the City of Portland are maintained by PDOT on contract from the City of Portland Corporate GIS. These taxlot parcels are updated on a weekly basis. Those taxlots outside of the City are delivered by Metro on a quarterly basis. The Multnomah County assessor data is updated on a weekly basis and the data for the surrounding couties is updated when the Metro update is received. All data associated with the taxlot shape files are compiled by the City of Portland from existing records created and maintained by the Multnomah County Assessment and Taxation offices. Information outside of the City of Portland is compiled and delivered quarterly by Metro. 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. Complete 2021-07-12 15:57:00.0 -13746409.0654 -13542128.0058 5745197.8914 5603547.4915 Clackamas County, Multnomah County, and Washington County, Oregon Taxlots, Parcels None Portland, Multnomah County, Washington County, Clackamas County, Oregon None Available for Public Use These data are distributed under the terms of the City of Portland Data Distribution Policy. Care was taken in the creation of this data but it is provided "as is". The City of Portland cannot accept any responsibility for errors, omissions, or positional accuracy. Vector City of Portland and neighboring countie File Geodatabase Feature Class withheld STAND-ALONE New_Taxlots_pdx 2021-07-12 10:13:00.0 591551 50 Weekly Taxlots 50003 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-01-01 00:00:00.0 51788 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. 1989-01-01 00:00:00.0 51786 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-01-01 00:00:00.0 51794 Washington Co. rural taxlot linework created by Washington Co. using assessor maps. 1993-01-01 00:00:00.0 51787 Washington County began maintaining this layer within their boundaries. 1993-01-01 00:00:00.0 51792 Metro converted the coverage from NAD27 to NAD83 and from single to double precision. 1994-01-01 00:00:00.0 51789 Clackamas County began maintaining this layer within their boundaries. 1995-01-01 00:00:00.0 51793 Multnomah Co. rural taxlot linework created by Metro using 1:24000 USGS quad for control. 1995-07-01 00:00:00.0 51790 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. 1997-06-01 00:00:00.0 51784 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. 1997-10-01 00:00:00.0 51795 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). 1998-01-01 00:00:00.0 51796 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-01-01 00:00:00.0 51785 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. 1998-04-01 00:00:00.0 51797 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. 1998-07-01 00:00:00.0 51798 This layer was reprojected to the NAD83/91 projection (also known as HPGN) as part of a conversion of all RLIS map layers. 1998-07-01 00:00:00.0 51791 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. 2000-01-01 00:00:00.0 51799 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. 2000-11-01 00:00:00.0 51800 Projection information (.prj file), compatible with ArcGIS 8.1, was added to the layer. 2001-07-15 00:00:00.0 51801 Incorporated Clackamas County COGO-ed taxlot data for Lake Oswego and West Linn. 2001-10-31 00:00:00.0 51802 Add XML metadata compatible with ArcCatalog 8.1 2001-10-31 00:00:00.0 51803 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-01-01 00:00:00.0 51804 Clackamas County replaced data with COGO'ed areas in Lake Oswego and West Linn to Willamette River. 2002-01-01 00:00:00.0 51805 Clackamas County replaced data in Oregon City with COGO'ed sections. 2002-11-01 00:00:00.0 51806 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 & Taxation office. This quarter, the county provided taxlots for the rural portion of the county. 2003-02-01 00:00:00.0 51808 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. 2003-04-01 00:00:00.0 51807 Over the past eighteen months, Multnomah County gradually took over maintenance of taxlots. Metro now receives all taxlot shapes and A&T data directly from the county. 2004-07-01 00:00:00.0 51809 Simple FALSE 0 FALSE FALSE International feet North American Datum of 1983/1991 (HPGN) North American Datum of 1983/1991 (HPGN) taxlots_pdx 51990 95 1 Feature Class 0 FID FID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. Shape Shape Geometry 0 0 0 Feature geometry. Esri Coordinates defining the features. NAME NAME String 50 0 0 Bureau of Technology Services - Corporate GIS Bureau of Technology Services - Corporate GIS City of Portland - BTS/CGIS 503-823-4000 503-823-5194 Maps@portlandoregon.gov 30 Mailing and Physical Address

1120 SW Fifth Avenue, Suite 450

Portland OR 97204 503 823-5632 503 823-5194 Maps@portlandoregon.gov 50124 50026 The information in this file was derived from digital databases on the City of Portland GIS. Care was taken in the creation of this file. The City cannot accept any responsibility for errors, omissions, or positional accuracy. There are no warranties, expressed or implied. ArcGIS Distribution by City of Portland not allowed by contract Not requested for Open Data site withheld The agencies make their data available for use in online applications and desktop GIS Programs - Multnomah Couty - http://www3.multco.us/arcgispublic/rest/services; Clackamas County - http://www.clackamas.us/gis/dataportal.html; Metro - http://rlisdiscovery.oregonmetro.gov; City of Portland - http://CivicApps.org. None, for online data varies 2015-05-19 00:00:00.0 2021-07-12 17:53:00.0 Bureau of Technology Services - Corporate GIS BTS/CGIS Bureau of Technology Services - Corporate GIS City of Portland - BTS/CGIS Mailing and Physical Address

1120 SW Fifth Avenue, Suite 450

Portland OR 97204 503 823-5632 503 823-5194 Maps@portlandoregon.gov 503-823-4000 503-823-5194 Maps@portlandoregon.gov 50124 56 1 50099 29 1 52065.png image/png 54251 http://dev.portlandmaps.com/metadata/index.cfm?action=DisplayFile&FileID=159 159 1 20220808 17202800 1.0 FALSE merge1 002 0.000 Projected GCS_North_American_1983_HARN Linear Unit: Foot (0.304800) 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.3'><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>37675770.731007516</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808398950131233</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>2913</WKID><LatestWKID>2913</LatestWKID></ProjectedCoordinateSystem> 20210715 00420600 20210715 00420600 Version 6.2 (Build 9200) ; Esri ArcGIS 10.3.1.5004 merge1 Shapefile 0.000 dataset EPSG 8.6.2 0 20210715