From c9ebff79d8d5d90b1233a25de2a7d08ed651d7fa Mon Sep 17 00:00:00 2001
From: Emma Blue <90632321+emmambd@users.noreply.github.com>
Date: Fri, 9 Aug 2024 10:48:47 -0400
Subject: [PATCH 1/6] Update FAQ.tsx
---
web-app/src/app/screens/FAQ.tsx | 42 +++++++++++++++------------------
1 file changed, 19 insertions(+), 23 deletions(-)
diff --git a/web-app/src/app/screens/FAQ.tsx b/web-app/src/app/screens/FAQ.tsx
index 702fe3ca7..978556d56 100644
--- a/web-app/src/app/screens/FAQ.tsx
+++ b/web-app/src/app/screens/FAQ.tsx
@@ -35,11 +35,21 @@ 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
+ 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.
+ 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?
@@ -67,18 +77,12 @@ export default function FAQ(): React.ReactElement {
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.
- 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
+ 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.
@@ -100,15 +104,7 @@ 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
+ 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.
From 6e7d88c6c2fe218d219a9afbc3300fb4e237cc04 Mon Sep 17 00:00:00 2001
From: Emma Blue <90632321+emmambd@users.noreply.github.com>
Date: Fri, 9 Aug 2024 10:53:06 -0400
Subject: [PATCH 2/6] Update FAQ.tsx
---
web-app/src/app/screens/FAQ.tsx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/web-app/src/app/screens/FAQ.tsx b/web-app/src/app/screens/FAQ.tsx
index 978556d56..3e65ae34d 100644
--- a/web-app/src/app/screens/FAQ.tsx
+++ b/web-app/src/app/screens/FAQ.tsx
@@ -80,7 +80,7 @@ export default function FAQ(): React.ReactElement {
What about TransitFeeds?
- 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.
+ 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.
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.
From 5112b8094754741b4e1485ab8b8b4c3a0c6ec727 Mon Sep 17 00:00:00 2001
From: Emma Blue <90632321+emmambd@users.noreply.github.com>
Date: Fri, 9 Aug 2024 10:57:57 -0400
Subject: [PATCH 3/6] Update Home.tsx
---
web-app/src/app/screens/Home.tsx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/web-app/src/app/screens/Home.tsx b/web-app/src/app/screens/Home.tsx
index 27b73cc06..643489c5b 100644
--- a/web-app/src/app/screens/Home.tsx
+++ b/web-app/src/app/screens/Home.tsx
@@ -218,8 +218,8 @@ function Component(): React.ReactElement {
}}
>
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).
+ 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
From ef01b0569494589819998c25f501ba316fcb3c0f Mon Sep 17 00:00:00 2001
From: Emma Blue <90632321+emmambd@users.noreply.github.com>
Date: Fri, 9 Aug 2024 11:04:33 -0400
Subject: [PATCH 4/6] Update Home.tsx
---
web-app/src/app/screens/Home.tsx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/web-app/src/app/screens/Home.tsx b/web-app/src/app/screens/Home.tsx
index 643489c5b..7850e9b16 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
+ 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.
From decdcd399102bf318d080cb94cae93cbe95eec8a Mon Sep 17 00:00:00 2001
From: Emma Blue <90632321+emmambd@users.noreply.github.com>
Date: Fri, 9 Aug 2024 11:08:10 -0400
Subject: [PATCH 5/6] Update feeds.json
---
web-app/public/locales/en/feeds.json | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
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"
},
From 73da032aca6a0603d58108351e66bbd369d40c9a Mon Sep 17 00:00:00 2001
From: Alessandro Kreslin
Date: Thu, 15 Aug 2024 09:25:14 -0400
Subject: [PATCH 6/6] lint fix
---
web-app/src/app/screens/FAQ.tsx | 59 ++++++++++++++++++++++----------
web-app/src/app/screens/Home.tsx | 10 ++++--
2 files changed, 47 insertions(+), 22 deletions(-)
diff --git a/web-app/src/app/screens/FAQ.tsx b/web-app/src/app/screens/FAQ.tsx
index 3e65ae34d..1bc65aea0 100644
--- a/web-app/src/app/screens/FAQ.tsx
+++ b/web-app/src/app/screens/FAQ.tsx
@@ -35,21 +35,39 @@ export default function FAQ(): React.ReactElement {
Why would I use the Mobility Database?
- 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.
+ 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.
+ 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?
@@ -76,14 +94,16 @@ export default function FAQ(): React.ReactElement {
longer term solutions for the architecture that require more
community investment.
-
- What about TransitFeeds?
-
+ What about TransitFeeds?
- 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.
+ 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.
- 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.
+ 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?
@@ -104,7 +124,8 @@ export default function FAQ(): React.ReactElement {
What’s coming next?
- The MobilityData team is working to add historical data before 2024 and route and stop visualizations to the Mobility Database.
+ 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 twice a week using the
- producer's URL, on Mondays and Thursdays. We store the new feed version if we detect a
- change.
+ 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 7850e9b16..153e8c0d1 100644
--- a/web-app/src/app/screens/Home.tsx
+++ b/web-app/src/app/screens/Home.tsx
@@ -217,9 +217,13 @@ function Component(): React.ReactElement {
mt: 5,
}}
>
- 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.
+ 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