[mapguide-users] polyline layer from ODBC data feature

[Dave Wilson]

Firstly your primary feature class must contain the geometry. This is
the only geometry that will/can be displayed from a join.

Joined feature sources (secondary sources) are for attribute data only,
not to pick up additional geometries. Geometry from a join is not used
at this time.

It seems to me you really need 2 layers. One for the polylines and one
for the points. They don't need to be joined together as you can't
combine the geometries from 2 different sources.

Regards,
Dave

-----Original Message-----
From: mapguide-users-bounces at lists.osgeo.org
[mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of GM_Mizar
Sent: Thursday, February 22, 2007 4:21 AM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] polyline layer from ODBC data feature


Hello,

I'm trying to define a layer showing polylines starting from tables in
SQL Server 2005. I've two tables:

Roads - with the list of roads monitored by our system UI_Vertex - with
the list of point touched by the line that represents the road

I've defined a data connection with ODBC and inside a join with itself
with Roads as primary feature class and UI_Vertex as secondary. The
UI_Vertex has its own geometry defined by X and Y fields.

When I define the layer, I choose the join as feature class and the only
geometry available is the one associated with the join (because the
primary feature class doesn't have a geometry I think).

The result is that nothing is shown on the layer.

Now my questions:
1) is that feasable?
2) if yes, what is the correct way to configure the layer?

Thank you very much for your attention.


--
View this message in context:
http://www.nabble.com/polyline-layer-from-ODBC-data-feature-tf3272211s16
610.html#a9098140
Sent from the MapGuide Users mailing list archive at Nabble.com.

_______________________________________________
mapguide-users mailing list
mapguide-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapguide-users