MBTA GTFS feed doesn't work / OTP doesn't support missing stop_lat/stop_lon

[blackmad]

NOTE: this issue system is intended for reporting bugs and tracking progress in software development. For all other usage and software development questions or discussion, please write to one of the mailing lists (Google groups):
https://groups.google.com/forum/#!forum/opentripplanner-dev
https://groups.google.com/forum/#!forum/opentripplanner-users

Expected behavior

OTP successfully builds an index from boston MBTA gtfs feed

Observed behavior

OTP crashes on "missing required field stop_lat"

The MBTA team maintains their own OTP fork that supports this behavior, which they say is valid in the current GTFS spec mbta@a704bb5#commitcomment-36591815

@abyrd suggested I report this in https://groups.google.com/forum/#!topic/opentripplanner-users/tsebCMHRe6c

Exception in thread "main" org.onebusaway.csv_entities.exceptions.CsvEntityIOException: io error: entityType=org.onebusaway.gtfs.model.Stop path=stops.txt lineNumber=7819
at org.onebusaway.csv_entities.CsvEntityReader.readEntities(CsvEntityReader.java:161)
at org.onebusaway.csv_entities.CsvEntityReader.readEntities(CsvEntityReader.java:120)
at org.onebusaway.csv_entities.CsvEntityReader.readEntities(CsvEntityReader.java:115)
at org.onebusaway.csv_entities.CsvEntityReader.readEntities(CsvEntityReader.java:108)
at org.opentripplanner.graph_builder.module.GtfsModule.loadBundle(GtfsModule.java:181)
at org.opentripplanner.graph_builder.module.GtfsModule.buildGraph(GtfsModule.java:108)
at org.opentripplanner.graph_builder.GraphBuilder.run(GraphBuilder.java:139)
at org.opentripplanner.standalone.OTPMain.run(OTPMain.java:103)
at org.opentripplanner.standalone.OTPMain.main(OTPMain.java:73)
Caused by: org.onebusaway.csv_entities.exceptions.MissingRequiredFieldException: missing required field: stop_lat
at org.onebusaway.csv_entities.schema.AbstractFieldMapping.isMissingAndOptional(AbstractFieldMapping.java:100)
at org.onebusaway.csv_entities.schema.DefaultFieldMapping.translateFromCSVToObject(DefaultFieldMapping.java:43)
at org.onebusaway.csv_entities.IndividualCsvEntityReader.readEntity(IndividualCsvEntityReader.java:131)
at org.onebusaway.csv_entities.IndividualCsvEntityReader.handleLine(IndividualCsvEntityReader.java:98)
at org.onebusaway.csv_entities.CsvEntityReader.readEntities(CsvEntityReader.java:157)

Version of OTP used (exact commit hash or JAR name)

1.4.0-shaded

Data sets in use (links to GTFS and OSM PBF files)

https://www.mbta.com/developers/gtfs

Command line used to start OTP

(base) ➜ otp java -Xmx2G -jar otp-1.4.0-shaded.jar --build input

[barbeau]

Looks like these changes were needed to support the official GTFS Pathways spec:
google/transit#143

[SKalt]

Looks like the MBTA has a WIP implementing GTFS pathway support in #2924.

[leonardehrenfried]

This issue has been resolved in OTP2 since February 2020. I just tried the MTBA feed and it works fine.

Here is an example of pathways at Alewife station: