GTFS expired

[samvermette]

No description provided.

[seabre]

@samvermette Like @jden said, I'm working with CARTA on the update

I'll keep you posted here.

[samvermette]

@seabre cool appreciate the quick responses. We manually extended the feed on our end in the meantime

[seabre]

@samhashemi @jden Just met with CARTA. Got the new markup in the repo. Pending validation issues, we should be able to go pretty soon.

Edit: Just realized I pinged the wrong Sam. Sorry about that!

[samvermette]

@seabre any news? Are the validation issues for the gtfs-validator tool or is it validations with CARTA directly?

[seabre]

@samvermette Two validation issues. One of them wasn't caught by the validation tool on Travis for some reason.

• The stops "BRAINERD RD + EASTGATE DR" (ID 861) and "BRAINERD RD + KRISPY KREME" (ID 952) are 1.82m apart and probably represent the same location.
• A trip in the trips.txt file was found with a trip_headsign value that includes the trip's route_long_name value, as specified in the routes.txt file. The route long name should not be included in the trip headsign, as the two value are often displayed together.

We're going to delete one of the stops and I think @jden is working with CARTA on the second issue.

[junosuarez]

@seabre yes I'll run the headsign cleanup this evening.

[seabre]

@jden Is this headsign validation error a special case with chatt-gtfs-cleanup? I thought it already did this.

[samvermette]

no big deal then, we moved forward with the update since they're mainly cosmetic issues.

[seabre]

@samvermette We fixed the stop issues and possibly the headsign issues. It's passing on Travis now, but we're waiting on Google to give us the final verdict.

[LeoFrachet]

Hi guys, GTFS expired May the 2nd (last Saturday). Do you plan to update it?