ItemInfo

Item Information

snippet:	DTS has been maintaining the County-wide bldg_ps (i.e. polygons) geography since the late 90's. Each building polygon is assigned an address label under the field name PS_LABEL which contains the addrnum and the bldg unit number if the building addrnum is a duplicate. This file is used by DFRS in Altaris View to show building addresses on a map. Address matching, and geocoding data tables with address information should use the ADDRNUM field when creating a geocode locator. Bldg files were first created in the early 90's for the county, by a contractor hired by the Maryland National Capital Park and Planning Commission (MNCPPC) to be included in Planimetric layers. It was used by MNCPPC to display buildings on QC maps to minimize MNCPPC's encroaching property lines. DTS, then known as DIST, maintains bldg_ps, a geographic base file created using MNCPPC's property and bldgs data . Property data was initially used to add premise addresses to bldg_ps geography. DTS enhanced and expanded the building layer to include premise addresses and preplan drawings for Montgomery County Fire and Rescue. The new geographic database is dubbed as bldg_ps. Using the Arc/Info GIS software, DTS enhanced the County bldg_ps to a level surpassing MNCPPC's Planimetric bldg data using such sources as State Department of Assessments and Taxation, Department of Permitting Services, Motor Vehicle Administration and the Internet for addresses and Pictometry Ortho photos to cartographically (and spatially) enhance the bldg_ps data layer. Some 34,611shape polygons were added to the 267,8474 bldg_ps database. As a result, a spatially accurate and cartographically pleasing bldg_ps file was generated. Since 2000, DTS staff has improved the accuracy of the bldg_ps file from 267,847 polygons without premise addresses, preplans and shapes, to 326,524 (as of 09/24/2012) polygons with premise addresses, preplans and shapes.
summary:	DTS has been maintaining the County-wide bldg_ps (i.e. polygons) geography since the late 90's. Each building polygon is assigned an address label under the field name PS_LABEL which contains the addrnum and the bldg unit number if the building addrnum is a duplicate. This file is used by DFRS in Altaris View to show building addresses on a map. Address matching, and geocoding data tables with address information should use the ADDRNUM field when creating a geocode locator. Bldg files were first created in the early 90's for the county, by a contractor hired by the Maryland National Capital Park and Planning Commission (MNCPPC) to be included in Planimetric layers. It was used by MNCPPC to display buildings on QC maps to minimize MNCPPC's encroaching property lines. DTS, then known as DIST, maintains bldg_ps, a geographic base file created using MNCPPC's property and bldgs data . Property data was initially used to add premise addresses to bldg_ps geography. DTS enhanced and expanded the building layer to include premise addresses and preplan drawings for Montgomery County Fire and Rescue. The new geographic database is dubbed as bldg_ps. Using the Arc/Info GIS software, DTS enhanced the County bldg_ps to a level surpassing MNCPPC's Planimetric bldg data using such sources as State Department of Assessments and Taxation, Department of Permitting Services, Motor Vehicle Administration and the Internet for addresses and Pictometry Ortho photos to cartographically (and spatially) enhance the bldg_ps data layer. Some 34,611shape polygons were added to the 267,8474 bldg_ps database. As a result, a spatially accurate and cartographically pleasing bldg_ps file was generated. Since 2000, DTS staff has improved the accuracy of the bldg_ps file from 267,847 polygons without premise addresses, preplans and shapes, to 326,524 (as of 09/24/2012) polygons with premise addresses, preplans and shapes.
accessInformation:	MCG, GIS
thumbnail:
maxScale:	5000
typeKeywords:	[]
description:	<DIV STYLE="text-align:Left;"><DIV><DIV><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>Field name explanations:</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_ID – unique identifier for every footprint</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>PS_LABEL – building labels for Public Safety (geoload) or a reference for map making (a concatenation of ADDRNUM and BLDG_NUM)</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_NUM – Unit number or letter on a building to distinguish same addrnum’s</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>PREM_NUM – individual addresses that equal ADDRNUM and equal BLDG_CLASS (‘P’ and ‘Q’)but exclude footprint with a BLDG_CLASS = ‘S’ (used for individual address geocoding)</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_CLASS - ‘S’ represents footprints that are of the smallest square footage on a property that has multiple buildings(that are separated)of the same ADDRNUM, ‘P’ represents one footprint of the largest square footage on a property that has multiple buildings of the same ADDRNUM, ‘Q’ represents large square footage buildings (that are connected) with unit numbers or same ADDRNUM with a BLDG_NUM</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>ADDRNUM – all building individual address numbers, includes duplicates</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>PRE_DIR – n, s, e, w</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>STREET_NAME – value based on Clines data layer</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>SUF_DIR – n, s, e, w</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>STREET_TYPE – ave, st, rd, dr, la, way, mews, etc</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_NAME – names based on Places of Interest data layer</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>SOURCE – name of organization that digitized, edited, added value, corrected or changed the building</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_DATE – date that a footprint has been digitized, edited, added value, corrected or changed</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>FTR_CODE – Park and Planning code to describe a building under construction or not</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>X_COORD and Y_COORD – geographical reference, can be used for finding locations based on x,y values</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_TYPE – Land use code based on Park and Planning’s definitions</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>PREPLAN_URL – Fire Rescue’s .pdf files that represent some buildings</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_URL – In researching a footprint for an address on the web, and there is not one to be found a </SPAN></SPAN><A href="http://www.site" STYLE="text-decoration:underline;"><SPAN><SPAN>www.site</SPAN></SPAN></A><SPAN><SPAN>is given in this field</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>STATUS - information on irregular addresses</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>CENSUS_ID – Id based on the buildings Street name cline census_id</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN><SPAN>BLDG_PROP_TAX_ID – Account number based on Park and Planning property account number </SPAN></SPAN></P><P><SPAN><SPAN>POSTAL_CITY- The city name given by DTS</SPAN></SPAN></P><P><SPAN><SPAN>UNICORP_COMMUNITY- The city name given by USPS</SPAN></SPAN></P><P><SPAN><SPAN>ADDRNUM_NCR- The address number format used for NexGen911(NCR)</SPAN></SPAN></P><P><SPAN><SPAN>BLDG_NCR_DATE- The date format used for NexGen911(NCR)</SPAN></SPAN></P><P STYLE="margin:0 0 14 0;"><SPAN /><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
licenseInfo:
catalogPath:
title:	SDE.BAR
type:
url:
tags:	["bldg_ps","bldpre","bld300","bld3k","bld","coverage","shapefile","geodatabase"]
culture:	en-US
portalUrl:
name:
guid:
minScale:	150000000
spatialReference: