urbanobservatory / uo-api-v1.1

Data API for UO data
3 stars 0 forks source link

Server error 500 getting sensor data #9

Open davidherbert2 opened 3 years ago

davidherbert2 commented 3 years ago

http://uoweb3.ncl.ac.uk/api/v1.1/sensors/json?theme=Vehicles&sensor_type=Car%20Count currently returns:

<h1>Server Error (500)</h1>

http://uoweb3.ncl.ac.uk/api/v1.1/sensors/json?theme=Air%20Quality&sensor_type=NO2 returns the expected JSON. The former was working correctly on Friday 12th March. Not sure what has changed, but would appreciate if you could take a look at this a.s.a.p as it is holding me up somewhat.

geoanorak commented 3 years ago

David, Car Count is variable so http://uoweb3.ncl.ac.uk/api/v1.1/sensors/json/?theme=Vehicles&Variable=Car%20Count Works fine

davidherbert2 commented 3 years ago

Thanks for this Phil - the parameter "Variable" isn't documented as existing however, and under "sensor_type" we have "Subset the sensors by the variables​ that they record". At least, I am looking at http://uoweb3.ncl.ac.uk/api_docs/doc/sensors-json/. So a bit confusing I think?

David.


From: Phil James @.> Sent: Monday, March 15, 2021 12:50 PM To: urbanobservatory/uo-api-v1.1 @.> Cc: David Herbert @.>; Author @.> Subject: Re: [urbanobservatory/uo-api-v1.1] Server error 500 getting sensor data (#9)

⚠ External sender. Take care when opening links or attachments. Do not provide your login details.

David, Car Count is variable so http://uoweb3.ncl.ac.uk/api/v1.1/sensors/json/?theme=Vehicles&Variable=Car%20Count Works fine

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Furbanobservatory%2Fuo-api-v1.1%2Fissues%2F9%23issuecomment-799392914&data=04%7C01%7CDavid.Herbert2%40newcastle.ac.uk%7Cbd44af76c7fd41d044fe08d8e7b0e3a8%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C637514094202528180%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=0CvzNEkXIkvGnQsKok1PTX7%2B5pgY8dyAAZwvayO3LoY%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALXVMA6RGWPFG5AY5PIRZWDTDX7AVANCNFSM4ZGOEXKA&data=04%7C01%7CDavid.Herbert2%40newcastle.ac.uk%7Cbd44af76c7fd41d044fe08d8e7b0e3a8%7C9c5012c9b61644c2a91766814fbe3e87%7C1%7C0%7C637514094202538169%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=TbuVllR%2F8imlpEK9fAKwFdo5jCIgB7w9FqiLttJLG2A%3D&reserved=0.

nharris172 commented 3 years ago

you call should work David. Not sure why it's now returning 500. I'll have a look

geoanorak commented 3 years ago

Not sure of the semantic difference between sensor type and variable. I've always used variable.