<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>1.2.0 Beta and overriding coordinate systems?</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=401145818-27042007><FONT face=Arial
color=#0000ff size=2>The override does work in some instances, but not
consistently from what we have seen so far in MGOS Beta. MySQL is a special case
if you are using non-FDO datastores (native MySQL geometry). The override
appears to be ignored and hence the previews don't display, but added to a map
of the correct coordinate system with the correct extent it will preview. I
don't believe it will transform, but we haven't tested that.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=401145818-27042007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=401145818-27042007><FONT face=Arial
color=#0000ff size=2>Although I understand most collected point data will likely
be Lat Lon this is no longer a restriction in an ODBC datasource. If you capture
your data in another coordinate system or convert it prior to storing it you can
just specify that in your ODBC FeatureSource connection and avoid the
transformation. MG 6.5 had the Lat Lon restriction for point
data.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=401145818-27042007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=401145818-27042007><FONT face=Arial
color=#0000ff size=2>I believe the fastest retrieval will occur from MySQL
Spatial Point Geometry using an FDO datastore. I suspect ODBC will be the
slowest depending on the dataset size, but have yet to actually confirm that.
Native MySQL probably lies somewhere in between.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=401145818-27042007><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=401145818-27042007><FONT face=Arial
color=#0000ff size=2>Dave</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mapguide-users-bounces@lists.osgeo.org
[mailto:mapguide-users-bounces@lists.osgeo.org] <B>On Behalf Of </B>Andy
Morsell<BR><B>Sent:</B> Friday, April 27, 2007 11:08 AM<BR><B>To:</B> 'MapGuide
Users Mail List'<BR><B>Subject:</B> [mapguide-users] 1.2.0 Beta and overriding
coordinate systems?<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial size=2>Hi,</FONT> <BR><FONT face=Arial size=2>Is the new
overriding coordinate system of feature source functionality currently broken in
1.2.0 beta 1? I saw a note for MGE beta that stated such and I just tried
it in MGOS beta with a MySQL geometry field while setting an LL override and it
did not appear to work. So, is this a known problem in the current MGOS
beta as well? I'm very curious to find out what will perform better: an
ODBC data connection to MySQL with lat lon fields defining geometry, or a MySQL
connection with point geometry with a coordinate system override. In both
cases, the layer is being embedded into a state plane map so a coordinate
transformation has to occur. My preliminary tests of just previewing the
layers indicates that MySQL geometry performs better.</FONT></P>
<P><FONT face=Arial size=2>Thanks.</FONT> </P>
<P><FONT face=Tahoma size=1>Andy Morsell, P.E.</FONT> <BR><FONT face=Tahoma
size=1>Spatial Integrators, Inc.</FONT> <BR><A
href="http://www.SpatialGIS.com"><U><FONT face=Tahoma color=#0000ff
size=1>http://www.SpatialGIS.com</FONT></U></A> </P></BODY></HTML>