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.

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

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.

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 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.

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.

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 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.

NOTE: This metadata file contains Draft information for Waterbody features delineated for NJ from 2015 color 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 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.

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

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.

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.

This database is a conflation of the older database and the more current data collected by the Department of Engineering. Many fields have been combined and some removed to make the database more readable and easier to edit. A subtype has been put in place to render the features as either 1) Chatham County Maintained, or 2) Not Chatham County Maintained.The purpose of including non-County maintained structures serves to understand the complete drainage system connectivity, and also, to easily add or remove existing features into the MS4 should a mistake be discovered or annexation/de-annexations occur.

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.

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.

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.

Election layer is a conflation of all electable districts within Sedgwick County that all other districts are derived from. Primary attributes include Precinct, City Code, CouDistNO, BOCCDistNO, SenDistNO, etc...

This database is a conflation of the older database, data collected by the Department of Engineering, and LiDAR derived drainage features. Many fields have been combined and some removed to make the database more readable and easier to edit. A subtype has been put in place to render the features as either 1) Chatham County Maintained, or 2) Not Chatham County Maintained.The purpose of including non-County maintained structures serves to understand the complete drainage system connectivity, and also, to easily add or remove existing features into the MS4 should a mistake be discovered or annexation/de-annexations occur.