I'm no expert either, but the problems described in these two links
would seem to be dependent on the scale of the maps being rendered. As
John Deck admits in his text, "The interesting thing is that if we
were to zoom in on a particular portion of the world, the boundaries
would line up." Since I'm rendering maps at such high resolution, I
would not expect the projection conversion being done by TerraServer
(from EPSG:4326 to UTM) to introduce the positional error I am seeing.
More importantly, my application does not require that four such
points be rendered as a rectangle by both engines.

That said, I am expecting my latitude and longitude coordinates to be
rendered properly by Google Maps as well. As mentioned in my original
email, these coordinates come from the USGS Geographic Names
Information System (GNIS), which claims them to be NAD83. I had
expected that such coordinates would be placed correctly when sent
directly into the Google Maps APIs, and when sent to the TerraServer
as EPSG:4326.

On Oct 22, 5:16 am, Rossko <ros...@culzean.clara.co.uk> wrote: