ArcGIS REST Services Directory
JSON

Layer: CTDOT_PublicTrans_BusRoutes (ID:25)

View In:   Map Viewer

Name: CTDOT_PublicTrans_BusRoutes

Display Field: BusRouteName

Type: Feature Layer

Geometry Type: esriGeometryPolyline

Description: This feature class contains polyline bus route features that were provided to the CTDOT in various file formats (GIS Shapefile or GTFS data package). The data was compiled, edited, and verified by referencing PDF maps and schedules published on Transit Service Provider (TSP) websites. Each bus route's linear geometry captures all possible fixed route variations that run Monday through Sunday. Sub route variations that can be used to identify specific trips along the bus route's existing geometry are currently being built out in a separate database. Uncommon Field Names: Route_Number: The current bus route number according to the transit system/Transit Service Area (TSA) the bus route is operated in State_Bus_Number: A route number proposed under a new statewide numbering system yet to take effect Route_Name: An approximation of the name of the route on the schedule posted for each route by the TSP or the names of areas the route extends to if no other route names were provided by the TSP Service_Mode: Indicates the type of bus service provided – Bus Rapid Transit (BRT), Local, Express, Shuttle, or Loop Operator: The operator of the bus route. *The operator is the operator of the TSA's fixed route service and may differ from the TSP responsible for managing and funding the service or the TSP that provides ADA paratransit service. Service_Area: The transit system/TSA of the bus routes according to TSP. Symbolize this field to view bus stops by TSP system.

Copyright Text: The following credits list the TSP/regional COG responsible for managing the GIS data for the given TSA. Edits made on an irregular as-needed basis may result in slight differences in route geometry. • Cttransit routes for Hartford, Meriden, New Haven, Stamford, and Waterbury were provided as shapefiles by 1st Transit on 01/24/2020 • Cttransit routes for Bristol and New Britain were provided as a shapefile by 1st Transit on 02/13/2020 • Greater Bridgeport Transit routes were provided as GTFS data by GBT on 01/30/2020 and as a shapefile by MetroCOG on 01/31/2020 • Norwalk routes were provided as a shapefile by WestCOG on 01/29/2020 • Southeast Area Transit routes were digitized by hand using published schedules and route maps by the Bureau of Public Transportation on 01/29/2020 • Housatonic Area Regional routes were provided as a shapefile by WestCOG on 01/29/2020 • Middletown Area routes were digitized by hand using published schedules and route maps by the Bureau of Public Transportation on 02/07/2020 • Windham Region routes were provided as GTFS data by WRTD on 01/30/2020 • Milford routes were provided as a shapefile by SCRCOG on 12/18/2019 • Northwestern CT routes were digitized by hand using published schedules and route maps by the Bureau of Public Transportation on 02/06/2020 • Estuary routes were provided as GTFS data by Estuary - 9 Town Transit on 01/30/2020 • Northeastern CT routes were provied as a shapefile by NECCOG on 02/04/2020

Min. Scale: 0

Max. Scale: 0

Default Visibility: true

Max Record Count: 2000

Supported query Formats: JSON, geoJSON, PBF

Use Standardized Queries: True

Extent:

Drawing Info:

HasZ: false

HasM: true

Has Attachments: false

Has Geometry Properties: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Object ID Field: OBJECTID

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:
Templates:

Is Data Versioned: false

Has Contingent Values: false

Supports Rollback On Failure Parameter: true

Last Edit Date: 11/11/2024 4:45:29 PM

Schema Last Edit Date: 11/11/2024 4:45:29 PM

Data Last Edit Date: 11/11/2024 4:45:29 PM

Supported Operations:   Query   Query Pivot   Query Top Features   Query Analytic   Query Bins   Generate Renderer   Validate SQL   Get Estimates   ConvertFormat