diff --git a/web-app/public/locales/en/feeds.json b/web-app/public/locales/en/feeds.json index e81c63c11..abef49fcb 100644 --- a/web-app/public/locales/en/feeds.json +++ b/web-app/public/locales/en/feeds.json @@ -1,9 +1,9 @@ { "feeds": "Feeds", - "dataType": "Data Type", + "dataType": "Data Format", "transitProvider": "Transit Provider", "location": "Location", - "feedDescription": "Feed Description", + "feedDescription": "Description", "searchFor": "Search For", "resultsFor": "{{startResult}}-{{endResult}} of {{totalResults}} results", "deprecated": "Deprecated", @@ -11,7 +11,7 @@ "noResults": "We're sorry, we found no search results for “{{activeSearch}}”.", "searchSuggestions": "Search suggestions: ", "searchTips": { - "twoDigit": "Use a two digit code to search for country, e.g “FR” for France", + "twoDigit": "Use the full English name of a location e.g \"France\" or \"New York City\"", "fullName": "Include the full name for transit provider, e.g “Toronto Transit Commission” instead of “TTC”", "checkSpelling": "Double check the spelling" }, diff --git a/web-app/src/app/screens/FAQ.tsx b/web-app/src/app/screens/FAQ.tsx index 702fe3ca7..1bc65aea0 100644 --- a/web-app/src/app/screens/FAQ.tsx +++ b/web-app/src/app/screens/FAQ.tsx @@ -35,11 +35,39 @@ export default function FAQ(): React.ReactElement { Why would I use the Mobility Database? - The Mobility Database catalogs has over 100 feeds that were - inaccurate on TransitFeeds, and over 150 new feeds. It's a more - accurate and comprehensive resource for ensuring your data is - discoverable and for scraping the data you need. The community - regularly adds and updates feeds using Github. + The Mobility Database has over 100 feeds that were inaccurate on + TransitFeeds, and over 250 new feeds. It's a more accurate and + comprehensive resource for ensuring your data is discoverable and + for scraping the data you need. The community regularly adds and + updates feeds using Github. The Mobility Database integrates with{' '} + + the Canonical GTFS Schedule Validator + {' '} + to display data quality information about each feed. + + + How do I use the Mobility Database? + + + There are 3 ways to use the Mobility Database: +
+
+ 1. The feed search on the website, where you can discover feeds and + see details on their bounding box, data quality, and historical + data. 2. The API, where you can pull feed information to display in + your own application or for research analysis 3. The{' '} + + spreadsheet export available here + + . You can find{' '} + + the GTFS Schedule and Realtime schemas for the spreadsheet here + + . Why are you making this change? @@ -66,20 +94,16 @@ export default function FAQ(): React.ReactElement { longer term solutions for the architecture that require more community investment. - - What about the TransitFeeds user interface? - + What about TransitFeeds? - We plan to develop a new user interface as part of the Mobility - Database by summer 2024, since this is critical for making data - discoverable and fostering collaboration on data quality - improvements. + TransitFeeds.com is still available to access historical data before + February 2024 and see feed visualizations. It will be deprecated + once both these features are available on the Mobility Database. We + commit to giving 6 months notice once the decision is finalized.

- In order to ensure the community has access to more up-to-date data - as soon as possible, we've focused on providing a catalog of - data without an interface as a first step. How quickly we scale the - architecture to build the user interface depends on how much - engagement and contribution we get from the community in this phase. + How quickly we scale the architecture to add these features depends + on how much engagement and contribution we get from the community in + this phase. What about the TransitFeeds API? @@ -100,15 +124,8 @@ export default function FAQ(): React.ReactElement { What’s coming next? - The MobilityData team is working to add validation info from the{' '} - - Canonical GTFS Schedule Validator - {' '} - for each feed, and create a user interface. + The MobilityData team is working to add historical data before 2024 + and route and stop visualizations to the Mobility Database.

- The Mobility Database checks for feed updates every week using the - producer's URL. We store the new feed version if we detect a - change. + The Mobility Database checks for feed updates twice a week using the + producer's URL, on Mondays and Thursdays. We store the new feed + version if we detect a change. diff --git a/web-app/src/app/screens/Home.tsx b/web-app/src/app/screens/Home.tsx index 27b73cc06..153e8c0d1 100644 --- a/web-app/src/app/screens/Home.tsx +++ b/web-app/src/app/screens/Home.tsx @@ -101,7 +101,7 @@ function Component(): React.ReactElement { sx={{ textAlign: 'center', color: 'black', fontWeight: 700, mt: 4 }} > Currently serving over 2000{' '} - GTFS feeds from 70{' '} + transit data feeds from 70{' '} countries. - The Mobility Database catalogs is a repository of 2000+ mobility - feeds across the world. It has over 150 updated feeds previously - unavailable on TransitFeeds (OpenMobilityData). + The Mobility Database is a directory of 2000+ mobility feeds across + the world. It has over 250 updated feeds previously unavailable on + TransitFeeds (OpenMobilityData) and shares data quality reports from{' '} + + the Canonical GTFS Schedule Validator + + .

We’re in the first phase of building a sustainable, central hub for