Thanks to all who joined in to help me with the problem. I appreciate it. I
got to thinking that since I'm using the exact same set up on another site
that works fine that maybe the problem was in the actual setup of the event
within the Wordpress event-manager. I deleted the location and re-entered it
and now all works fine.

Thanks again,
Randy (a.k.a. purposeman)

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Chris Schneider
Sent: Thursday, October 22, 2009 10:56 AM
To: Google Maps API
Subject: Re: TerraServer EPSG:4326 lat/long precision


Thanks for the quick response, Rossko!

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 <[email protected]> wrote:
> Might be worth
followinghttp://lists.osgeo.org/pipermail/webmap-discuss/2006-September/0001
54...
>
andhttp://johndeck.blogspot.com/2005/09/overlaying-mercator-projected-wm...
>
> I'm no expert but it seems to me that sending WGS84 coords and calling
> themEPSG:4326 without doing any actual conversion will lead to the
> kind of inaccuracy you describe?  Those sources seem to suggest
thatEPSG:41xx would be closer, if still inaccurate?


No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.5.423 / Virus Database: 270.14.26/2451 - Release Date: 10/22/09
08:51:00


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-maps-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to