mapimportfdo - point to block with attribute - attribute on current layer? Why?

[luc.vanlinden]

Hi

A block definition with an attribute. The attribute has its own layer. Normal behavior as far as I know is when inserting a block, the block gets inserted on the current layer while the attribute will end up on its own layer. This is as far my experience with plain AutoCAD.

Now when using the mapimportfdo command and mapping point features (from oracle) to blocks it turns out that the block as such ends up to the target layer defined by the mapping specs (so far so good), however the attribute ends up at the current layer at the moment the mapimportfdo command is issued, and not on the layer of the attribute definition, as it does when inserting it in a normal autocad way.

Working with different block/attributes on the import will end up that all different attributes will end up at the same (current) layer. 

Why are these attributes not drawn on their proper (definition) layer? Will have to add it to the long issue/inconsistency list of mapimportfdo/mapexportfdo.

Luc

[braudpat]

Hello from France

- I am a very old user of ACAD : sincre R1.4 in 1984/1985 ...

- I am a very old user of MAP : since ADE module on ACAD R12

and then it was the worst MAP : MAP R1 based on ACAD R13 (the worst ACAD) ...

Historically the MAIN problem with AutoCAD MAP is :

<Humour ON>

- The MAP development Team doesn't speak/collaborate with the ACAD Team

- The FDO development Team doesn't speak/collaborate with the OLD MAP development Team which doens't ...

<Humour OFF>

A lot of things have not been "terminated correctly" with MAP and especially with the FDO Technology !!!

So we have to play with some nice features (like FDO) which needs YET a few improvments / optimisations ...

Why we have not a Grid View of Object Data ?

Why we have not a Quick Select on Object Data ?

Why we can't interact easily between FDO Attributes and Object Data and (only for XYZ Points) with Attributes on Blocks

Of course I don't speak about Dynamic blocks which are not supported ...

etc ...

Why we havn't a better MAPIMPORT / MAPEXORT

and MAPIMPORTFDO / MAPEXPORTFDO ...

Please we need InterOperability (if it's possible) between these differents concepts :

FDO, Object Data, Attributes on Blocks, etc

Bye, Pat

[Murph_Map]

Can not aruge with any of what you wrote Pat.

[braudpat]

Hello Murph

What do you say exactly ? (My US/English is not "very good")

Maybe : aruge --> argue ??

Bye, Pat

[Murph_Map]

---

@braudpat wrote:

Hello Murph

What do you say exactly ? (My US/English is not "very good")

Maybe : aruge --> argue ??

Bye, Pat

---

Yes ARGUE, my spelling error. meaning I agree with everything you wrote in the reply.