Buildings
Category	Building
Feature Dataset Name	STAND-ALONE
Item Name	buildings_3d_pdx
Database Type	SDE
Originator	City of Portland
Bureau	Bureau of Planning and Sustainability
Publication Date	01/01/2002
Abstract	Regional buildings with building height and roof elevation information. Many buildings are constructed of multiple "polygons" representing the different building heights. All polygons making up a single building have the same "building ID" [Bldg_ID], which can be used to dissolve the buildings into generalized building footprints.
Purpose	To develop and maintain an inventory of all buildings in the Portland metropolitan region. Used to store attribute information for buildings throughout the region. Also used for 3D modeling.
Supplemental Information	Portland Central City, Lloyd District, Central Eastside, and OHSU all mapped by the Bureau of Planning and Sustainability using photogrammetric data and aerial photos. Buildings constructed after 2007 are derived from building permit information and aerial photos. All other buildings are derived from 2004 to 2007 LiDAR data. All elevation and height data are in US Survey feet.
Last Dataset Update	05/13/2022 19:55
Last Source Update	05/12/2022 19:33
Maintenance/Update Frequency	As needed
Extent	Portland Metro area
Data Type	Vector
Shape Type	Polygon
Feature Count	249102
Horizontal Position Accuracy	Horizontal Accuracy: Original building polygons have been modified to more accurately register with taxlots where appropriate. Overall horizontal accuracy is unknown. Buildings derived from LiDAR should have a horizontal accuracy of +/- 2'. Vertical Accuracy: Elevations and heights derived from photogrammetric data are within +/- 2' in most cases. Heights derived from LUR information or 3D models should be precise. Heights derived from LiDAR data are generally within +/- 15cm (~6") for buildings not obscured by vegetation, +/- .7m (~2.5') where buildings are covered by vegetation. Heights derived from field laser-range finder measurements are usually within +/- 7'. Some building heights have been estimated using aerial photos or field visits. The accuracy of estimated elevations and heights are unknown. Surface elevations derived from LiDAR data are generally within +/- 15cm (~6") for relatively flat areas not obscured by vegetation, +/- .7m (~2.5') where in areas of steep slopes or surfaces covered by vegetation. Surface elevations derived from the 2001 DEM are within +/- 5' in most cases.
Horizontal Position Accuracy Link	Taxlots
Progress	Complete
North Bounding Coordinate	731057.974081367
South Bounding Coordinate	651014.319225728
East Bounding Coordinate	7696668.63582677
West Bounding Coordinate	7604320.33759843
Theme Keyword(s)	buildings, 3d buildings, building model
Theme Keyword Thesaurus	None
Place Keyword(s)	Portland, Multnomah County, Washington County, Clackamas County, Oregon, Metro
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
Output Geodatabase	EGH_Public
Distribution	Grid: State plane coordinate system 1983(91). Units: International feet Datum: North American Datum of 1983/1991 (HPGN) Liability: 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. Format: Shapefile or File Geodatabase Feature Class - Data will be provided via City of Portland FTP Site. Online Resource: http://portlandmaps.com/opendata Online Instructions: City of Portland Public/Open Data is distributed via the PortlandMaps Open Data Site - http://portlandmaps.com/opendata. Data not available on the PortlandMaps Open Data site can be requested by contacting the City of Portland CGIS Group - maps@portlandoregon.gov Transfer Size: varies SPCS Zone Identifier: 5076
Contact(s) Add
Neil Loehlein 503-823-7061 503-823-7800 Neil.Loehlein@portlandoregon.gov 1900 SW 4th Avenue, Suite #7100 Portland, OR 97201 City of Portland - BPS 503-823-7700 503-823-7800 BPS@portlandoregon.gov
File(s) Add Add File File Description Cancel Add File
Images	52412.png 58.59Kb X
Lineage Add
	Buildings in Portland's Central City were originally digitized from photogrammetric data derived from aerial photos flown from 1987 to 1994. Created for the Bureau of Environmental Services. Not registered directly to the Taxlot Base Maps. New Central City buildings since 1994 were manually digitized using land-use review (LUR) case information submitted as part of the building permit approval process, and, when available, CAD and 3D models provided by the project architects or developers. The 3D models provided by developers were retained with all of their original detail as Sketchup files. These Sketchup files were then used as reference to create the more generalized "massing" models in the 3D buildings GIS dataset. If no case information or 3D model was available, Central City buildings were digitized using 1996 to 2007 aerial photos and/or 2004 to 2007 LiDAR data as reference. All edits were performed in ArcGIS using a custom ArcMap interface allowing the editor to automatically populate surface and roof elevations/heights and attribute the other database fields. All editing was performed using the standard ArcMap editing tools. All buildings were created as unique, non-overlapping polygons in order to facilitate the conversion to other formats (such as ArcInfo coverages) for modeling and analysis purposes.
	Surface Elevations: Derived surface elevation for a point within each building polygon using LiDAR digital elevation models (derived from 2004 to 2007 LiDAR acquisition flights) or, where LiDAR data was not available, a 2001 DEM developed by the Bureau of Planning. Roof Elevation/Height: Roof elevations were derived from the LiDAR first-return points, photogrammetric elevation points, LUR case information, or from 3D models provided by the project architect or developer. If none of this information was available, roof elevations were estimated using laser-range finder measurements or aerial photos. Height was calculated by subtracting the roof elevation from the surface elevation.
	Buildings outside Portland's Central City were derived from 2004 to 2007 LiDAR data. The following steps were used to delineate building footprints from the LiDAR data: MicroStation was used to convert the Lower Columbia 2005 LiDAR point data from its raw asciiformat into LAS files. The projection was transformed from Washington State Plane South toOregon State Plane North. The data did not contain usable pulse return information, so the returnsfield for all points was set to 1/1 and the data was treated as single return. Rasters were created from 1/100th quad *.las files for ground-classified points for each LiDAR dataset, as well as first and last returns for the PSLC 2007 LiDAR and single returns for the Lower Columbia 2005 LiDAR. Rasters were imported into LiDAR Analyst and several building and tree models with differentparameters were run to delineate building footprints that would provide an alternative best-fit foreach structure. The initial polygon output was overlaid on a hillshaded DEM of the bare earth and buildings LiDARraster and manually edited as necessary. The types of manual edits included: Splitting of single polygons covering multiple distinct buildings. Adjustment of polygon edges to more accurately outline buildings or selection ofalternative building footprint model. Rotation of an entire footprint if it was tilted more than 30 degrees from the building?sactual orientation (smoothing and squaring routines within LiDAR Analyst sometimes causea building footprint to ?tilt? on its axis). Deletion of non-building polygons. e. Digitization of building footprints missed by LiDAR Analyst. f. Removal of ?holes? or extraneous structures (HVAC, antennae) within footprint polygons.(Courtyards were not removed.) Aerial photographs (2008) were laid beneath the building footprint polygons and used for visualverification of building shape. Unless the LiDAR data was completely insufficient for classifying abuilding (e.g., zero returns from a portion or all of a particular building), the footprints were notdelineated from the photographs. Polygon topology was checked for overlaps, duplicates, and other errors. Edits were applied asneeded. LiDAR Analyst was used to square up manual edits, and then apply elevation and geometryattributes from the LiDAR data. LIDAR Analyst *.las point cloud classification routines were used after all polygon edits had beencompleted. A customized script was run to compare the output ground model with the originalmodel delivered to PSLC by Watershed Sciences and remove any new ground-classified points, thusimproving the accuracy of building heights calculated in subsequent steps. Manual declutter inMicroStation removed erroneously classified objects such as trees, and power lines overhangingrooflines. Building and ground rasters were exported from the classified point cloud at 1.5? resolution (PSLCLiDAR) and 3.0? resolution (Lower Columbia LiDAR).
	Buildings constructed since the most recent LiDAR flight are digitized using building permit information as reference (when available). Updates are made as needed, and new permits are updated and reviewed monthly. Geometry is derived from building permit information (site plans) where the building does not already exist, or 6" aerial photos where the building does exist.
	As buildings are edited and updated, the Portland building data is combined with the most recent regional building data to create a complete regional set of building data.
	Residential units were assigned to buildings using a variety of sources, including building permit information, research of individual buildings, tax assessment information, and Metro's regional multi-family residential inventory. In the case of the latter, which is parcel-based, where there was more than one building on a parcel, units were assigned to buildings based on weighted building square footage.

Attribute Tables & Domains

X buildings_3d_pdx
Table Description
Table Jurisdiction
Column Sort	Column Name	Column Alias	Column Type	Column Size	Domain Value(s)	Column Description Add
1	SOURCE	SOURCE	String	30	Add Aerial Photos 6" resolution regional aerial photos. X Lidar-Derived Building was digitzed automatically from most recent LiDAR data (2004, 2005, 0r 2007) X LUR/Building Permit Land use review or building permit information, including site plans X Other Other reference source (see notes) X Photogrammetrics Derived from 1990's photogrammetric information. X 3D Model 3D model provided by developer (usually a SketchUp model) X	X The reference source used to map the building (same domain as the HGT_SOURCE attribute)
1	SURF_SRC	SURF_SRC	String	30	Add LiDAR DEM Surface elevation derived from a 3' resolution LiDAR surface elevation model generated from 2004 through 2007 bare earth LiDAR point returns. Vertical accuracy is generally within +/- 15cm (~6") for relatively flat areas not obscured by vegetation, +/- .7m (~2.5') where in areas of steep slopes or surfaces covered by vegetation. X 2001 DEM A 10' resolution DEM generated from a 2001 DTM created from 2001 aerial photos. Surface elevations derived from the 2001 DEM are within +/- 5' in most cases. X	X The source information for the surface elevation
1	BLDG_NAME	BLDG_NAME	String	150	Add	X The building name (if known)
1	NUM_STORY	NUM_STORY	Integer	2	Add	X The maximum number of building stories (if known)
1	BLDG_SQFT	BLDG_SQFT	Integer	4	Add	X The building square footage (if known, usually gross)
1	YEAR_BUILT	YEAR_BUILT	Integer	2	Add	X The year construction of the building was completed (if known)
1	OBJECTID		Integer	4	Add	X A unique ID for each shape (polygon) in the database. These IDs are arbitrailiy assigned by the GIS software and can change.
1	BLDG_ADDR	BLDG_ADDR	String	50	Add	X The building's street address
1	STATE_ID	STATE_ID	String	20	Add	X The state ID of the primary taxlot on which the building resides.
1	BLDG_NUMB	BLDG_NUMB	Integer	2	Add	X The building number. Each building on a single parcel receives a unique number, starting with #1. These numbers are used to construct the unique building ID.
1	BLDG_TYPE	BLDG_TYPE	String	30	Add	X The type of building (house, garage, etc.). Not yet populated. Domain to-be-determined.
1	BLDG_USE	BLDG_USE	String	30	Add Commercial General General commercial use X Commercial Grocery Grocery store or market X Commercial Hotel Hotel or motel use X Commercial Restaurant Restaurant or bar X Commercial Office Commercial office use X Commercial Retail Commercial retail use X Institutional Institutional use including hospitals and universities X Industrial Industrial use X Institutional Religious Institutional Religous X Multi Family Residential Multi family residential use (including condos, apartments, 3 or more unit plexes) X Parking Structured parking X Single Family Residential Single Family Residential (including ADUs, rowhouses, and duplexes) X Vacant Vacant X	X Predominant building use. Not consistently populated outside Portland's Central City.
1	ROOF_ELEV	ROOF_ELEV	Numeric	8	Add	X The average roof elevation (above NAVD 88 datum) of the building or portion of a building in feet.
1	ROOF_TYPE	ROOF_TYPE	String	15	Add Complex Complex structure with no consistent features. X Flat Flat roof X Multi-level Flat Flat roof with multiple levels (portions of the building are different heights) X Pitched Pitched roof structure X	X The basic roof structure type. Automatically populated for all LiDAR-derived buildings, manually populated for other buildings on a case-by-case basis.
1	ORIENT	ORIENT	Numeric	8	Add	X The orientation The orientation angle of the building along it's longest axis. Automatically populated for all LiDAR-derived buildings, manually populated for other buildings on a case-by-case basis.
1	AVG_HEIGHT	AVG_HEIGHT	Numeric	8	Add	X The average roof height of the building or portion of a building in feet.
1	MAX_HEIGHT	MAX_HEIGHT	Numeric	8	Add	X The maximum roof height of the building or portion of a building in feet. Consistently populated for LiDAR-derived buildings only.
1	MIN_HEIGHT	MIN_HEIGHT	Numeric	8	Add	X The minimum roof height of the building or portion of a building in feet. Consistently populated for LiDAR-derived buildings only.
1	HEIGHT_SRC	HEIGHT_SRC	String	30	Add Aerial Photos Building height estimated from 6" aerial photos (flown every year). X Field Estimate Building height estimated in the field (by counting stories, for example). X Field Measurement Building height estimated in the field using a laser range-finder or other measurement method. X Inferred form Asessor Sq. Ft Building height inferred from County Assessor square footage. Total assessed square footage is divided by the footprint square footage and the result multiplied by average floor height. Used for single-family buildings only. X Lidar DSM Building height manually derived from 2004 to 2007 LiDAR first-return "digital surface model" (DSM) X Lidar-Derived Building heights automatically derived from 2004 to 2007 LiDAR data by Watershed Sciences using the process described in the data lineage section above. X LUR/Building Permit Building height information derived from documents and plans submitted as part of the land-use review (LUR) and building permit process. X Other Building height information derived from a non-standard source (refer to notes) X Oblique Aerial Photos Building height information derived from oblique aerial photos and "street view" photos accessible in Bing, Google Earth, and Google Maps. X Photogrammetrics Building height derived from photogrammetric data derived from aerial photos flown from 1987 to 1994. X 3D Model Building height information derived from a digital 3D model provided by the developer (usually in Google SketchUp format). X	X The reference data source used to derive the height and elevation of the building or portion of a building.
1	SURF_ELEV	SURF_ELEV	Numeric	8	Add	X The average surface elevation (above NAVD88 datum) of the land beneath the building or portion of a building in feet.
1	SURF_OFF	SURF_OFF	Numeric	8	Add	X The surface offset a portion of a building. 10', for example, would indicate that a portion the building structure starts 10' above the ground (i.e., an overhang).
1	SURF_ADJ	SURF_ADJ	Numeric	8	Add	X The "adjusted" surface elevation, including any surface offset (Formula: [SURF_ELEV] + [SURF_OFF])
1	VOLUME	VOLUME	Integer	4	Add	X Estimated volume of building (in cubic feet). Calculated by multiplying the footprint area by the average building height.
1	CREATEDATE	CREATEDATE	Date	36	Add	X The date that the building was originally mapped (added to the GIS data, if known)
1	CREATED_BY	CREATED_BY	String	50	Add BPS City of Portland Bureau of Planning and Sustainability X CGIS City of Portland Corporate GIS group X City of Beaverton X City of Gresham X City of Hillsboro X City of Lake Oswego X City of Portland Building created by other City of Portland organization X City of Tualitan X City of West Linn X Metro X Oregon City X PPR City of Portland Parks and Recreation X Watershed Sciences Building automatically derived from LiDAR by LiDAR consultant Watershed Sciences X	X Name of agency that originally mapped the building
1	MOD_DATE	MOD_DATE	Date	36	Add	X The date of the most recent edits to the building polygon (if known)
1	MOD_NAME	MOD_NAME	String	50	Add	X The initials of the person that last edited the building or portion of a building
1	FIELD_DATE	FIELD_DATE	Date	36	Add	X The date of any field visit to the building
1	REVIEW	REVIEW	String	30	Add	X "T" indicates a building or portion of a building needs to be reviewed for mapping and/or height accuracy.
1	NOTES	NOTES	String	150	Add	X Notes and comments related to the building or portion of a building
1	SOURCE_REF	SOURCE_REF	String	50	Add	X Additional details about the mapping source (e.g., the date of LiDAR data used, the LUR/building permit case number, etc.)
1	SUBAREA	SUBAREA	String	30	Add City of Portland City of Portland maintenance area X Metro Metro regional maintenance area X	X Names of regional data-maintenance subareas
1	LAT_CTR	LAT_CTR	Numeric	8	Add	X Latitude of the center of the building or portion of the building
1	LONG_CTR	LONG_CTR	Numeric	8	Add	X Longitude of the center of the building or portion of the building
1	WSUNIQUEID	WSUNIQUEID	String	30	Add	X Unique ID assigned by Watershed Sciences for buildings automatically derived from LiDAR (no longer used)
1	BPS_BLDGID	BPS_BLDGID	Integer	4	Add	X Old BPS unique building ID (no longer used)
1	BLDG_ID	BLDG_ID	String	30	Add	X The unique building ID. This is the master identifier for the building. These IDs do not change and will not be reused.
1	SQFT_SRC	SQFT_SRC	String	50	Add	X Source of square footage information
1	STORY_SRC	STORY_SRC	String	50	Add	X Source of number of stories
1	STRUC_TYPE	STRUC_TYPE	String	30	Add Reinforced Masonry reinforced masonry construction X Steel Framed steel frame construction X Unreinforced Masonry unreinforced masonry construction X Wood Framed wood frame construction X	X The predominant construction method used to build the structure. Where not populated, strucure type is unknown.
1	STRUC_COND	STRUC_COND	String	30	Add Unsafe Structure deemed unsafe by the Portland Fire Bureau X	X The general condition of the structure. Currently only used to identify unsafe buildings.
1	BLDG_STAT	BLDG_STAT	String	50	Add Demolished Demolished building X Existing Existing building (or under construction) X Proposed Proposed building (not yet under construction) X	X The status of the building
1	UNITS_RES	UNITS_RES	Integer	2	Add	X Total number of residential units in the building. Derived from building permit information, tax assessment information, and Metro's regional multi-family inventory. In the case of the latter, which is parcel-based, units are assigned to buildings based on weighted building square footage.
1	UNITS_SRC	UNITS_SRC	String	30	Add County Asessor Database Derived from tax asessor information. X Developer Unit information received directly from developer. X Development Capacity GIS Model Units estimated by BPS buildable lands inventory GIS development capacity model. X LUR/Building Permit Derived from land use review or building permit information. X Metro MFR Inventory Units derived from Metro's regional mult-family inventory. X Marketing Information/Research Source is online research of the building (we googled it). X	X Source of the residential unit information.
1	OCCUP_CAP	OCCUP_CAP	Integer	2	Add	X Maximum building occupancy (where known).
1	OCCUP_SRC	OCCUP_SRC	String	50	Add Portland Parks Bureau X Portland Fire Bureau X	X Source of maximum building occupancy information.
1	ADA_ACCESS	ADA_ACCESS	String	5	Add	X "T" indicates the building is ADA accessible (where known).
1	PROPKEY	PROPKEY	Integer	4	Add	X
1	EDIT_STAT	EDIT_STAT	String	50	Add	X
1	DATA_SOURCE	DATA_SOURCE	String	5	Add	X
1	RETIRED_BY	RETIRED_BY	String	50	Add	X
1	RETIRED_DATE	RETIRED_DATE	Date	36	Add	X