-
we are trying to call a external api in our app.js file and are using the nom request module. however we are confused how to include the api key into the header for it to work.
right now below is the…
-
no jk.
so our api call is now working but I am trying to connect the url path "/:id" , req.params.id to populate in the variable options but it is not connecting. Is this another issue where I would…
-
we are using the npm request module to simplify the http call
https://www.npmjs.com/package/request
I am trying to make a api call and incorporate it's response it into a busStopInfo object however …
-
trying to deploy app to heroku today, getting this error:
`Error: Cannot find module './config/keys.json'
2015-08-26T07:21:42.042478+00:00 app[web.1]: throw err;
2015-08-26T07:21:42.042484+00:00 …
-
Some Western G2 stops never show arriving buses, while nearby stops do. Stop IDs also don't match posted signs.
E.g. O St & 34th and 37th & O never work, while Dumbarton St. & Wisconsin Ave shows b…
Areia updated
10 years ago
-
No predictions are made for the bus stop at e st & 7th st sw. For example, the 52 and 54 northbound stop there and it doesn't display times. If you go to the WMATA website though, it shows real time l…
-
Add a link to the WMATA API and to the ART GTFS to assist in finding the IDs of bus stops.
-
When a Metro prediction says "No to No Passenger" it should be ignored. I'm not sure whether "No" line might still be valid -- I think "--" is used when a train is not properly labeled. It's probably …
-
When I run API queries against a graph built from the [WMATA](http://www.wmata.com) GTFS file, which contains correct agency definitions, the returned data contains reference to the incorrect default …