For more information about this layer please see the GIS Data Catalog.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.

Formerly known as the Massachusetts Highway Department (MHD) Roads, then the Executive Office of Transportation - Office of Transportation Planning (EOT-OTP) Roads, the MassGIS-MassDOT Roads layer includes linework from the 1:5,000 road and rail centerlines data that were interpreted as part of the 1990's Aerial Imagery project. The Massachusetts Department of Transportation - Office of Transportation Planning, which maintains the primary source for this layer, continues to add linework from municipal and other sources and update existing linework using the most recent aerial ortho imagery as a base. The attribute table includes many "road inventory" fields maintained in MassDOT's linear referencing system.The current MassGIS-MassDOT hybrid data layer was first published in November 2018, based on the MassDOT 2017 year-end Road Inventory layer and results of a 2014-2015 MassDOT-Central Transportation Planning Staff project to conflate street names and other attributes from MassGIS' "base streets" to the MassDOT Road Inventory linework. The base streets are continually maintained by MassGIS as part of the NextGen 911 and Master Address Database (MAD) projects. MassGIS staff reviewed the conflated layer and added many base street arcs digitized after the completion of the conflation work. MassGIS added several fields to support legacy symbology and labeling. Other edits included modifying some linework in areas of recent construction and roadway reconfiguration to align to 2017-2018 Google ortho imagery, and making minor fixes to attributes and linework. MassGIS continues to modify the layer as needed, modifying the linework using the latest aerial imagery and adding line features from the base street arcs.From this data layer MassGIS extracted Major Roads and Major Highway Routes layers.See full metadata

The Bicycle Plan is the countywide planning document for bicycle facilities. The GIS data component of the Bicycle Plan consists of an inventory of existing and proposed bikeways with a class I through IV designation. Bikeway data was captured using road centerlines captured from the aerial photography as the apparent centerline and heads up digitizing directly from the orthophotography by GIS staff. Attributes were compiled via a conflation process from the original bikeway data to the new coverage captured from the aerial photography. Subsequently a QC process followed to correct errors in the conflation and digitizing process. Bikeways captured from the Merrick Street centerlines do not represent the actual location of the bikeway feature. Heads up digitized features do represent the apparent centerline of the bikeway feature.

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.

Road centerlines are captured from the aerial photography as the apparent centerline. Attributes originally compiled via a conflation process from the original street centerline data to the new centerline coverage captured from the aerial photography. Subsequently an extensive QC process followed to correct errors in the conflation process. These areas where identified by staff in phase one of the QC process.

This layer represents all the public and many of the private roadways in Massachusetts, including designations for Interstate, U.S. and State routes. Formerly known as the Massachusetts Highway Department (MHD) Roads, then the Executive Office of Transportation - Office of Transportation Planning (EOT-OTP) Roads, the MassDOT roads layer includes linework from the 1:5,000 road and rail centerlines data that were interpreted as part of the 1990s Black and White Digital Orthophoto project. The Massachusetts Department of Transportation - Office of Transportation Planning, which maintains this layer, continues to add linework from municipal and other sources and update existing linework using the most recent color ortho imagery as a base. The attribute table includes many "road inventory" items maintained in MassDOT's linear referencing system. The data layer published in November 2018 is based on the MassDOT 2017 year-end Road Inventory layer and results of a 2014-2015 MassDOT-Central Transportation Planning Staff project to conflate street names and other attributes from MassGIS' "base streets" to the MassDOT Road Inventory linework. The base streets are continually maintained by MassGIS as part of the NextGen 911 and Master Address Database projects. MassGIS staff reviewed the conflated layer and added many base street arcs digitized after the completion of the conflation work. MassGIS added several fields to support legacy symbology and labeling. Other edits included modifying some linework in areas of recent construction and roadway reconfiguration to align to 2017-2018 Google ortho imagery, and making minor fixes to attributes and linework.In ArcSDE this layer is named EOTROADS_ARC.From this data layer MassGIS extracted the Major Roads and Major Highway Routes layers.

Road centerlines are captured from the aerial photography as the apparent centerline. Attributes originally compiled via a conflation process from the original street centerline data to the new centerline coverage captured from the aerial photography. Subsequently an extensive QC process followed to correct errors in the conflation process. These areas where identified by staff in phase one of the QC process.

Metrorail lines in operation in Fairfax County. The data set was originaly obtained from the Metro Washington Council of Governments (MWCOG) GIS data clearinghouse and conflated to the Fairfax County railroad data set.

Shapefile (NJ State Plane NAD 1983) download: Click "Open" or Click hereFile Geodatabase (NJ State Plane NAD 1983) download: Click hereNOTE: This metadata file contains information for Waterbody features delineated for NJ from 2002 color infrared (CIR) imagery with attributes extracted from the National Hydrography Dataset (NHD). Digitizing of this data was initally done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). Conflation of USGS 1:24,000 High resolution NHD attributes was done by Data Enhancement Services, LLC (DES) partenered with Civil Solutions. This statewide conflation of NHD High resolution information was completed in 2010. All QA/QC was done by NJDEP, Bureau of GIS and USGS. This represents a subset of the statewide extract for NJ dated August 25, 2010.

NOTE: This metadata file contains information for Flowlines delineated for NJ from 2002 color infrared (CIR) imagery with attributes extracted from the National Hydrography Dataset (NHD). Digitizing of this data was initially done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). Conflation of USGS 1:24,000 High resolution NHD attributes was done by Data Enhancement Services, LLC (DES) partnered with Civil Solutions. This statewide conflation of NHD High resolution information was completed in 2010. All QA/QC was done by NJDEP, Bureau of GIS and USGS. This represents a subset of the statewide extract for NJ dated August 25, 2010.

This data set is intended to serve as a resource for analysis rather than regulatory delineations. Digitizing of this data was initially done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). Conflation of USGS 1:24,000 High resolution NHD attributes was done by Data Enhancement Services, LLC (DES) partnered with Civil Solutions. This statewide conflation of NHD High resolution information was completed in 2010. All QA/QC was done by NJDEP, Bureau of GIS and USGS. Somerset County data extracted & processed from the latest NJDEP dataset by the Somerset County Office of GIS Services (SCOGIS) on April 05, 2024

NOTE: This dataset contains information for Waterbody features delineated for NJ from 2020 color imagery as part of the Land Use/Land Cover 2020 update. Attributes extracted from the National Hydrography Dataset (NHD) are maintained for the 2020 (TYPE20=WATER) water features only. Digitizing of this data was initially done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). All QA/QC was done by NJDEP, Bureau of GIS and USGS. Conflation into the USGS 1:24,000 High resolution NHD has not been done. This statewide conflation of NHD High resolution information was completed in 2010. This represents an update to a subset of the statewide extract for NJ dated December 23, 2023.

The dataset is a spatial representation of waterbodies (2015) in Somerset County, New Jersey. The data set will provide Waterbody information for regulators, planners, and others interested in hydrography data. This data set is intended to serve as a resource for analysis rather than regulatory delineations. Digitizing of this data was initially done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). Conflation of USGS 1:24,000 High resolution NHD attributes has not been done was done. This statewide conflation of NHD High resolution information was completed in 2019. All QA/QC was done by NJDEP, Bureau of GIS and USGS. This represents a subset of the statewide extract for NJ dated August 25, 2015. Somerset County data extracted & processed from the latest NJDEP dataset by the Somerset County Office of GIS Services (SCOGIS) on April 2024

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.

The Oregon Private Forest Accord and Forest Practices Act specified the methodology to develop and maintain the Statewide Flow Line data. Initial development of these data began with using best available Digital Elevation Models (DEMs) to model a synthetic stream network. Where available, lidar DEMs were resampled to a 2 meter resolution. Where lidar was not available, the National Elevation Dataset (NED, resolution of 10 meters) was used. After streams were model the Fransen fish model (Brian R. Fransen, Steven D. Duke, L. Guy McWethy, Jason K. Walter & Robert E. Bilby. 2006. A Logistic Regression Model for Predicting the Upstream Extent of Fish Occurrence Based on Geographical Information Systems Data, North American Journal of Fisheries Management, 26:4, 960-975, DOI: 10.1577/M04-187.1) was applied to predict fish presence for all streams across Oregon. Historic ODF data (maintained in the ODF Statewide Streams Fish Presence dataset) was then conflated to the synthetic streams to overwrite the fish model outputs with any valid fish survey. These data were checked by Oregon Department of Forestry (ODF) and Oregon Department of Fish & Wildlife (ODFW) GIS staff to meet minimum conflation success rates. Errors were identified and documented for future updates.The Flow Line data will be continuously updated with fish and flow permanence surveys, following established protocols and workflows developed by ODF and ODFW. Errors in conflation with historic data, and errors in geometry from the DEM modeling will also continue to be corrected. This data should be treated as a dynamic layer, with any export product frequently updated to ensure the most current information is being used.

Road centerlines are captured from the aerial photography as the apparent centerline. Attributes originally compiled via a conflation process from the original street centerline data to the new centerline coverage captured from the aerial photography. Subsequently an extensive QC process followed to correct errors in the conflation process. These areas where identified by staff in phase one of the QC process.

September 05, 2025 update: Updated dataMay 09, 2025 update: The Statewide Flow Line data was updated to enhance data management functionality and performance of the data. Some field names were changed in this process.The Oregon Private Forest Accord and Forest Practices Act specified the methodology to develop and maintain the Statewide Flow Line data. Initial development of these data began with using best available Digital Elevation Models (DEMs) to model a synthetic stream network. Where available, lidar DEMs were resampled to a 2 meter resolution. Where lidar was not available, the National Elevation Dataset (NED, resolution of 10 meters) was used. After streams were model the Fransen fish model (Brian R. Fransen, Steven D. Duke, L. Guy McWethy, Jason K. Walter & Robert E. Bilby. 2006. A Logistic Regression Model for Predicting the Upstream Extent of Fish Occurrence Based on Geographical Information Systems Data, North American Journal of Fisheries Management, 26:4, 960-975, DOI: 10.1577/M04-187.1) was applied to predict fish presence for all streams across Oregon. Historic ODF data (maintained in the ODF Statewide Streams Fish Presence dataset) was then conflated to the synthetic streams to overwrite the fish model outputs with any valid fish survey. These data were checked by Oregon Department of Forestry (ODF) and Oregon Department of Fish & Wildlife (ODFW) GIS staff to meet minimum conflation success rates. Errors were identified and documented for future updates.The Flow Line data will be continuously updated with fish and flow permanence surveys, following established protocols and workflows developed by ODF and ODFW. Errors in conflation with historic data, and errors in geometry from the DEM modeling will also continue to be corrected. This data should be treated as a dynamic layer, with any export product frequently updated to ensure the most current information is being used.

The Oregon Private Forest Accord and Forest Practices Act specified the methodology to develop and maintain the Statewide Flow Line data. Initial development of these data began with using best available Digital Elevation Models (DEMs) to model a synthetic stream network. Where available, lidar DEMs were resampled to a 2 meter resolution. Where lidar was not available, the National Elevation Dataset (NED, resolution of 10 meters) was used. After streams were model the Fransen fish model (Brian R. Fransen, Steven D. Duke, L. Guy McWethy, Jason K. Walter & Robert E. Bilby. 2006. A Logistic Regression Model for Predicting the Upstream Extent of Fish Occurrence Based on Geographical Information Systems Data, North American Journal of Fisheries Management, 26:4, 960-975, DOI: 10.1577/M04-187.1) was applied to predict fish presence for all streams across Oregon. Historic ODF data (maintained in the ODF Statewide Streams Fish Presence dataset) was then conflated to the synthetic streams to overwrite the fish model outputs with any valid fish survey. These data were checked by Oregon Department of Forestry (ODF) and Oregon Department of Fish & Wildlife (ODFW) GIS staff to meet minimum conflation success rates. Errors were identified and documented for future updates.The Flow Line data will be continuously updated with fish and flow permanence surveys, following established protocols and workflows developed by ODF and ODFW. Errors in conflation with historic data, and errors in geometry from the DEM modeling will also continue to be corrected. This data should be treated as a dynamic layer, with any export product frequently updated to ensure the most current information is being used.

Road centerlines are captured from the aerial photography as the apparent centerline. Attributes originally compiled via a conflation process from the original street centerline data to the new centerline coverage captured from the aerial photography. Subsequently an extensive QC process followed to correct errors in the conflation process. These areas where identified by staff in phase one of the QC process.

NOTE: This dataset contains information for Streams (NHDFlowlines) delineated for NJ from 2020 color infrared (CIR) imagery with attributes extracted from the National Hydrography Dataset (NHD). Updates are made with relation to the waterbodies 2020 extracted from the Landuse 2020 Update. This represents a schema update to a subset of the statewide extract for NJ dated December 23, 2023. Digitizing of this data was initially done by Aerial Information Systems, Inc., Redlands, CA, under direction of the New Jersey Department of Environmental Protection (NJDEP), Bureau of Geographic Information System (BGIS). Conflation of USGS 1:24,000 High resolution NHD attributes was done by Data Enhancement Services, LLC (DES) partnered with Civil Solutions. This statewide conflation of NHD High resolution information was completed in 2010. All QA/QC was done by NJDEP, Bureau of GIS and USGS.