Alexei Ababilov

Good point. The problems are: (a) implement that for a long list of languages (well, we can cover some 20-30 top languages) (b) avoid false positives when "Station" or "Stop"...

Where is this best practice coming from and what is the rationale? Does that also include a requirement to provide `agency_id` in `agency.txt` even for a single agency? To be...

> Hi @aababilov, thanks for this contribution! My pleasure! > Just had a look and I'm not sure I understand what exactly we're doing with the identified HVT values. thinking...

Although HVT (hierarchical vehicle type) won't be a part of the standard GTFS, we may still have support for it because HVT is really widely used. Custom validation rules may...

I think that we already give enough details. We ask the user to look into report.json. I am unsure if we can maintain a more specific way to briefly describe...

I would not recommend that. Entrances, platforms and generic nodes should have a name that helps to identify them when the station is already known. Placing stop_name of the parent...

OK, here is a quotation regarding *platform* names from [the best practices](https://docs.google.com/document/d/1zQ2SEHh3Uvv3kkmOoeMCCSzyS5ny5_ZPQyS2gG0yVk0/edit) that I wrote in 2019. > stop_name may follow different naming patterns. We recommend to give it as...

Thanks for filing that issue. What do you want to use as the start and end date for a dataset? Google uses a so called majority service date. Does that...

> @aababilov Very interesting! How is this majority service date defined? We find the max amount of trips per day (`MAX_TPD`), then find the first and last days that demonstrate...

> At any time, the published GTFS dataset should be valid for at least the next 7 days [...] > http://gtfs.org/best-practices/#dataset-publishing--general-practices This rule is quite ambiguous when it comes to...