title: Google Maps APIv3 elevation resolution
body: <p>I'm building a web application that uses elevations along a path, so I'm using the Maps API to extract elevations. However, it is important that I know the degree of accuracy of this information. The API documentation states that the elevation resolution is a value <strong><em>"indicating the maximum distance between data points from which the elevation was interpolated, in meters."</em></strong> This is exactly what I'm wanting, but the values I get from this resolution seem odd. Try this example given below for the south coast of England.</p>
  
  <p><a href="https://maps.googleapis.com/maps/api/elevation/json?locations=50.8,-1.1">https://maps.googleapis.com/maps/api/elevation/json?locations=50.8,-1.1</a></p>
  
  <p>This example gives a resolution of 610 metres. Now having sifted through the net to find out about what google uses for elevation data, SRTM 3 crops up a lot. I have personally used this dataset extensively and I know it has a resolution of 3 arcseconds, which is approx 90m, and is available for most of the world. But google also states that they use many many sources for elevation data to give the best <a href="https://groups.google.com/forum/#!topic/google-maps-js-api-v3/KcjkS-U36dE">possible coverage</a>. So based on this, I would expect the elevation resolution to be of the order of at least 90m, or better. But sampling across europe this doesn't seem to be the case, and is often well over 100m. And being 610 metres for the south coast of England seems far too high given the type of data Google would be using.</p>
  
  <p>So my question is, can anyone shed any light on this, or am I missing something or even doing something wrong? I know for the US some regions give great resolution (~4 metres), but as I say, intuitively you would expect the world to have at least 90m res.</p>