|Feature Dataset Name||STAND-ALONE|
|Originator||City of Portland and neighboring countie|
|Bureau||Bureau of Technology Services - Corporate GIS|
|Abstract||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.|
|Purpose||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.|
|Last Dataset Update||09/15/2021 10:11|
|Last Source Update||09/13/2021 10:30|
|Extent||Clackamas County, Multnomah County, and Washington County, Oregon|
|Horizontal Position Accuracy||Varies depending on location. When the taxlot layer was started in 1988, the standard was +/- 10 feet in urban areas, except Beaverton and Tigard's planning areas which were +/- 5 feet accuracy. In 2003, Oregon Department of Revenue prepared the Cadastral Data Content Standard that specifies horizontal accuracy. The standard specifies the majority of taxlot lines in areas of urban density to be within 2 feet accuracy. In the remaining urban growth boundary, taxlot line work is to be within 5 feet. Taxlots on farmland are to be +/- 10 feet accuracy, and on resource land, +/- 40 feet accuracy. The City of Portland and three counties have brought much of this layer into compliance with the ODOR standard. As of June 30, 2003, the following locations meet the standard: Hillsboro, Lake Oswego, Molalla, all of Multnomah County, Oregon City, east Sherwood, southeast Tualatin, and West Linn.|
|Horizontal Position Accuracy Link|
|North Bounding Coordinate||783256.070209978|
|South Bounding Coordinate||446892.410761148|
|East Bounding Coordinate||7904865.35826772|
|West Bounding Coordinate||7435739.30971129|
|Theme Keyword(s)||Taxlots, Parcels|
|Theme Keyword Thesaurus||None|
|Place Keyword(s)||Portland, Multnomah County, Washington County, Clackamas County, Oregon|
|Place Keyword Thesaurus||None|
|Access Constraints||Available for Public Use|
|Use Constraints|| 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.
|Source Dataset Type||File Geodatabase|
|Distribution|| Grid: State plane coordinate system 1983(91) |
Units: International feet
Datum: North American Datum of 1983/1991 (HPGN)
Liability: Multnomah County information in this file was derived from digital databases in the Multnomah County GIS. Washington County information in this file was derived from digital databases in the Washington County GIS. Clackamas County information in this file was derived from digital databases in the Clackamas County GIS. The Taxlot information from the individual Counties was combined to create a Regional Dataset by Metro and the City of Portland GIS. Care was taken in the creation of this file. None of the Counties or data manipulators accept any responsibility for errors, omissions, or positional accuracy. There are no warranties, expressed or implied.
Format: Distribution by City of Portland not allowed by contract
Offline Media: NONE
Offline Format: NONE
Online Resource: Multnomah County - https://multco.us/gis, Washington County -http://www.co.washington.or.us/AssessmentTaxation/GISCartography/, Clackamas County -http://www.clackamas.us/gis/, Metro -http://rlisdiscovery.oregonmetro.gov, City of Portland -http://CivicApps.org.
Online Instructions: 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.
Transfer Size: varies
SPCS Zone Identifier: 5076
| File(s) |
|01/01/1980||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.|
|01/01/1989||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.|
|01/01/1991||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.|
|01/01/1993||Washington Co. rural taxlot linework created by Washington Co. using assessor maps.|
|01/01/1993||Washington County began maintaining this layer within their boundaries.|
|01/01/1994||Metro converted the coverage from NAD27 to NAD83 and from single to double precision.|
|01/01/1995||Clackamas County began maintaining this layer within their boundaries.|
|07/01/1995||Multnomah Co. rural taxlot linework created by Metro using 1:24000 USGS quad for control.|
|06/01/1997||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.|
|10/01/1997|| 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.
|01/01/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).
|01/01/1998||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.|
|04/01/1998||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.|
|07/01/1998||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.|
|07/01/1998||This layer was reprojected to the NAD83/91 projection (also known as HPGN) as part of a conversion of all RLIS map layers.|
|01/01/2000|| 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.
|11/01/2000|| 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.
|07/15/2001||Projection information (.prj file), compatible with ArcGIS 8.1, was added to the layer.|
|10/31/2001||Incorporated Clackamas County COGO-ed taxlot data for Lake Oswego and West Linn.|
|10/31/2001||Add XML metadata compatible with ArcCatalog 8.1|
|01/01/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).|
|01/01/2002||Clackamas County replaced data with COGO'ed areas in Lake Oswego and West Linn to Willamette River.|
|11/01/2002||Clackamas County replaced data in Oregon City with COGO'ed sections.|
|02/01/2003||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.|
|04/01/2003|| 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.
|07/01/2004||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.|
|BES_REFERENCE||Do not use for cartographic web maps. These layers are intended to be used exclusively for editing applications.||Dynamic||Taxlots|
|Basemap_Color||Color basemap for the City of Portland, Oregon||Cached||Taxlots|
|Basemap_Color_Complete||Color basemap for the City of Portland, Oregon||Cached||Taxlots|
|Basemap_Color_Complete_Aerial||Color basemap for the City of Portland, Oregon||Cached||Taxlots|
|Basemap_Gray_Complete||Gray basemap for the City of Portland, Oregon||Cached||Taxlots|
|Fire_Integration_Layers||Reference layer that will be consumed by an application for Portland Fire and Rescue||Dynamic||Taxlot|
|Taxlots||Portland Metro Area Taxlots||Dynamic||Regional Taxlots|
|Taxlots||Portland Metro Area Taxlots||Dynamic||Regional Taxlots (IDs Only)|
|Column Sort||Column Name||Column Alias||Column Type||Column Size||Domain Value(s)||Column Description||1||STATE_ID||STATE_ID||String||20||Tax parcel account number (assigned by County Assessor), modified to conform to City of Portland format.||1||RNO||RNO||String||35||Unique account or parcel number used by the County Assessor's Offices. In Multnomah County a 10 character number. Contains a Plat number originating from Multnomah County Assessor.||1||OWNER1||OWNER1||String||35||Owner's name line 1.||1||OWNER2||OWNER2||String||35||Owner's name line 2.||1||OWNER3||OWNER3||String||35||Owner's name line 3.||1||OWNERADDR||OWNERADDR||String||35||Owner's address (street and number).||1||OWNERCITY||OWNERCITY||String||28||Owner's city of residence.||1||OWNERSTATE||OWNERSTATE||String||2||Owner's state of residence.||1||OWNERZIP||OWNERZIP||String||10||Owner's zip code.||1||SITEADDR||SITEADDR||String||37||Site address (street and number).||1||SITECITY||SITECITY||String||30||Site city. Not populated in Washington County. Zip code is occassionally included.||1||SITE_STATE||SITE_STATE||String||6||Site state (all Oregon)||1||SITEZIP||SITEZIP||String||10||Site zip code.||1||LEGAL_DESC||LEGAL_DESC||String||250||The legal description of the tax parcel boundary.||1||TAXCODE||TAXCODE||String||7||County Tax Code (Levy Code in Multnomah County).||1||PROP_CODE||PROP_CODE||String||4||Oregon Department of Revenue property classification land use code.||1||PRPCD_DESC||PRPCD_DESC||String||50||Textual interpretation of the Property Code.||1||LANDUSE||LANDUSE||String||4|| |
|Land Use categorization, derived from "Prop_Code".||1||YEARBUILT||YEARBUILT||String||10||Year structure was built.||1||BLDGSQFT||BLDGSQFT||Numeric||8||Square footage of residential living area.||1||BEDROOMS||BEDROOMS||Numeric||8||Number of bedrooms in the dwelling (currently not populated).||1||FLOORS||FLOORS||Numeric||8||Number of floors in the dwelling (currently not populated).||1||UNITS||UNITS||Numeric||8||Number of units in a multi-family residential dwelling (currently not populated).||1||MKTVALYR1||MKTVALYR1||String||4||The tax year for the valuations in the LandVal1, BldgVal1, and TotalVal1 fields.||1||LANDVAL1||LANDVAL1||Numeric||8||The real market land value of the tax parcel for the tax year listed in the MKTValYr1 field.||1||BLDGVAL1||BLDGVAL1||Numeric||8||The real market value of all structures on the tax parcel for the tax year listed in the MKTValYr1 field.||1||TOTALVAL1||TOTALVAL1||Numeric||8||The total real market value of the tax parcel (LandVal1 + BldgVal1) for the tax year listed in the MKTValYr1 field.||1||MKTVALYR2||MKTVALYR2||String||4||The tax year for the valuations in the LandVal2, BldgVal2, and TotalVal2 fields.||1||LANDVAL2||LANDVAL2||Numeric||8||The real market land value of the tax parcel for the tax year listed in the MKTValYr2 field.||1||BLDGVAL2||BLDGVAL2||Numeric||8||The real market value of all structures on the tax parcel for the tax year listed in the MKTValYr2 field.||1||TOTALVAL2||TOTALVAL2||Numeric||8||The total real market value of the tax parcel (LandVal2 + BldgVal2) for the tax year listed in the MKTValYr2 field.||1||MKTVALYR3||MKTVALYR3||String||11||The tax year for the valuations in the LandVal3, BldgVal3, and TotalVal3 fields.||1||LANDVAL3||LANDVAL3||Numeric||8||The real market land value of the tax parcel for the tax year listed in the MKTValYr3 field.||1||BLDGVAL3||BLDGVAL3||Numeric||8||The real market value of all structures on the tax parcel for the tax year listed in the MKTValYr3 field.||1||TOTALVAL3||TOTALVAL3||Numeric||8||The total real market value of the tax parcel (LandVal3 + BldgVal3) for the tax year listed in the MKTValYr3 field.||1||SALEDATE||SALEDATE||String||11||Date of the most recent sale of the property (recording).||1||SALEPRICE||SALEPRICE||Numeric||8||Price paid for the most recent sale of the property.||1||ACC_STATUS||ACC_STATUS||String||1|| |
|Current status of the tax account.||1||A_T_SQFT||A_T_SQFT||Numeric||8||Square footage of the tax lot as shown in the County Assessor's database.||1||A_T_ACRES||A_T_ACRES||Numeric||8||Acreage of the tax lot as shown in the County Assessor's database.||1||FRONTAGE||FRONTAGE||Numeric||8||A calculation of the width of the tax parcel where it abuts the public right-of-way.||1||COUNTY||COUNTY||String||2|| |
|County abbreviation.||1||SOURCE||SOURCE||String||10||The jurisdiction responsible for maintaining and updating the information for the tax parcel.||1||PROPERTYID||PROPERTYID||String||7||Multnomah County Assessor unique tax account number, which appears on property tax forms.||1||TLID||TLID||String||25||Field added by Oregon Metro to match the Multnomah County Assessor’s MAPTAXLOT field. This is a regional version of the STATE_ID field with standardized formats across multiple counties.|