[mapguide-users] Does anyone use Feature Joins?

[Kori Maleski]

The one to one join issue has a side effect -

If you have disparate geometry with the same ID - only one of the objects
will display - and it will randlomly alternate between displaying each
object on each map redraw.

You have to ensure that the geometry is multipolygon etc. in order for the
entirety of the geometry to display.   The one to many join did not solve
the issue.


Cheers,

Kori Maleski

On Fri, Dec 12, 2008 at 9:23 AM, Andy Morsell <amorsell at spatialgis.com>wrote:

> I have encountered very similar problems with almost every join I have
> attempted in MGOS or MGE.  My most recent experience was for a class that I
> taught at AU where a polygon SDF file is joined to a small Access database.
> Both MGE 2009 and MGOS 2.0.2 just spin on this join with the a CPU maxed
> anytime the layer is accessed.  I will let it spin for a couple of minutes
> and then end the process.  The crazy thing is that I know for a fact that
> this exact join worked just fine in MGE 2008 / MGOS 1.2 because I used the
> same dataset for the same class last year!
>
> Andy Morsell, P.E.
> Spatial Integrators, Inc.
> www.SpatialGIS.com <http://www.spatialgis.com/>
>
>
> -----Original Message-----
> From: mapguide-users-bounces at lists.osgeo.org
> [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of Jackie Ng
> Sent: Thursday, December 11, 2008 8:39 PM
> To: mapguide-users at lists.osgeo.org
> Subject: [mapguide-users] Does anyone use Feature Joins?
>
>
> Hi All,
>
> I was wondering if anyone uses this feature (pardon the pun).
>
> When I first started with MapGuide, this was the feature that was of most
> interest to me as it seemed like an easy way to link spatial data with
> whatever non-spatial databases we have around.
>
> But after many bad experiences with performance, and some really nasty join
> bugs (mainly http://trac.osgeo.org/mapguide/ticket/502), I've have totally
> shunned using feature joins, and either resorting to either pre-joining,
> baking the data and refreshing the dataset at regular intervals, or using a
> spatially enabled rdbms that does the joins at the dbms level.
>
> I've have followed the best practices guide, but is seems every database I
> have encountered has its own set of quirks that don't play nice with
> MapGuide.
>
> Most of our clients were sold on the feature joins capability (well by my
> sales colleagues anyway), and it pains me (as an implementer, one to has to
> deliver) to have to workaround this feature because it fails to perform at
> a
> satisfactory level.
>
> I'd like to hear other people's experiences with feature joins. Is your
> experience better/worse?
>
> - Jackie
> --
> View this message in context:
> http://n2.nabble.com/Does-anyone-use-Feature-Joins--tp1646599p1646599.html
> 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
>
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapguide-users/attachments/20081212/e70ac61e/attachment.html