Skip to content

[Outreach Campaign Request]: Agencies without GTFS Fares v2 data #580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
evansiroky opened this issue Nov 26, 2024 · 1 comment
Closed
Assignees
Labels
communications Anything related to internal/external comms

Comments

@evansiroky
Copy link
Member

Subject Matter of Campaign

Transit Data Quality

Which teams are involved in this campaign

Transit Data Quality

Does this campaign have a specific deadline/timeline?

None

If you do have a timeline, could you please share below

Jan 30, 2025

What is the reason for conducting this campaign?

To learn about the reasons why transit agencies are currently not producing Fares v2 data in their GTFS feeds.

What is the goal of this campaign?

Reach out to agencies of various sizes and ask them questions about how they would like customers to learn about fares via trip planners if at all.

We can interview agencies, but a simple email reply listing out reasons could suffice.

Who does this campaign target?

Probably 9 total transit agencies ideally:
3 - small or very small
3 - medium
3 - large

Does your campaign request to hold interviews with the customers?

Yes

Do you envision needing a pipeline for this campaign?

None

@evansiroky evansiroky added the communications Anything related to internal/external comms label Nov 26, 2024
@o-ram
Copy link
Member

o-ram commented Dec 10, 2024

Since this campaign will use the same agency target list as GTFS-RT, we will use the same campaign guide as well. Campaign guide will be updated in Jan. 2025 to reflect these changes.

@o-ram o-ram moved this from Todo to Paused in Customer Success Dec 10, 2024
@o-ram o-ram moved this from Paused to Todo in Customer Success Jan 6, 2025
@laneymangan laneymangan moved this from Todo to In Progress in Customer Success Jan 17, 2025
@o-ram o-ram moved this from In Progress to In Review in Customer Success Feb 12, 2025
@o-ram o-ram closed this as completed Feb 14, 2025
@github-project-automation github-project-automation bot moved this from In Review to Done in Customer Success Feb 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
communications Anything related to internal/external comms
Projects
Status: Done
Development

No branches or pull requests

3 participants