Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is related to a change / outage of the service. See: <a href="http://status-dashboard.com/32226/47728" rel="nofollow noreferrer">http://status-dashboard.com/32226/47728</a></p> <p><img src="https://i.stack.imgur.com/ILUrK.png" alt="enter image description here"></p> <p>I have been using Google's Weather API for over a year to feed a phone server so that the PolyCom phones receive a weather page. It has run error free for over a year. As of August 7th 2012 there have been frequent intermittent 403 errors.</p> <p>I make a hit of the service once per hour (As has always been the case) so I don't think frequency of request is the issue. More likely the intermittent nature of the 403 is related to the partial roll-out of a configuration change or a CDN change at Google.</p> <p>The Google Weather API isn't really a published API. It was an internal service apparently designed for use on iGoogle so the level of support is uncertain. I tweeted googleapis yesterday and received no response.</p> <p>It may be better to switch to a promoted weather API such as: <a href="http://www.wunderground.com/weather/api" rel="nofollow noreferrer">WUnderground Weather</a> or <a href="http://developer.yahoo.com/weather/" rel="nofollow noreferrer">Yahoo Weather</a>.</p> <p>I have added the following 'unless defined' error handling perl code myself yesterday to cope with this but if the problem persists I will switch to a more fully supported service:</p> <pre><code>my $url = "http://www.google.com/ig/api?weather=" . $ZipCode ; my $tpp = XML::TreePP-&gt;new(); my $tree = $tpp-&gt;parsehttp( GET =&gt; $url ); my $city = $tree-&gt;{xml_api_reply}-&gt;{weather}-&gt;{forecast_information}-&gt;{city}-&gt;{"-data"}; unless (defined($city)) { print "The weather service is currently unavailable. \n"; open (MYFILE, '&gt;/home/swarmp/public_html/status/polyweather.xhtml'); print MYFILE qq(&lt;?xml version="1.0" encoding="utf-8"?&gt;\n); print MYFILE qq(&lt;!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "xhtml11.dtd"&gt;\n); print MYFILE qq(&lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;\n); print MYFILE qq(&lt;head&gt;&lt;title&gt;Weather is Unavailable!&lt;/title&gt;&lt;/head&gt;\n); print MYFILE qq(&lt;body&gt;\n); print MYFILE qq(&lt;p&gt;\n); print MYFILE qq(The weather service is currently unavailable from the data vendor.\n); print MYFILE qq(&lt;/p&gt;\n); print MYFILE qq(&lt;/body&gt;\n); print MYFILE qq(&lt;/html&gt;\n); close MYFILE; exit(0); }... </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POGoogle Weather API 403 Error
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAbdul Rahman
    1. USClearCrescendo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POGoogle Weather API 403 Error
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COExcellent answer! I would be pushed to speculate that the dismantling of iGoogle is affecting this service. I was vaguely aware that the API was "for widget use only" so I suppose it isn't overly surprising that there are issues with service reliability. I will look into using those alternatives and possibly adapting the ideas behind your exception handling. Thanks again!
      singulars
      1. PO
      1. USmitchimus
    2. COSheesh! Break out your try/catches everyone... +1
      singulars
      1. PO
      1. USDerek Hunziker
    3. COAs of August the 27th, 2012 the service is responding with a consistent 403 error and a message indicating that you are sending automated queries.:
      singulars
      1. PO
      1. USClearCrescendo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload