Feed Submission December 17

[ianktc]

Addresses Issues:

#723 and #1024: Trafiklab GTFS Sweden 3 schedule and realtime feeds (the GTFS Regional feeds will be addressed in a separate issue and PR)

#1061:

• https://gtfs-validator-results.mobilitydata.org/567137bd-74cb-4beb-b09c-ad2ccf63d1ec/report.html
• https://gtfs-validator-results.mobilitydata.org/d99373d3-fd2b-4f3c-bfdd-1c416917f072/report.html
• https://gtfs-validator-results.mobilitydata.org/5c16cda3-4ebb-44a7-8087-30a7eca4968b/report.html
• https://gtfs-validator-results.mobilitydata.org/49f6fab9-f9b4-474b-980b-0d2a7e4a8b65/report.html
• https://gtfs-validator-results.mobilitydata.org/7ddd3216-a9b0-4ed5-b3b2-1e5c339e9e29/report.html

#1186: https://gtfs-validator-results.mobilitydata.org/4db93739-338b-4c0b-8fcd-9f58549cdb5f/report.html
#1187: https://gtfs-validator-results.mobilitydata.org/361212d3-5450-47bb-bc40-8ab6a1f1bd93/report.html
#631: https://gtfs-validator-results.mobilitydata.org/5647b031-f401-46c3-b5e3-dbc48fab9d8e/report.html
#628: https://gtfs-validator-results.mobilitydata.org/360e142f-fc4b-4cdd-bf59-a706de46bd75/report.html

[ianktc]

Feed Submission Checklist

Thanks for contributing to the MobilityDatabase!

This is a comprehensive checklist detailing the things to consider before submitting a feed to the database. The schema links in this checklist will follow the convention of [1] for schedule feed schema and [2] for realtime feeds. You will find the schema definitions for schedule and realtime feeds are often the same, but both references are always included for completeness. If you have any questions, reach out to @ianktc.

General Checks

• Valid Direct Download URL: Does the URL produce a zip file and is it valid gtfs? [1] If realtime, is it a protobuf? [2]

All feeds in this import are valid

• Official Status: Is the feed official? Check contact email, direct download URL, website etc. [1] or [2]

All feeds in this import are official

• Service Status: Is the status active? Check feed_info file for service window. [1] or [2]

All realtime feeds are active.
Following schedule feeds are active:

• mdb-2941
• mdb-2944
• mdb-2946
• mdb-2947
• mdb-2948

Following schedule feeds are inactive:

• mdb-2940

• mdb-2942

• mdb-2943

• mdb-2945

• Authentication: Is there any authentication required? [1] or [2] Enum values are described [1] and [2] (they are the same)

All feeds in this import require authentication(type 1 or 2).

Is Your Feed New?

• MDB Stable ID: Correct stable id in the file name? Does it match the mdb_source_id field? [1] or [2]. And stable id in the “latest url” field? [1]
• Sequential Ordering: Does the stable id increment from latest stable id? Do they increase in sequential order? Refer to this spreadsheet for the latest mdb stable id.

Is Your Feed an Update?

• Official Status: If unofficial, do not deprecate and redirect the old feed, but import this new feed as unofficial so both feeds are available in the database
• Deprecate and Redirect: If official, deprecate and redirect the old feed to this updated feed. [1] or [2]

Only mdb-2947 and mdb-2948 are feed updates. The deprecate and redirect are handled for both of these feeds.

Is it a Realtime Feed?

• Reference: Does it have a reference to the schedule feed? [2]

This feed import contains realtime feeds from Sweden 3 GTFS dataset. All realtime feeds have a static reference to mdb-2939 (its schedule feed counterpart).

Pre-existing Feed Existence [internal]

• Perform a check on the mobility database website to check for pre-existing unpublished (wip) feeds from other sources
• Sometimes the "old" feed is not included in the feed submission form, perform a check for fuzzy matches on Provider and Direct Download URL. In the case of probable matches, check with the validator for entity count, agency and feed info matches as well.

Other Considerations [internal]

Sometimes you will encounter two active schedule feeds. There are some possible reasons this may occur:

• Flex: Flex feeds are sometimes produced separately from schedule feeds. Import the flex feed as a brand new feed instead of a redirect of the schedule feed. [definition]
• Reference Schedule Feed: One schedule feed may be used as the schedule, while the other is used as a reference to the realtime feed. Look for feeds produced by Passio (or other vehicle tracking software). [example]

No flex feeds in this import.

[emmambd]

Looks great! Lots of good European feed additions here.

One general comment: I'd review Trafiklab's license and see if there are any attribution requirements. If we need to input a certain line of text to comply with their license, please add it to the name field.

[emmambd]

For the acronyms, can we include the longform transit authority names as well?

[emmambd]

@ianktc Do you need support going through the GTFS Schedule feed API key authentication workflow to add this? If it isn't in OnePassword, the feed won't actually download daily.

[emmambd]

@ianktc If the authentication is through a government website, can we mark this as official?

[ianktc]

I think this is marked as official already right? 🤔

[emmambd]

Ah I'm used to seeing this as the top of the file in the schema! It's at the bottom - all good

[ianktc]

@emmambd While adding api keys to 1Password, I noticed that the Slovenian NAP feeds have incorrectly labelled auth type 2 (header auth required). We should instead consider auth type 3 (ad hoc auth required) or a new auth type 4 (account login required). More information in #1061 (comment)