Hi GordonL,
Thank you so much for your response and great suggestions, I hadnt seen that
anyone responded to the post I made until today.
Your suggestion makes a lot of sense, I will go with this approach.
Thanks :)
Kindly,
Albin
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Use
Lack of GeometryCollection support looks to be a general limitation of the
stylization engine:
https://trac.osgeo.org/mapguide/browser/trunk/MgDev/Common/Stylization/LineBuffer.cpp#L1163
- Jackie
--
Sent from: http://osgeo-org.1560.x6.nabble.com/MapGuide-Users-f4182607.html
___
I haven't experienced problems with MapGuide viewing them, but I definitely
have had issues with ArcGIS.
I usually write a trigger or manually update like this in SQL Server:
update [dbo].[lot_lines]
set Geom= Geom.CurveToLineWithTolerance(0.01,0)
where Geom.STGeometryType() = 'CompoundCurve'
I have been having difficulty viewing data that is stored in SQL Server as a
GeometryCollection. If the collection is split up into its component
LINESTRING, COMPOUNDCURVE and CIRCULARSTRING elements I can see them just
fine but I don't see anything when these features are stored in a
collection.
Real world coordinates are actually what is difficult when you are dealing
with floor plan information. Sure, it is easy enough to move and rotate the
data to its actual position, but once you do this, viewing it in the
original "building north" rotation does not seem an easy (or even possible?)
f