Description: The Maryland-National Capitol Park and Planning Commission (Commission) required the creation of a new Point Feature Class containing address information for all known Multifamily properties/buildings within Prince George’s County, Maryland. The new feature class was created using existing Multifamily address data of approximately 115,000 addresses, which was maintained and provided the Commission. The existing Multifamily addresses were geocoded using a combination of the Commission’s PGAtlas.com Composite Geocoder and manual address identification and update. This Technical Memorandum documents the process that was used to geocode the existing Multifamily addresses to generate the new Multifamily Point Feature Class.
Description: This dataset contains buildings within Prince George's County. Building ruins, buildings under construction, and parking garages are also included. Overhead rooftops, or canopies, are shown with a separate feature code and features running under are not clipped out. Each feature is attributed with height in feet and roof type of either gable or flat. This data was captured for use in general mapping at a scale of 1:1200.
Description: The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census Blocks are statistical areas bounded on all sides by visible features, such as streets, roads, streams, and railroad tracks, and/or by nonvisible boundaries such as city, town, township, and county limits, and short line-of-sight extensions of streets and roads. Census blocks are relatively small in area; for example, a block in a city bounded by streets. However, census blocks in remote areas are often large and irregular and may even be many square miles in area. A common misunderstanding is that data users think census blocks are used geographically to build all other census geographic areas, rather all other census geographic areas are updated and then used as the primary constraints, along with roads and water features, to delineate the tabulation blocks. As a result, all 2010 Census blocks nest within every other 2010 Census geographic area, so that Census Bureau statistical data can be tabulated at the block level and aggregated up to the appropriate geographic areas. Census blocks cover all territory in the United States, Puerto Rico, and the Island Areas (American Samoa, Guam, the Commonwealth of the Northern Mariana Islands, and the U.S. Virgin Islands). Blocks are the smallest geographic areas for which the Census Bureau publishes data from the decennial census. A block may consist of one or more faces.
Description: The TIGER/Line Files are shapefiles and related database files (.dbf) that are an extract of selected geographic and cartographic information from the U.S. Census Bureau's Master Address File / Topologically Integrated Geographic Encoding and Referencing (MAF/TIGER) Database (MTDB). The MTDB represents a seamless national file with no overlaps or gaps between parts, however, each TIGER/Line File is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Block Groups (BGs) are defined before tabulation block delineation and numbering, but are clusters of blocks within the same census tract that have the same first digit of their 4-digit census block number from the same decennial census. For example, Census 2000 tabulation blocks 3001, 3002, 3003,.., 3999 within Census 2000 tract 1210.02 are also within BG 3 within that census tract. Census 2000 BGs generally contained between 600 and 3,000 people, with an optimum size of 1,500 people. Most BGs were delineated by local participants in the Census Bureau's Participant Statistical Areas Program (PSAP). The Census Bureau delineated BGs only where the PSAP participant declined to delineate BGs or where the Census Bureau could not identify any local PSAP participant. A BG usually covers a contiguous area. Each census tract contains at least one BG, and BGs are uniquely numbered within census tract. Within the standard census geographic hierarchy, BGs never cross county or census tract boundaries, but may cross the boundaries of other geographic entities like county subdivisions, places, urban areas, voting districts, congressional districts, and American Indian / Alaska Native / Native Hawaiian areas. BGs have a valid code range of 0 through 9. BGs coded 0 were intended to only include water area, no land area, and they are generally in territorial seas, coastal water, and Great Lakes water areas. For Census 2000, rather than extending a census tract boundary into the Great Lakes or out to the U.S. nautical three-mile limit, the Census Bureau delineated some census tract boundaries along the shoreline or just offshore. The Census Bureau assigned a default census tract number of 0 and BG of 0 to these offshore, water-only areas not included in regularly numbered census tract areas.
Description: Council of Governments Traffic Analysis Zones - COGTAZ is a stand-alone geography. COGTAZ is a geographic designation used by the Council of Governments to collect and analyze statistical information for input to COG's travel demand forecasting model. This geography is maintained by the Research Section and corresponds to the geography for which dwelling unit, household, population, and employment estimates are maintained and forecasts developed. There are currently a total of 2,191 COG-TAZs in the entire COG modeled region, and 380 of the zones are in Prince George's County. Each zone in the county is uniquely identified by a number ranging from 640 to 1020. (Since the unification of Takoma Park, there is no TAZ 648 in Prince George's County.) Coverage Derivation: The original coverage from the COG came with unspecified scale which has been adjusted to 1:2,400 scale. The following coverages (layers) were used to adjust the COGTAZ boundaries: PAZ, CAZ, PA, Streams, Muni., PGTAZ, Cline, Property, 2000 Aerial, Roadsall and Zoning. In addition, the Research Section also sought input from the Community and Countywide Planning Divisions to achieve further refinements to the geography and data. The boundaries and attribute data were checked by the Research Section staff for quality control. This data is current to Round 9 of the Council of Governments projections.
Copyright Text: Source information provided by Council of Governments.