Assigned
Status Update
No update yet.
Comments
sh...@google.com
In addition to the PACE OCI ocean-related datasets that were suggested, I would also suggest adding the PACE OCI Land Vegetation Indices (Land VI) data (10 indices), and the [terrestrial] surface reflectance data (122 spectral bands). The details of the Land VI data can be found here: https://oceancolor.gsfc.nasa.gov/data/10.5067/PACE/OCI/L2/LANDVI/3.0 , while details of the surface reflectance data can be found here: https://oceancolor.gsfc.nasa.gov/data/10.5067/PACE/OCI/L2/SFREFL/3.0 .
ti...@sjsu.edu
Thanks for the reply,
Our use case does not involve a map, but is rather a ticketing app where we try to determine the price of individual route segments. As you can tell the above mentioned stations are part of the BART network, where we let the user plan a route from A to B and then offer the option to purchase tickets for their route, which can involve VTA, BART, Muni, or CalTrain. We currently have a list of all BART stations which we get from their REST API and that represent the data that they have in their most current GTFS file. After retrieving the route through the Google Directions API I then make a request to the BART fare API to get the price for that route segment, as you only provide us with a total price, but not a price per segment. However this currently is not possible as the station names have slight variations in spelling, this also applies to CalTrain (however we wrote our own fare API for that).
Thanks for pointing me to your ToS, but I don't see how this section would apply to us.
Our use case does not involve a map, but is rather a ticketing app where we try to determine the price of individual route segments. As you can tell the above mentioned stations are part of the BART network, where we let the user plan a route from A to B and then offer the option to purchase tickets for their route, which can involve VTA, BART, Muni, or CalTrain. We currently have a list of all BART stations which we get from their REST API and that represent the data that they have in their most current GTFS file. After retrieving the route through the Google Directions API I then make a request to the BART fare API to get the price for that route segment, as you only provide us with a total price, but not a price per segment. However this currently is not possible as the station names have slight variations in spelling, this also applies to CalTrain (however we wrote our own fare API for that).
Thanks for pointing me to your ToS, but I don't see how this section would apply to us.
sh...@google.com
Thanks for your suggestion!
We have passed the suggestion on to the product team for further consideration.
Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.
We have passed the suggestion on to the product team for further consideration.
Please star to add your vote and receive further updates, and feel free to add any comments to discuss your use case.
Description
# It is OK to share your API Project ID, but _not_ API keys.
Feature Request
-----------------------
Add the correct names, as they appear in the GTFS data to the directions transit API
Issue report
----------------
1. Plan a route from San Jose to San Francisco
2. Look at the returned JSON for the BART segments
3.
JSON: "19th St / Oakland"
GTFS: "19th St. Oakland"
JSON: "Civic Center"
GTFS: "Civic Center/UN Plaza"
Summary
-------------
This is not only the issue with BART, but CalTrain as well. It makes it really hard to convert between the two formats. I understand that you are trying to sanitize these names so your users have a better experience. But please additionally also return the right GTFS name so we developers can plug them into other APIs.