Coordinate System Overrides Not Working for ODBC or MySQL

[amorsell@…]

This worked in 1.2.0 beta 1 but is no longer working in 1.2.0 beta 2. I have a MySQL table with lat lon fields. I created an ODBC data connection to it and specified these fields as the geometry. The coordinate system is set as LL in Autodesk MapGuide Studio. When viewing this data in a map with a different coordinate system, the data is not drawn in the transformed location. However, a custom search command to the same layer will zoom to that points Lat Lon coordinates where they are also drawn on the map.

The same thing happens if I use a MySQL data connection with lat lon point geometry defined in the table. The data connection has the coordinate system override set to LL.

[ronnielouie]

Andy, I have attempted to reproduce this, but it seems work for me. For clarification, here's what I am doing. I have a table in a MySQL database with lat/lon columns which I define as the geometry. I set the the coordsys for this to be LL84. The layer I create for this source is inserted into a map, which has a Lambert Conformal Conic coordsys (WORLD-LM-CONIC). When I view the map, the geometry from the MySQL layer is indeed transformed to the map coord sys. Can you confirm these steps? What else do I need or should be doing to reproduce the behaviour you are seeing?

[amorsell]

I can't get this to work for me. I tried re-creating from scratch my ODBC data connection and the lat lon field geometry association, assigning LL84, and so on. Then, I created a layer from it and am able to preview the data fine. If I embed in a map from scratch, the map picks up the spatial extents correctly and everything lands where it should in LL space. But, if I reference this data in a Texas State Plane, NAD83, Central Zone, Feet map, the data is definetely not being transformed. I know for a fact that this worked fine in 1.2.0 beta 1 so I'm at a loss here.

If I view just my points layer and a U.S. states layer, both in LL84, reference the map to a NA-LM-CONIC coordinate system, the states boundary transforms, but the points do not.

Administrator shows that I'm using MapGuide Server (Version 1.2.0.1108)

[amorsell]

I noticed some entries in the error.log that may be related: <2007-05-31T19:04:32> Anonymous

Error: An exception occurred in FDO component.

RDBMS: Data truncation error.

StackTrace:

• MgFeatureServiceHandler.ProcessOperation line 83 file c:\build_bond_area\mapguide_open_source_v1.2\build_11.8\mgdev\server\src\services\feature\FeatureServiceHandler.cpp
• MgOpGetIdentityProperties.Execute line 116 file c:\build_bond_area\mapguide_open_source_v1.2\build_11.8\mgdev\server\src\services\feature\OpGetIdentityProperties.cpp
• MgServerDescribeSchema.GetIdentityProperties line 1581 file c:\build_bond_area\mapguide_open_source_v1.2\build_11.8\mgdev\server\src\services\feature\ServerDescribeSchema.cpp
• MgServerDescribeSchema.ExecuteDescribeSchema line 173 file c:\build_bond_area\mapguide_open_source_v1.2\build_11.8\mgdev\server\src\services\feature\ServerDescribeSchema.cpp An exception occurred in FDO component.

RDBMS: Data truncation error.

[ronnielouie]

Have you tried the 1.2.0.1307 build? That is the official beta 2 build. I just tried using 1.2.0.1108 and could see that the points from MySQL layer did not transform to the current map space. After installing the 1.2.0.1307, the points transformed as expected.

[amorsell]

Is that build what is here? http://mapguide.osgeo.org/downloads.html#MapGuideOpenSource120

This is where I downloaded the build that I installed, but maybe it has been updated since then? If not, how can I get the 1.2.0.1307 build?

[ronnielouie]

Yes, that is the correct link for 1.2.0.1307 and yes it was updated.

[tomfukushima]

Is this still a problem? Please close if there is no response by July 13th/2007.

[amorsell]

This does appear to be fixed for both ODBC and MySQL geometry coordinate system overrides.