MDProperty View Subscriber Guide
MDProperty View Subscriber Guide
Harford County is used as the example jurisdiction throughout this document. Please substitute your
current jurisdiction as applicable.
MdProperty View, now in its thirteenth year with the release of the 2008 Edition by the Maryland Department of
Planning, is a series of jurisdiction-level datasets and image collections that include a custom ArcGIS map document
file (.mxd file) and custom ArcView project files that allow you to quickly work with MdProperty View shapefiles.
Having both a custom ArcGIS map document file and custom ArcView project files on each 2008 Edition DVD benefits
organizations using both applications concurrently or transitioning from ArcView to ArcGIS.
This combination of information, a custom ArcGIS map document file or custom ArcView project files and the
appropriate ESRI software package allows you to easily view property maps, or in Baltimore City, detailed street maps,
locate and select parcels and display many different dataset items for each property. ESRI software is not included on
your 2008 Edition DVD product, but can be obtained directly from Environmental Systems Research, Inc. (ESRI) or any
MDP private business partner.
Following is a detailed MdProperty View Subscriber’s Guide that discusses both the ArcGIS 9.x and the ArcView
3.x versions of the DVD product. See one or more of the following sections for the information you need:
MdProperty View uses a hierarchical folder structure that follows logical file naming conventions. The folder structure
includes a root folder at the top that further divides or branches into various subfolders, and may also contain files.
Each subfolder may also contain files and/or further divide or branch into additional subfolders. The MdProperty View
2008 Edition root folder name is different for each county or Baltimore City, but it is always 8 characters for all
jurisdictions. The first four characters are the 4-letter jurisdiction abbreviation, and the last four characters are the
MdProperty View Edition year. For Harford County, the root folder is Harf2008.
The folder structure is the same for all counties in Maryland with some slight variations. Only the 4-letter jurisdiction
abbreviation changes from county to county. You may substitute the county of your choice in the following discussion,
bearing in mind that there are subtle differences, as noted below, for some counties and more pronounced differences
for Baltimore City. The Baltimore City folder structure differs significantly from the county folder structure because
detailed street maps rather than property maps are displayed for Baltimore City.
There are a few things you need to do before getting started with MdProperty View ArcGIS Version:
ArcGIS 9.1 Users Only: Install the 9.1 Raster Patch (for display of counties only)
ESRI's 9.1 release of ArcGIS contains a known issue relating to raster data. This "bug" affects the spatial
referencing of property map images in MdProperty View, which are stored as TIFF files (CCITT G4 compression
format). The bug causes ArcGIS 9.1 to display these images incorrectly. This is a defect in the ArcGIS 9.1 software
and is not in any way related to the data that are distributed on each MdProperty View DVD.
As of August 10, 2005, ESRI released ArcGIS Desktop 9.1 Raster Patch, which among other fixes, resolves the
problems associated with displaying MdProperty View property map images. For more information and to download
this patch, visit the ESRI website at:
http://support.esri.com/index.cfm?fa=downloads.patchesServicePacks.viewPatch&PID=26&MetaID=1056#intro
The raster patch does not need to be installed if you are still using ArcGIS Version 9.0. This bug was corrected with
the release of ArcGIS 9.2.
If your 2006 Edition CD-ROM contains an ArcGIS 9.2 .mxd file (for example, Carr92gis.mxd), just use that .mxd file
and you are “good to go”. If your 2006 Edition CD-ROM does not contain an ArcGIS 9.2 .mxd file, go to the
MdProperty View website at:
http://www.mdp.state.md.us/data/index.htm
and download a program you can run to fix tax map display only, then go to the Subscriber website at:
http://www.mdp.state.md.us/mdpview/
and download a new ArcGIS 9.2 .mxd file for any of your 2006 Edition MdProperty View jurisdictions that were
issued prior to May of 2007.
After placing the DVD in your drive or copying the entire contents including the appropriate MdProperty View map
document file to a folder on your local or network hard drive, you are ready to access the property maps or detailed
street map for Baltimore City and assessment information within MdProperty View. To access the data, first load
Windows and then load the ArcGIS software − once you are in the software, find Harf9gis.mxd for ArcGIS 9.1
and earlier or Harf92gis.mxd for ArcGIS 9.2 located in the Harf2008 folder and load it to organize jurisdiction
assessment information into an integrated display.
If you want to use the full resolution image, you must copy the HarfNAIP07 folder with the Harf2008 folder to a
local or network hard drive and run Harford County MdProperty View 2008 Edition from that location, as the full
resolution image will not run very efficiently off of the DVD. ArcGIS does not require the DVD contents to be
copied to a root folder as does the ArcView software, so you can copy both folders to a sub-folder if you prefer, as
long as they are copied to the same location.
If you get stuck installing MdProperty View, or if you need more information about MdProperty View ArcGIS
Version, continue reading for additional help and resources.
As noted in the introduction, the root folder of each MdProperty View DVD contains ArcGIS 9.x map document files with
a .mxd file extension. A map document file is an integrated collection of various property data and image layers. A map
document file itself does not contain any data − it is simply a link or pointer to source data. The presence of .mxd files
under the root folder means that custom map document files have been created for you, the MdProperty View
Subscriber.
The MdProperty View map document files are set up to work either directly from a DVD drive or with the entire
contents copied under the root folder (for example, C:\Harf2008) or any subfolder of any local drive on a computer or a
network. Remember also that MdProperty View is set up with all data sets spatially referenced using NAD83 meters in
the State Plane Coordinate System as required by the Maryland State Geographic Information Committee (MSGIC).
Thus the DVD product is consistent with other State GIS data layers.
While the data are in NAD83 meters, all distance units in the map document file are set to display in feet. An Alternate
Coordinates shapefile set, described in Appendix H: Alternate Coordinates Dataset Structure and Download
Instructions, is made available for reprojecting to other datums as each jurisdiction is completed for MdProperty
http://www.mdp.state.md.us/mdpview
ArcGIS terminology such as map document file, data frame, data view, map layer and shapefile are used throughout
the remainder of this document. If you are unfamiliar with these terms, you may find it helpful to consult ArcGIS
Online Help at:
Harf9gis.mxd for ArcGIS 9.1 and earlier or Harf92gis.mxd for ArcGIS 9.2 includes everything you need to view
county property maps and associated Parcel and Computer Assisted Mass Appraisal (CAMA) dataset layers, along with
frame of reference layers including a property map grid, State Highway Administration (SHA) major and detailed roads,
jurisdiction boundaries and a National Agriculture Imagery Program (NAIP) 2007 color digital-ortho image that is a 10
meter sample from a 1 meter original. Also included is a single seamless composite image of all property maps for
counties.
For Baltimore City, the map document file includes everything you need to view Baltimore City detailed street maps and
associated Parcel and CAMA dataset layers, along with frame of reference layers including State Highway Administration
(SHA) major and detailed roads, jurisdiction boundaries and a NAIP 2007 color digital-ortho image that is a 3 meter
sample from a 1 meter original. These layers are automatically loaded into the MdProperty View data frame once the
map document file is loaded.
Using MdProperty View’s custom ArcGIS map document file eliminates the need to access and load individual property
map images. The composite Harf Property map layer is set up to be displayed when you zoom into the map display
at a scale that is below that of the roads files shown in the ArcGIS Data view. As mentioned above, jurisdiction-wide
datasets, converted to shapefiles, are included in each jurisdiction map document file as data layers. User-friendly layer
names are used to identify these files in the Table of Contents − the actual file names appear after the user-friendly
names listed below:
Both the Parcel and CAMA data layers included in the MdProperty View map document file contain located as well as
unlocated parcels. Because unlocated parcels have x,y coordinates with 0, -1, or -9 values, they cannot be viewed in
any meaningful way on a jurisdiction map, and instead can only be looked at as part of the tables included in the map
document file.
Also included in the data view are the following map layers. Map layers are shown as they appear in ArcGIS, and are
therefore ordered differently than in ArcView. Jurisdiction exceptions are noted.
General Layers
• ADC Page Index Harford County ADC Page Number Grid Harfpage.shp
Not available for Allegany, Garrett or Somerset counties
Property Layers
• Property Map Layer Seamless, composite image of all Harford County All county .tiffs
property maps − Not available for Baltimore City
• SHA Grid Map SHA 1:24,000 Harford County detailed grid map Harfgrid.shp
• SHA Grid Map Text Text for the SHA 1:24,000 detailed grid map Harftext.dxf
• SHA Grid Features Features for the SHA 1:24,000 detailed grid map Harfsymb.shp
• SHA County Map SHA 1:100,000 Harford County road map Harflin2.shp
• SHA County Map Text Text for the SHA 1:100,000 county map Harftext.dgn
• SHA County Features Features for the SHA 1:100,000 county map Harfsymb.shp
• SHA Major Roads SHA Harford County major roads map Harfmjrd.shp
Imagery Layers
MdProperty View ArcGIS version contains a custom drop-down menu located on the menu bar, entitled MdProperty
View. Property data extracts (agricultural, commercial and industrial, exempt properties and unimproved residential
properties), overlays (including census, congressional/legislative district, ZIP code, land use/land cover layers) and
Priority Funding Area layers can be added to the data frame and displayed in the data view through this menu. There
are also selections for the Search Tool and links to other helpful websites. The custom menu selections are described
below.
http://dnrweb.dnr.state.md.us/gis/data
• Not included in this sub-menu, 1973 Land Use/Land Cover GIS layer: Harflu73.shp
1973 classification of jurisdiction land use/land cover for Harford County based on Level 2 U.S.G.S.
classification scheme, originally developed as ink on Mylar maps (1"= 1 mile, State Highway Administration)
using uncontrolled high altitude aerial photography. Not included in this layer, but you may add it to the
data frame if you wish, loading it from the Harf2008\OVERLAYS\LULC\1973 folder.
http://www.mdp.state.md.us/zip_downloads_accept.htm
Harfpfa.shp County priority funding area (PFA) for Harford County in its entirety
Not included on the Harford County MdProperty View DVD, but included in other jurisdictions are:
Map and Data Layers not included in the ArcGIS Custom Menu
For the 2008 Edition of MdProperty View ArcGIS version, there are jurisdiction map and data layers you can access that
are not available through the custom menu. These layers can be added to the data frame if you wish, by loading them
from the following locations:
• Not included in the custom menu, Summary Total Sales CY2007-02: Ct_tot_sales.shp
Statewide map layer showing summary sales data by census tract for all residential, improved sales. The
summary characteristics for each tract are the total number of sales by individual year (CY2007 thru CY2002),
median dollar value of sales by year and mean dollar value of sales by year based on the consideration at time
of sale. You may add this layer to the data frame if you wish, loading it from the Harf2008\OVERLAYS\ResSale\
Ct_Sales_Summary folder.
• Not included in the custom menu, Summary Single Family Sales CY2007-02: Ct_sf_sales.shp
Same as above for single family residential improved sales. You may add this layer to the data frame if you
wish, loading it from the Harf2008\OVERLAYS\ResSale\Ct_Sales_Summary folder.
• Not included in the custom menu, Summary Townhouse Sales CY2007-02: Ct_th_sales.shp
Same as above for townhouse residential improved sales. You may add this layer to the data frame if you wish,
loading it from the Harf2008\OVERLAYS\ResSale\Ct_Sales_Summary folder.
• Not included in the custom menu, Summary Condominium Sales CY2007-02: Ct_con_sales.shp
Same as above for condominium residential improved sales. You may add this layer to the data frame if you
wish, loading it from the Harf2008\OVERLAYS\ResSale\Ct_Sales_Summary folder.
The bottom-most data layer in the Table of Contents is Print Individual Property Maps. Using selection this allows
you to zoom in on the extent of and print a single county tax map (not available for Baltimore City). To execute this
action:
1. While holding down the CTRL key on your keyboard, click on any check box in front of a data layer in the Table
of Contents. This turns off all the data layers.
2. Click on the check box in front of Print Individual Property Maps and expand the layer to see all of the
individual tax map image files (.tif) for the county.
3. Scroll down to the county tax map file you want to view (print) and click on the check box in front of this file (for
example Harf001.tif). Most images have a 3-digit number associated with them. In cases where town map
supplements and/or inset maps are available, a 4-digit number may be used.
4. Highlight the entire file name by clicking your mouse over it, and right click on the file to get a local menu.
Select Zoom to Layer to display the full tax map image in the data view, then select Print… from the File menu to
print the tax map.
There are a few things you need to do before getting started with MdProperty View ArcView Version:
The Harfgeoc.apr Geocode project file includes the Geocode Tool, a utility for referencing your customer and
client address dataset records to MdProperty View parcel points so you can map your data. The Geocode project
file must be loaded to use this tool with the ArcView software.
The Geocode Tool links records in the two datasets by matching street names and addresses. When your dataset
records are successfully matched to MdProperty View parcels, your records are tagged with x,y coordinates for map
display. The result is a new map layer containing your dataset information that can be displayed and accessed
along with the other map layers included in the MdProperty View DVD product.
After placing the DVD in your drive or copying the DVD contents including the MdProperty View project files to a
root folder on your local or network hard drive, you are ready to access the property maps or detailed street map
for Baltimore City and assessment information within MdProperty View. To access the data, first load Windows and
then load ArcView 3.x − once you are in the software, find the project files located in the Harf2008 folder and load
one of the files to organize jurisdiction assessment information into an integrated display.
If you get stuck installing MdProperty View, or if you need more information about MdProperty View ArcView
Version, continue reading for additional help and resources.
As noted in the introduction, the root folder of each MdProperty View DVD contains ArcView 3.x project files with an
.apr file extension. Each project file is an integrated collection of various property data and image layers. A project file
does not contain any data. It is simply a link or pointer to source data. The presence of .apr files under the root folder
means that specialized project files have been created for you, the MdProperty View Subscriber. The project file that
you will be working with the most as an ArcView user is the Master Project File.
MdProperty View project files are set up to work either directly from a DVD drive or with the entire DVD contents copied
under the root folder (for example, C:\Harf2008) of any local drive on a computer or a network. MdProperty View
ArcView Version will not work if the DVD contents are copied under a new or existing folder your
computer − the Harf2008 folder and contents must be copied to C:\ or D:\ or to the root of a network drive.
Remember also that MdProperty View is set up with all datasets spatially referenced using NAD83 meters in the State
Plane Coordinate System as required by the Maryland State Geographic Information Committee (MSGIC). Thus the
MdProperty View product is consistent with other State GIS data layers.
While the data are in NAD83 meters, all distance units in the map document file are set to display in feet. An Alternate
Coordinates shapefile set, described in Appendix H: Alternate Coordinates Dataset Structure and Download
Instructions, is made available for reprojecting to other datums as each jurisdiction is completed for MdProperty
View. This shapefile is available for downloading from the Subscriber Website at:
http://www.mdp.state.md.us/mdpview
ArcView terminology such as project file, view, data frame, data view, theme, layer and shapefile are used throughout
the remainder of this document. If you are unfamiliar with these terms, you may find it helpful to consult ArcView
Online Help at:
http://support.esri.com/index.cfm?fa=software.filteredGateway&PID=15
Harfmast.apr includes everything you need to view county property maps and associated Parcel and Computer
Assisted Mass Appraisal (CAMA) dataset layers, along with frame of reference layers including a property map grid,
State Highway Administration (SHA) major and detailed roads, jurisdiction boundaries and a National Agriculture
Imagery Program (NAIP) 2007 digital-ortho color sampled image. Also included is a single seamless composite image of
all property maps for the county.
For Baltimore City, the Master project file includes everything you need to view Baltimore City detailed street maps and
associated Parcel dataset layers, along with frame of reference layers including State Highway Administration (SHA)
major and detailed roads, jurisdiction boundaries and a NAIP 2007 digital-ortho color sampled image for Baltimore City.
Using MdProperty View’s custom Master project file eliminates the need to access and load individual property map
images. The composite HarfProperty_Map parcel map theme (or in Baltimore City, the BaciRoad MdLandbase detailed
street map theme) displays when you zoom into the map display at a scale that is below that of the roads files shown in
any project file view. As mentioned above, jurisdiction-wide datasets, converted to shapefiles, are included as themes in
all Master project file views:
Both the Parcel and CAMA dataset themes included in the Master project file contain located as well as unlocated
parcels. Because unlocated parcels have x,y coordinates with 0, -1, or -9 values, they cannot be viewed in any
meaningful way on a jurisdiction map, and instead can only be looked at as part of the tables included in each Master
project file view.
Only one Master project file is provided on a jurisdiction DVD. This Master project file includes four views for counties,
three views for Baltimore City. County Master project file views 1-4 enable you to select the desired reference layers to
be viewed with the property map and Parcel dataset layers:
Baltimore City Master project file views 1-3 for Baltimore City enable you to select the desired reference layers to be
viewed with the detailed street map and Parcel dataset layers:
By using the Master project file, you can open just one project file and select the view with the desired reference
layers to provide the context in which to access and view property maps and parcel data for the entire jurisdiction.
This makes using the Master project file simpler and more versatile.
The Geocode project file, intended for use with the Geocode Tool, contains one view that includes the Parcel dataset
for Harford County set up for geocoding, as described in Part III: About the MdProperty View Enhanced User
Interface − go there for step-by-step instructions on using this tool. The Geocode Tool is a utility for referencing your
customer and client address dataset records to MdProperty View parcel points so you can map your data. Geocoding is
the process of matching records in two datasets: your client or customer address dataset that contains no map position
information and a reference map dataset containing address information, in this case MdProperty View geographically
referenced parcel points with cleaned-up premise or, in some cases, owner addresses.
The Geocode Tool links records in the two datasets by matching on street address (street address number, street
address name and street address ZIP code). When your dataset records are successfully matched to MdProperty View
parcels, your records are tagged with x, y coordinates for map display. The result is a new map layer containing your
dataset information that can be displayed and accessed along with the other map layers included in the MdProperty
View DVD product.
There are four Extract project files included on the Harford County DVD. While any of these project files can be used
independently, they each contain extract datasets primarily intended for use with the Master project file.
Once you have done this, the Commercial and Industrial Properties project file appears as an additional view in the
Master project file. Open the view and highlight Harfcmin.shp in the legend, then use the cut themes and paste
options under Edit to bring the theme into one of the four Master project file views. You can now use this new
theme along with the original themes in the Master project file.
Appendix F: Exempt Class Codes and Descriptions contains information about the exemption class codes and
descriptions used to describe parcels contained in the exempt properties project file.
While the four Overlays project files views and corresponding themes described below can be used independently, they
are intended primarily for use with the Master project file. By importing the Overlays project file into a project file that
contains parcel data and property maps (counties) or detailed street maps (Baltimore City) and copying and pasting
these themes into the current view, you can examine the spatial relationship between boundary and thematic files such
as legislative districts or land use/land cover and property information. The first view in the Overlays project file
contains these nine themes:
Census themes:
• Not included in a project file, 2007 ZIP Codes GIS theme: Harfzc07.shp
A 2007 enhanced (1:24,000) 5-digit ZIP Code boundary file for the jurisdiction is included on the DVD, but not
contained within any Overlays project file view.
The second view in the Overlays project file contains these themes:
http://www.mdp.state.md.us/zip_downloads_accept.htm
Not included on the Harford County MdProperty View DVD, but included in other jurisdictions are:
The third view in the Overlays project file contains these Planning themes:
http://dnrweb.dnr.state.md.us/gis/data
The Maryland Department of Planning has included an enhanced user interface in MdProperty View that contains
several menu-driven tools to make the DVD product extremely easy to use. All of these tools can be accessed through
icon buttons located on the ArcGIS dockable toolbar or the ArcView button bar.
Geocode Tool
ArcGIS ArcView
The Geocode Tool is a utility for referencing your customer or client address dataset records to the MdProperty View
Parcel dataset so you can map your data. Geocoding is the process of matching records in two datasets: your client or
customer address dataset, which contains no map position information, and a reference map dataset containing
address information, in this case MdProperty View geographically referenced parcel points with cleaned-up premise
address or owner address data. For MdProperty View ArcGIS Version, the Geocode Tool is part of the
Harf9gis.mxd for ArcGIS 9.1 and earlier and Harf92gis.mxd for ArcGIS 9.2 map document files. There is no
need to load an additional file to use this tool. For MdProperty View ArcView Version, the Harfgeoc.apr Geocode
project file includes the Geocode Tool, and the Geocode project file must be loaded to use the Geocode Tool with the
ArcView software.
The Geocode Tool links records in the two datasets by matching street names and addresses. When your dataset
records are successfully matched to the MdProperty View parcels, your records are tagged with x and y coordinates for
map display. The result is a new map layer containing your dataset information that can be displayed and accessed
along with the other map layers included in the MdProperty View DVD product. Before using the Geocode Tool, any
separate address fields in your dataset (street address number, directional, name and street type) except for ZIP code
must be combined into a single dataset field. Your client or customer dataset should look like the example shown
below. Additional fields may be present in your dataset, but ADDRESS and ZIPCODE fields must be present to do
geocoding, for example:
The Harf9GIS.mxd for ArcGIS 9.1 and earlier or Harf92gis.mxd for ArcGIS 9.2 Harford County map
document file must be loaded to use the Geocode Tool. When you select the tool and the Parcel dataset point layer
is active, a browser entitled MdProperty View - Select an address table (.DBF) opens. Browse to the location
on your computer where your customer or client address dataset is located, select the dataset and click Open.
The next window that appears is a browser that looks for an ArcGIS geocoding service file. The browser should
automatically open to the location where these files are located − if not, they can be found under the
Harf2008\Atdata\Database folder. Two geocoding service files should be displayed:
Select one of the geocoding service files to proceed. Harf9_2008A has stricter preference settings that typically
result in fewer, highly confident geocoding matches and Harf9_2008B has less strict preference settings that
typically result in more geocoding matches, including some lower confidence geocoding matches. Once you have
selected a geocoding service file, click Open. If an Information dialog box appears, click OK to continue.
MdProperty View Subscriber’s Guide (MdpUsr08.pdf) MdProperty View copyright 1996-2008/09
ArcView and ArcGIS are registered trademarks of Environmental Systems Research Institute, Inc.
Prepared by the Maryland Department of Planning, Planning Data Services 09/01/2008 Page 20 of 29
Next, select the location on your computer where the new geocoded layer will be saved. A browse window titled
Select a location for the geocoded feature class… appears. Browse to the folder where you want to save
your geocoded address dataset, type in a filename and click Save.
ArcGIS Step 2: The Geocoded File is added to the Current View as a Joined Layer
When the address matching and geocoding process is complete, a series of dialog boxes appear asking if you want
to delete temporary files − typically you should respond by clicking Yes. Next, a dialog box appears to let you know
that the geocoding is complete − click OK. The new geocoded layer is displayed as a map layer in the current data
frame. The default symbol used for this layer is a gold 20-point star. The attribute table of the geocoded layer
includes all records from your original customer or client address dataset, both those that successfully geocoded
and those that were not geocoded. The following additional fields appear in the layer attribute table:
STATUS
Matching status of an event, either M or T (successfully matched) or U (not matched).
SCORE
Matching score or matching confidence. In a range of 0 to 100, a 0 indicates an address that is unmatched (the
record has a value of U in the STATUS field) and a 100 indicates a record with a highly confident or exact
match.
X, Y
The x,y coordinates (NAD83 meters) where the address record was geocoded.
REF_ID
A numeric reference number for each geocoded record. Ignore this field.
FID_#
Unique identifiers create on the fly and used to join the Parcel dataset to your customer or client address
dataset.
DISTANCE
Ignore this field.
Combined street address (ADDRESS field) from the Parcel dataset record to which each record in your dataset was
geocoded is also joined to the geocoded layer using a field name created on the fly during the geocoding process.
Also joined to the geocoded layer is every field in the Parcel dataset for each record to which your address dataset
records geocoded (or matched). Appendix C: Parcel and Sales Dataset Structure and Sale Download
Instructions contains information about fields in the Parcel dataset.
If the Parcel dataset ADDRESS field for a particular geocoded record is not the same as the address for that record
in your address dataset, the geocoding score may be of a lower matching confidence or in error. Another possibility
is that your dataset record geocoded to the correct x,y coordinate location, but the fields were populated with data
from a Parcel dataset record that is a stacked point. An example of where a stacked point could occur is in a
condominium. Different addresses in a condominium could be assigned the same x,y coordinates. If your dataset
record is a stacked point, it may be populated with the fields of another parcel in the condominium development
that has a different address than the record in your dataset.
The output from ArcGIS Step 2 consists of two shapefile sets and an .xml file in the location you specified above.
These files are named as follows (where Yourfile is the filename that you specified):
Yourfile .dbf/.shp/.shx/.xml
Yourfileb .dbf/shp/.shx
STATUS
Matching status of an event, either M (successfully matched) or U (not matched).
SCORE
Matching score or matching confidence. In a range of 0 to 100, a 0 indicates an address that is unmatched (the
record has a value of U in the STATUS field) and a 100 indicates a record with a highly confident or exact
match.
Yourfileb contains only address records that successfully geocoded. For these records the following fields are
appended:
STATUS
Matching status of an event, either M (successfully matched) or U (not matched).
SCORE
Matching score or matching confidence in a range of greater than 0 to 100. The higher the score, the more
reliable the match, with 100 indicating a record with a highly confident or exact match.
DISTANCE
Value is always 0.000. Ignore this field.
ADDRESS
Combined street address from the Parcel dataset record to which each record in your customer or client
address dataset was geocoded is also added to Yourfileb using a field name created on the fly during the
geocoding process.
If you wish to increase the number of matches you get after first geocoding your data “as is”, here are some
options you may consider:
Option 1: copy your geocoded shapefile to create a new customer or client address dataset and remove any
records that were successfully geocoded. Blank the ZIP code data contained in each record of the new dataset and
run the dataset through the geocoding process. Then add any records that successfully geocoded back into the
dataset that contains your customer or client address records that successfully geocoded on the first pass. Option 1
may increase your geocoding “hit rate” in those cases where the ZIP code contained in your customer or client
address dataset failed to match the ZIP code in the Parcel dataset.
Option 2: copy your geocoded shapefile to create a new customer or client address dataset and remove any
records that were successfully geocoded. Edit the data in the new customer or client address dataset to more
closely match the data in the Parcel dataset geocoding fields using the address format guidelines found in
Appendix G: About Address Cleanup in the Parcel Dataset, then run the edited records through the
geocoding process again. Add any records that successfully geocoded back into the dataset that contains your
customer or client address dataset records that successfully geocoded on the first pass.
The geocoded layer including joined fields from the Parcel dataset layer can be written to a shapefile. With the
layer active, right click on the layer, select Data to open a drop-down menu, and select Export Data… from the
drop-down menu. An Export Data window appears − specify the following:
Export: All features Use the same Coordinate System as the data frame
Enter a location and name for the export shapefile and click OK.
Harfgeoc.apr, the Harford County Geocode project file, must be loaded to use the Geocode Tool. When you select
the Geocode Tool and the Harf2008.shp parcel point theme is active, you are asked to locate the dataset you wish
to geocode and fill in the Geocode dialog box. When the Geocode dialog box pops up, it should contain the name of
your customer or client address dataset as the Address Table. If not, select your dataset using the drop-down
window.
Address Field Enter the field that contains complete addresses in your dataset.
Zone Field Enter the field that contains ZIP codes in your dataset.
Geocoded Theme Enter the location to which the new interim shapefile is saved under a name you
specify.
Once this information has been filled in, press the Batch Match Button to begin the address-matching portion of the
program. Results of the address matching are posted in the Re-match Addresses dialog box. At this point, you
can go on to ArcView Step 2 if you want to increase your geocode matches, or skip directly to ArcView Step 3 if you
are satisfied with the geocoding results from ArcView Step 1.
If you wish to increase the number of matches you get after first geocoding your data “as is”, you can consider
modifying the geocoding preferences. Geocoding preferences can be changed at the Re-match Addresses dialog
box. When the Geocoding Preferences tab is selected, a dialog box appears showing the current preference
settings, which default to:
Spelling Sensitivity: 80
Minimum Match Score: 60
Minimum Score to be Considered a Candidate: 30
You can change these values, for example, to 75, 25 and 25 respectively and press OK. Now from the Re-match
Addresses dialog box, press the Batch Re-match button to repeat the address-matching portion of the program for
records that were not matched using the previous geocoding preferences. Results of the updated address matching
process are then reposted in the Batch Re-match dialog box.
Using less restrictive geocoding preferences usually results in increased matches with lower match scores. A match
with a lower score typically indicates that the address was geocoded to a nearby parcel with a close but not exact
address match, for example, a parcel with the same street name but different street number. Parcels with lower
match scores should be carefully reviewed to ensure that the geocoded location is acceptable. For records in your
address dataset that did not geocode, further review and editing of the address fields in the dataset may result in
improved geocoding. Once you are satisfied with your geocoding results, go on to ArcView Step 3.
From the Re-match Addresses dialog box, press Done to continue and create an interim geocoded shapefile and
join new data such as parcel account number, x,y coordinates and census geography to your geocoded dataset.
When this step is complete, you are prompted to enter the location to which the final geocoded shapefile is saved
under a name and location you specify.
Once geocoding is finished, ArcView displays a Status Processing Complete dialog box. Press OK and the final
geocoded shapefile appears in the current view. Your new geocoded dataset shapefile contains all fields from your
original customer or client address dataset plus these additional fields that ArcView automatically adds to your
geocoded dataset theme:
AV_ADD
The actual address used for matching. If you correct an address in the Geocoding Editor, the edited address is
saved in this field.
AV_ZONE
Only available if the reference theme is made matchable using an address style that contains a zone (ZIP code)
field. This field lists the zone value used for matching. If you correct the zone in the Geocoding Editor, the
edited value is saved in this field.
AV_STATUS
Matching status of an event, either M (successfully matched) or U (not matched).
AV_SCORE
Matching score or matching confidence. In a range of 0 to 100, 0 indicates an address that is unmatched (the
record has a value of U in the AV_STATUS field) and a 100 indicates a record with a highly confident or exact
match.
DISTANCE
Value is always 0.000. Ignore this field.
Additional fields are also added to your geocoded dataset theme based on the Parcel dataset records to which each
record in your customer or client address dataset geocoded (or matched):
ACCTID
Parcel account number (the State Department of Assessments and Taxation unique identifier for each parcel
within a jurisdiction) associated with the GEOADDR (see the GEOADDR field below) for each record to which
your dataset record was geocoded.
GEOADDR
Combined street address from the Parcel dataset record to which each record in your dataset was geocoded.
If the GEOADDR field for a particular record is not the same as the ADDRESS field for that record in your
dataset, the geocoding may be an error. Another possibility is that your dataset record geocoded to the correct
x,y coordinate location, but the fields were populated with data from a Parcel dataset record that is a stacked
point. An example of where a stacked point could occur is in a condominium. Different addresses in a
ADDRTYP
Source of the parcel address data that each record in your dataset was matched to, either P source data are
from the premise address in the Parcel dataset or M source data are from the Maryland Department of Planning
cleanup of owner addresses designated as owner occupied in the Parcel dataset.
CITY
Street address city of the GEOADDR for each record in your dataset.
GEOZIP
5-digit ZIP code associated with the GEOADDR (see the GEOADDR field below) for each record to which your
dataset record was geocoded.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions contains information
about fields in the Parcel dataset.
Merge Tool
ArcGIS ArcView
Use this tool to merge two or more vector data layers (point/line/polygon) into one layer. Two or more themes must be
active to use this tool. When you select the tool, a browser opens so you can select a folder to which the new merged
theme is saved under a name you specify. Once you select a location, you are asked if you want to add the new
shapefile as a theme to a view.
If you select Yes, the new merged theme is saved to the location you selected and the merged theme is loaded into the
current view. If you select No, the new merged theme is saved to the location you selected, but the merged theme is
not loaded into the current view.
ArcGIS ArcView
Use this tool to quickly and easily search Parcel datasets on account number, street address, owner name or map
reference (MAP and PARCEL fields). When you press this button and the correct theme is active, you are asked if you
wish to search for a property by any of these criteria and prompted to enter the appropriate information. Standard
wildcards may be used, as explained in ArcGIS Online Help or ArcView Online Help.
For map location, you see examples that show how many zeros to type in front of the MAP and PARCEL field entries
you are searching for to ensure that the data you enter match the MAP and PARCEL format used in all Parcel datasets
so the property you are searching for can be found if it exists in a dataset. Once the property you are searching for is
located or selected from a list of multiple hits, it is displayed as a red dot on the appropriate property map at a scale of
1 to 5,000 feet. If you press this button and the correct theme is not active, you are prompted to select a theme, and
the search proceeds once a theme has been selected.
ArcGIS ArcView
Use this tool to export a map in .jpg file format and print the map as it is displayed on the screen. When you press this
button, the current map image is exported to Mdpvads.jpg in the Mdpvads folder, the folder that was created on your
hard drive when you ran the Mdpvads.exe zip file.
Mdpvads.jpg automatically opens in the default image software installed on your computer (for example, Microsoft
Photo Editor or Paint Shop Pro) and the current map image displays so you can set up the image as you prefer and
send it to a local or network printer. This file is overwritten each time the tool is used − if you wish to save the file, use
the Save as… function under the File menu in your image software and save the file under a new name to a different
location on your hard drive.
Report Tool
ArcGIS ArcView
Use this tool to generate professional printed reports for individual or multiple properties or to generate mailing labels
using MdProperty View report templates. When you press this button, you get a list of all report templates that reside in
the Datadocs\Mdpvtmp3 folder on your hard drive. Once you select a report, the report is generated to the output
mode of your choice, file or printer. Additional tools such as the Search Property Tool and Distance Search Tools
described in this section can also be used to make it easier to select parcels to subsequently use with the report
templates in MdProperty View.
Remember that for this tool to work properly, you must run the self- extracting Mdpvads.exe zip file included in the
Datadocs folder on each MdProperty View DVD. The executable file creates an Mdpvads\Mdpvtmp3 folder at the root of
the hard drive of your choice that contains the report templates used by this tool to generate your reports. The report
templates work with the 2003 Edition of MdProperty View and above.
To use this tool in either ArcGIS or ArcView, it is best to have Seagate Crystal Reports for ArcView installed
locally on your computer − this tool may not work if you are running the software off of a network drive. Also, note that
a conflict may occur between versions of Seagate Crystal Reports when both ArcView and ArcGIS are installed on the
same computer.
Templates to create a report based on the Parcel and CAMA datasets are:
This is the only report that includes CAMA data − there is no separate report template for the CAMA dataset. For
this report to work, you must first join the CAMA dataset to the Parcel dataset using the ACCTID field.
http://www.mdp.state.md.us/mdpview
Templates to create Owner Address mailing labels using popular Avery label formats:
Mailing labels addressed to Owner for owner addresses. These mailing label reports yield the best set of mailing
labels for mailing to property owners, whether or not they actually live on a property. Owner address fields in
MdProperty View almost always have a complete street address, city and ZIP code.
Templates to create Cleaned-Up Street Address mailing labels using popular Avery label formats:
Mdpvl60.rpt Mailing Labels for Cleaned-Up Addresses – Complete Mailing Addresses (Avery 5160)
Mdpvl62.rpt Mailing Labels for Cleaned-Up Addresses – Complete Mailing Addresses (Avery 5162)
Mailing labels addressed to Resident for street addresses. Includes only cleaned-up street addresses with a
complete mailing address. Owner addresses data are used where the premise address data are incomplete and the
property is owner-occupied. These mailing label reports yield the best set of mailing labels for mailing to residents
who actually live on a property, whether they are homeowners or not, because these reports use the MdProperty
View cleaned-up address fields − ADDRESS, CITY and ZIPCODE.
Each label printed using either of these two reports is guaranteed to have a complete street address (street address
number and street name, as well as street address directional, street address suffix directional and street type if
they exist). Each label also has a CITY and a ZIP code, and city names are standardized to the United States Postal
Service (USPS) associated with each ZIP code in a given jurisdiction. Where city names are not available through
the premise city (PREMCITY field) or owner city (OWNCITY field) source information obtained from the State
Department of Assessments and Taxation, the CITY field is populated with the USPS city where a ZIP code can be
determined for a given address.
Templates to create Premise Address mailing labels using popular Avery label formats:
Mailing labels addressed to Resident for premise addresses. Includes premise addresses only with either a partial or
a complete mailing address.
ArcGIS ArcView
Use this tool to check the State Department of Assessments and Taxation (SDAT) Real Property Search website on the
Internet for the most up-to-date information about an individual property selected in MdProperty View. To use this tool,
you must be connected to the Internet via an Internet access provider − this tool will not work unless you are
connected to the Internet.
When you select a single property and press this button, you connect to the SDAT Real Property Search website and
the current property information is displayed for the property you selected. When you press the button and no property
ArcGIS ArcView
Use this tool to display jurisdiction-wide Priority Funding Area (PFA) layers as an overlay to any parcel map. By using
these layers, you can quickly determine if a subject property is inside or outside of a jurisdiction’s PFA.
When you press this button, jurisdiction-wide Priority Funding Areas are selected by default and a list of sub-areas that
can also be selected are displayed, such as Designated Neighborhoods, Enterprise Zones or Municipal PFAs. Once you
make any additional selections and click OK, the appropriate PFA layers are turned on. Layers can subsequently be
cleared from a view by selecting Clear PFAs from Map from the ArcGIS MdProperty View Menu or the ArcView
Smart Growth Tools Menu.
ArcGIS ArcView
Use these tools to draw a circle around all properties within a user-defined distance in feet from a selected property or
properties, select all points within the circle and export the points to a new file in a few simple steps.
When you press the first button with a single property or multiple properties selected, you are asked to enter a search
distance in feet (units can be changed) and a circle is drawn at that specified distance around each of the selected
properties. When you press the second button, all properties within the circle(s) are selected − circles may merge to
create a buffer zone around all selected properties if the circles intersect. When you press the third button, a browser
opens so you can select a folder to which the selected points are exported to a new shape file and saved under a
filename you specify. Once you select a location, you are asked if you want to add the new shapefile as a theme to a
view.
If you select Yes, the new merged theme is saved to the location you selected and the merged theme is loaded into the
current view. If you select No, the new merged theme is saved to the location you selected, but the merged theme is
not loaded into the current view. When you press this button and no property is currently selected, you are prompted
to select a single property, and the distance search process proceeds once a property has been selected.
ArcGIS ArcView
Use this tool to go directly to the Subscriber Website. To use this tool, you must be connected to the Internet via an
Internet access provider − this tool will not work unless you are connected to the Internet.
ArcGIS ArcView
Use this tool to go directly to the Maryland Department of Planning website, where you can get information about
Smart Growth-related projects and initiatives in Maryland. To use this tool, you must be connected to the Internet via
an Internet access provider − this tool will not work unless you are connected to the Internet.
ArcGIS ArcView
Use this tool to go directly to the Metropolitan Regional Information Systems, Inc. (MRIS) Homes Database website and
view properties for sale by ZIP code. To use this tool, you must be connected to the Internet via an Internet access
provider − this tool will not work unless you are connected to the Internet.
The following tools are only found in the ArcGIS versions of MdProperty View:
Use this tool to delete the distance placed by the Draw Distance Circle tool.
Use this tool to refresh the map displayed in the data view.
Use this tool to return the map displayed in the data view to the full county scale.
Use this tool to change the foreground (lines and text) and the background colors of the countywide composite tax
map. The first time a color change is performed in a session, it takes longer than for subsequent color changes.
Use this tool to zoom in and out from the center of the map continuously by dragging the pointer when the pointer is
placed over the map display and the left mouse button is held down.
Use this tool to set a layer to be the selectable layer. Highlight a layer in the Table of Contents and click on this tool
and a message confirms that the current layer is now selectable.
Use this tool to generate a parcel report as a text file in Windows Notepad when a single property is selected.
MdProperty View 2008 Edition allows users to work directly off of a jurisdiction DVD or copy the data down to a local or a
network drive.
To use MdProperty View ArcGIS 9.x Version, you need the following PC configuration:
ArcGIS 9.x is designed with an intuitive Windows user interface and includes Visual Basic for Applications for
customization. They consist of three desktop applications: ArcMap, ArcCatalog and ArcToolbox. ArcMap provides data
display, query, and analysis. ArcCatalog provides geographic and tabular data management, creation, and organization.
ArcToolbox provides basic data conversion.
Seagate Crystal Reports for ArcView software must be installed on your PC with Report Writer Extension enabled in
order to generate MdProperty View printed reports. To access current property data via the Internet, you must be
connected to the Internet and have an Internet browser installed on your PC.
To use MdProperty View ArcView 3.x Version, you need the following PC configuration:
ArcView 3.x includes Seagate Crystal Reports for ArcView software. Crystal Reports must be installed on your PC with
Report Writer Extension enabled in order to generate MdProperty View printed reports. To access current property data
via the Internet, you must be connected to the Internet and have an Internet browser installed on your PC.
ArcGIS can be ordered through ESRI or any of the following MdProperty View Business Partners:
The Local Office serving GIS Users in the Mid-Atlantic Region is:
8615 Westwood Center Drive Telephone: 703-506-9515
Vienna, VA 22182-2218 Fax: 703-506-9514
Appendix A: Hardware/Software Requirements and Where to Get ArcGIS or ArcView MdProperty View copyright 1996-2008/09
ArcView and ArcGIS are registered trademarks of Environmental Systems Research Institute, Inc.
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page A1 of A2
MDP has entered into agreements with private businesses to act as resellers of MdProperty View. In addition to selling the
ESRI software and marketing MdProperty View, the following private business partners may provide value-added services to
tailor the DVD product to our Subscribers’ specific application or needs.
Appendix A: Hardware/Software Requirements and Where to Get ArcGIS or ArcView MdProperty View copyright 1996-2008/09
ArcView and ArcGIS are registered trademarks of Environmental Systems Research Institute, Inc.
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page A2 of A2
Appendix B: Help Desk, Support, Training and How to Contact MDP
MdProperty View Subscribers can get help with the DVD product through the following channels:
9 Can I join MdProperty View datasets with my external dataset, merge MdProperty View datasets spatially to create a
custom study area or link an MdProperty View dataset to a spreadsheet?
9 Can I import and overlay files created in other GIS applications using MdProperty View?
9 Can I easily create and print detailed MdProperty View reports or mailing labels?
Subscriber Website
The Subscriber Website is your place to go for downloadable datasets such as monthly Sales transaction files, the latest
MdProperty View product updates and the latest news about the MdProperty View DVD product. You can also submit Help
Desk questions via the Subscriber Website at:
http://www.mdp.state.md.us/mdpview
Appendix B: Help Desk, Support, Training and How to Contact MDP MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page B1 of B1
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions
Parcel data from the State Department of Assessments and Taxation are a comprehensive dataset that incorporates
parcel ownership and address information, parcel valuation information and basic information about the land and
structure(s) associated with a given parcel. These data form the basis for the Parcel dataset (for example,
Harf2008.shp), which also includes selected Computer Assisted Mass Appraisal (CAMA) characteristics, text descriptions
to make parcel code field data more readily accessible and logical True/False fields which identify parcels with certain
characteristics, and can be used as a basis for performing various analyses based on parcel data.
The Parcel dataset resides in the Atdata\Database folder on each jurisdiction MdProperty View DVD. The dataset is
sorted on cleaned-up combined street address (ADDRESS) and is included in the ArcGIS map document file and in
ArcView project files included on each DVD.
For your convenience, MDP has also created special jurisdiction-wide extracts of the Parcel dataset that contain parcels
with certain characteristics. These special extract datasets include an agricultural parcels extract dataset for all
jurisdictions except Baltimore City, a commercial/industrial parcels extract dataset, a residential unimproved parcels
extract dataset and seven exempt class code extract datasets. Extract datasets reside in the Extracts folder on each
jurisdiction MdProperty View DVD.
Two new dwelling type codes (DWLL_TYPE field) and descriptions (DWLL_TDESC field) have been added to the CAMA
dataset by SDAT: 014 condominium parking space and 015 condominium storage unit. These codes and
descriptions are primarily used in Maryland’s five largest jurisdictions: Anne Arundel, Baltimore, Montgomery and Prince
George’s counties and Baltimore City. The codes only (not the descriptions) appear in the structure code field
(STRUCODE), and the codes also appear in the STRUDWEL field, with the descriptions appearing in the DESCDWEL
field. See Pages C11 and C12 for a description of the STRUCODE, STRUDWEL and DESCDWEL fields.
Sale datasets are created on a monthly basis using data obtained from the State Department of Assessments and
Taxation. Each monthly download contains a full year's worth of sale data, ending with the current month. This dataset
file structure applies to sale transaction data files including and subsequent to January of 2008.
Sale datasets are not included on the MdProperty View DVD for each jurisdiction − instead they are posted to the
Subscriber Website each month for MdProperty View Subscribers to download. A username and password are required
to access the web site. Each downloaded Sale dataset can be used with the ArcGIS 9.x or ArcView 3.x version of
MdProperty View.
Fields are described below in the order in which they appear in the Parcel and/or the Sale datasets. Please note that
although the majority of fields appear in both datasets, some fields appear only in the Parcel dataset or only in the Sale
dataset.
Dataset fields are listed as Optional, Required or Automatic (computer generated) for State Department of Assessments
and Taxation purposes. Dataset fields listed as MdProperty were created by the Maryland Department of Planning
exclusively for MDP’s DVD products.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C1 of C22
Parcel Sale ACCTID Character Field Width 16 Required
Parcel account number, a unique identifier for each account within any jurisdiction.
• For Anne Arundel County: positions 1-2 are the jurisdiction (county) code, positions 3-4 are the tax district,
positions 5-7 are the subdivision, positions 8-15 are the parcel account number and the remaining position is blank.
• For Baltimore City: positions 1-2 are the jurisdiction (city) code, positions 3-4 are the ward, positions 5-6 are the
section, positions 7-10 or 7-11 are the block (position 11 may be blank for some parcels), positions 12-14 or 12-15
are the lot (position 15 may be blank for some parcels) and the remaining position is blank.
• For all other counties: positions 1-2 are the jurisdiction (county) code, positions 3-4 are the tax/election district
and the remaining positions up to 12 positions are the parcel account number.
In MdProperty View, the parcel x and y coordinates for all jurisdictions are in the NAD83 meters version of the Maryland
State Plane Coordinate System. If the value of the parcel x or y coordinate is -9, -1 or 0, there is no linkage between a
tax map and MdProperty View datasets for the record.
Alternate x and y coordinates (NAD27 feet and NAD83 feet) are available for each parcel in the jurisdiction Alternate
Coordinates dataset, which is placed on the Subscriber Website as each jurisdiction is completed for the current Edition
of MdProperty View.
Census 2000 census tract and block group: position 1-2 are the State code (024), positions 3-5 are the jurisdiction FIPS
code, positions 6-11 are the census tract and position 12 of BG2000 is the census block group.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C2 of C22
Parcel Sale OOI Character Field Width 1 Required
Owner occupied indicator: H for occupied by owner, N for not occupied by owner, D for dual use, partly occupied by
owner, part of the property is devoted to agricultural, commercial or rental use.
Cleaned-up combined street address. Populated with data from the premise address number (PREMSNUM), premise
address direction (PREMSDIR), premise address name (PREMSNAM) and premise address street type (PREMSTYP)
fields. ADDRESS is only populated with premise address data if there are data in both premise address number and
premise address name.
If ADDRESS cannot be populated by premise address, the field is populated with owner address line 1 (OWNADD1) for
parcel accounts with an owner occupied indicator (OOI) of either H (occupied by owner) or D (dual use, partly occupied
by owner, part of the property is devoted to agriculture, commercial or rental use), provided that owner address line 1
contains a valid street address and not a post office box.
Appendix G: About Address Cleanup in the Parcel Dataset (MdpUsr08.pdf) in the Datadocs folder contains
detailed information about how ADDRESS field data are cleaned up and how the ADDRESS field is populated for
inclusion in the MdProperty View DVD product.
The street address number, street address prefix directional, street address name, street address type, street address
suffix directional, and street address unit components of cleaned-up combined street address (ADDRESS).
Appendix G: About Address Cleanup in the Parcel Dataset (MdpUsr08.pdf) in the Datadocs folder contains
detailed information about how STRT field data are cleaned up and how STRT fields are populated for inclusion in the
MdProperty View DVD product.
Street address source indicator: O if the ADDRESS field was populated from owner address line 1 (OWNADD1) and P if
the ADDRESS field was populated from premise address (PREMSNUM, PREMSDIR, PREMSNAM and PREMSTYP).
Cleaned-up combined street address city. CITY is populated with data from premise city (PREMCITY) if there are data
in both premise address number (PREMSNUM) and premise address name (PREMSNAM). CITY is populated with owner
city data (OWNCITY) if owner address data have been used to populate ADDRESS as described above. Because
PREMCITY is not populated in the State Department of Assessments and Taxation dataset for Baltimore County, CITY in
Baltimore County MdProperty View datasets is populated with owner city data for parcel accounts with an owner
occupied indicator (OOI) of either H (occupied by owner) or D (dual use, partly occupied by owner, part of the property
is devoted to agriculture, commercial or rental use).
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C3 of C22
Appendix G: About Address Cleanup in the Parcel Dataset (MdpUsr08.pdf) in the Datadocs folder contains
detailed information about how CITY field data are cleaned up and how the CITY field is populated for inclusion in the
MdProperty View DVD product.
Cleaned up combined street address primary (5 digit) ZIP code. Must be numeric. ZIPCODE is populated with data from
premise primary (5 digit) ZIP code (PREMZIP) if there are data in both premise address number (PREMSNUM) and
premise address name (PREMSNAM). ZIPCODE is populated with owner primary (5 digit) ZIP code data (OWNERZIP) if
owner address data have been used to populate ADDRESS as described above. Because PREMZIP is not populated in
the State Department of Assessments and Taxation dataset for Baltimore County, ZIPCODE in Baltimore County
MdProperty View datasets is populated with owner primary (5 digit) ZIP code data (OWNERZIP) for parcel accounts
with an owner occupied indicator (OOI) of either "H" (occupied by owner) or "D" (dual use, partly occupied by owner,
part of the property is devoted to agriculture, commercial or rental use). ZIPCODE is further improved by:
• Standardization of ZIPCODE field content to the current United State Postal Service (USPS) ZIP code shown for a
given address, and
• Population of missing ZIPCODE field content for address ranges where the field content is missing and ZIPCODE
can be determined from the current USPS ZIP code used for the address range.
Owner name key, used to facilitate sorting and account look-up. Ensures that like entries are grouped together or
entries appear in a particular name order. For example, all 7-11 stores may be keyed in as "SEVENELEVEN STORE". If
not filled in through data entry, the first 25 characters of the owner's name are used to generate a name key. In
Montgomery County, the first eight characters of the owner’s last name plus a space plus the first two characters of the
owner’s first name are used to generate a name key.
Owner address lines 1 and 2, owner address city and owner address state United States Postal Service (USPS)
abbreviations for any of the 50 states or the District of Columbia. The following USPS abbreviations are also used:
Owner address primary (5 digit) and secondary (4 digit) ZIP code (must be numeric). OWNZIP2 cannot be filled in
unless OWNERZIP contains a ZIP code.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C4 of C22
Parcel Sale PREMSNUM Character Field Width 5 Optional
Parcel Sale PREMSDIR Character Field Width 2 Optional
Parcel Sale PREMSNAM Character Field Width 22 Optional
Parcel Sale PREMSTYP Character Field Width 5 Optional
Parcel Sale PREMCITY Character Field Width 22 Optional
Parcel Sale PREMZIP Character Field Width 5 Optional
Parcel Sale PREMZIP2 Character Field Width 4 Optional
Premise address number (must be numeric), premise address prefix directional (may be left blank), premise address
name (must be filled in if there are data in PREMSTYP), premise address street type and premise address city. Premise
address primary (5 digit) and secondary (4 digit) ZIP code (must be numeric). PREMZIP2 cannot be filled in unless
PREMZIP contains a ZIP code.
Legal description lines 1, 2 and 3. Positions 1-4 of LEGAL1 must contain blanks, or IMPS if there is a structure on the
property.
Deed reference 1 and deed reference 2 clerk's initials (or blank), liber (must be numeric) and folio (must be numeric).
Deed reference 2 additional deed reference indicator: A for additional deed reference. Cannot be filled in unless there
are data in DR2CLERK, DR2LIBER and DR2FOLIO.
Incorporated town code and town code description (town name). Town code must be numeric. County keywords are
included at the beginning of the DESCTOWN field to make it easier to select all parcels in a county that have been
assigned a town code. Please note that Baltimore City and Baltimore and Howard counties do not use town codes.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C5 of C22
Baltimore City Dorchester (continued) Montgomery (continued)
No town codes 008 DORC Brookview 012 MONT Rockville
009 DORC Eldorado 013 MONT Gaithersburg
Baltimore County 014 MONT Barnesville
No town codes Frederick 015 MONT Laytonsville
001 FRED Brunswick 016 MONT Poolesville
Calvert 002 FRED Burkittsville 017 MONT Garrett Park
001 CALV Chesapeake Beach 003 FRED Emmitsburg 018 MONT Glen Echo
002 CALV North Beach 004 FRED Frederick City 019 MONT Somerset
005 FRED Middletown 020 MONT Brookville
Caroline 006 FRED Mount Airy 021 MONT Washington Grove
010 CARO Denton 007 FRED Myersville 022 MONT Kensington
020 CARO Federalsburg 008 FRED New Market 023 MONT Takoma Park
030 CARO Greensboro 009 FRED Rosemont
040 CARO Hillsboro 010 FRED Thurmont Prince George's
050 CARO Marydel 011 FRED Walkersville 072 PRIN New Carrollton
060 CARO Preston 012 FRED Woodsboro 073 PRIN Eagle Harbor
070 CARO Ridgely 074 PRIN Greenbelt
080 CARO Goldsboro Garrett 075 PRIN Berwyn Heights
090 CARO Henderson 264 GARR Accident 076 PRIN Bladensburg
100 CARO Templeville 300 GARR Deer Park 077 PRIN Bowie
312 GARR Friendsville 078 PRIN Brentwood
Carroll 324 GARR Grantsville 079 PRIN Capitol Heights
011 CARR Taneytown 336 GARR Kitzmiller 080 PRIN Cheverly
051 CARR Sykesville 348 GARR Loch Lynn Heights 081 PRIN College Park
061 CARR Manchester 360 GARR Mountain Lake Park 082 PRIN Colmar Manor
071 CARR Westminster 372 GARR Oakland 083 PRIN Cottage City
081 CARR Hampstead 084 PRIN District Heights
111 CARR New Windsor Harford 085 PRIN Edmonston
121 CARR Union Bridge 200 HARF Aberdeen 086 PRIN Fairmount Heights
131 CARR Mount Airy 300 HARF Bel Air 087 PRIN Glenarden
600 HARF Havre De Grace 088 PRIN Hyattsville
Cecil 089 PRIN Landover Hills
010 CECI Cecilton Howard 090 PRIN Laurel
020 CECI Chesapeake City No town codes 091 PRIN Mount Rainier
030 CECI Elkton 092 PRIN North Brentwood
040 CECI North East Kent 093 PRIN Riverdale
050 CECI Charlestown 010 KENT Betterton 094 PRIN Seat Pleasant
060 CECI Rising Sun 020 KENT Chestertown 096 PRIN University Park
070 CECI Port Deposit 030 KENT Galena 097 PRIN Upper Marlboro
080 CECI Perryville 040 KENT Millington 098 PRIN Morningside
050 KENT Rock Hall 099 PRIN Forest Heights
Charles
010 CHAR Indian Head Montgomery Queen Anne's
029 CHAR La Plata 001 MONT Friendship Heights 001 QUEE Sudlersville
030 CHAR Port Tobacco 002 MONT Drummond 002 QUEE Church Hill
003 MONT Oakmont 003 QUEE Centreville
Dorchester 004 MONT Chevy Chase Village 004 QUEE Queenstown
001 DORC Secretary 005 MONT Chevy Chase Sec. 3 005 QUEE Queen Anne
002 DORC East New Market 006 MONT Chevy Chase Town of 006 QUEE Templeville
003 DORC Cambridge 007 MONT Chevy Chase Sec. 5 008 QUEE Barclay
004 DORC Hurlock 008 MONT Martins Addition 040 QUEE Millington
005 DORC Vienna 009 MONT Chevy Chase North
006 DORC Church Creek 010 MONT Chevy Chase View St. Mary's
007 DORC Galestown 011 MONT Battery Park 100 STMA Leonardtown
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C6 of C22
Somerset Washington (continued) Worcester
001 SOME Crisfield 050 WASH Hancock 001 WORC Pocomoke
002 SOME Princess Anne 060 WASH Boonesboro 002 WORC Snow Hill
070 WASH Smithsburg 003 WORC Berlin
Talbot 100 WASH Funkstown 010 WORC Ocean City
001 TALB Easton 190 WASH Keedysville 101 WORC Ocean City
002 TALB St. Michaels 102 WORC Ocean City
003 TALB Trappe Wicomico 103 WORC Ocean City
004 TALB Oxford 001 WICO Salisbury 104 WORC Ocean City
005 TALB Queen Anne 002 WICO Mardela Springs 105 WORC Ocean City
003 WICO Pittsville 106 WORC Ocean City
Washington 004 WICO Sharptown 107 WORC Ocean City
010 WASH Sharpsburg 005 WICO Delmar 108 WORC Ocean City
020 WASH Williamsport 006 WICO Willards 109 WORC Ocean City
030 WASH Hagerstown 007 WICO Hebron
040 WASH Clear Spring 008 WICO Fruitland
Subdivision code. In Prince George's County only, the PLAT field is also used to assign subdivision codes − subdivision
codes in that county are assigned based on a combination of tax district, subdivision code and plat. Subdivision codes
and code descriptions are not included in the MdProperty View data documentation because the State Department of
Assessments and Taxation subdivision description list contains over 20,000 entries statewide.
Subdivision codes/descriptions are only used by the following jurisdictions: Allegany, Anne Arundel, Calvert, Cecil,
Charles, Garrett, Harford, Kent, Montgomery, Prince George's, Queen Anne's, St. Mary's, Somerset, Washington and
Worcester counties. Using Harford County as the example, see Harfsb08.dbf/.txt in the Datadocs\County folder on
each MdProperty View DVD for a detailed dataset and ASCII text file of subdivision codes and code descriptions.
Subdivision plat, where a plat is a piece of land divided into building lots. Contents of this field are usually a sequential
number assigned to a plat. Plat numbers in Prince George's County that begin with A or E may appear on property
maps as numbers only.
Subdivision plat section, block and lot and parcel map number, grid and parcel. The first four positions of MAP, GRID
and PARCEL must be numeric. Parcel map numbers that appear in MdProperty View datasets for Montgomery County
are the paper tax map numbers rather than the State Department of Assessments and Taxation dataset tax map
number equivalents used in previous editions of MdProperty View.
MdProperty View map group (counties). Consists of the last four characters of the file name of the ArcView project file
(view) containing the group of parcel map images for any given located parcel account. For example, an Allegany
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C7 of C22
County located parcel account in the ALLEG01.apr project file would have an MDPV_GROUP entry of G01.
MDPV_GROUP is empty for all located parcels in Baltimore City, because there are no map images to group in that
jurisdiction.
MDPV_GROUP contains UNLC for any unlocated county or Baltimore City parcel account. An unlocated parcel is any
parcel where the value of the parcel x (DIGXCORD) or y (DIGYCORD) coordinate is -9, -1 or 0, indicating that there is
no linkage between that parcel and a property map.
Zoning code. For an explanation of zoning codes used in a given jurisdiction, contact the determining zoning authority
or authorities in the jurisdiction you are using. Appendix J: Assessment Office Supervisors and Determining
Zoning Authorities (MdpUsr08.pdf) in the Datadocs folder contains a web link to a clickable map of determining
zoning authority contacts for each jurisdiction in Maryland.
Important – Read before using MdProperty View ZONING data in your projects
Data included in the ZONING fields found in the Parcel and Sale datasets are as received in the parcel download for
each jurisdiction provided to the Maryland Department of Planning (MDP) by the State Department of Assessments and
Taxation (SDAT). SDAT neither substantiates nor warrants the completeness or validity of entries in the
ZONING field.
Several variables may affect the quality of the zoning data available for a given jurisdiction. Zoning data may not be
updated to reflect current zoning changes in a jurisdiction. In some or many cases, no zoning data may be provided for
a given jurisdiction. Zoning decisions are made at the county or municipality level, and as such, may not be
communicated to SDAT.
MDP and SDAT strongly suggest that you verify data contained in the ZONING field with the determining zoning
authority or authorities in the jurisdiction you are using, which is the best and responsible source for timely and
accurate zoning data. Many jurisdictions make their GIS zoning layer available in electronic format. You can add this
layer as an overlay to your map in MdProperty View provided that it is available as a shapefile that is projected in
Maryland State Plane Coordinate System NAD83 meters.
Multiple zoning indicator: M for multiple zoning − cannot be filled in unless there are data in ZONING. Multiple family
indicator: F for multiple family dwelling.
Exempt status: 0 for taxable, 1 for exempt county, 2 for exempt state or 3 for exempt county and state. Exemption
class code (must be numeric) and code description. Exemption class code data must be 000 if EXSTATUS data are 0
(indicating a taxable property) or 999 if EXSTATUS data are unknown. EXCLASS must be filled with a numeric entry
ranging from 010 to 994 if EXSTATUS data are 1, 2 or 3. Exemption class codes are grouped as follows:
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C8 of C22
700-795 PVT Privately Owned Real Property
800-994 NPF Non-Profit or Charitable Organizations
Keywords are included in the descriptions contained in the DESCEXCL field to make it easier to select groups of
records by subject area. Keywords appear in the field at the beginning of each description. Appendix F: Exempt
Class Codes and Descriptions (MdpUsr08.pdf) in the Datadocs folder contains a detailed list of codes, code
descriptions and keywords.
Property factor utilities, water: 1 for public water 2 for private water or 0
Property factor utilities, sewer: 1 for public sewer 2 for private sewer or 0
May contain an alphabetic character indicating the type of income producing property:
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C9 of C22
Parcel Sale PFIH Character Field Width 1 Optional
Sale PFTL Character Field Width 1 Optional
Sale PFTR Character Field Width 1 Optional
Sale PFSR Character Field Width 1 Optional
Sale PFSI Character Field Width 1 Optional
LANDAREA converted to acres. Land area acres or square feet, as indicated by LUOM. Land area unit of measure: A for
acres or S for square feet. LUOM must be filled in if there are data in LANDAREA.
Effective width and effective depth. WIDTH must be filled in if there are data in DEPTH and DEPTH must be filled in if
there are data in WIDTH.
Current full market land value (appraised land value), current full market improvement value (appraised improvement
value) and current full market total value (land value plus improvement value). May be zero.
Date last inspected and assessed − the date must be numeric and the format must be YYYYMM. Assessor numeric code.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C10 of C22
Parcel Sale STRUCODE Character Field Width 10 Optional
Structure code, a coded identifier for type of structure. STRUCODE must be filled in if there are data in YEARBLT or
SQFTSTRC. This field is populated from the Computer Assisted Mass Appraisal (CAMA) dataset for residential properties.
Where there is a corresponding CAMA record for the structure, position 1 is always an M. For M records:
Position 2 is the CAMA quality of construction/grade code. Data are extracted to STRUGRAD and DESCGRAD. Position 2
is equivalent to DWLL_GRADE and DWLL_GDESC in the CAMA dataset.
Positions 3-4 are the CAMA type of construction code. Data are extracted to STRUCNST and DESCCNST. Data are
tracked in more detail in CAMA dataset dwelling sections 1-5 CONST and CDESC (SEC1_CONST, SEC1_CDSEC, and so
on).
Positions 5-6 are the CAMA number of stories code. Data are extracted to STRUSTRY and DESCSTRY. Data are tracked
in more detail in CAMA dataset dwelling sections 1-5 STORY and SDESC (SEC1_STORY, SEC1_SDSEC, and so on).
Positions 9-10 are the CAMA type of dwelling code. Data are extracted to STRUDWEL and DESCDWEL. Positions 9 and
10 are equivalent to DWLL_TYPE and DWLL_TDESC in the CAMA dataset.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C11 of C22
Parcel Sale STRUGRAD Character Field Width 1 MdProperty
Parcel Sale DESCGRAD Character Field Width 33 MdProperty
Parcel Sale STRUCNST Character Field Width 2 MdProperty
Parcel Sale DESCCNST Character Field Width 24 MdProperty
Parcel Sale STRUSTRY Character Field Width 2 MdProperty
Parcel Sale DESCSTRY Character Field Width 25 MdProperty
Parcel Sale STRUDWEL Character Field Width 2 MdProperty
Parcel Sale DESCDWEL Character Field Width 43 MdProperty
Where there is a corresponding Computer Assisted Mass Appraisal (CAMA) record for the structure:
• Type of construction code component (STRUCNST) of STRUCODE and Type of construction description
(DESCCNST) − see Positions 3-4 of STRUCODE.
• Number of stories code component (STRUSTRY) of STRUCODE and Number of stories description (DESCSTRY) −
see Positions 5-6 of STRUCODE.
• Type of dwelling code component (STRUDWEL) of STRUCODE and type of dwelling code description (DESCDWEL) −
see Positions 9-10 of STRUCODE.
Year structure was built (must be numeric and format CCYY). Must be filled in if there are data in STRUCODE or
SQFTSTRC.
Foundation square footage of the principal structure (may be zero). Must be filled in if there are data in STRUCODE or
YEARBLT.
Commercial and industrial property use code (must be numeric), used to identify the specific uses of improved
commercial/industrial properties. This field appears in Sale datasets earlier than in the Parcel dataset. See the full Parcel
dataset description of this field on Page C14 below.
Sale transfer number (must be numeric). Must be a number that has not been used previously.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C12 of C22
Parcel Sale GRNTNAM1 Character Field Width 34 Automatic
Sale grantor name (the name of the person who last sold the house). If not filled in through data entry, the previous
owner's name is used to automatically generate a grantor name.
Grantor deed reference 1 (most recent grantor) and deed reference 2 (prior) clerks’ initials (may be blank), liber (must
be numeric) and folio (must be numeric). If not filled in through data entry, data from the previous owner's deed
reference 1 and deed reference 2 are automatically used to generate these fields.
How conveyed (what kind of sale was it when the house was last sold). If the transfer date (TRADATE) is on or after
October 1, 1994, there are four possible values for "how conveyed":
If the transfer date (TRADATE) is prior to October 1, 1994, there are ten possible values for "how conveyed":
Total/partial transfer indicator: P for partial transfer or T for total transfer. Transfer date. Transfer date (must be
numeric, format YYYYMMDD).
Consideration (the amount of money paid for the property − may be zero) and mortgage.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C13 of C22
Parcel NFMLNDVL Numeric Field Width 9 Optional
Parcel NFMIMPVL Numeric Field Width 9 Optional
Parcel NFMTTLVL Numeric Field Width 11 MdProperty
New full market land value (appraised land value), new full market improvement value (appraised improvement value)
and new full market total value (land value plus improvement value). May be zero.
Critical area code: C for conservation area, L for limited development area or I for intensely developed area
Commercial and industrial property use code (must be numeric), used to identify the specific uses of improved
commercial/industrial properties. The code is also used to identify properties owned by public utilities and railroads
(both vacant and improved) and to indicate their status as to operating or non-operating. This field appears in Sale
datasets earlier than in the Parcel dataset. See Page C12 above.
Keywords are included in the descriptions contained in the DESCCIUSE field to make it easier to select groups of
records by subject area. Keywords appear in the field at the beginning of each description. New commercial and
industrial property use codes and code descriptions have been added for MdProperty View 2008 Edition. Appendix E:
Commercial and Industrial Use Codes and Descriptions (MdpUsr08.pdf) in the Datadocs folder contains a
detailed list of codes, code descriptions and keywords.
Personal property code: P for personal property was involved in the sale.
Grantor account number district and grantor account, used for partial transfers (must be numeric). GRDISTR1 and
grantor account number (GRACCT1) represent the account from which the new parcel was created.
Sale analysis code: 1 for non-arms-length transfer such as a foreclosure, gift or auction or 0 for unknown
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C14 of C22
Sale SALLNDVL Numeric Field Width 9 Optional
Sale SALIMPVL Numeric Field Width 9 Optional
Sale SALTTLVL Numeric Field Width 11 MdProperty
Sale land value (appraised land value), sale improvement value (appraised improvement value) and sale total value
(land value plus improvement value) of the property at the time of the sale. May be zero.
Improvement indicator: I for property was improved at the time of sale or V for property was vacant at the time of
sale.
Computer Assisted Mass Appraisal (CAMA) set number. Positions 1-2 are the district number, position 3 is a decimal
point separator and positions 4-5 are the neighborhood within the district. CAMA subset number, identifies further
subsets of the neighborhood contained within CAMA set number (CAMASET).
Non-condominium located parcels which were assigned the same x,y coordinate by the Computerized Property Mapping
Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels. "Stacked" non-
condominium parcels may be found in any or all MdProperty View datasets.
Condominium located parcels which were assigned the same x,y coordinate by the Computerized Property Mapping
Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels. "Stacked"
condominium parcels may be found in any or all MdProperty View datasets.
Baltimore County parcels that could not be located by the Maryland Department of Planning’s Computerized Property
Mapping Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels, but which
were subsequently geolocated externally. Geolocated parcels with a PTYPE of 22 may be found in any or all Baltimore
County datasets. PTYPE 22 parcels were geolocated externally using either MDP’s U.S. Census Bureau TIGER/Line 2004
file (First Edition, Spring 2005), MdLandbase file (State Highway Administration 1:24,000 roads circa 1992) or some
other external source such as aerial photography or Google Earth™.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C15 of C22
23 "stacked" property geolocated externally (Baltimore County only)
Baltimore County located parcels which were originally assigned the same x,y coordinate by the Computerized Property
Mapping Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels, and then
subsequently geolocated externally to achieve a better geographic distribution of the parcels. "Stacked" geolocated
parcels may be found in any or all Baltimore County datasets. PTYPE 23 parcels were geolocated externally using either
MDP’s U.S. Census Bureau TIGER/Line 2004 file (First Edition, Spring 2005), MdLandbase file (State Highway
Administration 1:24,000 roads circa 1992) or some other external source such as aerial photography or Google Earth™.
Baltimore City located parcels were geolocated externally using either MDP’s U.S. Census Bureau TIGER/Line 2004 file
(First Edition, Spring 2005), MdLandbase file (State Highway Administration 1:24,000 roads circa 1992) or some other
external source such as aerial photography or Google Earth™ and referenced using collateral materials (ortho-
photography, parcel images and Baltimore City street maps), resulting in enhanced spatial placement of the parcel x,y
reference points along the Baltimore City 1:24,000 road network. Baltimore City located parcels are found in all
Baltimore City datasets.
Number of dwellings on the property. Obtained from the Computer Assisted Mass Appraisal (CAMA) dataset for
residential properties only.
Number of dwelling units and total number of rooms on the property (may be zero), obtained as a special Computer
Assisted Mass Appraisal (CAMA) extract for commercial properties with residential uses only. Available for only for
properties where the commercial and industrial property use code (CIUSE) is a residential use code.
Year in which the dwelling was constructed. Obtained from the Computer Assisted Mass Appraisal (CAMA) dataset for
residential properties only.
Indicates whether ADDRESS, CITY and ZIPCODE contain cleaned-up combined street address data.
• New full market improvement value (NFMIMPVL) is equal to or greater than $1000.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C16 of C22
Parcel RESIUTHS Logical Field Width 1 MdProperty
Indicates whether a property is T for residential improved with a value less than $1000, based on the following criteria:
Indicates whether a property is T for residential improved with a value equal to or greater than $1000 and built in or
after 1990, based on the following criteria:
• New full market improvement value (NFMIMPVL) is equal to or greater than $1000.
• Computer Assisted Mass Appraisal (CAMA) year built (YRBLT_CAMA) is equal to or greater than 1990 and equal to
or less than 1999.
OR
Year built (YEARBLT) is equal to or greater than 1990 and equal to or less than 1999 and CAMA year built
(YRBLT_CAMA) is blank or equal to 0000.
Indicates whether a property is T for residential improved with a value equal to or greater than $1000 and built in or
after 2000, based on the following criteria:
• New full market improvement value (NFMIMPVL) is equal to or greater than $1000.
• Computer Assisted Mass Appraisal (CAMA) year built (YRBLT_CAMA) is equal to or greater than 2000 and equal to
or less than 2009.
OR
Year built (YEARBLT) is equal to or greater than 2000 and equal to or less than 2009 and CAMA year built
(YRBLT_CAMA) is blank or equal to 0000.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C17 of C22
Parcel APRTMENT Logical Field Width 1 MdProperty
Indicates whether a parcel is T for an apartment with a value equal to or greater than $1000, based on the following
criteria:
• Commercial and industrial property use code (CIUSE) is one of the following:
OR
• New full market improvement value (NFMIMPVL) is equal to or greater than $1000.
Indicates whether a property is T for a trailer park, based on the following criteria:
• Commercial and industrial property use code (CIUSE) is: 03000 for HOUSING Trailer Park
Indicates whether a property is T for may house special populations, based on the following criteria:
• Commercial and industrial property use code (CIUSE) is one of the following:
OR
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C18 of C22
410 JUR Hospital/Health Related Facility county/Baltimore City
470 JUR Detention Center county/Baltimore City
Indicates whether a property is T for falls outside of any of the categories described above.
Contains the Parcel dataset record number for each property. The Parcel dataset is sorted in street address order.
Properties lacking a valid street address, which are properties with no data in ADDRESS, fall to the end of the dataset in
account number (ACCTID) order. Record numbers are loaded into SEQNUMB so that they appear sequentially in street
address order followed by account number order.
When working with the special jurisdiction-wide extracts of the Parcel dataset, sorting on SEQNUMB puts properties in
street address order for those properties with data in ADDRESS. All other properties fall to the end of the extract
datasets in account number (ACCTID) order.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C19 of C22
Downloading Sale Datasets
The Maryland Department of Planning (MDP) offers downloadable monthly Sale datasets on the Subscriber Website as
a way of keeping the MdProperty View Parcel dataset (Harf2008.shp) as up-to-date as possible. Sale datasets represent
a twelve-month history of jurisdiction sales transactions as recorded by the State Department of Assessments and
Taxation. The datasets include all transactions related to a given sale or transfer posted through the 10th of the month
that each set of Sale datasets is processed. After receiving, processing and compressing the data, MDP places the latest
Sale datasets in .zip files on the Subscriber Website prior to the end of each month for you to download.
Each MdProperty View Subscriber is assigned a unique username, based on the name of the person who signed the
MdProperty View License Agreement, and an initial password so they can access the Subscriber Website. If you don’t
already have a username and an initial password, or if you have any trouble downloading or working with MdProperty
View Sale datasets once you have read the following instructions, contact the MdProperty View Help Desk
The Subscriber Website is accessed via your Internet service provider at:
http://www.mdp.state.md.us/mdpview
You are prompted to type in your username and password. Your username and password are case-sensitive, so type
carefully. This takes you to your MdProperty View account on the Subscriber Website home page − the Subscriber
Website defaults to the MdProperty View area when you first enter the website. From here you can download Sale
datasets for the jurisdictions you subscribe to. On the Subscriber Website home page you see the following links:
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions
This link displays a copy of the document you are reading right now.
Sale Datasets
This link takes you to a list of jurisdiction names that are hypertext links to the Sale datasets.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions
Appendix E: Commercial and Industrial Property Use Codes and Descriptions
Appendix F: Exempt Class Codes and Descriptions
To download the current MdProperty View Harford County Sale dataset, click on the Sale Datasets link and then click on
Harford County. You find another hypertext link to the current file available for Harford County. Begin the download
process by clicking on the hyperlink.
Some Internet browsers prompt you with a message asking what file type is being downloaded or asking what you
want to do with the file. Select Save this file to disk and click OK to download. Be sure you have enough hard drive
space and remember to save files to a folder on your hard drive that is convenient and that you will remember. Most
Subscribers download to a TEMP folder.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C20 of C22
Naming conventions for MdProperty View Sale datasets are: the first four characters of the file name indicate the
jurisdiction (for example, Harf indicates Harford County) and the next four characters indicate the month and year the
Sale data were obtained from the State Department of Assessments and Taxation (0908 indicates September of 2008):
Harf0908 .zip
Sale datasets on the Subscriber Website are compressed, or zipped, to save disk space. The two most popular
decompression software tools available are available at:
Click on the Go to Compression Software Sites link from the Subscriber Website home page to go to either of the
compression software sites.
We suggest that once you have downloaded a Sale file, you unzip and place it in a separate folder that is not part of
the root folder tree associated with files that you received on your MdProperty View DVD. For example, you could
create a folder called Sale under your root folder. That way, if you need to remove MdProperty View data associated
with a given jurisdiction from your hard drive, you will not erase the Sale datasets you have downloaded.
We have also found it helpful to set up separate subfolders for each jurisdiction in which to save Sale datasets, new
project files, related new data extracts and themes, etc. For example, under Sale you could have a folder named
HARF for Harford County Sale datasets and one named HOWA for Howard County Sale datasets. If you use separate
folders, you can erase and restore original MdProperty View jurisdiction data without having to recreate the ArcGIS
map document file or ArcView project files if you have limited hard drive space.
Once Sale datasets have been decompressed, they are ready to use with MdProperty View. Five files are unzipped from
every .zip file. One file is a database with a .dbf extension, and the other four files with .shp/.shx/.sbn/.sbx extensions
help reference the dataset in ArcGIS or ArcView. An entire dataset of this type is referred to as a shapefile.
Remember to copy all files to a folder where you can find them and where they will be safe should you decide to delete
the MdProperty View jurisdiction you are working on.
To display a shapefile in ArcGIS 9.x, select Add Data… from the File Menu. When the Add Data dialog box appears,
browse to the folder that contains the file you just downloaded. The file that appears in the dialog box has a .shp
extension. Click OK to create a new layer for the Sale dataset.
The new layer appears at the top of the data frame Table of Contents. Click the check box in front to display the Sale
dataset. At this point you may wish to change the color and symbol set used to display the file by changing the
Properties of the layer − see the ArcGIS 9.x software documentation or ArcGIS Online Help for details on
changing layer properties. Choosing a larger symbol and a contrasting color can help differentiate Sale dataset
properties from existing MdProperty View parcel points.
To display a shapefile in ArcView, first make the desired view active then choose Add Theme from the View Menu.
When the dialog box appears, browse to the folder that contains the file you just downloaded. The file that appears in
the dialog box has a .shp extension. Click OK to add the new Theme for the Sale dataset.
The new theme appears at the top of the view Table of Contents. Click the check box in front to display the Sale
dataset. At this point you may wish to change the color and symbol set used to display the file by using the Theme
Editor − see the ArcView 3.x software documentation or ArcView Online Help for details on using the theme
editor. Choosing a larger symbol and a contrasting color can help differentiate Sale dataset properties from existing
MdProperty View parcel points.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C21 of C22
Updating Your Subscriber Password and Email Address
You can and should periodically change your password in the Subscriber Website. We encourage you to do this after
logging on with the initial password we provide to you. To change your password, click on the following link found
along the left side of the home page:
Update Profile
Highlight your current password and replace it with one of your choosing. You may use any combination of letters and
numbers up to 10 characters in length, but not spaces or special characters. When you create your new password,
remember that passwords are case-sensitive.
You may also change your email address at the same time you change your password. Please remember to keep your
email address current by checking it the each time you log on. This will be important if you ever forget your password.
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page C22 of C22
Appendix D: CAMA Dataset Structure
The Computer Assisted Mass Appraisal (CAMA) dataset is created on a yearly basis using data obtained from the State
Department of Assessments and Taxation (SDAT). Each yearly download contains additional residential housing
characteristics as available for parcels included in the CAMA dataset and the CAMA supplementary datasets for each
jurisdiction.
MdProperty View CAMA data resides in five datasets, the CAMA dataset (for example, Harfcama.shp) and four CAMA
supplementary datasets. The CAMA dataset is available on each MdProperty View DVD, and the CAMA supplementary
datasets are available for download from the Subscriber Website at:
http://www.mdp.state.md.us/mdpview
This document only covers the CAMA dataset − the CAMA supplementary datasets are discussed in CAMA
Supplementary Dataset Structure and Download Instructions (CamSup08.pdf), available on the Subscriber
Website.
The CAMA dataset contains those data characteristics that are basic to every dwelling. Subscribers receive CAMA data
for all dwellings on a particular property − this means that the CAMA dataset may contain multiple records for a single
property if that property contains more than one dwelling. Each record with the same parcel account number (ACCTID
field) is an individual data record for dwelling 001, 002, etc. found on the property associated with that parcel account
number.
The CAMA dataset also contains selected summarized features, accessory structures and other land data from three of
the CAMA supplementary datasets, which gives Subscribers access to a full range of data for all dwellings on a
property, including other land designations assigned to a given property. These selected summarized data are available
for a broad spectrum of data characteristics, and should serve the needs of most MdProperty View Subscribers − the
majority of Subscribers will not need to access the CAMA supplementary datasets.
Two new dwelling type codes (DWLL_TYPE field) and descriptions (DWLL_TDESC field) have been added to the CAMA
dataset by SDAT: 014 cond0minium parking space and 015 condominium storage unit. These codes and descriptions
are primarily used in Maryland’s five largest jurisdictions: Anne Arundel, Baltimore, Montgomery and Prince George’s
counties and Baltimore City.
In an effort to offer timely Residential CAMA data to Subscribers, CAMA data obtained from SDAT in January of 2008
are used in 2008 Edition releases of MdProperty View until updated data are obtained from SDAT in January of 2009.
Once updated Residential CAMA data are received in January of 2009, the new data will be used in the remaining 2008
Edition releases of MdProperty View and in the initial 2009 Edition releases.
Because of the way CAMA data are included in MdProperty View, this data document applies to both the 2007 and 2008
Editions of the product, because 2007 Edition jurisdictions issued during and after January of 2008 include January of
2008 CAMA data. This means that any references below to the 2008 Edition CAMA (CAMADATA) datasets also apply to
the 2007 Edition CAMA dataset.
Fields are described below in the order in which they appear in the CAMA dataset. Dataset fields are listed as Optional,
Required or Automatic (computer generated) for State Department of Assessments and Taxation purposes. Dataset
fields listed as MdProperty were created by the Maryland Department of Planning exclusively for MDP’s DVD products.
Linking field used to join the CAMA dataset to the CAMA supplementary datasets. Data contained in the CAMALINK field
are a combination of parcel account number (ACCTID field) and dwelling number (DWLL_NUMB field).
Parcel account number, a unique identifier for each account within any jurisdiction.
• For Anne Arundel County: positions 1-2 are the jurisdiction (county) code, positions 3-4 are the tax district,
positions 5-7 are the subdivision, positions 8-15 are the parcel account number and the remaining position is blank.
• For Baltimore City: positions 1-2 are the jurisdiction (city) code, positions 3-4 are the ward, positions 5-6 are the
section, positions 7-10 or 7-11 are the block (position 11 may be blank for some parcels), positions 12-14 or 12-15
are the lot (position 15 may be blank for some parcels) and the remaining position is blank.
• For all other counties: positions 1-2 are the jurisdiction (county) code, positions 3-4 are the tax/election district
and the remaining positions up to 12 positions are the parcel account number.
Individual dwelling number out of a total number of dwellings on a particular property (for example, dwelling 002 out of
6 total dwellings on a particular property). For properties with accessory structures or other land that contain
no dwellings, the value of this field is 999.
In MdProperty View, the parcel x and y coordinates for all jurisdictions are in the NAD83 meters version of the Maryland
State Plane Coordinate System. If the value of the parcel x or y coordinate is -9, -1 or 0, there is no linkage between a
tax map and MdProperty View datasets for the record.
Alternate x and y coordinates (NAD27 feet and NAD83 feet) are available for each parcel in the jurisdiction CORD
dataset, which is placed on the Subscriber Website as each jurisdiction is completed for the current Edition of
MdProperty View.
Census 2000 census tract and block group: position 1-2 are the State code (024), positions 3-5 are the jurisdiction FIPS
code, positions 6-11 are the census tract and position 12 of BG2000 is the census block group.
Subdivision plat section, block and lot and parcel map number, grid and parcel. The first four positions of MAP, GRID
and PARCEL must be numeric. Parcel map numbers that appear in MdProperty View datasets for Montgomery County
are the paper tax map numbers rather than the State Department of Assessments and Taxation dataset tax map
number equivalents used in previous editions of MdProperty View.
Computer Assisted Mass Appraisal (CAMA) set number. Positions 1-2 are the district number, position 3 is a decimal
point separator and positions 4-5 are the neighborhood within the district. CAMA subset number, identifies further
subsets of the neighborhood contained within CAMA set number (CAMASET).
001 low cost: The lowest dwelling unit providing minimal shelter − generally built without plans using economy
materials, and may meet minimum building codes. Construction is usually performed by the owner or by people with
limited skills. Service equipment is inexpensive or non-existent. Older dwellings in this class may have numerous add-
ons that may not complement the main structure. This is low quality construction and is the lowest quality grade in the
residential costing system.
003 fair: Homes in this grade usually meet minimum local building codes. Standard plans are used and there is some
exterior ornamentation. Workmanship and materials are acceptable and service equipment consists of stock type items.
These residences are typically mass-produced with overall quality being slightly below average.
004 average: Homes in this grade usually meet and may exceed current local building codes. Modified standard plans
are used, with some exterior ornamentation and interior refinements. Materials and service equipment are of standard
grade and construction is supervised. These dwellings are mass-produced and are encountered more often than
residences of other quality grades.
005 good: Dwellings in this construction grade generally include individual designed mass-produced homes in better
subdivisions. Homes are built from designer plans, using skilled craftsmen and standard to good materials throughout.
There is exterior ornamentation and interiors are well finished.
006 very good: Homes in this construction grade generally include those designed for individual homeowners using
good quality materials throughout. Construction is supervised by a competent builder. These homes may be built in
better than average developments. In the construction of this grade of home, there is more emphasis on detail of both
exterior and interior refinements.
007 excellent: Dwellings in this construction grade are designed for individual homeowners and are characterized by
excellent quality materials throughout. Supervision is by a competent builder with architectural supervision.
Workmanship, interior finishes and appointments and exterior ornamentation are of the highest quality. While unique in
design and quality, these costs are not the highest cost quality grade.
008 luxury: Residences in this construction grade are designed for individual owners using excellent quality materials
with construction supervised by an architect. These homes are built from detailed architectural plans and written
specifications by a custom builder using the best grade materials throughout. In the construction of this grade
residence, there is major emphasis on detail of both exterior and interior refinements performed by craftsmen. This is
the next to highest quality grade residential costing system before individual quality adjustments.
009 luxury plus: Residences in this construction grade are of the highest luxury quality grade. They are designed for
individual owners using exclusive quality materials with construction supervised by an architect. These homes are built
from detailed architectural plans and written specifications by a custom builder using the best grade materials
throughout. In the construction of this grade residence, there is major emphasis on detail of both exterior and interior
appointments performed by craftsmen. This is the highest quality grade in the residential costing system. These
residences are characterized by the use of extraordinary materials and workmanship.
000 no data
Year in which the dwelling was constructed. Obtained from the Computer Assisted Mass Appraisal (CAMA) dataset for
residential properties only.
Number of combined air conditioning systems (CAIR_NUMB) and total enclosed square feet for all combined air
conditioning systems (CAIR_ENCL) summarized from source features data for records with the following code: 047 air
conditioning combined system
Number of separate air conditioning systems (SAIR_NUMB) and total enclosed square feet for all separate air
conditioning systems (SAIR_ENCL) summarized from source features data for records with the following code: 048 air
conditioning separate system
Number of full baths (FBTH_NUMB). Number of half baths (HBTH_NUMB) summarized from source features data for
records with the following code: 050 half bath
Construction material code (SEC1_CONST, SEC2_CONST, SEC3_CONST, SEC4_CONST) and description (SEC1_CDESC,
SEC2_CDESC, SEC3_CDESC, SEC4_CDESC) of sections 1 through 4 of the dwelling:
Square feet of sections 1 through 4 of the dwelling (SEC1_SQFT, SEC2_SQFT, SEC3_SQFT, SEC4_SQFT).
Story height code (SEC1_STORY, SEC2_STORY, SEC3_STORY, SEC4_STORY) and description (SEC1_SDESC,
SEC2_SDESC, SEC3_SDESC, SEC4_SDESC) of sections 1 through 4 of the dwelling:
Perimeter linear feet of section 1 of the dwelling (SEC1_PERLF) and perimeter linear feet of all sections of the dwelling
(TOTL_PERLF).
Cumulative foundation square feet of all sections of the dwelling (FNDAT_SQFT) and cumulative total square feet of the
dwelling, including both finished and unfinished areas multiplied by the story height of each section of the dwelling
(ENCLS_SQFT). Cumulative total square feet of the dwelling may not include the attic or basement finished
areas.
Square feet either negative or positive as a partial basement adjustment to the dwelling. Data in this field may be either
negative or positive square feet as an adjustment for the presence or absence of a basement under a section of a
dwelling when the structure story height of all sections is the same except for the presence or absence of a basement.
Number of storage rooms over garage (SOGR_NUMB) and total square feet for all storage rooms over garage
(SOGR_SQFT) summarized from source features data for records with the following code: 015 storage over garage
Number of rooms over garage (ROGR_NUMB) and total square feet for all rooms over garage (ROGR_SQFT)
summarized from source features data for records with the following code: 016 room over garage
Number of basements under (BSUN_NUMB) and total square feet for all basements under (BSUN_SQFT) summarized
from source features data for records with the following code: 017 basement under
Number of basement rooms (BSRM_NUMB) summarized from source features data for records with the following code:
027 basement room
Number of basement bedrooms (BSBD_NUMB) summarized from source features data for records with the following
code: 028 basement bedroom
Number of attic rooms (ATTC_NUMB) and total square feet for all attic rooms (ATTC_SQFT) summarized from source
features data for records with the following code: 038 attic room
A positive number in the ATTC_SQFT field indicates the square footage of an attic room and a negative
number indicates the square footage of an unfinished attic.
Number of finished basements (BSFN_NUMB) and total square feet for all finished basements (BSFN_SQFT)
summarized from source features data for records with the following code: 039 finished basement
Number of regular attached garages (ATGR_NUMB) and total square feet for all regular attached garages (ATGR_SQFT)
summarized from source features data for records with the following codes:
073 attached garage frame 075 attached garage stone 077 attached garage basement
074 attached garage brick 076 attached garage built-in
Number of carport attached garages (ATCP_NUMB) and total square feet for all carport attached garages (ATCP_SQFT)
summarized from source features data for records with the following code: 078 attached garage carport
Number of regular detached garages (DTGR_NUMB) and total square feet for all regular detached garages
(DTGR_SQFT) summarized from source accessory structures data for records with the following codes:
Number of carport detached garages (DTCP_NUMB) and total square feet for all carport detached garages
(DTCP_SQFT) summarized from source accessory structures data for records with the following code: 042 detached
garage carport
Number of wood-burning fireplaces summarized from source features data for records with the following codes:
Number of gas fireplaces summarized from source features data for records with the following codes:
084 1 story gas fireplace 085 2 story gas fireplace 086 3 story gas fireplace
Number of decks (DECK_NUMB) and total square feet for all decks (DECK_SQFT) summarized from source features
data for records with the following codes:
Number of porches (PRCH_NUMB) and total square feet for all porches (PRCH_SQFT) summarized from source features
data for records with the following codes:
062 porch with no roof 064 2 story open porch 066 enclosed porch
063 1 story open porch 065 3 story open porch
Number of patios (PTIO_NUMB) and total square feet for all patios (PTIO_SQFT) summarized from source features data
for records with the following codes:
Number of saunas (SAUN_NUMB) summarized from source features data for records with the following code: 009
sauna.
Number of whirlpools (WHRL_NUMB) summarized from source features data for records with the following code: 010
whirlpool
Number of hot tubs (HTUB_NUMB) summarized from source features data for records with the following code: 013 hot
tub
Number of fiberglass spas (FBSP_NUMB) summarized from source features data for records with the following code:
011 fiberglass spa
Number of concrete spas (CNSP_NUMB) summarized from source features data for records with the following code:
012 concrete spa
Number of vinyl pools (VNPL_NUMB) and total square feet for all vinyl pools (VNPL_SQFT) summarized from source
accessory structures data for records with the following code: 001 vinyl pool
Number of concrete pools (CNPL_NUMB) and total square feet for all concrete pools (CNPL_SQFT) summarized from
source accessory structures data for records with the following code: 002 concrete pool
Number of concrete tennis courts (CNTC_NUMB) and total square feet for all concrete tennis courts (CNTC_SQFT)
summarized from source accessory structures data for records with the following code: 005 concrete tennis court
Number of asphalt tennis courts (ASTC_NUMB) and total square feet for all asphalt tennis courts (ASTC_SQFT)
summarized from source accessory structures data for records with the following code: 006 asphalt tennis court
Number of attached greenhouses (AGRN_NUMB) and total square feet for all attached greenhouses (AGRN_SQFT)
summarized from source accessory structures data for records with the following code: 024 attached greenhouse
Number of residential greenhouses (RGRN_NUMB) and total square feet for all residential greenhouses (RGRN_SQFT)
summarized from source accessory structures data for records with the following code: 008 residential greenhouse
Number of linear foot piers with no utilities (FTPR_NUMB) and total linear feet for all linear foot piers with no utilities
(FTPR_LNFT) summarized from source accessory structures data for records with the following codes:
Number of linear foot piers with utilities (UTPR_NUMB) and total linear feet for all linear foot piers with utilities
(UTPR_LNFT) summarized from source accessory structures data for records with the following codes:
014 pier with water 015 pier with electric 016 pier with water and electric
Number of linear foot pier additions (ADPR_NUMB) and total linear feet for all linear foot pier additions (ADPR_LNFT)
summarized from source accessory structures data for records with the following code: 017 pier addition
Number of pieces of class 2 farmland (CLS2_NUMB) and total acres for all pieces of class 2 farmland (CLS2_ACRE)
summarized from source other land data for records with the following code: 010 class 2 farmland
Number of pieces of class 3 farmland (CLS3_NUMB) and total acres for all pieces of class 3 farmland (CLS3_ACRE)
summarized from source other land data for records with the following codes: 011-089 class 3 farmland
Non-condominium located parcels which were assigned the same x,y coordinate by the Computerized Property Mapping
Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels. "Stacked" non-
condominium parcels may be found in any or all MdProperty View datasets.
Condominium located parcels which were assigned the same x,y coordinate by the Computerized Property Mapping
Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels. "Stacked"
condominium parcels may be found in any or all MdProperty View datasets.
Baltimore County parcels that could not be located by the Maryland Department of Planning’s Computerized Property
Mapping Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels, but which
were subsequently geolocated externally. Geolocated records with a PTYPE of 22 may be found in any or all Baltimore
County datasets. PTYPE 22 parcels were geolocated externally using either MDP’s U.S. Census Bureau TIGER/Line 2004
file (First Edition, Spring 2005), MdLandbase file (State Highway Administration 1:24,000 roads circa 1992) or some
other external source such as aerial photography or Google Earth™.
Baltimore County located parcels which were originally assigned the same x,y coordinate by the Computerized Property
Mapping Section based on the MAP, GRID, PARCEL, SECTION, BLOCK and LOT data available for the parcels, and then
subsequently geolocated externally to achieve a better geographic distribution of the parcels. "Stacked" geolocated
parcels may be found in any or all Baltimore County datasets. PTYPE 23 parcels were geolocated externally using either
MDP’s U.S. Census Bureau TIGER/Line 2004 file (First Edition, Spring 2005), MdLandbase file (State Highway
Administration 1:24,000 roads circa 1992) or some other external source such as aerial photography or Google Earth™.
Baltimore City located parcels were geolocated externally using either MDP’s U.S. Census Bureau TIGER/Line 2004 file
(First Edition, Spring 2005), MdLandbase file (State Highway Administration 1:24,000 roads circa 1992) or some other
external source such as aerial photography or Google Earth™ and referenced using collateral materials (ortho-
photography, parcel images and Baltimore City street maps), resulting in enhanced spatial placement of the parcel x,y
reference points along the Baltimore City 1:24,000 road network. Baltimore City located parcels are found in all
Baltimore City datasets.
Commercial and Industrial Property Use Codes are used to identify the specific uses of improved commercial/industrial
properties. They are also used to identify properties owned by public utilities and railroads (both vacant and improved)
and indicate their status as to operating or non-operating.
The descriptions listed below are contained in the CIUSE and DESCCIUSE dataset fields in MdProperty View datasets.
Keywords are included in the descriptions to make it easier to select groups of records by subject area − they appear at
the beginning of each description as shown below. Please note that the commercial and industrial use property codes
shown below are not listed in exact numeric order by code, because codes are grouped by subject area.
Codes and code definitions are obtained from the State Department of Assessments and Taxation and are current as of
late August 2008. In some instances, discontinued codes may appear in MdProperty View datasets. Descriptions for
discontinued codes are provided where available, but discontinued codes and descriptions do not appear in the
following list. Codes new to MdProperty View 2008 Edition appear in burgundy.
00020 MISC Residence on Commercial or Industrial Zoned Land that receives a Rezoned Real Property Valuation
(See SDAT Procedure 019-120-010)
00050 MISC Common Use Facility that receives No Assessment or a Zero Value (See SDAT Procedure 014-055-010)
00060 MISC Property that cannot be physically located or plotted on a map and that receives a Zero Value
Appendix E: Commercial and Industrial Property Use Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page E1 of E6
Vehicle-Related Keyword: AUTO
Appendix E: Commercial and Industrial Property Use Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page E2 of E6
Bank-Related Keyword: BANK
60000 REC Recreational Property 60750 REC Miniature Golf/Driving Range/Batting Cage
60010 REC Amusement Park 60800 REC Handball/Racquetball Court
60020 REC Camp Ground 60850 REC Tennis Court
60030 REC Fair Ground 60900 REC Bowling Alley
60300 REC Golf Course/Subject To Use Agreement 60950 REC Roller/Ice Skating Rink
60400 REC Country Club/Subject To Use Agreement 61000 REC Social Club
60500 REC Golf Course 62000 REC Track
60550 REC Country Club/Golf Course 63000 REC Movie Theater
60600 REC Swimming Pool 80110 REC Museum
60700 REC Health Club
Appendix E: Commercial and Industrial Property Use Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page E3 of E6
Community-Related Keyword: COMMUNITY
For other TELECOM codes see the Utilities and Railroad Use Codes section below
Appendix E: Commercial and Industrial Property Use Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page E4 of E6
Operating Non-Operating Utilities and Railroads Use Codes
Property Property Gas Keyword: GAS
Appendix E: Commercial and Industrial Property Use Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page E5 of E6
Operating Non-Operating Utilities and Railroads Use Codes
Property Property Telecommunications Keyword: TELECOM
Appendix E: Commercial and Industrial Property Use Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page E6 of E6
Appendix F: Exempt Class Codes and Descriptions
Exempt class codes and descriptions contained in the EXCLASS and DESCEXCL dataset fields are grouped as follows:
The EXCLASS and DESCEXCL dataset fields appear in all MdProperty View datasets except the Computer Assisted Mass
Appraisal (CAMA) dataset and the Alternate Coordinates dataset. Data from the Parcel dataset are also grouped by exempt
class code into the following datasets located in the Extracts folder (using Harford County as the example):
Harf_pub.dbf Harf_pvt.dbf
Harf_sta.dbf Harf_npf.dbf
Harf_jur.dbf Harf_oth.dbf
Harf_mun.dbf
Keywords are included in the descriptions to make it easier to select groups of records by subject area. Keywords appear in
the field at the beginning of each description as shown below. Codes and code definitions are obtained from the State
Department of Assessments and Taxation and are current as of late August 2008. No new exempt class codes were
added to MdProperty View 2008 Edition.
Exemption Class Codes not extracted for MdProperty View Keyword: NOT EXTRACTED
000 NOT EXTRACTED Taxable Property 999 NOT EXTRACTED Unknown Tax Status
Public Owned Real Property or USA Federal Property: Harf_pub.dbf Keyword: PUB
Appendix F: Exempt Class Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page F1 of F3
County or Baltimore City Owned Real Property: Harf_jur.dbf Keyword: JUR
700 PVT Church/Rectory/Mosque/Synagogue 760 PVT Other such as the Salvation Army or Mission
710 PVT Church School 770 PVT Church Society/Club
720 PVT Church College 780 PVT Church Aged/Rehabilitation Home
730 PVT Church Cemetery 790 PVT Other
740 PVT Church Hospital/Health Related Facility 794 PVT Parking Lot
750 PVT Church Camp 795 PVT Parking Lot
Appendix F: Exempt Class Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page F2 of F3
All Other Classes of Real Property: Harf_oth.dbf Keyword: OTH
Appendix F: Exempt Class Codes and Descriptions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page F3 of F3
Appendix G: About Address Cleanup in the Parcel Dataset
When you use the Geocode Tool, your client or customer dataset fields are matched to street address fields in the Parcel
dataset (the STRTNUM, STRTDIR, STRTNAM, STRTTYP, STRTSFX and ZIPCODE fields). These fields are loaded with data
from State Department of Assessments and Taxation (SDAT) premise address fields (PREMSNUM, PREMSDIR, PREMSNAM,
PREMSTYP and PREMZIP). Where SDAT premise address data are not available, SDAT owner address data (OWNADD1 and
OWNERZIP) are used to load the geocoding fields if a property is owner occupied.
Data in Parcel dataset street address fields are cleaned up after source field data are loaded to increase your chances of
getting a good address match when you geocode your client or customer dataset. As part of the clean-up process, typos in
Parcel dataset street address fields are corrected, and all punctuation is removed. Spaces are removed where apostrophes
are removed (for example, O’CONNOR becomes OCONNOR), but retained where periods or dashes are removed (DEL-MAR
becomes DEL MAR).
Street address numbers, street address directionals and suffix directionals (N, NORTH, S, SOUTH, E, EAST, W, WEST, NW,
NE, SE and SW) and street address types (AVENUE, LANE, ROAD, etc.) are moved out of premise name before source data
are loaded if they were entered into that field by mistake. Also, certain types of street address names, and all street address
types, are standardized to current United States Postal Service (USPS) standards in Parcel dataset street address fields,
unless an alternate spelling can be verified on the USPS ZIP Code website. For example, the following street name changes
are made:
DOCTOR All occurrences of DOCTOR (DR. MUNSEY or DR MUNSEY) are spelled out in Parcel dataset geocoding fields
(DOCTOR MUNSEY)
FORT All occurrences of FORT (FT. MCHENRY or FT MCHENRY) are spelled out in Parcel dataset geocoding fields
(FORT MCHENRY)
GENERAL All occurrences of GENERAL (GEN. LEE or GEN LEE) are spelled out in Parcel dataset geocoding fields
(GENERAL LEE)
MOUNT All occurrences of MOUNT (MT. HOREB or MT HOREB) are spelled out in Parcel dataset geocoding fields
(MOUNT HOREB)
SAINT All occurrences of SAINT (ST. MARK or ST MARK) are spelled out in Parcel dataset geocoding fields (SAINT
MARK)
ROUTE All occurrences of ROUTE street names are standardized as in the following examples:
In some cases, street address types may be included in the Parcel dataset street address name field (STRTNAM) instead of
in the street address type field (STRTTYP). This might occur if a street address type could be followed by another street
address type, for example, street address name might be DEER PATH and street address type might be ROAD, or if the most
commonly used form of the street address type is different than the standard USPS abbreviation for that street type, for
example, instead of street address name FORREST and street address type HTS, street address name FORREST HEIGHTS.
Appendix G: About Address Cleanup in the Parcel Dataset MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page G1 of G3
Street address types usually included in street address name are:
In some jurisdictions, more that one premise address number (PREMSNUM field) may be assigned to the same parcel
account number. Often the additional premise numbers appear in the State Department of Assessments and Taxations
(SDAT) legal description fields (LEGAL1 or LEGAL2 field) or in SDAT premise name (PREMSNAM field), as in the following
example:
Premise number: 101 Premise name: 103 105 107 MAIN Premise type: ST
In the Parcel dataset, these additional premise numbers are extracted and placed in street address unit (STRTUNT field), so
that the example above appears as:
STRTNUM: 101 STRTNAM: MAIN STRTTYP: ST STRTUNT: ALSO 103 THRU 107
The same method is used to handle 1/2 premise numbers, as in the example below:
Premise number: 101 Premise name: 101 1/2 MAIN Premise type: ST
Similarly, any apartment unit information that appears in the SDAT premise name field is also moved to street address unit.
Using the following example, if an address appears as follows in the SDAT parcel record:
Boat slip information that appears in the SDAT premise number field remains in street address number, but street address
name (which usually contains premise name information, but in the case of a boat slip, contains the condominium name that
the boat slip is attached to) is altered to include the words BOAT SLIP. Street address unit is then altered to contain the
actual physical location (the street address name) of the condominium if that information can be obtained from legal
description. Using the following example, if an address appears as follows in the SDAT parcel record:
Appendix G: About Address Cleanup in the Parcel Dataset MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page G2 of G3
In the Parcel dataset, the address appears as:
In addition to the field content improvements described above, three overall improvements to the address cleanup process
help make the geocoding process more reliable than ever before:
• Street address suffix directional (STRTSFX field) is included in the Parcel dataset. This improves the quality of the
directional information used for geocoding, because suffix directionals are included in the Parcel dataset, rather than
being dropped as in pre-2003 Editions of MdProperty View.
• ZIP code cleanup is improved. Where 5-digit ZIP codes are not available through premise ZIP code (PREMZIP field) or
owner ZIP code (OWNERZIP field) source information obtained from SDAT, the ZIPCODE field is populated by overlaying
Parcel dataset parcel points with 2008 ZIP Code boundaries which have been updated to reflect current geography. The
resulting ZIP code assignments for each parcel record are then checked for accuracy against current USPS ZIP code
information to ensure that ZIP code assignments for a given geographic area have not changed since the 2008 ZIP Code
boundary file was created.
• During ZIP code cleanup for jurisdictions with subdivisions, probable ZIP codes are assigned to properties in the Parcel
dataset that may be too new to have received ZIP code assignments from the USPS or to be assigned x,y coordinates in
the Parcel dataset. For these new properties, probable ZIP codes are assigned based on the ZIP code location of the
subdivision that contains the properties.
• City names are standardized to the United States Postal Service (USPS) city associated with each ZIP code in a given
jurisdiction. Where city names are not available through the premise city (PREMCITY field) or owner city (OWNCITY
field) source information obtained from SDAT, the CITY field is populated with the USPS city where a ZIP code can be
determined for a given address.
Appendix G: About Address Cleanup in the Parcel Dataset MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page G3 of G3
Appendix H: Alternate Coordinates Dataset Structure and Download Instructions
Alternate parcel x,y coordinates are available in the jurisdiction CORD dataset on the Subscriber Website in compressed
(.zip) file format (for example, Harfcord.zip). The Alternate Coordinates (CORD) dataset is placed on the website as
each jurisdiction is completed for the current Edition of MdProperty View.
Dataset fields are listed as Optional, Required or Automatic (computer generated) for State Department of Assessments
and Taxation purposes. Dataset fields listed as MdProperty were created by the Maryland Department of Planning
exclusively for MDP’s DVD products.
Parcel account number, a unique identifier for each account within any jurisdiction.
• For Anne Arundel County: positions 1-2 are the jurisdiction (county) code, positions 3-4 are the tax district,
positions 5-7 are the subdivision, positions 8-15 are the parcel account number and the remaining position is blank.
• For Baltimore City: positions 1-2 are the jurisdiction (city) code, positions 3-4 are the ward, positions 5-6 are the
section, positions 7-10 or 7-11 are the block (position 11 may be blank for some parcels), positions 12-14 or 12-15
are the lot (position 15 may be blank for some parcels) and the remaining position is blank.
• For all other counties: positions 1-2 are the jurisdiction (county) code, positions 3-4 are the tax/election district
and the remaining positions up to 12 positions are the parcel account number.
In MdProperty View, the parcel x and y coordinates for all jurisdictions are in the NAD83 meters version of the Maryland
State Plane Coordinate System. If the value of the parcel x or y coordinate is -9, -1 or 0, there is no linkage between a
tax map and MdProperty View datasets for the record.
Parcel x and y coordinates in the NAD27 feet. If the value of the parcel x or y coordinate is -9, -1 or 0, there is no
linkage between the map and MdProperty View datasets for the record.
Appendix H: Alternate Coordinates Dataset Structure and Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page H1 of H4
NAD83F_X Numeric Field Width 9 Decimal Places 1 MdProperty
NAD83F_X Numeric Field Width 9 Decimal Places 1 MdProperty
Parcel x and y coordinates in the NAD83 feet. If the value of the parcel x or y coordinate is -9, -1 or 0, there is no
linkage between the map and MdProperty View datasets for the record.
Parcel x and y coordinates in the NAD83 meters. If the value of the parcel x or y coordinate is -9, -1 or 0, there is no
linkage between the map and MdProperty View datasets for the record.
Appendix H: Alternate Coordinates Dataset Structure and Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page H2 of H4
Downloading Alternate Coordinate Datasets
Harford County is used as the example jurisdiction throughout the download instructions. Please
substitute your current jurisdiction as applicable.
As mentioned above, Alternate Coordinates (CORD) datasets are placed on the Subscriber Website in compressed (.zip)
file format as each jurisdiction is completed for the current Edition of MdProperty View. Each MdProperty View
Subscriber is assigned a unique username, based on the name of the person who signed the MdProperty View License
Agreement, and an initial password so they can access the Subscriber Website. If you don’t already have a username
and an initial password, or if you have any trouble downloading or working with Alternate Coordinates datasets once
you have read the instructions below, contact the MdProperty View Help Desk:
The Subscriber Website is accessed via your Internet service provider at:
http://www.mdp.state.md.us/mdpview
You are prompted to type in your username and password. Your username and password are case-sensitive, so type
carefully. This takes you to your MdProperty View account on the Subscriber Website home page. From here you can
download Alternate Coordinates datasets for the jurisdictions you subscribe to. On the Subscriber Website home page
you see the following links:
CORD datasets
This link takes you to a list of jurisdiction names that are hypertext links to the Alternate Coordinates (CORD)
datasets.
To download the Alternate Coordinates dataset for Harford County, click on the CORD datasets link and then click on
Harford County. You will find another hypertext link to the file available for the jurisdiction. Begin the download process
by clicking on the file you wish to download.
Some Internet browsers prompt you with a message asking what file type is being downloaded or asking what you
want to do with the file. Select Save this file to disk and click OK to download. Be sure you have enough hard drive
space and remember to save files to a folder on your hard drive that is convenient and which you will remember. Most
Subscribers download to a TEMP folder.
Naming conventions for the Alternate Coordinates datasets are: the first four characters of the file name indicate the
jurisdiction (for example, HARF indicates Harford County) plus CORD for Alternate Coordinates dataset. The Alternate
Coordinate dataset for Harford County is:
Harfcord .zip
Alternate Coordinates datasets on the Subscriber Website are compressed, or zipped, to save disk space. The two most
popular decompression software tools available are available at:
Click on the Go to Compression Software Sites link from the Subscriber Website home page to go to either of the
compression software sites.
Appendix H: Alternate Coordinates Dataset Structure and Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page H3 of H4
We suggest that once you have downloaded files, you unzip and place them in a separate folder that is not part of the
root folder tree associated with files that you received on your MdProperty View DVD. For example, you could create a
folder called Cord under your root folder. That way, if you need to remove MdProperty View data associated with a
given jurisdiction from your hard drive, you will not erase the CORD datasets you have downloaded.
It is not necessary to set up separate folders for each jurisdiction in which to save CORD datasets, because CORD
datasets are not generally used on their own in MdProperty View. Instead, they are usually joined to another
MdProperty View dataset such as the Parcel, CAMA or Sale dataset and used to update that dataset with alternate x,y
coordinates in the event you wish to work with MdProperty View data using the NAD27 feet or NAD83 feet versions of
the Maryland State Plane Coordinate System.
You can and should periodically change your password in the Subscriber Website. We encourage you to do this after
logging on with the initial password we provide to you. To change your password, click on the following link found
along the left side of the home page:
Update Profile
Highlight your current password and replace it with one of your choosing. You may use any combination of letters and
numbers up to 10 characters in length, but not spaces or special characters. When you create your new password,
remember that passwords are case-sensitive.
You may also change your email address at the same time you change your password. Please remember to keep your
email address current by checking it the each time you log on. This will be important if you ever forget your password.
Appendix H: Alternate Coordinates Dataset Structure and Download Instructions MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page H4 of H4
Appendix I: Census View 2000 and Multi-State Census View 2000 CD-ROMs
A statewide CD-ROM containing Census 2000 reports that display census data for various geographic areas (see below)
is available as an adjunct CD-ROM product that can be used with ArcView 3.x and the 2002 Edition of MdProperty
View and above.
Using the statewide Census View 2000 CD-ROM, ArcView 3.x, Seagate Crystal Reports for ArcView 3.x and pre-
formatted report templates, you can generate 5 pages of profiles containing Census 2000 data. The Summary File 1
(SF1) profiles contain selected population (Profile 1) and household and housing unit (Profile 2) characteristics based on
questions asked of all persons and households in the 2000 Census. The Summary File 3 (SF3) profiles contain selected
social (Profile 3), economic (Profile 4) and detailed housing (Profile 5) characteristics based on questions asked of a
sample of persons and households in the 2000 Census. Profiles are available for the geographic areas in Maryland listed
below:
Profiles Number of
2000 Census Geographic Area Available Geographic Areas
State 1, 2, 3, 4, 5 1
State - Inside/Outside the Priority Funding Area (PFA) 1, 2 2
Counties and Baltimore City 1, 2, 3, 4, 5 24
Counties - Inside/Outside the Priority Funding Area (PFA) 1, 2 47
Incorporated Places (parts within county) 1, 2, 3, 4, 5 157
Census Designated Places (parts within county) 1, 2, 3, 4, 5 211
Census Minor Civil Divisions (MCDs) 1, 2, 3, 4, 5 293
Census Tracts 1, 2, 3, 4, 5 1,216
Census Block Groups 1, 2, 3, 4, 5 3,676
Census Tabulation Blocks 1, 2 77,076
ZIP Code Tabulation Areas (ZCTAs):
whole 1, 2, 3, 4, 5 452
parts, includes the same ZIP split by jurisdiction 1, 2, 3, 4, 5 527
Voting Districts 1, 2, 3, 4, 5 1,685
Congressional Districts 1, 2 8
county parts 1, 2 40
total/county parts 1, 2 48
Legislative Districts 1, 2 65
total/subtotal 1, 2 80
total/subtotal/county parts 1, 2 165
Urban Areas 1, 2 44
Urban Areas (county parts) 1, 2 89
User Defined Areas (1) 1, 2, 3, 4, 5 ???
(1) User Defined Areas profiles can be created by aggregating your geographic area(s) of interest to generate profile reports.
Printed samples of the current report templates using Census 2000 data are available. The Census View 2000 for
Maryland CD-ROM is available to MdProperty View Subscribers at a cost of $25. For more information about
Census View 2000 for Maryland, please email us at:
Appendix I: Census View 2000 and Multi-State Census View 2000 CD-ROMs MdProperty View copyright 1996-2008/09
ArcView and ArcGIS are registered trademarks of Environmental Systems Research Institute, Inc.
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page I1 of I2
Multi-State Census View 2000 CD-ROM
A multi-state CD-ROM containing Census 2000 reports that display census data for various geographic areas is
available. The Multi-State Census View 2000 CD-ROM product was developed to allow users to easily obtain census
information down to a small-area level for states within a 250 mile radius of central Maryland. This product is an
extremely useful tool for accessing and gathering Census 2000 data for economic development projects or marketing
studies within Maryland or any of the other included states.
The Multi-State Census View 2000 CD-ROM product enables users to identify and select Census 2000 geographic layers
(states, counties, census tracts, and block groups) of interest in Maryland, Delaware, New Jersey, New York, Ohio,
Pennsylvania, North Carolina, Virginia, West Virginia, Connecticut and the District of Columbia. Nineteen of Maryland’s
24 jurisdictions share boundaries with other states or the District of Columbia, making Multi-State Census View 2000
ideal for analyzing projects within a multi-state area.
Using the Multi-State Census View 2000 CD-ROM, ArcView 3.x, Seagate Crystal Reports for ArcView 3.x and pre-
formatted report templates, you can generate 5 pages of profiles containing Census 2000 data. The Summary File 1
(SF1) profiles contain selected population (Profile 1) and household and housing unit (Profile 2) characteristics based on
questions asked of all persons and households in the 2000 Census. The Summary File 3 (SF3) profiles contain selected
social (Profile 3), economic (Profile 4) and detailed housing (Profile 5) characteristics based on questions asked of a
sample of persons and households in the 2000 Census. Profiles are available for the geographic areas in Maryland listed
below:
Profiles Number of
2000 Census Geographic Area Available Geographic Areas
States 1, 2, 3, 4, 5 11
(1) User Defined Areas profiles can be created by aggregating your geographic area(s) of interest to generate profile reports.
Printed samples of the current report templates using Census 2000 data are available. The Multi-State Census View
2000 CD-ROM is available to MdProperty View Subscribers at a cost of $25. For more information about Multi-
State Census View 2000, please email us at:
Using Census View 2000 and Multi-State Census View 2000 with ArcGIS
Census View 2000 and Multi-State Census View 2000 are older products that were created for use with ArcView 3.x,
Seagate Crystal Reports for ArcView 3.x and the 2002 Edition of MdProperty View and above before MdProperty View
ArcGIS Version was available. The current Census View products are not optimized for use with ArcGIS 9.x, and the
Maryland Department of Planning has no plans to create ArcGIS 9.x versions of these products.
If you are interested in using the Census View shapefiles only as added layers with ArcGIS 9.x, the Census View 2000
for Maryland and Multi-State Census View 2000 CD-ROMs are available to MdProperty View Subscribers at a cost of $25
each. However, the report templates associated with each data set are not usable with the ArcGIS 9.x software.
Appendix I: Census View 2000 and Multi-State Census View 2000 CD-ROMs MdProperty View copyright 1996-2008/09
ArcView and ArcGIS are registered trademarks of Environmental Systems Research Institute, Inc.
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page I2 of I2
Appendix J: Assessment Office Supervisors and Determining Zoning Authorities
Contact information for State Department of Assessments and Taxation (SDAT) Assessment Office Supervisors is available on
the SDAT website at:
http://www.dat.state.md.us/sdatweb/county.html
Questions about data content may need to be addressed to Assessment Office Supervisors, especially for dataset fields not
identified as MdProperty in the following documents:
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions
Appendix D: CAMA Dataset Structure
Only questions and inquiries about data content or the valuation of real property should be directed to the offices listed
below. Please do not contact Assessments Office Supervisors with questions about ZONING field data.
Information about ZONING field data content should be addressed to the Determining Zoning Authorities in Maryland’s 24
jurisdictions and jurisdiction municipalities. Contact information for Determining Zoning Authorities is available on the
Maryland Department of Planning website at:
http://www.mdp.state.md.us/localplan/counties.html
The link leads you to a clickable map of Maryland, which in turn leads you to contact information for the Determining Zoning
Authorities. If you use ZONING data in your projects, please check the website often for the latest information available on
each Determining Zoning Authority, as listings change frequently.
Important – Read before using MdProperty View ZONING data in your projects
Data included in the ZONING fields found in MdProperty View Parcel and Sale datasets are as received in the parcel
download for each jurisdiction provided to the Maryland Department of Planning (MDP) by the State Department of
Assessments and Taxation (SDAT). SDAT neither substantiates nor warrants the completeness or validity of
entries in the ZONING field.
Several variables may affect the quality of the zoning data available for a given jurisdiction. Zoning data may not be updated
to reflect current zoning changes in a jurisdiction. In some or many cases, no zoning data may be provided for a given
jurisdiction. Zoning decisions are made at the county or municipality level, and as such, may not be communicated to SDAT.
MDP and SDAT strongly suggest that you verify data contained in the ZONING field with the determining zoning authority or
authorities in the jurisdiction you are using, which is the best and responsible source for timely and accurate zoning data.
Many jurisdictions make their GIS zoning layer available in electronic format. You can add this layer as an overlay to your
map in MdProperty View provided that it is available as a shapefile that is projected in Maryland State Plane Coordinate
System NAD83 meters.
Appendix J: Assessment Office Supervisors and Determining Zoning Authorities MdProperty View copyright 1996-2008/09
Prepared by the Maryland Department of Planning, Planning Data Services 09/10/2008 Page J1 of J1
Appendix K: 2007-2002 Residential Sales
MdProperty View now includes map layers of residential arms-length sales with improvements for calendar year (CY)
2007 through and including 2002. In ArcGIS, these map layers are not included in the MdProperty View custom menu,
but can be loaded into the data frame from the Harf2008\OVERLAYS\ResSale folder. In ArcView, these map layers are
part of the Overlays project file and can be brought in as a view within any other project file, such as the Master
project file, by importing the Overlays project file into a project file that contains parcel data and property maps
(counties) or detailed street maps (Baltimore City) and copying and pasting these themes into the current view.
There are separate map layer shapefile sets for each calendar year located in the Harf2008\OVERLAYS\ResSale folder
on each MdProperty View DVD. Each dataset record includes key attribute data including parcel account number,
transaction date and dollar consideration at time of sale, dwelling unit type (single family, townhouse, condominium,
mobile home), dwelling unit year built and various geographic area identifiers. The map layer shapefile sets are named:
The dataset linked to each of these map layers contains these fields:
Fields Description
ACCTID Parcel account number, a unique identifier for each parcel account in a county or Baltimore City
HU Housing unit type
TRADATE Transfer date
CONSIDR1 Consideration − the amount of money paid for the property
IMPVALUE New full market improvement value − appraised improvement value
YEARBLT Year the structure was built
COUNTY Jurisdiction FIPS code from U.S. Census Bureau
DESCTOWN Name of municipality
ZIPCODE1 Primary (5 digit) ZIP code
ZIPCODE2 Secondary (4 digit) ZIP code
ZIPNAME Name of the ZIP code
CT2000 2000 census tract number
BG2000 2000 census block group number
PFA Priority Funding Area
Appendix C: Parcel and Sale Dataset Structures and Sale Download Instructions contains detailed
descriptions of the source data used to create the fields listed above. The source of the data and the methodology
applied to extract the 2007 through 2002 residential arms-length sales with improvements data used to create the
shapefile sets are described in SalesMethodology_CY2007.pdf, SalesMethodology_CY2006.pdf,
SalesMethodology_CY2005.pdf and SalesMethodology_CY02thru04.pdf in the Harf2008\OVERLAYS\ResSale
folder.
These map layers can be loaded into MdProperty View ArcGIS Version or ArcView Version as described above. The
dataset linked to these summary map layers contains these fields:
Fields Description
MED_2007 Median dollar value of sales for the census tract in CY2007
MED_2006 Median dollar value of sales for the census tract in CY2006
MED_2005 Median dollar value of sales for the census tract in CY2005
MED_2004 Median dollar value of sales for the census tract in CY2004
MED_2003 Median dollar value of sales for the census tract in CY2003
MED_2002 Median dollar value of sales for the census tract in CY2002
MEAN_2007 Mean dollar value of sales for the census tract in CY2007
MEAN_2006 Mean dollar value of sales for the census tract in CY2006
MEAN_2005 Mean dollar value of sales for the census tract in CY2005
MEAN_2004 Mean dollar value of sales for the census tract in CY2004
MEAN_2003 Mean dollar value of sales for the census tract in CY2003
MEAN_2002 Mean dollar value of sales for the census tract in CY2002