Emma Blue

It's now [clarified in the spec](https://github.com/google/transit/pull/378) that `stop_times.arrival_time` and `stop_times.departure_time` use `agency.agency_timezone` (many thanks to those who contributed and @e-lo for raising this!) Based on the discussion here, it looks...

This has been flagged as a valuable check by several community members. Although it is not explicit in the spec, I am wondering if this is implicit from the [`Remove...

@isabelle-dr Just to check my understanding, this notice is different than https://gtfs-validator.mobilitydata.org/rules.html#same_name_and_description_for_stop because it's checking that each stop name and description is unique across all stops, not just for 1...

Closed with [same_name_and_description_for_stop](https://gtfs-validator.mobilitydata.org/rules.html#same_name_and_description_for_stop)

Unblocked now that https://github.com/google/transit/pull/380 has passed 🎉 @cka-y's work on [the analytics for the spec issue ](https://github.com/MobilityData/mobility-database-catalogs/pull/275/files#diff-443ed678dc64f5a04f3b15c5844d9c03ab90d1c06ddb0a257243e9a71b37e759R42) will be relevant to the logic here.

@isabelle-dr Did https://gtfs-validator.mobilitydata.org/rules.html#platform_without_parent_station close out this issue?

#1292 is related to this

@qcdyx Hey Jingsi! The goal right now is to conduct analytics on when equal_shape_distance_diff_coordinates to make a decision — it's too soon to decide about severity at the moment without...

An update on our approach on this PR: https://github.com/MobilityData/gtfs-validator/pull/1675#issuecomment-1955249386 Current approach is to implement a threshold of 1.11m on distances between shape point pairs for the ERROR [(to capture any...

I'm going to close issue based on #1675 and re-open it if there is new community feedback after this release that indicates we should make the threshold more permissive.