Geometry Display in Grid View

13 views
Skip to first unread message

Crispin_at_1Spatial

unread,
Jan 9, 2010, 12:11:26 PM1/9/10
to fdotoolbox-users
Hi,

I wonder is a discussion would throw light on an observation... I am
currently testing the new direct SDE reader (FDO RFC42). So,
preamble, I have an ArcSDE server with an Oracle datastore and I can
use the OSGeo.ArcSDE provide with the ESRI DLLs to connect via the
ArcSDE service, and I can also use the new KingOra build to connect
directly to the Oracle service. Therefore I should see the same
results in the grid view when I query the same class. However, in
FDOToolbox the geomtry coordinates are displayed differently.
Specifically the KingOra ones do not have the right offset and
multiplication factor applied 123456.789 versus 223456789.

So, I had assumed it was an issue with the KingOra provider until I
ran the same connection through MapGuide (displayed OK) and our own
MapRelate (FDO reader for AutoCAD). With MapRelate (.net) I can step
into the same breakpoint as FDOToolbox at the .GetGeometry(<field>)
call and see the different coordinates.

So my question is - is there anywhere in FDOToolbox where a coordinate
system transformation is set or applied to the connection or schema?
Or any other suggestion as to why the differences in the coordinates
queried between two .net applications using the same version of FDO
and connecting to the same datastore?

Thanks for any input or consideration,

Crispin

jumpinjackie

unread,
Jan 11, 2010, 6:15:58 PM1/11/10
to fdotoolbox-users
Hi Crispin,

If there is any transformation happening, it would be in the SharpMap
component that is used to render the data.

FDO Toolbox itself doesn't do any transformations on the geometries
(other that stripping Z and M coordinates) when previewing data.

- Jackie

Crispin_at_1Spatial

unread,
Jan 19, 2010, 11:08:14 AM1/19/10
to fdotoolbox-users
It was in the grid-view that the coordinates were not displaying
correctly so had to be pure FDO / API / Provider related.
After a lot of wrong turns I tied it down to the calls to:

select.PropertyNames.Add( ___)

In "SetSelectOptions()" within FdoFeatureService.cs

I eventually passed an additional parameter to this function so that
when using the KingOra provider that line is not executed.
The geometry now appears as the first item on the grid but finally
appears with the coordinate values correctly displayed.

I am speaking to Haris about this...

Crispin

Reply all
Reply to author
Forward
0 new messages