The TIGER/Line shapefiles and related database files (.dbf) 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 shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Face refers to the areal (polygon) topological primitives that make up MTDB. A face is bounded by one or more edges; its boundary includes only the edges that separate it from other faces, not any interior edges contained within the area of the face. The Topological Faces Shapefile contains the attributes of each topological primitive face. Each face has a unique topological face identifier (TFID) value. Each face in the shapefile includes the key geographic area codes for all geographic areas for which the Census Bureau tabulates data for both the 2020 Census and the annual estimates and surveys. The geometries of each of these geographic areas can then be built by dissolving the face geometries on the appropriate key geographic area codes in the Topological Faces Shapefile.

DVRPC’s 2023 land use file is based on digital orthophotography created from aerial surveillance completed in the spring of 2023. This dataset supports many of DVRPC's planning analysis goals. Every five years, since 1990, the Delaware Valley Regional Planning Commission (DVRPC) has produced a GIS Land Use layer for its 9-county region.

lu20cat

Land use main category two-digit code. lu20catn

Land use main category name. lu20cat lu20catn

1- Residential, 3 - Industrial, 4 - Transportation, 5- Utility, 6 - Commercial, 7 - Institutional, 8 - Military, 9 - Recreation, 10 - Agriculture, 11 - Mining, 12 - Wooded, 13 - Water, 14 - Undeveloped lu20sub

Land use subcategory five-digit code. (refer to this data dictionary for code description) lu20subn

Land use subcategory name. lu20dev

Development status. mixeduse

Mixed-Use status (Y/N). Features belonging to one of the Mixed-Use subcategories (Industrial: Mixed-Use, Multifamily Residential: Mixed-Use, or Commercial: Mixed-Use). acres

Area of feature, in US acres geoid

10-digit geographic identifier. In all DVRPC counties other than Philadelphia, a GEOID is assigned by municipality. In Philadelphia, it is assigned by County Planning Area (CPA). state_name , co_name , mun_name

State name, county name, municipal/CPA name. In Philadelphia, County Planning Area (CPA) names are used in place of municipal names.

The classification of land according to what activities take place on it or how it is being used; for example, agricultural, industrial, residential, rural, or commercial. Land use information and analysis is a fundamental tool in the planning process.

DVRPC’s 2020 land use file is based on digital orthophotography created from aerial surveillance completed in the spring of 2020. This dataset supports many of DVRPC's planning analysis goals.

Every five years, since 1990, the Delaware Valley Regional Planning Commission (DVRPC) has produced a GIS Land Use layer for its 9-county region.

lu20cat: Land use main category two-digit code.

lu20catn: Land use main category name.

lu20cat

lu20catn

1 - Residential

3 - Industrial

4 - Transportation

5 - Utility

6 - Commercial

7 - Institutional

8 - Military

9 - Recreation

10 - Agriculture

11 - Mining

12 - Wooded

13 - Water

14 - Undeveloped

lu20sub: Land use subcategory five-digit code. (refer to this data dictionary for code description)

lu20subn: Land use subcategory name.

lu20dev: Development status.

mixeduse: Mixed-Use status (Y/N). Features belonging to one of the Mixed-Use subcategories (Industrial: Mixed-Use, Multifamily Residential: Mixed-Use, or Commercial: Mixed-Use).

acres: Area of feature, in US acres.

geoid: 10-digit geographic identifier. In all DVRPC counties other than Philadelphia, a GEOID is assigned by municipality. In Philadelphia, it is assigned by County Planning Area (CPA).

state_name, co_name, mun_name: State name, county name, municipal/CPA name. In Philadelphia, County Planning Area (CPA) names are used in place of municipal names.

The classification of land according to what activities take place on it or how it is being used; for example, agricultural, industrial, residential, rural, or commercial. Land use information and analysis is a fundamental tool in the planning process.

DVRPC’s 2023 land use file is based on digital orthophotography created from aerial surveillance completed in the spring of 2023. This dataset supports many of DVRPC's planning analysis goals.

Every five years, since 1990, the Delaware Valley Regional Planning Commission (DVRPC) has produced a GIS Land Use layer for its 9-county region.

lu23cat: Land use main category two-digit code.

lu23catn: Land use main category name.

lu23cat

lu23catn

• 1 - Residential

• 3 - Industrial

• 4 - Transportation

• 5 - Utility

• 6 - Commercial

• 7 - Institutional

• 8 - Military

• 9 - Recreation

• 10 - Agriculture

• 11 - Mining

• 12 - Wooded

• 13 - Water

• 14 - Undeveloped

lu23sub: Land use subcategory five-digit code. (refer to this data dictionary for code description)

lu23subn: Land use subcategory name.

lu23dev: Development status.

mixeduse: Mixed-Use status (Y/N). Features belonging to one of the Mixed-Use subcategories (Industrial: Mixed-Use, Multifamily Residential: Mixed-Use, or Commercial: Mixed-Use).

acres: Area of feature, in US acres.

geoid: 10-digit geographic identifier. In all DVRPC counties other than Philadelphia, a GEOID is assigned by municipality. In Philadelphia, it is assigned by County Planning Area (CPA).

state_name, co_name, mun_name: State name, county name, municipal/CPA name. In Philadelphia, County Planning Area (CPA) names are used in place of municipal names.

Municipal boundaries for DVRPC Region with Philadelphia's County Planning Areas. Municipal Boundaries have been edited by DVRPC to create a more accurate, seemless regional dataset for the DVRPC region and its surrounding area. This dataset was compiled from multiple sources. Original data sources (in order of drawing rank): DVRPC - for Mercer, Burlington, Camden, Gloucester counties in NJ (an adaptation of NJOIT's Mun Bounds) and Bucks, Montgomery, Philadelphia, Chester, and Delaware counties in PA. In most cases, boundaries have been adjusted to align with parcel data. Due to the name change from Washington Twp to Robbinsville Twp in Mercer County, the unique ID (GEOID) for this municipality has changed from 3402177210 to 3402163850 . However, if you download 2000 census data from the Bureau's website, the unique ID (GEOID) for Robbinsville Township will still be 3402177210 in the census data…you will have to manually change its GEOID to 3402163850 in order to get the 2000 data to join to the MCD file correctly. Edited in April 2021 to match PCPC's planning district boundaries and numbers dated 2013

DVRPC’s 2023 land use file is based on digital orthophotography created from aerial surveillance completed in the spring of 2023. This dataset supports many of DVRPC's planning analysis goals.Every five years, since 1990, the Delaware Valley Regional Planning Commission (DVRPC) has produced a GIS Land Use layer for its 9-county region.lu23cat: Land use main category two-digit code.lu23catn: Land use main category name.lu23catlu23catn1Residential3Industrial4Transportation5Utility6Commercial7Institutional8Military9Recreation10Agriculture11Mining12Wooded13Water14Undevelopedlu23sub: Land use subcategory five-digit code.(refer to this data dictionary for code description)lu23subn: Land use subcategory name.lu23dev: Development status.mixeduse: Mixed-Use status (Y/N). Features belonging to one of the Mixed-Use subcategories (Industrial: Mixed-Use, Multifamily Residential: Mixed-Use, or Commercial: Mixed-Use).acres: Area of feature, in US acres.geoid: 10-digit geographic identifier. In all DVRPC counties other than Philadelphia, a GEOID is assigned by municipality. In Philadelphia, it is assigned by County Planning Area (CPA).state_name, co_name, mun_name: State name, county name, municipal/CPA name. In Philadelphia, County Planning Area (CPA) names are used in place of municipal names.

This linear feature class contains representations of existing sidewalks for the DVRPC Region, without Philadelphia County.Please note that this data was created by interpreting 2017 aerial photos. As of February 2020, data has not been field checked. As a result, curb ramp presence will need to be verified before using this dataset as an accurate inventory. Data will be updated periodically. To receive notifications when the data has been updated, please visit walk.dvrpc.org and add your contact information in the "Stay in Touch" section.See "Pedestrian Data Development for the DVRPC Region Process Methodology, November 20, 2018" for more information.

This resource is a member of a series. The TIGER/Line shapefiles and related database files (.dbf) 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 shapefile is designed to stand alone as an independent data set, or they can be combined to cover the entire nation. Census tracts are small, relatively permanent statistical subdivisions of a county or equivalent entity, and were defined by local participants as part of the 2020 Census Participant Statistical Areas Program. The Census Bureau delineated the census tracts in situations where no local participant existed or where all the potential participants declined to participate. The primary purpose of census tracts is to provide a stable set of geographic units for the presentation of census data and comparison back to previous decennial censuses. Census tracts generally have a population size between 1,200 and 8,000 people, with an optimum size of 4,000 people. When first delineated, census tracts were designed to be homogeneous with respect to population characteristics, economic status, and living conditions. The spatial size of census tracts varies widely depending on the density of settlement. Physical changes in street patterns caused by highway construction, new development, and so forth, may require boundary revisions. In addition, census tracts occasionally are split due to population growth, or combined as a result of substantial population decline. Census tract boundaries generally follow visible and identifiable features. They may follow legal boundaries such as minor civil division (MCD) or incorporated place boundaries in some States and situations to allow for census tract-to-governmental unit relationships where the governmental boundaries tend to remain unchanged between censuses. State and county boundaries always are census tract boundaries in the standard census geographic hierarchy. In a few rare instances, a census tract may consist of noncontiguous areas. These noncontiguous areas may occur where the census tracts are coextensive with all or parts of legal entities that are themselves noncontiguous. For the 2010 Census, the census tract code range of 9400 through 9499 was enforced for census tracts that include a majority American Indian population according to Census 2000 data and/or their area was primarily covered by federally recognized American Indian reservations and/or off-reservation trust lands; the code range 9800 through 9899 was enforced for those census tracts that contained little or no population and represented a relatively large special land use area such as a National Park, military installation, or a business/industrial park; and the code range 9900 through 9998 was enforced for those census tracts that contained only water area, no land area.

About the G.M. Hopkins Maps

History and Background of the Maps

Maps produced by the G.M. Hopkins Company have made a lasting impression on the boundaries of many American cities. Between 1870 and 1940, the company produced over 175 atlases and real estate plat maps that primarily covered the Eastern sea board, including cities, counties, and townships in 18 different states and the District of Columbia. In the early years, the company produced county atlases, but gradually focused on city plans and atlases. They were among the first publishers to create a cadastral atlas, a cross between a fire insurance plat and a county atlas prevalent in the 1860s-1870s. These real estate or land ownership maps (also known as plat maps) not only depict property owners, but show lot and block numbers, dimensions, street widths, and other buildings and landmarks, including churches, cemeteries, mills, schools, roads, railroads, lakes, ponds, rivers, and streams.

Originally named the G.M. Hopkins and Company, the map-making business was jointly founded in 1865 in Philadelphia, Pa., by the Hopkins brothers, G.M. and Henry. The true identity of G.M. Hopkins remains somewhat of a mystery even today. “G.M.” either stands for Griffith Morgan or George Morgan. There are three different possibilities for the confusion over his identity. “Either the compilers of the earlier [city] directories were negligent; G.M. Hopkins changed his first name; or there were two G.M. Hopkins (father and son) working for the same firm” (Moak, Jefferson M. Philadelphia Mapmakers. Philadelphia: Shackamaxon Society, 1976, p. 258).

http://digital.library.pitt.edu/abouthp/#hopkins

This shapefile is intended as a master shapefile of non-Circuit trails in DVRPC's four New Jersey counties. It was compiled by DVRPC using several sources including county open data portals, PDF park and trail maps available online, and Google Maps' trails layer. Trails were corrected and verified manually using leaf-off Nearmap and Google imagery as well as PDF maps and Strava.com where aerial imagery was not sufficient. trail_name: The trail name field was inherited from individual source shapefiles and edited when necessary. Where possible, trail_name represents the official name of the trail. In the case that official names were not available, descriptive, colloquial names were added.county: This field refers to the county the trail exists in.owner: This field refers to the agency/organization responsible for the trail.surface_type: The surface_type field includes the primary surface material based on the following categories:Crushed Stone/Gravel, Dirt, Grass, Paved (includes asphalt, concrete, and other hard surfaces), Stone Dust, and Varies (in the case where a trail is composed of more than one surface material)multi_use: This field indicates whether a trail is suitable for more than one use, e.g. walking, hiking, biking, horseback riding, etc. Where possible, the width of trails was measured to determine compliance with AASHTO standards. verif_status: This field indicates whether the trail segment is fully verified. For records that were able to be verified, this field contains the value 'Verified'. For records that were not able to be verified, this field is left blank.verif_by: This refers to the individual who edited and/or verified the trail segment.verif_date: Date of verificationcomments_dvrpc: This field contains notes from the DVRPC planner/analyst about any issues or observations regarding the trail segment and its verification.

Parcels are a key framework data set for Sussex County's GIS spatial data network which serves the Sussex County information management system. Tax parcels data assist with day-to-day operations for the County, its municipalities, and not-for-profits. These data also provide one of the FGDC framework data sets.Although this data set does not contain property assessment information, each parcel record contains an attribute called the PAMS_PIN (a concatenation of the New Jersey Division of Taxation county/muncipality code, block number, lot number and qualification code) that uniquely identifies the parcel. The PAMS_PIN field can be used to join the data set to MOD-IV database tables maintained by the New Jersey Division of Taxation that contain supplementary attribute information regarding lot ownership and characteristics.This data set may not represent all current parcels because of lag in information flow and data development.Contact: Sussex County Office of GIS Management; 973-579-0430.

Prior to the year 2000, DVRPC’s aerial imagery consisted of mylar aerial photo enlargements or “atlas sheets”. These atlas sheets were produced from 9x9" aerial photos. The imagery dates from the years 1959, 1965, 1970, 1975, 1980, 1985, 1990, & 1995. The 1959s and 1965s primarily cover the urbanized portion of the DVRPC region (the DVRPC region is made up of nine counties: Bucks, Chester, Delaware, Montgomery, and Philadelphia in Pennsylvania; Burlington, Camden, Gloucester, and Mercer in New Jersey). Subsequent years provide full coverage of the region, minus the occasional missing scan. In order to increase the efficiency of using the historical aerial imagery, the sheets were scanned into TIFF (Tagged Image File Format) files. Each TIFF file ranges between 35- 40MB in size. Unlike DVRPC’s more recent aerial imagery (2000 and later), the historical aerials are not “orthorectified” or “orthocorrected”. In other words, they are simply aerial images with no spatial reference or uniform scale. Through the process of georeferencing, Montgomery County GIS assigned a spatial reference which will enabled them to be used more readily in a GIS environment. That said, georeferencing is not orthorectifying or orthocorrecting. What it does allow is for the scan to be displayed relative to other spatially referenced GIS layers. A georeferenced scan does not have the properties of an actual orthoimage. Whereas an orthoimage can be used for making accurate measurements, a georeferenced image cannot, as it does not have the spatial accuracy and uniform scale of an orthoimage.

Parcels are a key framework data set for Hunterdon County's GIS spatial data network which serves the Hunterdon County information management system.Although this data set does not contain property assessment information, each parcel record contains an attribute called the PAMS_PIN (a concatenation of the New Jersey Division of Taxation county/muncipality code, block number, lot number and qualification code) that uniquely identifies the parcel. The PAMS_PIN field can be used to join the data set to MOD-IV database tables maintained by the New Jersey Division of Taxation that contain supplementary attribute information regarding lot ownership and characteristics.This data set may not represent all current parcels because of lag in information flow and data development.Contact: Patricia Leidner; Hunterdon County Division of GIS; 908-806-5534; pleidner@co.hunterdon.nj.us

In 1760, two new roads were laid out in East Caln Township that linked the west branch of the Brandywine Creek with the frequently traveled Lancaster Road (modern Rt. 322). The new roads made markets in Philadelphia, Lancaster, and Wilmington more accessible to those living in Chester County’s remote northwest. Adventurous men like Andrew Culbertson were attracted to the area hoping to capitalize on the new commercial opportunities now afforded by the roads and creek.

Protected Open Space for the DVRPC Region as of 2016. Modified for ETA project. DVRPC maintains an inventory of protected public and private open space in the Delaware Valley. The inventory tracks all publicly-owned open space, preserved farmland, and non profit protected open space. State, county and municipal programs preserve farms by purchasing development rights with public funds. Non-profits (land trusts and conservancies) protect privately owned open space lands by purchasing easements or by acquiring land outright with a combination of public and private funds. This file is a compilation from the following sources and is not necessarily parcel-based: Bucks County Planning Commission; Burlington County Department of Economic Development and Regional Planning; Camden County Division of Open Space and Farmland Preservation; Camden County Improvement Authority; Chester County Planning Commission; Delaware County Planning Department; Gloucester County Planning Division; Mercer County Planning Division; Montgomery County Planning Commission; Natural Lands Trust; New Jersey Conservation Foundation; New Jersey Department of Environmental Protection; New Jersey State Agriculture Development Committee; Pennsylvania Department of Conservation and Natural Resources; Philadelphia City Planning Commission; Philadelphia Department of Parks and Recreation In the cases where land had multiple owners, the following heirarchy was applied: 1. Preserved Farmland 2. Federal 3. State 4. County 5. Municipal 6. Nonprofit

1. PineIsland (NY)8. Hamburg 9. Wawayanda10.GreenwoodLake (NY)11.Sloatsburg (NY)16.Franklin17.Newfoundland18.Wanaque19.Ramsey20.Park Ridge21.Nyack (NY)25.Tranquility26.Stanhope27.Dover28.Boonton29.Pompton Plains30.Paterson31.Hackensack32.Yonkers (NY)36.Hackettstown38.Mendham39. Morristown40.Caldwell41.Orange42.Weehawken43.Central Park (NY)47.Califon48.Gladstone 49.Bernardsville50.Chatham51.Roselle52.Elizabeth53.Jersey City59.Raritan60.Bound Brook61.Plainfield62.Perth Amboy 63.Arthur Kill (NY) 66.Lumberville(PA) 67.Stockton68.Hopewell 69.Rocky Hill70. Monmouth Junction71.New Brunswick 72.South Amboy73.Keyport74.Sandy Hook76. Lambertville77. Pennington78. Princeton79. Hightstown80.Jamesburg81.Freehold 82.Marlboro83.Long Branch86.Trenton West87.Trenton East88.Allentown89. Roosevelt90.Adelphia91.Farmingdale92.Asbury Park93.Frankford (PA)94.Beverly (PA)95.Bristol (PA)102. Philadelphia (PA)103.Camden104. Moorestown108.Whiting109.Keswick Grove110. Toms River111.Seaside Park112.Marcus Hook (PA)113.Bridgeport114.Woodbury115.Runnemede118.Indian Mills119.Chatsworth120.Woodmansie121.Brookville122.Forked River123.Barnegat Light124. Wilmington S. (DE)125. Penns Grove133.Oswego Lake134.West Creek137.Delaware City (DE) 138.Salem149.Taylors Bridge (DE)150.Canton153.Millville