Autodesk MapGuide Enterprise Developer

[#1]

I am loading some DWG files through MapGuide Studio
and wanting to preserve object data fields and values for each entity.  In
the load procedure, I am using the transform option of "Feature source" and
"Seperate into multiple resources" so that SDF files are generated for each
layer.  When I look at the resultant MapGuide Enterprise layers, they
include some of the AutoCAD properties derived from the entities, but nothing
for object data.

Any insight into whether object data can be carried
over into MapGuide Enterprise would be appreciated.

Thank you.

--
Andy Morsell, P.E.
Spatial
Integrators, Inc.

href="http://www.SpatialGIS.com">http://www.SpatialGIS.com

[#2]

Andy,
DWG object data cannot be included in the SDF3.0 of the feature source.

Currently, much of the issue lies with the lack of enforcement of a
'standard' schema for object data. In theory, every feature in the DWG could
use a different schema for object data. Dumping all of this into an SDF3.0
would mean creating every object data column in every feature in the SDF,
whether relevant/populated or not. A lot of useless overhead in an already
bloated (as compared to SDF2.x) data format.

Add this to the Wishlist newsgroup, _please_.
--
Chris L. Amos
Quality Assurance Autodesk MapGuide



"Andy Morsell" wrote in message
news:5253850@discussion.autodesk.com...
I am loading some DWG files through MapGuide Studio and wanting to preserve
object data fields and values for each entity. In the load procedure, I am
using the transform option of "Feature source" and "Seperate into multiple
resources" so that SDF files are generated for each layer. When I look at
the resultant MapGuide Enterprise layers, they include some of the AutoCAD
properties derived from the entities, but nothing for object data.

Any insight into whether object data can be carried over into MapGuide
Enterprise would be appreciated.

Thank you.


--
Andy Morsell, P.E.
Spatial Integrators, Inc.
http://www.SpatialGIS.com

[#3]

Thanks for the clarification Chris. I do see that some bloating may occur,
but it should not be too bad. In this case, I am having it write one SDF
file per layer, so if the export could determine only the object data tables
and fields for that layer, it would not be as bad.

The only way I can figure out how to get object data or database link
information from a DWG to MapGuide is to create feature classes in Map. In
that feature class definition, include the object data fields or link
templates that you want. Then, when that layer is loaded through Studio, it
carries those values with it.

This could end up being exteremely cumbersome for people with a lot of
object data in their drawings. I will add an item to the wishlist for
creation of default feature classes for a layer that has objects with object
data.

Andy


"Chris Amos" wrote in message
news:5253909@discussion.autodesk.com...
Andy,
DWG object data cannot be included in the SDF3.0 of the feature source.

Currently, much of the issue lies with the lack of enforcement of a
'standard' schema for object data. In theory, every feature in the DWG could
use a different schema for object data. Dumping all of this into an SDF3.0
would mean creating every object data column in every feature in the SDF,
whether relevant/populated or not. A lot of useless overhead in an already
bloated (as compared to SDF2.x) data format.

Add this to the Wishlist newsgroup, _please_.
--
Chris L. Amos
Quality Assurance Autodesk MapGuide



"Andy Morsell" wrote in message
news:5253850@discussion.autodesk.com...
I am loading some DWG files through MapGuide Studio and wanting to preserve
object data fields and values for each entity. In the load procedure, I am
using the transform option of "Feature source" and "Seperate into multiple
resources" so that SDF files are generated for each layer. When I look at
the resultant MapGuide Enterprise layers, they include some of the AutoCAD
properties derived from the entities, but nothing for object data.

Any insight into whether object data can be carried over into MapGuide
Enterprise would be appreciated.

Thank you.


--
Andy Morsell, P.E.
Spatial Integrators, Inc.
http://www.SpatialGIS.com

[#4]

Andy,
If you end up using Map to modify the data, another workaround might be to
save/export the DWG to SHP c/w object data and then load the SHP into
Autodesk MapGuide.

--
Chris L. Amos
Quality Assurance Autodesk MapGuide


"Andy Morsell" wrote in message
news:5254036@discussion.autodesk.com...
Thanks for the clarification Chris. I do see that some bloating may occur,
but it should not be too bad. In this case, I am having it write one SDF
file per layer, so if the export could determine only the object data tables
and fields for that layer, it would not be as bad.

The only way I can figure out how to get object data or database link
information from a DWG to MapGuide is to create feature classes in Map. In
that feature class definition, include the object data fields or link
templates that you want. Then, when that layer is loaded through Studio, it
carries those values with it.

This could end up being exteremely cumbersome for people with a lot of
object data in their drawings. I will add an item to the wishlist for
creation of default feature classes for a layer that has objects with object
data.

Andy


"Chris Amos" wrote in message
news:5253909@discussion.autodesk.com...
Andy,
DWG object data cannot be included in the SDF3.0 of the feature source.

Currently, much of the issue lies with the lack of enforcement of a
'standard' schema for object data. In theory, every feature in the DWG could
use a different schema for object data. Dumping all of this into an SDF3.0
would mean creating every object data column in every feature in the SDF,
whether relevant/populated or not. A lot of useless overhead in an already
bloated (as compared to SDF2.x) data format.

Add this to the Wishlist newsgroup, _please_.
--
Chris L. Amos
Quality Assurance Autodesk MapGuide



"Andy Morsell" wrote in message
news:5253850@discussion.autodesk.com...
I am loading some DWG files through MapGuide Studio and wanting to preserve
object data fields and values for each entity. In the load procedure, I am
using the transform option of "Feature source" and "Seperate into multiple
resources" so that SDF files are generated for each layer. When I look at
the resultant MapGuide Enterprise layers, they include some of the AutoCAD
properties derived from the entities, but nothing for object data.

Any insight into whether object data can be carried over into MapGuide
Enterprise would be appreciated.

Thank you.


--
Andy Morsell, P.E.
Spatial Integrators, Inc.
http://www.SpatialGIS.com