Lionel Nébot Janvier

@barbeau Do you think that this rule should be checked before entity is created, or be the subject of a new use case? To keep consistency, it would be a...

Indeed, I missed the fact that this is linked to `calendar.txt`. In this case, we should have a use case to verify that. After going through our rule prioritization spreadsheet,...

> (a) implement that for a long list of languages (well, we can cover some 20-30 top languages) We could possibly leverage the newly defined country code CLI parameter to...

> Perhaps the warning should be threshold-based? My gut tells me that the big issues are when almost every stop has the word "stop" in its name (same with station...

> Where is this best practice coming from and what is the rationale? I think that @e-lo refers to [this part](https://github.com/MobilityData/GTFS_Schedule_Best-Practices/blob/master/en/routes.md ) of the best practices: > > | Field...

Also to be considered: https://github.com/MobilityData/gtfs-validator/pull/1068#discussion_r751710647

Thanks for flagging this @rpedraza01 - From the first steps of the troubleshooting it appears that the root of the problem might be deeper than checking the rule's logic We...

What is your point of view on this @aababilov @barbeau ?

> which errors to pick? - that is the question). ~I would say the one that caused the parsing error.~ Probably list the errors that caused a parsing error. >...

> If parent_station !=0, stop_name should include parent_station stop_name @e-lo could you add reference from [this repo](https://github.com/MobilityData/GTFS_Schedule_Best-Practices) to support this suggestion please?