20260707 13071000 1.0 FALSE Transit_Routes_GTFS 002 6175807.554758 6581848.238410 1777930.812890 2089363.612267 1 Projected GCS_North_American_1983 Linear Unit: Foot_US (0.304801) <ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'><WKT>PROJCS["NAD_1983_StatePlane_California_VI_FIPS_0406_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",6561666.666666666],PARAMETER["False_Northing",1640416.666666667],PARAMETER["Central_Meridian",-116.25],PARAMETER["Standard_Parallel_1",32.78333333333333],PARAMETER["Standard_Parallel_2",33.88333333333333],PARAMETER["Latitude_Of_Origin",32.16666666666666],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2230]]</WKT><XOrigin>-118608900</XOrigin><YOrigin>-91259500</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>-100000</ZOrigin><ZScale>10000</ZScale><MOrigin>-100000</MOrigin><MScale>10000</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.001</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>102646</WKID><LatestWKID>2230</LatestWKID></ProjectedCoordinateSystem> NAD_1983_StatePlane_California_VI_FIPS_0406_Feet 20260706 15435500 20260706 15435500 150000000 5000 dataset 20260706 File Geodatabase Feature Class Data Librarian SanGIS Data Librarian 5500 Overland Ave, Suite 310 San Diego CA 92123 webmaster@sangis.org US 858-874-7000 Data Librarian Data can be downloaded in multiple formats (FileGDB, Shapefile, CSV, GeoJSON and JSON) from the SanGIS Data Warehouse at https://gis-sangis1.hub.arcgis.com/pages/download-data Refer to SanGIS website (www.sangis.org) to obtain further information on mapping and data extraction services available from SanGIS. Esri ArcGIS 13.5.5.57366 Transit_Routes_GTFS vector digital data Public transit routes covering the County of San Diego. Bus, commuter and light rail, and trolley routes managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Data is developed from the General Transit Feed Specification (GTFS) data available from the github mobility database. Layer is updated quarterly and may not reflect most current route information. <DIV STYLE="text-align:Left;"><DIV><DIV>Public transit routes in San Diego County managed by the San Diego County Metropolitan Transit System (MTS) and the North County Transit District (NCTD). Bus, commuter and light rail, and trolley routes managed and developed from the General Transit Feed Specification (GTFS) data available from the github mobility database. Routes are developed from the GTFS data available through the Github Mobility Database (<A href="https://www.sdmts.com/google_transit_files/google_transit.zip" STYLE="text-decoration:underline;">https://www.sdmts.com/google_transit_files/google_transit.zip</A> and <A href="http://www.gonctd.com/google_transit.zip" STYLE="text-decoration:underline;">http://www.gonctd.com/google_transit.zip</A>). GTFS data is provided to the exchange by the transit agencies and processed by SanGIS to create a consolidated GIS layer containing routes from both systems. SanGIS uses a publicly available ESRI ArcToolbox tool to create the GIS data layer. This data set is created using the ROUTES.txt and SHAPES.txt GTFS data files.Routes layers for MTS and NCTD are created separately and combined into a single layer using ArcGIS tools.</DIV></DIV></DIV> SanGIS using information provided by the San Diego Metropolitan Transit System and the North County Transit District Transit Routes Bus Rail Light Rail Trolley MTS NCTD San Diego <DIV STYLE="text-align:Left;"><DIV><DIV>Data is generalized and created for use in regional projects. Please refer to SanGIS GIS data end user use agreement and disclaimer which is available at the following: http://www.sangis.org.Data is as provided through the Github Mobility Database (<A href="https://www.sdmts.com/google_transit_files/google_transit.zip" STYLE="text-decoration:underline;">https://www.sdmts.com/google_transit_files/google_transit.zip</A> and <A href="http://www.gonctd.com/google_transit.zip" STYLE="text-decoration:underline;">http://www.gonctd.com/google_transit.zip</A>). . No representation is made as to the accuracy and currency of the data. Contributions to the feed registry are voluntary and outside SanGIS control. GTFS specifications are not managed or maintained by SanGIS and may change over time.Data layer is created from publicly available sources and is not verified, certified or endorsed by either MTS or NCTD. SanGIS does not verify alignments or accuracy of data. SanGIS recreates the Transit_Routes layer from the publicly available data only on a quarterly (or longer) basis and data may not be current.</DIV></DIV></DIV> Transportation, transit, bus lines, bus routes, light rail, trolley, commuter rail, public transportation California, County of San Diego, Carlsbad, Coronado, Chula Vista, Del Mar, El Cajon, Encinitas, Escondido, Imperial Beach, Lemon Grove, La Mesa, National City, Oceanside, Poway, San Diego, San Marcos, Solana Beach,Santee, Vista The spatial extent of this dataset is San Diego County. The Temporal Instant date is the date the feed was updated on the transit feeds for MTS and google transit feeds for NCTD. For MTS: 26 May 2026. For NCTD: 30 June 2026 2026-06-30T00:00:00 Data Librarian SanGIS Data Librarian 5500 Overland Ave, Suite 310 San Diego CA 92123 webmaster@sangis.org US 858-874-7000 1 -117.514230 -116.183874 33.400534 32.538233 782 EPSG 5.3(9.0.0) Transit_Routes_GTFS Feature Class 782 OBJECTID OBJECTID OID 4 0 0 Internal feature number. Esri Sequential unique whole numbers that are automatically generated. SHAPE Shape Geometry 0 0 0 Feature geometry. Esri Coordinates defining the features. shape_id shape_id String 255 0 0 Shape identifier created by ArcGIS processing tool ESRI route_id route_id String 255 0 0 The route_id field contains an ID that uniquely identifies a route. The route_id is dataset unique. Note that because this layer is a combination of two agency datasets, route_id may not be unique unless combined with the agency_id field GTFS Data Specification agency_id agency_id String 255 0 0 The agency_id field defines an agency for the specified route. This value is referenced from the agency.txt file. MTS = San Diego Metrolpolitan Transit System NCTD = North County Transit District GTFS Data Specification route_desc route_desc String 255 0 0 The route_desc field contains a description of a route which may provide useful, quality information. GTFS Data Specification route_type route_type String 255 0 0 The route_type field describes the type of transportation used on a route. Valid values for this field are: 0 - Tram, Streetcar, Light rail. Any light rail or street level system within a metropolitan area (includes Trolley) 1 - Subway, Metro. Any underground rail system within a metropolitan area. 2 - Rail. Used for intercity or long-distance travel. 3 - Bus. Used for short- and long-distance bus routes. 4 - Ferry. Used for short- and long-distance boat service. 5 - Cable car. Used for street-level cable cars where the cable runs beneath the car. 6 - Gondola, Suspended cable car. Typically used for aerial cable cars where the car is suspended from the cable. 7 - Funicular. Any rail system designed for steep inclines. GTFS Data Specification route_url route_url String 255 0 0 The route_url field contains the URL of a web page about that particular route. This should be different from the agency_url. GTFS Data Specification RouteShapeName RouteShapeName String 255 0 0 Route Shape Name created by by the ArcGIS processing tool. ESRI route_short_name route_short_name String 255 0 0 The route_short_name contains the short name of a route. This will often be a short, abstract identifier like "32", "100X", or "Green" that riders use to identify a route, but which doesn't give any indication of what places the route serves. At least one of route_short_name or route_long_name must be specified, or potentially both if appropriate. GTFS Data Specification route_long_name route_long_name String 255 0 0 The route_long_name contains the full name of a route. This name is generally more descriptive than the route_short_name and will often include the route's destination or stop. At least one of route_short_name or route_long_name must be specified, or potentially both if appropriate. GTFS Data Specification route_type_text route_type_text String 255 0 0 Route Type Text - text value for Route Type. Created by the ArcGIS tool used to create the routes layer. ESRI route_color route_color String 255 0 0 In systems that have colors assigned to routes, the route_color field defines a color that corresponds to a route. The color is provided as a six-character hexadecimal number, for example, 00FFFF. If no color is specified, the default route color is white (FFFFFF). GTFS Data Specification route_color_RGB route_color_RGB String 255 0 0 Route Color RGB value. Created by the ArcGIS tool used to develop the GIS layer. Hexadecimal format route color converted to a RGB triplet that can more easily be used as reference when choosing symbology in ArcMap ESRI route_text_color route_text_color String 255 0 0 The route_text_color field can be used to specify a legible color to use for text drawn against a background of route_color. The color is provided as a six-character hexadecimal number, for example, FFD700. If no color is specified, the default text color is black (000000). GTFS Data Specification route_text_color_RGB route_text_color_RGB String 255 0 0 Route Text Color RGB value. Created by the ArcGIS tool used to develop the GIS layer. Hexadecimal format route color converted to a RGB triplet that can more easily be used as reference when choosing symbology in ArcMap ESRI Shape_Length Shape_Length Double 8 0 0 Length of feature in internal units. Esri Positive real numbers that are automatically generated. GTFS data specifications are available at https://developers.google.com/transit/gtfs/reference. Data is developed from GTFS ROUTES.txt and SHAPES.txt data using a custom ArcGIS tool. The ArcGIS Toolbox can be downloaded at: http://www.arcgis.com/home/item.html?id=14189102b795412a85bc5e1e09a0bafa This GIS layer was created by merging data sets for NCTD and MTS. The agency responsible for the route is identified in the "agency_id" field. Note that because this field is a combined layer the "route_id" attribute may not be unique unless combined with the "agency_id". GTFS attribute definitions are copied from the GTFS Field Specifications for the routes.txt file at https://developers.google.com/transit/gtfs/reference#routes_fields As of 2022 go to https://github.com/MobilityData/mobility-database-catalogs and download the CSV Spreadsheet (Mobility Database Catalog) to get the most recent urls for San Diego (Search NCTD and MTS) or just try https://www.sdmts.com/google_transit_files/google_transit.zip and http://www.gonctd.com/google_transit.zip for direct links (there are other urls in the spreadsheet you download). Simple FALSE 782 TRUE FALSE