Closed GoogleCodeExporter closed 9 years ago
We discovered an addition to this issue. If you are previewing a Presentation
or using a Presentation on a Display using Geolocation and you are in a
location that has the issue above (where it reports you are in this Russian
town), you get a blank weather Gadget.
Original comment by robb.pr...@risevision.com
on 18 Jan 2013 at 2:16
We also discovered that the URL that returns weather data based on your
geographical location works, but the Gadget stays blank.
Original comment by robb.pr...@risevision.com
on 30 Jan 2013 at 4:04
Another example of the issue reported by a user: when "Little Rock, Arkansas"
or "Little Rock, AR" is used for Custom Address, then "Littlerock, California"
is displayed. Using zip code 72201 would return the proper weather and From
Service description.
Original comment by mark.kre...@risevision.com
on 4 Mar 2013 at 8:05
As part of the Displays address, I manually placed the %20 as shown in this
screenshot http://screencast.com/t/N9Qpksx1
This is the URL from the Display that correctly showed the location needed.
http://www.tinbuweather.com/wx_feed/wx_current_extended_by_name.php?passcode=ris
edisplay%7Cdkac&metric=false&language=en&name=El%2520Reno%2COK&dummy=75
Original comment by neal.god...@risevision.com
on 6 Jun 2013 at 8:45
Doesn't appear to be anything that can be done about this. The Weather Service
returns what it returns. I think it's actually because Tinbu can't handle an
encoded name parameter.
For example, the following (properly encoded) URL returns nothing -
http://www.tinbuweather.com/wx_feed/wx_current_extended_by_name.php?passcode=ris
edisplay%7Cdkac&metric=false&language=en&name=Little%20Rock&dummy=93
But this URL, with no encoding for the name parameter, returns results -
http://www.tinbuweather.com/wx_feed/wx_current_extended_by_name.php?passcode=ris
edisplay%7Cdkac&metric=false&language=en&name=LittleRock&dummy=93
This is probably why we initially removed spaces, so we should leave that in.
Introduce a state into the mix and things get worse.
If we continue to remove spaces, this URL returns data for California, probably
because it's interpreting %2CAR as the state of CA rather than the state of AR
-
http://www.tinbuweather.com/wx_feed/wx_current_extended_by_name.php?passcode=ris
edisplay%7Cdkac&metric=false&language=en&name=LittleRock%2CAR&dummy=14
Removing the comma results in no data being returned.
I have changed it so that if no results are returned by the data service, the
"Unable to retrieve weather data for that location." message appears instead
of a blank Gadget. Other than that, nothing can be done expect to contact Tinbu
and ask them to fix it.
Original comment by donnapep@gmail.com
on 19 Jun 2013 at 7:54
The following is from Tinbu:
"Hi Donna,
I fixed something in our code. It should work properly now if you have the
right encoding.
Looks like there is a city Littlerock in CA and obviously Little Rock, AR.
So, you can add a space between Little and Rock (%20), name=Little%20Rock%2CAR
It should pull feed for Little Rock, AR
If no space, it will pull Littlerock CA
Let me know if this solves your problem."
Since it sounds like the URL can now handle spaces, I've removed the
functionality that strips them out.
Original comment by donnapep@gmail.com
on 20 Jun 2013 at 6:48
Verified.
Original comment by robb.pr...@risevision.com
on 21 Jun 2013 at 7:29
Changing this to Started as we are still having issues with locations like King
City. Donna is contacting Tinbu about this.
Original comment by robb.pr...@risevision.com
on 25 Jun 2013 at 12:52
"We've updated our database. You should be able to see King City, ON now. You
can either use Ontario or Canada to narrow down the location."
Basically, it sounds like every one-off place like this has to be updated on
their end. In this case, King City, ON was not in their database. There is no
one-time solution.
Original comment by donnapep@gmail.com
on 25 Jun 2013 at 2:18
Original comment by robb.pr...@risevision.com
on 2 Jul 2013 at 8:50
Original comment by donnapep@gmail.com
on 3 Jul 2013 at 3:37
Original issue reported on code.google.com by
neal.god...@risevision.com
on 9 Jan 2013 at 10:12