conditions return 1

  • 1
  • Question
  • Updated 2 years ago
  • (Edited)
All the Data Features are returning 1 in my app

http://api.wunderground.com/api/<app key>/conditions/forecast/astronomy/hourly/forecast10day/...

{
  "response": {
"version":"0.1", "termsofService":"http://www.wunderground.com/weather/api/d/terms.html", "features": { "conditions": 1 , "forecast": 1 , "astronomy": 1 , "hourly": 1 , "forecast10day": 1 } , "results": [ { "name": "Montevideo", "city": "Montevideo", "state": "CA", "country": "UY", "country_iso3166":"UY", "country_name":"Uruguay", "zmw": "00000.1.86580", "l": "/q/zmw:00000.1.86580" } , { "name": "Montevideo", "city": "Montevideo", "state": "MO", "country": "UY", "country_iso3166":"UY", "country_name":"Uruguay", "zmw": "00000.2.86585", "l": "/q/zmw:00000.2.86585" } ] }
Photo of Javier Pérez

Javier Pérez

  • 2 Posts
  • 0 Reply Likes
  • frustrated,

Posted 2 years ago

  • 1
Photo of Brendan Hayes

Brendan Hayes, Official Rep

  • 962 Posts
  • 123 Reply Likes
That city name became ambiguous.  When that happens, use this field "l": "/q/zmw:00000.1.86580"

Some cities have become ambiguous because we have multiple meta data sources on one city.  We are working through ones that we can.  
Photo of Javier Pérez

Javier Pérez

  • 2 Posts
  • 0 Reply Likes
Thank you Brendan, that was quick!!
it is easier for me to just change the location to a long, lat value.