This lookup tool has been developed to provide quick access to the property information stored in the City-Parish GIS database. Users can search by Address, Subdivision Name, Business Name, North American Industry Classification System (NAICS) Code, or Lot Identification Number to find detailed information about property. Enter the required information in one of the search fields as shown in the example below each field. Next, click the button adjacent to the search criteria, and the search results will be displayed beneath the lookup tools in tabular format. Clicking on one of the search result records will invoke a new window with details about the property. The property details may then be printed and/or exported to a comma-separated values (CSV) file.

Crime data assembled by census block group for the MSA from the Applied Geographic Solutions' (AGS) 1999 and 2005 'CrimeRisk' databases distributed by the Tetrad Computer Applications Inc. CrimeRisk is the result of an extensive analysis of FBI crime statistics. Based on detailed modeling of the relationships between crime and demographics, CrimeRisk provides an accurate view of the relative risk of specific crime types at the block group level. Data from 1990 - 1996,1999, and 2004-2005 were used to compute the attributes, please refer to the 'Supplemental Information' section of the metadata for more details. Attributes are available for two categories of crimes, personal crimes and property crimes, along with total and personal crime indices. Attributes for personal crimes include murder, rape, robbery, and assault. Attributes for property crimes include burglary, larceny, and mother vehicle theft. 12 block groups have no attribute information. CrimeRisk is a block group and higher level geographic database consisting of a series of standardized indexes for a range of serious crimes against both persons and property. It is derived from an extensive analysis of several years of crime reports from the vast majority of law enforcement jurisdictions nationwide. The crimes included in the database are the "Part I" crimes and include murder, rape, robbery, assault, burglary, theft, and motor vehicle theft. These categories are the primary reporting categories used by the FBI in its Uniform Crime Report (UCR), with the exception of Arson, for which data is very inconsistently reported at the jurisdictional level. Part II crimes are not reported in the detail databases and are generally available only for selected areas or at high levels of geography. In accordance with the reporting procedures using in the UCR reports, aggregate indexes have been prepared for personal and property crimes separately, as well as a total index. While this provides a useful measure of the relative "overall" crime rate in an area, it must be recognized that these are unweighted indexes, in that a murder is weighted no more heavily than a purse snatching in the computation. For this reason, caution is advised when using any of the aggregate index values. The block group boundaries used in the dataset come from TeleAtlas's (formerly GDT) Dynamap data, and are consistent with all other block group boundaries in the BES geodatabase. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Parcel Data for Baltimore City obatined from BNIA will all extraneous fields removed. Editing in progress The following edits were performed: 1) Resolved edge matching issues with Baltimore County parcels that border it and fall within the Gwynns Falls Watershed. 2) BLOCKLOT errors were noted and if necessary corrected. The BLOCKLOT ID is used to link the parcel data to the MD Property View A and T database. It should be pointed out that in some instances a single BLOCKLOT ID in the Property View A and T database may correspond to more than one parcel. There are only 14 instances were a single BLOCKLOT ID corresponds to 4 or more parcels, these are typically railroads, utility, or government properties. In other cases a single BLOCKLOT ID may correspond to two separate parcels that are essentially one property bisected by a road. There are other instances where there appears no logical explanation for a single BLOCKLOT ID corresponding to multiple parcels. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Assessments and Taxation (A and T) Database from MD Property View 2004 for Baltimore County. The A and T Database contains parcel data from the State Department of Assessments and Taxation; it 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 2004 Database, 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. Documentation for A and T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A and T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the A and T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A and T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 5870 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Viabundus.eu is a freely accessible online street map of late medieval and early modern northern Europe (1350-1650). Originally conceived as the digitisation of Friedrich Bruns and Hugo Weczerka's Hansische Handelsstraßen (1962) atlas of land roads in the Hanseatic area, the Viabundus map moves beyond that. It includes among others: a database with information about settlements, towns, tolls, staple markets and other information relevant for the pre-modern traveller; a route calculator; a calendar of fairs; and additional land routes as well as water ways.

Viabundus is a work in progress. Version 1.1, released on 6 December 2021, contains a rough digitisation of the land routes from Hansische Handelsstraßen, as well as a thoroughly researched road network for the current-day Netherlands, Denmark and the German states of Lower Saxony, Schleswig-Holstein, Thuringia and Saxony-Anhalt. The roads in the German states Mecklenburg-Vorpommern and Brandenburg, as well as the part of the former Duchy of Pomerania now in Poland, have been corrected for historical accuracy. The inclusion of other regions is currently being planned. Additions to the dataset will be released as new versions in the future.

The project's homepage viabundus.eu contains a web map application to explore the data. To allow for more advanced spatial and historical analyses, the underlying dataset is available for download under the CC-BY-SA license.

The dataset is designed as a network model and therefore consists of two main elements: 1) a relational database of nodes, i.e. geographical places, with historical information about settlements, towns, tolls, staple markets, fairs, bridges, ferries, harbours and shipping locks; 2) a database with edges, i.e. the geospatial representations of the land and water routes that connected these nodes. The entire database is available in CSV format (with geospatial geometry as WKT); the edges and the outlines of towns in the 16th century are also separately available as geojson and GML files. For more information about the structure of the dataset, theoretical considerations and sources, please consult the enclosed documentation file.

Assessments & Taxation (A&T) Database from MD Property View 2004 for Baltimore City. The A&T Database contains parcel data from the State Department of Assessments and Taxation; it 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 2004 Database, 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. Documentation for A&T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A&T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the A&T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A&T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 379 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Assessments Taxation (A and T) Database from MD Property View 2004 for Harford County. The A and T Database contains parcel data from the State Department of Assessments and Taxation; it 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 2004 Database, 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. Documentation for A and T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the A and T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A and T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the A and T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A and T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 690 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Assessments and Taxation (A and T) Database from MD Property View 2004 for Carroll County. The A and T Database contains parcel data from the State Department of Assessments and Taxation; it 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 2004 Database, 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. Documentation for A and T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the A and T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A and T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the A and T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A and T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 848 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The CAMA (Computer Assisted Mass Appraisal) Database 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 Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 3999 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The CAMA (Computer Assisted Mass Appraisal) Database 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 Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 194 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The CAMA (Computer Assisted Mass Appraisal) Database 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 Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 236 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The CAMA (Computer Assisted Mass Appraisal) Database 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 Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 399 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Assessments and Taxation (A and T) Database from MD Property View 2004 for Howard County. The A andT Database contains parcel data from the State Department of Assessments and Taxation; it 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 2004 Database, 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. Documentation for A&T, including a thorough definition for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the A&T Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the A&T Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the A&T Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the A&T Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 1160 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

The CAMA (Computer Assisted Mass Appraisal) Database 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 Database and the CAMA supplementary databases for each jurisdiction.. Documentation for CAMA, including thorough definitions for all attributes is enclosed. Complete Property View documentation can be found at http://www.mdp.state.md.us/data/index.htm under the "Technical Background" tab. It should be noted that the CAMA Database consists of points and not parcel boundaries. For those areas where parcel polygon data exists the CAMA Database can be joined using the ACCTID or a concatenation of the BLOCK and LOT fields, whichever is appropriate. (Spaces may have to be excluded when concatenating the BLOCK and LOT fields). A cursory review of the 2004 version of the CAMA Database indicates that it has more accurate data when compared with the 2003 version, particularly with respect to dwelling types. However, for a given record it is not uncommon for numerous fields to be missing attributes. Based on previous version of the CAMA Database it is also not unlikely that some of the information is inaccurate. This layer was edited to remove points that did not have a valid location because they failed to geocode. There were 235 such points. A listing of the deleted points is in the table with the suffix "DeletedRecords." This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Urban area boundaries for 1966, part of the Baltimore-Washington Spatial Dynamics and Human Impacts dataset. The Baltimore-Washington Spatial Dynamics and Human Impacts dataset is an integrated and flexible temporal urban land characteristics database for the Baltimore-Washington metropolitan area. The compilation of this data is a collaborative effort led by the U.S. Geological Survey and the University of Maryland Baltimore County. The database provides visual and historical perspective of the urban growth experienced in the area between 1792 and 1992. Data on built-up areas exists as separate geographic layers for the dates: 1792, 1801, 1822, 1850, 1878, 1900, 1925, 1938, 1953, 1966, 1972, 1982, and 1992. Temporal urban mapping reconstructs past landscapes by incorporating historic maps, census statistics, and commerce records to generate a progressive geo-referenced picture of the past changes in a region. Contemporary mapping focuses on the use of remotely sensed data, existing digital land use data, digital census information, and a variety of earth science infrastructure data, such as Digital Line Graphs, Digital Elevation Models, and key ancillary demographic information. Different procedures were used for different time periods, more fully described for each file in the Process Step Section 2.5.2. The resulting database of temporal urban land use/land cover and demographic changes provides an ideal source of test data and information for both urban geographers and global change research scientists. While this dataset was developed by the University of Maryland Baltimore County final quality control and metadata generation was performed by the University of Vermont's Spatial Analysis Lab. Two significant problems were noted regarding this dataset. The first anomoly is that the 1801, 1822, and 1878 layers have a much smaller extent, and contain data only for Baltimore City. The second discrepancy is that there are also some very obvious positional errors causing misalignments between layers of different dates (i.e. urban areas become non-urban in a very short time period, an unlikely occurance). This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.

Urban area boundaries for 1925, part of the Baltimore-Washington Spatial Dynamics and Human Impacts dataset. The Baltimore-Washington Spatial Dynamics and Human Impacts dataset is an integrated and flexible temporal urban land characteristics database for the Baltimore-Washington metropolitan area. The compilation of this data is a collaborative effort led by the U.S. Geological Survey and the University of Maryland Baltimore County. The database provides visual and historical perspective of the urban growth experienced in the area between 1792 and 1992. Data on built-up areas exists as separate geographic layers for the dates: 1792, 1801, 1822, 1850, 1878, 1900, 1925, 1938, 1953, 1966, 1972, 1982, and 1992. Temporal urban mapping reconstructs past landscapes by incorporating historic maps, census statistics, and commerce records to generate a progressive geo-referenced picture of the past changes in a region. Contemporary mapping focuses on the use of remotely sensed data, existing digital land use data, digital census information, and a variety of earth science infrastructure data, such as Digital Line Graphs, Digital Elevation Models, and key ancillary demographic information. Different procedures were used for different time periods, more fully described for each file in the Process Step Section 2.5.2. The resulting database of temporal urban land use/land cover and demographic changes provides an ideal source of test data and information for both urban geographers and global change research scientists. While this dataset was developed by the University of Maryland Baltimore County final quality control and metadata generation was performed by the University of Vermont's Spatial Analysis Lab. Two significant problems were noted regarding this dataset. The first anomoly is that the 1801, 1822, and 1878 layers have a much smaller extent, and contain data only for Baltimore City. The second discrepancy is that there are also some very obvious positional errors causing misalignments between layers of different dates (i.e. urban areas become non-urban in a very short time period, an unlikely occurance). This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful. This is part of a collection of 221 Baltimore Ecosystem Study metadata records that point to a geodatabase. The geodatabase is available online and is considerably large. Upon request, and under certain arrangements, it can be shipped on media, such as a usb hard drive. The geodatabase is roughly 51.4 Gb in size, consisting of 4,914 files in 160 folders. Although this metadata record and the others like it are not rich with attributes, it is nonetheless made available because the data that it represents could be indeed useful.