ArcGIS REST Services Directory |
Home > services > Transit (FeatureServer) > Muni | | API Reference |
SFMTA MUNI routes.
Sourced from http://services.sfmta.com/arcgis/rest/services/Transit/transit/FeatureServer/1
Updated weekly from the URL above, although MTA update the source data irregularly, see the URL above for the most recent update date.
Description: | A. PURPOSE | Provide spatial route data for all routes.| B. METHODOLOGY | Route data is exported from the Trapeze scheduling system and filtered only for full length patterns. | C. UPDATE FREQUENCY | Updated by “Sign-up”, when transit system changes are put into effect. Updates range from every 3-6 months. | D. OTHER CRITICAL INFO | Inbound and Outbound route lines are included and represented with separate polylines for each route. Route numbers 59, 60, 61 are all Cable Car routes. | E. ATTRIBUTES |PATTERN: Pattern designation. A pattern represents one of the variations of a route. For example, the 38-Geary outbound may terminate at Fort Miley, 48thAve, or 32ndAve. See the following pattern code document for full description of pattern codes: \\mtanas\sfmtagis\03_Geodata\Additional Documentation\Route Patterns Naming Conventions.docx;PATTERNID: Pattern unique ID;ROUTE_NAME: Public-facing route number;DIRECTION: “I” = Inbound, “O” = Outbound;PATTERN_TYPE: See pattern code document;SUB_TYPE: See pattern code document;PATTERN_VERSION: See pattern code document;LINEABBR: Line code in Trapeze;SIGNID: Signup unique ID - See https://transtat.sfmta.com/#/views/SignupsPlatformRevenueHoursandMiles/SignupPeriodsfor definition of signup periods;SERVICE_CA: As part of Muni Forward, SFMTA proposed a new framework that reorganizes Muni service into transit categories.
CUSTODIAN | Alex Demisch, alex.demisch@sfmta.com