title: Google Geolocation API library
body: <p>Is there a library out there that will get you your approximate location using the google service (<a href="https://www.google.com/loc/json" rel="noreferrer">https://www.google.com/loc/json</a>)?</p>
  <p>Google Gears has support for it as described here <a href="http://code.google.com/p/gears/wiki/GeolocationAPI" rel="noreferrer">http://code.google.com/p/gears/wiki/GeolocationAPI</a> There is also good doco on the web service request/response schema.</p>
  <p>Firefox and iPhone Safari use the service as well and they have their own implementations. I would like to use the service in my own C# application so I would like a library that I can use (either one of C/C++/C#). Currently the only way my colleague got it working is using a gears plugin for IE and hosting the embedded IE window in our WPF app. This is a bit cumbersome and poorly re-distributable.</p>
  <p>Any ideas?</p>
  <p><strong>Edit</strong>  This is a comment from the above page:</p>
  <blockquote>
  <p>Comment by steveblock@google.com,  Dec 02, 2008</p>
  <p>Thanks for all the comments. A few responses ...</p>
  <p>Answers to many of the questions about use of the API can be found in the Geolocation &gt;API documentation at <a href="http://code.google.com/apis/gears/api_geolocation.html" rel="noreferrer">http://code.google.com/apis/gears/api_geolocation.html</a>. This Wiki page is intended to document work in progress for those developing Gears, not to serve as definitive documentation of the API.</p>
  <p>Regarding the JSON protocol, I've updated this document to reflect the current behaviour in Gears. Note that official documentation of the protocol will soon be added to the Geolocation API documentation.</p>
  <p>The Gears Terms of Service prohibits direct use of the Google location server (<a href="http://www.google.com/loc/json" rel="noreferrer">http://www.google.com/loc/json</a>) via HTTP requests. This service may only be accessed through the Geolocation API.</p>
  </blockquote>
  <p>This kinda sucks. So how does Firefox gets away using this service directly via a HTTP request.</p>