[mapguide-users] Projection problems with ArcSDE FDO and GetKMLresponses

[Brad Nesom]

Since you are using command line sde I would venture that you perhaps are
not createing feature datasets for those feature classes. The feature data
set holds the information for the crs. Your data would be going into the
geodatabase at the root level without a feature dataset. There may be an
issue with mapguide not getting the "second" crs. You could test this by
removing all data (don't know what kind of system you are running production
or development) and loading the opposite shape first the next time (if you
loaded the utm first last time load the ll first this time). Then see how
mapguide reacts. 

 

 

  _____  

From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Trent Pingenot
Sent: Thursday, May 17, 2007 1:57 PM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] Projection problems with ArcSDE FDO and
GetKMLresponses

 

Hey Group,

I'm sure those of you more experienced will groan at my ArcSDE related
question but here goes.

I'm having problems get raw KML data back when connected to ArcSDE. I am
using
Map Guide OS 1.2.0 beta and AutoDesk Map Guide Studio evaluation. I do have
the same
problem using MGOS 1.1.

I have loaded my layer of points into ArcSDE via command line utilities,
shp2sde because
I don't have ArcEditor or ArcInfo.
The first layer I loaded into my db was in a UTM projection. The second
layer of points
I loaded to SDE was in WGS84.  I specified a projection code and the layers
report
their correct projections via SDE and ArcMap.  I am able to successfully
connect to SDE using the
ArcSDE FDO to create a data connection.  I can create separate Map Guide
layers
for both of my point layers.  

Here is where it starts to get sketchy. In Map Guide Studio when I create a
blank Map and 
add my first layer by itself, whether it be my UTM points or my WGS84 points
or some other layer in
another projection the map default projection comes up as UTM. I can of
course change this to LL84 
if I am just creating a map with my WGS84 points.  My first question is why
does the map projection 
default to a UTM projection when the first layer added is in another
projection and does this shed light
on my resulting problems?

I can make web layouts with any combination of my point layers and other
layers in other
projections and they display correctly in an AJAX web browser.  

The problems start when I try to use the KML calls GetMapKML, GetLayerKML or
GetFeaturesKML.
I can successfully make these calls either from a web browser with a
response type of XML or in
Google Earth against my layer in UTM or other layers, however I get failed
responses against my layer in
WGS84 either through url calls or through GE.  More specifically when I try
and debuging at the root 
GetFeaturesKML from a url call 

http://localhost:8008/mapguide/mapagent/mapagent.fcgi?OPERATION=GetFeaturesK
ml&
VERSION=1.0.0&LAYERDEFINITION=Library://TEST/Layers/WGS_LOCS.LayerDefinition
&
FORMAT=XML&DRAWORDER=6&BBOX=-106.7621,38.7261,-105.7026,41.7703&WIDTH=500&HE
IGHT=500

for XML I get this response...

<?xml version="1.0" encoding="UTF-8"?>
<kml xmlns="http://earth.google.com/kml/2.1">
<NetworkLinkControl><minRefreshPeriod>2</minRefreshPeriod></NetworkLinkContr
ol>
<Document>
<visibility>1</visibility>
</Document>
</kml>

instead of xml with placemarks.

As further testing I added other datasets in various projections to ArcSDE.
Any data that
is UTM is returned successfully, but the other geographic projections I
tested; NAD27, NAD83, WGS84 yield
the same non-results.

It's almost as if because my first ArcSDE layer was in UTM, MapGuide sees
some type of ArcSDE schema
and things all the data is in UTM.  I even tried creating a second SQLSERVER
DB with my points but had
the same results.

When I connect to via FDO for Shapefiles for data in various projections
everything is hunky dory. I have
performed some additional testing to try and isolate the problem but won't
overwhelm the list with all
my tests.

Any ideas as to if my problem lies in ArcSDE, FDO or the MGOS KML
re-projection piece, or something I've done? 
Or feel free to humble me with some small detail I missed.

Thanks in advance!

Trent





-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20070517/832f2388/attachment-0001.html