feat: seal of reliability description page #178
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -557,13 +557,143 @@ | |
| "openSource": "An open source community actively working to improve the tools" | ||
| } | ||
| }, | ||
| "sealOfReliability": { | ||
| "title": "Seal of Reliability", | ||
| "hero": { | ||
| "title": "The Benchmark for Reliable GTFS Schedule Data", | ||
| "paragraphs": [ | ||
| "It's hard to measure if data is trustworthy. Transit agencies struggle to know if their GTFS data works for riders; data vendors lack a baseline bar of quality to aspire to, and trip planning apps end up spending time pre-processing feeds rather than seamlessly consuming them", | ||
| "That's where the MobilityData Seal of Reliability comes in. As a clear measure of baseline quality, the Seal of Reliability is applied to feeds that meet five key criteria: they're official, stable, available, compliant, and fresh." | ||
| ], | ||
| "ctaButton": "See a feed measured against the standard (todo)", | ||
| "imageAlt": "current placeholder", | ||
| "feedsMeetingStandard": "Feeds meeting the standard", | ||
| "meetsPercent": "{percent}% meets", | ||
| "belowStandardPercent": "{percent}% below standard" | ||
| }, | ||
| "benefits": { | ||
| "title": "Benefits", | ||
| "agencies": { | ||
| "title": "For Transit Agencies", | ||
| "items": [ | ||
| "Use the Seal definition in procurement contracts to set a clear baseline for vendor GTFS data quality", | ||
| "Triage data quality issues using Mobility Database analytics", | ||
| "Give riders a better experience by ensuring feeds meet a minimum reliability bar" | ||
| ] | ||
| }, | ||
| "applications": { | ||
| "title": "For Applications", | ||
| "items": [ | ||
| "Quickly identify feeds that are ready to ingest without heavy pre-processing and testing", | ||
| "Assess regional launch readiness based on how many feeds in an area have earned the Seal", | ||
| "Reference a neutral, third-party standard when explaining data quality requirements to data producers" | ||
| ] | ||
| }, | ||
| "vendors": { | ||
| "title": "For Vendors", | ||
| "items": [ | ||
| "Evaluate prospective clients' current data quality", | ||
| "Adjust quotes based on the anticipated level of effort to bring a feed up to the Seal's standard" | ||
| ] | ||
| }, | ||
| "regulators": { | ||
| "title": "For Regulators", | ||
| "items": [ | ||
| "Reference the Seal definition in policy requirements", | ||
| "Use the Seal as a measurable, automated standard for GTFS Schedule data quality" | ||
| ] | ||
| } | ||
| }, | ||
| "criteria": { | ||
| "title": "The criteria for the Seal of Reliability", | ||
|
There was a problem hiding this comment. I would capitalize here: |
||
| "official": { | ||
| "title": "Official", | ||
| "subtitle": "Authorized by the transit agency.", | ||
| "description": "The feed has been confirmed as an official source, published by or on behalf of the transit agency." | ||
| }, | ||
| "stable": { | ||
| "title": "Stable", | ||
| "subtitle": "The download URL doesn't change", | ||
| "description": "For at least six uninterrupted months, the same URL serves the feed, and the URL appears to be permanent." | ||
| }, | ||
| "available": { | ||
| "title": "Available", | ||
| "subtitle": "Can be downloaded from the URL each day.", | ||
| "description": "Once a day, the Mobility Database fetches the feed and downloads it cleanly." | ||
| }, | ||
| "compliant": { | ||
| "title": "Compliant", | ||
| "subtitle": "Adheres to every \"must\" in the General Transit Feed Specification.", | ||
| "description": "The feed has 0 errors in the Official GTFS Schedule Validator. Warnings and info notices do not affect compliance." | ||
| }, | ||
| "freshRolling": { | ||
| "title": "Fresh: Rolling 7 days of coverage", | ||
|
There was a problem hiding this comment. Capitalize |
||
| "subtitle": "Always includes 7 days or more of service coverage.", | ||
| "description": "Following GTFS Best Practices, the feed provides at least 7 days of rolling future service coverage. This means at least a full week of service is covered every day it is fetched." | ||
| }, | ||
| "freshContinuous": { | ||
| "title": "Fresh: Continuous coverage", | ||
|
There was a problem hiding this comment. Capitalizse: |
||
| "subtitle": "A realistic service window with no gaps between feed versions.", | ||
| "description": "Service coverage is continuous across subsequent feed versions with no gaps, and the service window spans two years or less." | ||
| } | ||
| }, | ||
| "gracePeriods": { | ||
| "title": "Grace periods", | ||
|
|
||
| "description": "Temporary issues won't immediately cost an agency its Seal. The following windows apply per violation type.", | ||
|
Contributor
There was a problem hiding this comment. Nitpick, but agencies don't have seals. Feeds have.
Contributor
There was a problem hiding this comment. Good catch! "cost a feed its Seal" should be the replacement. |
||
| "tableAriaLabel": "Grace periods", | ||
| "columns": { | ||
| "criterion": "Criterion", | ||
| "triggerCondition": "Trigger Condition", | ||
| "gracePeriod": "Grace Period", | ||
| "description": "Description" | ||
| }, | ||
| "compliant": { | ||
| "criterion": "Compliant", | ||
| "triggerCondition": "Validation error", | ||
| "gracePeriod": "30 days", | ||
| "consequence": "If a feed develops a validation error, producers have 30 days to fix it. After 30 days, if the errors persist, the feed loses its Seal." | ||
| }, | ||
| "available": { | ||
| "criterion": "Available", | ||
| "triggerCondition": "Download failure", | ||
| "gracePeriod": "14 days", | ||
| "consequence": "If a feed cannot be downloaded, producers have 14 days to restore access. After 14 days, if the feed remains unavailable, the feed loses its Seal." | ||
| }, | ||
| "freshCoverage": { | ||
| "criterion": "Fresh (7‑day coverage)", | ||
| "triggerCondition": "Coverage gap", | ||
| "gracePeriod": "14 days", | ||
| "consequence": "If a feed stops covering far enough into the future, producers have 14 days to publish an update before the feed loses its Seal." | ||
| } | ||
| }, | ||
| "faq": { | ||
| "title": "Frequently asked questions", | ||
|
|
||
| "coverage": { | ||
| "question": "What does the Seal cover?", | ||
| "answer": "The Seal evaluates GTFS Schedule feeds only. It does not cover GTFS Realtime or GBFS data. We focused on GTFS Schedule given the established state of the GTFS Schedule Validator and our existing processing pipeline for this data on the Mobility Database. We will explore extending the Seal to other data formats based on user feedback." | ||
| }, | ||
| "definition": { | ||
| "question": "How do you define reliability?", | ||
| "answer": "A reliable feed is trustworthy. It is official, stable, available, compliant and fresh. We consulted a variety of consuming applications to finalize this definition and identify the most common pain points with data reliability. This does exclude other key aspects of data quality, such as accuracy relative to the real world service. These elements are more complex and require local knowledge of each transit network. Our goal for the Seal of Reliability is to define a minimum, measurable threshold that GTFS Schedule data should meet, so our scope is narrowly focused." | ||
| }, | ||
| "agencyOrVendor": { | ||
| "question": "Can an agency or vendor earn the Seal?", | ||
| "answer": "No. Only a feed can earn the Seal, not an agency or a vendor. This keeps evaluation automated and consistent. An agency may have some feeds that earn the Seal and others that don't -- both outcomes will be visible on the Mobility Database." | ||
| }, | ||
| "riskAwareness": { | ||
| "question": "As a data producer, how do I know if I'm at risk of losing the Seal?", | ||
| "answer": "The best way is to check your feed on the Mobility Database 1-2 times a month to see your Seal status. Our team is working on email notifications, so in the future you can be notified when you've entered a grace period." | ||
| } | ||
| } | ||
| }, | ||
| "footer": { | ||
| "tagline": "An open catalog of transit and mobility data feeds, serving the global transportation community.", | ||
| "maintainedBy": "Maintained with 💙 by MobilityData", | ||
| "copyright": "© {year} MobilityDatabase. All rights reserved.", | ||
| "columns": { | ||
| "platform": "Platform", | ||
| "tools": "Tools", | ||
| "resources": "Resources", | ||
| "company": "Company", | ||
| "legal": "Legal" | ||
| }, | ||
|
|
@@ -575,6 +705,7 @@ | |
| "gtfsValidator": "GTFS Validator", | ||
| "gtfsRtValidator": "GTFS-RT Validator", | ||
| "gbfsValidator": "GBFS Validator", | ||
| "sealOfReliability": "Seal of Reliability", | ||
| "about": "About", | ||
| "faq": "FAQ", | ||
| "contactUs": "Contact Us", | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.