ArcGIS REST Services Directory Login | Get Token
JSON

ItemInfo

Item Information

snippet: Connectors - Cartographic Highlight polygon layer is designed for visualization only and is not part of the Undeveloped Habitat Blocks datasets.
summary: Connectors - Cartographic Highlight polygon layer is designed for visualization only and is not part of the Undeveloped Habitat Blocks datasets.
accessInformation: Cartographic Highlight polygon represents a 150 meter buffer on connectors segments. Connectors were prepared by TNC Maine for the Beginning with Habitat Program 2024.
thumbnail:
maxScale: 5000
typeKeywords: []
description: <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>The Block Connector line segments represent stretches of roads that are at least 500 ft. long that separate undeveloped blocks and are the only fragmenting feature of the undeveloped blocks at these locations -- see the undeveloped blocks datasets for details. The are coded for whether they intersect a Beginning with Habitat mapped riparian area and/or are withing 50 feet of a non-open-water wetland as mapped by the National Wetlands Inventory. These connector segments represent stretches of roads that are the least developed stretches of roads between undeveloped blocks of habitat. Roads used in this analysis were a subset of MaineDOT Public Roads (Maine Office of GIS: 2023), E911 Roads Features (Maine Office of GIS: 2023), and NHDOT Roads (New Hampshire Granit 2023). The primary roads dataset utilized was the MDOT Public Roads dataset -- important: Only non-highway roads qualify as connectors (because of the outsized fragmenting nature of divided highways). Therefore, only MDOT roads with a FedFuncClas not equal to 'Interstate' or 'Other Freeway or Expressway' are included as potential connector segments. The E911 roads were used as a supplement to the MDOT public roads - mainly as the best representation of private roads available - only E911 roads with RdClass equal to 'Private', 'Local', or 'Gated' that didn't overlap MDOT public road lines were used in the undeveloped blocks analysis and therefore, this Block Connector Segment product. For more details on the data sources used to define the undeveloped blocks, see the undeveloped block outer boundary and undeveloped block component dataset metadata.</SPAN></P></DIV></DIV></DIV>
licenseInfo:
catalogPath:
title: Block Connector Segments 2024
type:
url:
tags: ["Maine","Beginning with Habitat","Conservation Planning","Landscape Connectivity","Undeveloped Habitat","Road Connector Segments"]
culture: en-US
name:
guid:
minScale: 500000
spatialReference: