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.

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

Cycle Network Connectors - OCP 8383 & Active Transportation Plan

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.

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.

Fort Circle Connectors

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.

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.

Medium- and heavy-duty (MDHD) zero-emission vehicle (ZEV) hydrogen refueling and charging station data was collected from the following agencies: California Air Resources Board (CARB), California Energy Commission (CEC), CALSTART Inc., California State Transportation Agency (CalSTA), California Department of Transportation (Caltrans), California Transportation Commission (CTC) and San Diego Gas & Electric (SDGE). “Chargers” (charging): Typically high-powered (150 kW or more) direct current fast chargers (DCFCs) for simultaneous charging at each location. “Dispensers” (hydrogen): Typically 700-bar dispensers for simultaneous refueling at each location. “Nozzles” (both charging/hydrogen): Connector that latches to the ZEV for charging or refueling.Following data fields are included:Charging or Hydrogen: Whether the station is classified as charging or hydrogenCharger or Dispenser Count: Number of chargers for DCFC and number of dispensers for hydrogenNozzle Count: Number of nozzlesAddress: Location of the stationLatitudeLongitudeFunding Agencies: Agency/agencies that have provided funding for building the stations

The National Highway System consists of a network of roads important to the economy, defense and mobility. On October 1, 2012 the existing National Highway System (NHS) was expanded to include all existing Principal Arterials (i.e. Functional Classifications 1, 2 and 3) to the new Enhanced NHS. Under MAP-21, the Enhanced NHS is composed of rural and urban roads nationwide serving major population centers, international border crossings, intermodal transportation facilities, and major travel destinations.The NHS includes:The Interstate System. Other Principal arterials and border crossings on those routes (including other urban and rural principal arterial routes, and border crossings on those routes, that were not included on the NHS before the date of enactment of the MAP-21).Intermodal connectors -- highways that provide motor vehicle access between the NHS and major intermodal transportation facilities. STRAHNET -- the network of highways important to U.S. strategic defense. STRAHNET connectors to major military installations.

Open the Data Resource: https://www.chesapeakeconservation.org/our-work/goal-mapping/habitat Open the Map Viewer: https://chesbay.maps.arcgis.com/apps/instant/basic/index.html?appid=e961d8ef2367436d8a3603b3491f0b2b Open the Map Service:https://cicgis.org/arcgis/rest/services/CCP/Habitat/MapServer The Chesapeake Conservation Partnership Habitat Model is a suitability model aimed at identifying a network of large natural areas and corridors sufficient to allow nature to respond to a changing climate and land development, support thriving populations of native wildlife, migratory birds, fish and plants, and sustain at-risk species. This map focuses on four mappable resources: The lotic core network (rivers and streams), lentic core network (lakes and ponds), aquatic buffers and a terrestrial core-connector network. The data layer includes the following: Aquatic Core Network: This consists of the streams, lakes and ponds that are intact, connected and support a wide diversity of aquatic species and ecosystems. The core areas are based on the Index of Ecological Integrity and are scaled to HUC 6 watersheds and were developed through a set of regional analyses that assess the physical and biological value of aquatic systems and species across the Northeast region. Aquatic Buffers: Aquatic buffers surround the aquatic (both lotic and lentic) cores. Buffers represent the areas estimated to have a strong influence on the integrity of the aquatic cores based on watershed processes. Terrestrial Core-connector Network: Core areas are intact, well-connected places that, if protected, will continue to support a broad diversity of fish, wildlife, plants and the ecosystems on which they depend. These include especially intact, resilient examples of each major ecosystem type. They contain widespread ecosystems such as hardwood forests, rare natural communities and important habitat for a variety of fish, wildlife and plants. Core areas are stratified by HUC 6 watersheds. Core areas are linked together by a network of connectors. The connectors allow movement of animals and plants from one core area to another, and establish a flow pattern for ecological features and processes, as landscape conditions and climate change. Note: The initial terrestrial core-connector network did not seem to sufficiently address landscape features adjacent to tidal waters that contribute to tidal aquatic habitat integrity. To partially address this, a National Wetlands Inventory derived potential black duck habitat layer was used to supplement the terrestrial core network. Future deliberations of the partnership will consider ways to strengthen the assess and prioritize the habitat conservation value of wetlands and terrestrial habitat adjacent to tidal waters.

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

These data have been compiled by the Martha's Vineyard Commission. This Island-wide network of trails has been GPSed with various GPS devices over the years. The accuracy of each trail segment does vary based on GPS device. Some Connector Roads were either on-screen digitized or imported from MassDOT or MassGIS Roads data layers.Attribution is included to indicate surface, special designation, status - managed/unmanaged, open space/conservation property the trail is associated with, etc.This dataset also contains the trails that are used in the TrailsMV App spearheaded by the Sheriff's Meadow Foundation. To view only the App trails, set a filter/definition query to [Show in TrailsMV] = yes. This is the dataset that is also used in the Walking Trails of Martha's Vineyard book published by the Vineyard Conservation Society. Lastly, this dataset is also used for the Martha's Vineyard Land Bank's 'Conservation Lands Map' brochure. To see only those trails utilized on the MVLB map, set the filter to [Show on MVLB] = yes.This online dataset is the most current. The other products were current at date of publication or last data upload to the TrailsMV App. As of 8/11/2022, this view of the trails data does not include planned trails.The MVC is grateful to the MV Island-wide Conservation Partnership for making it possible to work collaboratively to compile such an awesome trail network and freely share it with the world.

Web map depicting road-separated bicycle routes throughout the State of Maryland. In many instances these routes can be used by pedestrians, but not by any motorized vehicle. “Road Separated” indicates that these segments are physically separated from roads in which motorized vehicles travel. That is, these are not bike lanes, sharrows, or signed bike routes per se – these segments are separated from the main road by a physical barrier (E.g., grass, natural earth, trees, etc.) and in many instances do not follow a motorized vehicle route network at all (E.g., a wholly separated trail). This information in this web map will be used in conjunction with the One Maryland One Centerline (OMOC) initiative to provide a Level of Traffic Stress (LTS) map for the State of Maryland. The recommended LTS score for each road-separated bicycle route is listed in the pop-up menu.Bikeways included in the map are of varying surface material but are typically paved or hard-packed surface. Sidewalks, typically 6-feet-wide, hard surface pathways primarily for pedestrian use, are not included in this map. The preferred width of bikeways included is at least 10-feet wide, although bikeways may be narrower if anticipated traffic volumes are minimal. For instance, while most pathways within Columbia are 8 to 10 feet wide, some pathways are narrower when connecting to cul-du-sacs. These narrower pathways are included in the map as the anticipated traffic volume are low enough to minimize user conflict. The feature class used in the web map was compiled by the Maryland Department of Transportation (Secretary’s Office) using a variety of sources including (but not limited to) state data sources from various agencies including the Maryland Department of Transportation (MDOT), Maryland Department of Planning (MDP), and Maryland Department of Natural Resources (DNR). Data has also been augmented by counties and municipalities throughout the State of Maryland as well as several agencies, organizations, and conservancies. Certain named trails are included within this dataset and their sources have varied from state, local, and non-profits as well as through the digitizing of various aerial/satellite imagery, digital elevation models (DEM), right-of-ways, former railways, and corridors by MDOT staff. None of the alignments included in this dataset are restricted to private use.The searchable data includes attribute information containing the route’s name (if applicable), calculated segment length (using the Maryland State Plane 1983 Projection), and Level of Traffic Stress (LTS) score. The data mostly contains alignment segments with a LTS of 0, the lowest score. This score indicates that the bikeway can be comfortably used by cyclists of all levels and experience and has minimal automobile traffic interaction. There are several segments with LTS scores of 1 or 2 within this feature class as well, but these are mostly connector paths/trails between larger segments. LTS scores of 1 or 2 indicate very little automobile traffic and/or slower speeds required for the automobile traffic.This web map will be updated as needed but is scheduled to be comprehensively reviewed on an annual basis. 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 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.

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.

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

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 dataset contains the 43 passages of the Arizona Trail, a National Scenic Trail. It has been converted from GPX files which have been gathered by volunteers and agency employees for the Arizona Trail Association (501c3 Charitable organization) with a number of different types of Garmin to Trimble GPS units. Links to the description for each passage are within the attribute table. For more information on the Arizona Trail visit www.aztrail.orgMay 1, 2015 - This is a newly digitized data set at 1:1200 scale using Statewide aerial imagery, GPS data, LiDar and 10M USGS DEM for 3D values that represents the Arizona National Scenic Trail. For further details about the the trail and to download GPX files for each passage that fit onto GPS devices please visit www.aztrail.org