This data set contains the full system map of the Fairfax Connector bus routes.Contact: Fairfax County Department of TransportationData Accessibility: Publicly AvailableUpdate Frequency: As NeededLast Revision Date: 2/9/2023Creation Date: 2/9/2023Feature Dataset Name: DOTMGR.TRANSITLayer Name: DOTMGR.FAIRFAX_CONNECTOR_SYSTEM

Cycle Network Connectors - OCP 8383 & Active Transportation Plan

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.

The Trimble TAIP Connector for GeoEvent Server allows you to receive messages in the TAIP format.

Access the Trimble TAIP Connector for GeoEvent Server GitHub project here.

Releases

Each release contains a connector compatible with the version of GeoEvent Server listed. The release of the component you deploy does not have to match your version of ArcGIS GeoEvent Server, so long as the release of the component is compatible with the version of GeoEvent Server you are using. For example, if the release contains a connector for version 10.6; this connector is compatible with ArcGIS GeoEvent Server 10.6 and later. Each release contains a Release History document with a compatibility table that illustrates which versions of ArcGIS GeoEvent Server the component is compatible with.

NOTE: The release strategy for ArcGIS GeoEvent Server components delivered in the ArcGIS GeoEvent Server Gallery has been updated. Going forward, a new release will only be created when

  a component has an issue,
  is being enhanced with new capabilities,
  or is not compatible with newer versions of ArcGIS GeoEvent Server.

This strategy makes upgrades of these custom
components easier since you will not have to
upgrade them for every version of ArcGIS GeoEvent Server
unless there is a new release of
the component. The documentation for the
latest release has been
updated and includes instructions for updating
your configuration to align with this strategy.

Latest

Release 9 - October 24, 2019 - Compatible with ArcGIS GeoEvent Server 10.4 and later.

Previous

Release 8 - September 13, 2019 - Compatible with ArcGIS GeoEvent Server 10.4 and later.

Release 7 - August 14, 2019 - Compatible with ArcGIS GeoEvent Server 10.4 and later.

Release 6 - June 15, 2018 - Compatible with ArcGIS GeoEvent Server 10.5 and later.

Release 5 - May 3, 2016 - Compatible with ArcGIS GeoEvent Server 10.4 and later.

Release 4 - April 28, 2016 - Compatible with ArcGIS GeoEvent Server 10.4 and later.

Release 3 - May 3, 2016 - Compatible with ArcGIS GeoEvent Server 10.3.x.

Release 2 - April 28, 2016 - Compatible with ArcGIS GeoEvent Server 10.3.x.

Release 1 - January 6, 2014 - Compatible with ArcGIS GeoEvent Server 10.2.x.

{ "releases": [{ "name": "TrimbleTAIP", "galleryItemId": "8513241a8c9445339d108185642f7af9", "galleryItemUrl": "https://www.arcgis.com/home/item.html?id=8513241a8c9445339d108185642f7af9", "installBaseUrl": "/gallery/TrimbleTAIP/", "installHistoryUrl": "/gallery/TrimbleTAIP/Release History.pdf", "installDocumentationUrl": "/gallery/TrimbleTAIP/GeoEvent Server - Trimble TAIP Connector.pdf", "releaseDate": "2019-10-24T00:00:00Z", "releaseItemId": "62853c56471d4e08b6c7fba77de1aade", "releaseItemUrl": "https://www.arcgis.com/sharing/rest/content/items/62853c56471d4e08b6c7fba77de1aade/data", "sdkVersion": "10.4.0", "compatibilityMin": "10.4.0", "compatibilityMax": "", "releaseNumber": 9, "releaseName": "Release 9", "releaseFileName": "GeoEventServer-TrimbleTAIPConnector-R9.zip", "components": [{ "buildDate": "2019-10-24T00:00:00Z", "groupId": "com.esri.geoevent.adapter.trimble.taip", "artifactId": "trimble-taip-adapter", "symbolicName": "com.esri.geoevent.adapter.trimble.taip.trimble-taip-adapter", "uri": "com.esri.geoevent.adapter.trimble.taip/trimble-taip-adapter/10.4.0", "fileName": "trimble-taip-adapter-10.4.0.jar" }] }] }

Local connector alignments and designations were adopted as part of the Comprehensive Transportation Plan element of Advance Apex. The Plan was adopted February 5, 2019, and subsequent amendments have been approved by Town Council.

To create and display land information where one polygon contains multiple Assessor Parcels as of FY 2021. THE GIS DATA IS PROVIDED "AS IS". THE COUNTY MAKES NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OR MERCHANTABILITY AND/OR FITNESS FOR A PARTICULAR PURPOSE, REGARDING THE ACCURACY, COMPLETENESS, VALUE, QUALITY, VALIDITY, MERCHANTABILITY, SUITABILITY, AND CONDITION, OF THE GIS DATA. USER'S OF COUNTY'S GIS DATA ARE HEREBY NOTIFIED THAT CURRENT PUBLIC PRIMARY INFORMATION SOURCES SHOULD BE CONSULTED FOR VERIFICATION OF THE DATA AND INFORMATION CONTAINED HEREIN. SINCE THE GIS DATA IS DYNAMIC, IT WILL BY ITS NATURE BE INCONSISTENT WITH THE OFFICIAL COUNTY DATA. ANY USE OF COUNTY'S GIS DATA WITHOUT CONSULTING OFFICIAL PUBLIC RECORDS FOR VERIFICATION IS DONE EXCLUSIVELY AT THE RISK OF THE PARTY MAKING SUCH USE.

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.

Legislative AuthorizationAssembly Bill 1808 appropriated $4 million to establish the California Geographic Lead Agencies (Lead Agency) to build the capacity of county offices of education (COEs) to ensure that counties are equipped to build the capacity of their local educational agencies (LEAs) to support the continuous improvement of student performance within the state priorities as defined in California Education Code (EC) sections 52060 and 52066 and address the gaps in achievement between student groups as defined in EC Section 52052.PurposeThe 6 to 10 Lead Agencies will work together to support the following goals for all counties. The Lead Agencies will also connect COEs to the other initiatives within California's System of Support.Support the continuous improvement of student performance within the state priorities across student groups as defined in EC sections 52060 and 52066.Address the gaps in achievement between student groups as defined in EC Section 52052.Improve outreach and collaboration with stakeholders to ensure that goals, actions, and services as described in school district and COEs Local Control and Accountability Plans reflect the needs of the community, especially for historically under-represented or low-achieving populations.Serve as a facilitator, resource connector, and capacity builder for COEs.Funding DescriptionEach Lead Agency is selected for a term ending no later than June 30, 2023. Each awardee will receive a minimum of $250,000 and additional funds will be allocated based on a formula derived from the 2018 list of school districts eligible for differentiated assistance

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

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.

The truck freight economic corridor designation is built upon Freight and Goods Transportation System (FGTS) tonnage classification and takes into account freight system resiliency and first/last mile connectivity to freight land uses and facilities. A truck freight economic corridor designation helps understand how freight connectors are being used by industry, and informs future planning efforts to identify the needs and opportunities for improving those connectors. This designation includes three components: 1) High volume truck corridors: T-1 and T-2 freight corridors that are defined in the FGTS as carrying at least four million tons of gross truck tonnage per year; 2) Alternative freight routes: routes that serve as alternatives to primary cross-state freight routes during severe weather or other disruptions to increase freight system resiliency; 3) First/last mile connector routes: truck routes that connect freight-intensive land uses to T-1 and T-2 freight corridors, and alternative freight routes. First/last mile connectors provide important freight linkages to strategic national defense facilities, significant intermodal facilities, warehouse districts, industrial land and distribution centers, and agricultural processing centers, and the National Highway Freight Network. For more information about this designation, please visit https://www.wsdot.wa.gov/freight/fgts

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

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.

This PDF is hosted on UPLAN to prevent hotlinking to outside resources which may become broken over time. This document details the Guidance Criteria for Evaluating Requests for Modifications to the National Highway System. It is provided to document the criteria required for a route to be designated as an intermodal connector. These routes connect significant freight centers to the National Highway System of freight routes. It is current as of 1/2017.About the destination story map: This series of maps contains the extent information for the Utah Freight Network through the series of subsequent federal funding bills. There are no plans for it to be refreshed. It contains time enabled data that may be subject to change in subsequent funding bills.

The extents of proposed urban and rural critical freight routes, as well as various proposals of intermodal connectors are displayed.For questions on the data, please contact Vern Keeslar at vkeeslar@parametrix.com.

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

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

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.

This service is used in the Utah's Highway Freight Network app and related maps. It contains proposed Intermodal Connector extents as proposed to the FHWA connecting facilities to the Utah Highway Freight network. ||For questions on the data, please contact the UDOT Freight and Railroad Planner, Daniel Kuhn at dkuhn@utah.gov.