This layer was created as part of Esri’s Green Infrastructure Initiative and is one of five newly generated companion datasets that can be used for Green Infrastructure (GI) planning at national, regional, and more local scales. If used together, these layers should have corresponding date-based suffixes (YYYYMMDD). The corresponding layer names are: Intact Habitat Cores, Habitat Connectors, Habitat Fragments, Habitat Cost Surface, and Intact Habitat Cores by Betweeness. These Esri derived data, and additional data central to GI planning from other authoritative sources, are also available as Map Packages for each U.S. State and can be downloaded from the Green Infrastructure Data Gallery.This layer represents the modeled Least Cost Paths (LCPs) among neighboring Intact Habitat Cores. Least cost paths reflect the route of least resistance between neighboring habitat core edges, and by extension, represent possible paths of wildlife movement. Esri generated this comprehensive network of LCPs using the Cost Connectivity tool which was introduced in ArcGIS 10.4 and ArcGISPro in 1.3. The Habitat Cost Surface layer was used as the input computational surface. The resulting network was also utilized to compute Betweenness Centrality attribution for the Intact Habitat Cores by Betweenness layer, denoting a measure of the Core’s connectivity importance compared to all others in the network.The PathCost field represents the non-directional cumulative cost of this route. Cost is not accrued for movement within habitat cores, thus the portion of each path that falls within a core’s boundary should be considered schematic only. These paths can be used to create a network dataset for use in additional analysis. If a network dataset is created, it should be cost-based, rather than length-based due to the schematic and costless nature of traveling within a core. The PathCost, LowCoreValue, and HighCoreValue fields were used to generate a network graph.While least cost paths are useful for illuminating the discrete path of least resistance from one location to another, they should not be interpreted as least cost corridors. Least cost corridors expand least cost paths to encompass functionally larger areas that may facilitate species movement.

Trail Accesses (Trail Heads filtered view points) - PA State Parks DCNR Esri connector, then filter out where Trails Access file - SUBTYPE_CODE = '9' to find the Trail heads data.

Cycle Network Connectors - OCP 8383 & Active Transportation Plan

This layer contains hydrography such as streams, rivers, and other linear hydrography features. Hidden hydrography, inferred drainage connectors, or culverts connect visible hydrography to form a continuous network. These connectors or hidden features maintain a predictable direction connecting the 2 points that conceal or infer the feature. Streams: Captured as single line if less than two meters wide. Both water edges plotted if wider than two meters. Docks and Piers: Visible outline delineated. Jetty: Visible outline delineated. Seawall: Single line plotted at the face of the seawall. Hidden Hydrography: Hidden hydrography is not obvious, even to someone standing under a bridge for example; it cannot be seen photogrammetrically and can be captured only from other sources. Segments of rivers, streams, and canals that flow under features such as bridges and roads are captured as continuous portions of the river, stream, or canal.

Note - this data is intended to be used with the "Maryland Road-Separated Bicycle Routes" hosted feature (view) layer hosted by MDOT and not in isolation.Maryland Road-Separated Connectors data comprises linear geometric features which represent the connections for bicycle routes that are separated from roadways carrying motorized vehicle traffic throughout the State of Maryland to road centerlines. This data is primarily used for the purposes of network analysis and in many instances, the 'connectors' are GIS vector creations and not true, paved, bicycle connections. This data is complimentary and to be used in conjunction with the "Maryland Road-Separated Bicycle Routes" hosted feature view layer (also hosted by MDOT). That data - and these connections from roadway to that data - are used to map Bicycle routes that are Shared-Use Paths, typically 10-feet wide, which can be used for transportation or recreational-related purposes.ATTRIBUTES:Route Name (if Applicable): The name of the route is provided if the route is namedCounties within Route: The counties in Maryland through which the route passes are listedRoute's Length: The route distance is calculated and listed in miles. Note that this is the length of the entire named route - and not just the segment selected. Distance calculated using the NAD 1983 StatePlane Maryland FIPS 1900 (US Feet) Projection.LTS Score: Level of Traffic Stress. For this map (road-separated routes) the scores range from 0 (road-separated) to 2 (generally low traffic). The areas that are not 0 in this map/data represent portions of the road-separated routes that cross streets or have portions that are briefly on-road as connections.

This connector wye feature class represents current wastewater information in the City of Los Angeles. The connector wye is the location of a chimney. The Mapping and Land Records Division of the Bureau of Engineering, Department of Public Works provides the most rigorous geographic information of the sanitary sewer system using a geometric network model, to ensure that its sewers reflect current ground conditions. The sanitary sewer system, pump plants, wyes, maintenance holes, and other structures represent the sewer infrastructure in the City of Los Angeles. Wye and sewer information is available on NavigateLA, a website hosted by the Bureau of Engineering, Department of Public Works.For a complete list of attribute values, please refer to (TBA Wastewater data dictionary). Wastewater Connector Wye points layer was created in geographical information systems (GIS) software to display the location of wastewater connection points at the wye pipe lines. The connector wye layer is a feature class in the LACityWastewaterData.gdb Geodatabase dataset. The layer consists of spatial data as a point feature class and attribute data for the features. The connector wye points are entered when the wye pipe lines are edited based on wastewater sewer maps and BOE standard plans, and information about the points is entered into attributes. The connector wye is a structure connected to the wye pipe line. Reference the WYE_SUBTYPE field for the type of structure. The WYE_ID field value is the unique ID. The WYE_ID field relates to the Sewer Permit tables. The wastewater connector wye points are inherited from sewer spatial data originally created by the City's Wastewater program. The database was known as SIMMS, Sewer Inventory and Maintenance Management System. Wye pipe information should only be added to the Wastewater wye pipes layer if documentation exists, such as a wastewater map approved by the City Engineer. Sewers plans and specifications proposed under private development are reviewed and approved by Bureau of Engineering. The Department of Public Works, Bureau of Engineering's, Brown Book (current as of 2010) outlines standard specifications for public works construction. For more information on sewer materials and structures, look at the Bureau of Engineering Manual, Part F, Sewer Design, F 400 Sewer Materials and Structures section, and a copy can be viewed at http://eng.lacity.org/techdocs/sewer-ma/f400.pdf.List of Fields:REHAB: This attribute indicates if the pipe has been rehabilitated.BOTTOM: When a chimney is present, this is the depth at the bottom of the chimney.TOP_: When a chimney is present, this is the depth at the top of the chimney.PL_DEPTH: This value is the depth of the service connection at the property line.TYPE: This is the old wye status and is no longer referenced.SHAPE: Feature geometry.LAST_UPDATE: Date of last update of the point feature.USER_ID: The name of the user carrying out the edits of the wye data.SPECIAL_STRUCT: This describes the special structure. The design of the special structure doesn't follow the BOE Standard Plans.PIPE_ID: The value is a combination of the values in the UP_STRUCT, DN_STRUCT, and PIPE_LABEL fields. This is the 17 digit identifier of each pipe segment and is a key attribute of the pipe line data layer. This field named PIPE_ID relates to the field in the Annotation Pipe and to the field named PIPE_ID in the Pipe line feature class data layers.WYE_NO: This value is the number of the line segment for the wye structure located along the pipe segment. This is a 2 digit value. The number starts at 1 for the first wye connected to a pipe. The numbers increase sequentially with each wye being unique.C_HUNDS: This value is the hundreds portion of the stationing at the curb line.DEPTH: This value is the depth of the Wye from the surface in feet.STAT_TENS: This value is the tens portion of the stationing.WYE_SUBTYPE: This value is the type of sewer connection. Values: • 1 - Vertical tee. • 7 - . • 3 - Offset Chimney. • 4 - . • 2 - Chimney.ENABLED: Internal feature number.PL_TENS: This value is the tens portion of the stationing at the property line.SIDE: The side of the pipe looking up stream to which structure attaches. Values: • R - Right. • L - Left. • C - Centered. • U - Unknown.ENG_DIST: LA City Engineering District. The boundaries are displayed in the Engineering Districts index map. Values: • H - Harbor Engineering District. • C - Central Engineering District. • V - Valley Engineering District. • W - West LA Engineering District.STATUS: This value is the active or inactive status of the connector wye. Values: • INACT - Inactive. • ABAN - Abandoned. • ACT - Active. • PROP_ACT - Proposed Active. • ABAN - Proposed Inactive.BASIN: This attribute is the basin number.OBJECTID: Internal feature number.C_TENS: This value is the tens portion of the stationing at the curb line.STAT_HUND: This value is the hundreds portion of the stationing.SERVICEID: User-defined unique feature number that is automatically generated.CRTN_DT: Creation date of the point feature.WYE_ID: The value is a combination of PIPE_ID and WYE_NO fields, forming a unique number. This 19 digit value is a key attribute of the wye lines data layer. This field relates to the Permit tables.PL_HUNDS: This value is the hundreds portion of the stationing at the property line.REMARKS: This attribute contains additional comments regarding the wye line segment, such as a line through in all caps when lined out on wye maps.ASSETID: User-defined unique feature number that is automatically generated.C_DEPTH: This value is the depth of the service connection at the curb line.

The USGS Transportation service from The National Map (TNM) is based on TIGER/Line data provided through U.S. Census Bureau and road data from U.S. Forest Service. Some of the TIGER/Line data includes limited corrections done by USGS. Transportation data consists of roads, railroads, trails, airports, and other features associated with the transport of people or commerce. The data include the name or route designator, classification, and location. Transportation data support general mapping and geographic information system technology analysis for applications such as traffic safety, congestion mitigation, disaster planning, and emergency response. The National Map transportation data is commonly combined with other data themes, such as boundaries, elevation, hydrography, and structures, to produce general reference base maps. The National Map Download Client allows free downloads of public domain transportation data in either Esri File Geodatabase or Shapefile formats. For additional information on the transportation data model, go to https://nationalmap.gov/transport.html.

This applications purpose is to create a common operating picture (COP) for emergency related events that are occurring in the State of Arizona & Regional Southwest. The application focuses on standard Incident Command System (ICS) that goes Local, County, State, & Federal Government. The application uses a variety of data-sources including the Bi-Directional Connector from WebEOC to report Event Reporting, Shelters, and Road Closures.

Stormwater Connectors in the City of Port Adelaide Enfield.

This layer displays all the catch basins, catch basin grated tops, sandboxes, junction boxes, inlets and trash racks within the City of Seattle (and the former service area north of the City limits) regardless of ownership.A catch basin is a connector to the storm drain system that typically includes an inlet where stormwater enters the catch basin and a sump to capture sediment, debris, and associated pollutants prior to the surface water flowing into a storm or sewer pipe. There are two main types of inlets: side inlets and grated inlets. Side inlets are located adjacent to the curb and rely on the ability of the opening under the curb to capture flow. Grated inlets have gratings or metal grids to prevent large objects and debris from falling into the combined sewer or drainage system. They collect surface runoff for conveyance in a pipe system. Sandboxes have wooden lids and are filled with sand or gravel and drain directly into the ground or to a culvert as part of the informal drainage system. Sandboxes are no longer being installed. Junction boxes are cement structure with a grated metal lid, shallow in depth, generally connect culverts and are inline as part of the informal ditch and culvert system. Trash racks are grated structures that collect debris. Trash racks may be on maintenance holes, catch basins, other structures, or streams.Data source is DWW.catch_basin_pt_pv, and DWW.APPURTENANCE_PT_PV. Maintained by SPU GIS DWW Data Maintenance staff. This layer does not display when zoomed out beyond 1:899.Refreshed daily.

About the Bay Trail Gap Closure Implementation PlanThe Bay Trail Gap Closure Implementation Plan (BTGCIP) sets priorities for future work to complete the vision of the San Francisco Bay Trail—an interconnected system of on- and off-street trails circumnavigating San Francisco and San Pablo Bays. Implementation of the trail began in the early 1990s and continues today. The purpose of the BTGCIP is to identify and evaluate segments of the Bay Trail and Connector Trails that are currently missing (i.e., trail gaps) in order to prioritize their design and construction as the full build-out of the Bay Trail is implemented. For more details about the Bay Trail Gap Closure Implementation Plan, scoring methodology, and results, please visit the Bay Trail Gap Closure Implementation plan website (https://mtc.ca.gov/operations/regional-trails-parks/san-francisco-bay-trail/bay-trail-gap-closure-implementation-plan) and interactive map (https://experience.arcgis.com/experience/817c5f3b503848deb44e83d337285fd6/#data_s=id%3AdataSource_2-18e39aa3ee3-layer-17%3A86). History of the San Francisco Bay TrailSenate Bill 100, authored by then-state Senator Bill Lockyer and passed into law in 1987, directed the Association of Bay Area Governments (ABAG) to develop a plan for this regional trail system including a specific alignment for the Bay Trail.The Metropolitan Transportation Commission works with ABAG to implement the Bay Trail Plan, adopted by ABAG in July 1989. It includes a proposed alignment; a set of policies to guide the future selection, design, and construction of routes; and strategies for implementation and financing. Since its inception, the Bay Trail Plan has enjoyed widespread support in the region.

EPA Southeastern Ecological Framework

The EPA developed a GIS model to identify environmentally unique areas within the southeastern part of the country through the Southeastern Ecological Framework Project. Ecologically important areas were prioritized after organizing the data into four categories: Habitat Hubs, Priority Ecological Areas, Significant Ecological Areas, and Habitat Linkage areas. Last updated: 2015

This layer contains the shapes of the four circulators (Purple, Green, Orange, Banner) as well as the three Harbor Connector Ferry Routes, which are part of the Charm City Circulator transit system. The layer was converted from GTFS format to GIS format. Any and all variations are displayed in this layer. Created by Central Maryland Regional Transit (CMRT). This is a MD iMAP hosted service. Find more information on https://imap.maryland.gov.Feature Service Layer Link: https://mdgeodata.md.gov/imap/rest/services/Transportation/MD_LocalTransit/FeatureServer/13

Area Regional Transit (ART) fka Treasure Coast Connector. This is a bus route layer for St Lucie County Florida, includes: transit routes, bus stops and places of interest. Mapping application of the Area Regional Transit system within St Lucie County Florida, There are 7 bus routes that serve St Lucie County. We have 1 park and ride location and 2 Inter-modal transit facilities. Area Regional Transit (ART) formally known as Treasure Coast Connector

National Highway System (NHS) connectors are roads, which may be either state or locally owned, which connect intermodal facilities to major highways on the National Highway System. The NHS Connectors in this data layer are officially designated NHS freight connectors that serve any of three types of facilities: intermodal rail facility, port, and/or airport. These routes were digitized based on DVRPC's street centerline data set to correspond with the officially designated NHS Connector routes.

The Gilpin County Parcel Fabric provides a single source of titled and surveyed lands in Gilpin County, Colorado. This dataset is best viewed through the Gilpin County Parcel Fabric Viewer.Gilpin County is in the early stages of rebuilding all surveyed lands within the County. This is complicated by significant known positional errors in the BLM Cadastre of 1 to 300-meters on section corners along with information that has been lost over the last 150 years. The current focus is the residential core of Gilpin County and Central City. It is expected that this project will take several years to complete. Every attempt is made to enter the data as accurately as possible. THIS DATA IS NOT SURVEY-GRADE. It is intended to assist surveyors to locate monuments in the field and provide historical context for properties, when possible. The Records layer contains valuable information in the Notes field for any assumptions or alterations made to the conversion of surveys to GIS. NOTE TO SURVEYORS: To accurately calculate the ground-to-grid conversion of your plats, please submit the XYZ coordinates of the Basis of Bearing monuments in Colorado State Plane North, NAD83 (NAVD88 for Z), U.S. Survey Feet on your plat. Thank you.

Bicycle-pedestrian facilities consisting of the Maybrook, Putnam, and connector trails within and immediately surrounding Putnam County. Both the Putnam and the Maybrook Trailways are part of New York's Empire State Trail (EST). The EST is a 750-mile rail trail that traverses the state from Buffalo to Albany and from New York City to the Canadian border.

Bike Routes that are made up of separate layers consisting of Connectors, Regional and Statewide routes.

Fairfax Connector is the largest local bus system in the Northern Virginia region transporting approximately 26,000 passengers on 93 routes daily. This system map shows all Fairfax Connector routes in service.Contact: Fairfax County Department of Transportation (FCDOT)Data Accessibility: PublicUpdate Frequency: As needed

This layer was created as part of Esri’s Green Infrastructure Initiative and is one of five newly generated companion datasets that can be used for Green Infrastructure (GI) planning at national, regional, and more local scales. If used together, these layers should have corresponding date-based suffixes (YYYYMMDD). The corresponding layer names are: Intact Habitat Cores, Habitat Connectors, Habitat Fragments, Habitat Cost Surface, and Intact Habitat Cores by Betweeness. These Esri derived data, and additional data central to GI planning from other authoritative sources, are also available as Map Packages for each U.S. State and can be downloaded from the Green Infrastructure Data Gallery.

This layer represents Intact Habitat Cores, symbolized based on their connectivity importance (Betweenness Centrality (BC). BC provides a metric depicting each core’s importance in a connectivity network, thus illuminating each core’s relative contribution to facilitating landscape connectivity and potential species movement. BC represents the number of paths that flow through a given habitat core. It is normalized by the total number of shortest paths between all pairs of nodes, except those paths connecting immediate neighbors. High BC values reflect greater use of that core in traversing the network, thus elevating the core’s importance in facilitating connectivity when compared to cores of lower value. Every time you change your viewing extent, the layer dynamically recalculates to depict the most important cores, based on its betweenness centrality value.

The Habitat Cost Surface layer was used to generate a comprehensive network of Least Cost Paths (LCPs) amongst the Intact Habitat Cores layer. This was accomplished using the Cost Connectivity tool which was introduced in ArcGIS 10.4 and ArcGISPro in 1.3. The resulting Habitat Connectors layer was then utilized as the network upon which BC was calculated. The Betweenness_Centrality function in the NetworkX Python library was used to first calculate the number of cost based optimal paths passing through each core and then dividing this number by the range of values in the LCP Routes field. This work was based on the NetworkX Parallel Betweenness example. Data Coordinate System: NAD_1983_Albers