Hello,
I’m making a Goggle map of different air quality monitors throughout NYC and I want to include a layer for the purple air monitors. Does anyone know how I can download the sensor location data so that I can add it to my google map?
I saw something on the website about downloading data from a specific sensor, but this is different than the pollutant data that the sensors are collecting. Thank you!
Hi @Eugene
The easiest way to retrieve this information would be to query that data through the API, where both latitude and longitude are available fields. At this time, they are only queryable through real-time API endpoints.
Please let us know if you have any questions.
Would there be a way to download sensor locations in a certain state/province using the download tool? Is so what would be the best way to go about that?
I’ve tried using the download tool but it basically looks like I would have to input one sensor index at a time, which is pretty much the same as just manually inputting them into a custom google maps layer. Is there a faster way?
Hi mford,
After working on something similar myself, I figured out that the easiest ways is with a “bounding box” where you enter the lat and long coordinates for the region (in this case of that state). You can do it on the API sampler for free and it codes it for you and spits out the results. But you still need the data download tool to get an API Key.
Here is one discussion I found very helpful: Finding Large Amounts of Sensor Indexes (Bounding Box API Call)
Hi @mford
Eugene is correct here. We would recommend obtaining the indexes by way of a bounding box call, and then querying those indexes using the download tool.
It seems like lat and long are no long available fields. Does anyone have updates on this? All my requests for lat long fail now which was not an issue before.
I also noticed in the real-time map that the lat/long does not properly update in the URL.
My apologies, my earlier response was not correct. Latitude and Longitude are available through the API, but only to real-time endpoints. Given that the download tool can only query historical endpoints, lat and long are not available through it.
From what is sounds like, you previously made real-time request for lat and long with no issue, but now they are not working. Lat and Long are still available, so those requests are failing for other reasons. Could you describe what you mean when you say the requests fail? Images would also be helpful.
Lastly, we are not aware of any lat or long issues with the map currently. Could you describe what you mean when you say they do not properly update? To be clear, the lat and long in the URL reflect your current view of the map and not those of a sensor.