So far, fare_zone are only managed in 2 places in NTFS:

• In stops ( https://github.com/CanalTP/navitia/blob/dev/documentation/ntfs/ntfs_fr.md#stopstxt-requis ).
• In fares application conditions ( https://github.com/CanalTP/navitia/blob/dev/documentation/ntfs/ntfs_fare_extension_fr.md#farescsv-optionnel ).

No object is managed, we only deal with a fare_zone_id. So we use it as the name w

As a visitor, I want to see what devices look like so that I can understand how they would integrate into the environment.

Acceptance criteria

• It's done when product pictures are added for relevant README.md files.
• It's done when usage pictures/videos are added for relevant README.md files.
• It's done when all images and videos used are open-source.

I get a blank screen when visiting:
http://developer.onebusaway.org/modules/onebusaway-application-modules/current/api/where/methods/report-problem-with-stop.html

Would help to highlight walk network, walk connectors, and transit modes separately.

calculate all the patterns belonging to a route into route_pattern

further, do we need a current_route_pattern? alt, do we really need a current_pattern table, ala #45 ?

I think we need current_route_pattern, since we currently have route_id 100 (which doesn't change over time), but the list of patterns for route_id 100 do change over time.

And with a current_route_pattern, do we need a

Need to replace use of geopy vincenty with geodesic in the instance it is used in urbanaccess. vincenty is discontinued in geopy version 2.0 and replaced with geodesic with default projection WGS84.

Reference:
vincenty depreciation notice: https://geopy.readthedocs.io/en/stable/#geopy.distance.vincenty
geodesic: https://geopy.readthedocs.io/en/stable/#geopy.distance.geodesic

Work out how to integrate transitfeed's feedvalidator.py. Command:
python feedvalidator.py -l 10000 gtfs.zip

-l 10000 pushes up the limit of errors/warnings per type, and this helps to list down all the errors/warnings so we can trace them.)

The validation script runs on python2 so that is a challenge, as the program is

https://github.com/public-transport/friendly-public-transport-format/blob/master/README.md describes the vision, without any examples of the format itself

it links to https://github.com/public-transport/friendly-public-transport-format/blob/master/spec/readme.md that has no introduction or basic examples. It immediately starts from "In order to be able to use this format in both static data and

In order to generate proper GTFS files good data quality in OSM is recommended, if not required.A little writeup/manual would help users how to assure data quality.

I think the wiki here would be the best place to live for this information. Maybe once it's getting to be more complete we could integrate it into learnOSM.org

Just a rough brainstorm list of the contents I suggest to include:

• Use

http://transitfeeds.com/api/swagger/#!/default/getFeeds lists stringEnum:"gtfs", "gtfsrealtime" but I found that the list has grown to

    GTFS = 'gtfs'
    GTFS_REALTIME = 'gtfsrealtime'
    URL = 'url'
    TWITTER = 'twitter'
    RSS = 'rss'

Summary:

Feedback from agencies - it would be useful to see small details on the entity that triggered the error in the error message. Right now we show the ID, like:

trip_id 1234...

However, it would be more useful if we included the trip headsign, route shortname, and stop name along with the ID, like:

trip_id 1234 South to Downtown

Steps to reproduce:

Trigger an

In the UserAccountInfoPanel the user description only displays whether the user is an application admin, organization admin, or standard user. It doesn't describe if the user is a project admin and it doesn't detail which projects and/or feeds the user has permissions for.

https://github.com/ibi-group/datatools-ui/blob/4293884e821326b5dd3816272ae40e034c9c139e/lib/manager/components/UserAccoun

As a Developer i wish to have utility for read and updates info from firestore DB, so everyone could use it without duplicate code.

Crud class with read and update method based on route id and time.