I have a dgn that have attributes for some elements:
these attributes i'm guessing that are from exporting a shp file to dgn directly from microstation.
How can i read these attributes and if possible create new one or change the value of existing ones.
Is it even possible?
Inspector does not show these attributes anywhere.
Readers also does not show them anywhere
+4Hi, have you tried reading dgn as Attribute Schema.
If that doesn't solve it can you provide data sample so we can play with it?
Hi, have you tried reading dgn as Attribute Schema.
If that doesn't solve it can you provide data sample so we can play with it?
+4
Also, while at it, check options to show attributes, maybe that works also.
Also, while at it, check options to show attributes, maybe that works also.
it seems that attaching a sample is not working(the form just froze on 100% upload)
+4it seems that attaching a sample is not working(the form just froze on 100% upload)
or provide download link ;)
Also, while at it, check options to show attributes, maybe that works also.
sample.zip
+4Stupid question... What is this entity in Microstation called. Is it an item set?
Stupid question... What is this entity in Microstation called. Is it an item set?
i've attached an example (look at zzupljanin commants)
+4Unfortunatelly, I really don't know what kind of data are those. Mine Microstation opens geometry without attributes.
+1@loganj, when I loaded the DGN into Data Inspector, I noticed this attribute has a rather large value:
igds_xattributes{0}.data =
"000001011580A2000001424543584D4C00FF0A0D010000030000301FFA0C4772696666697468
31316B56FA0A696E7374616E63654964FA00FA05786D6C6E73FA3F477269666669746831316B
565F7368705F3336353532323642373237344435363130443641414534443730413036443036313
73738353532412E30312E3030FA0553575F4944FA03464944FA054C4142454CFA0F3936303230
39333A39363032303934FA054445504F54FA0E4772696666697468204465706F74FA0646454544
4552FA0757415232313233FA06524547494F4EFA08536F75746865726EFA06535441545553FA0A
496E2053657276696365FA07564F4C54414745FA0431316B56FA0A434F4D4D4E5F4E414D45FA
174D65726375727920372F342E3530204141432F31333530FA0A434F4E5F4D4154455249FA0841
41432F31333530FA0A434F4E53545F54595045FA03414143FA06504841534553FA03485633FA0A
4E4F5F4F465F4341424CFA0133FA09535452414E44494E47FA06372F342E353003000501110205
03110406020510F3F87A350004020610F281140402071108040209110A04020B110C04020D110E0
4020F11100402111112040213111404021511160402171118040219111A04021B111C04021D111E0
404"
When I copied this into a HEX to ISO-Latin-1 converter, I'd get something garbled text like this:
???¢??BECXML?ÿ
????0úGriffith11kVú
instanceIdú?úxmlnsú?Griffith11kV_shp_3655226B7274D5610D6AAE4D70A06D061778552A.01.00úSW_IDúFIDúLABELú9602093:9602094úDEPOTúGriffith DepotúFEEDERúWAR2123úREGIONúSouthernúSTATUSú
In ServiceúVOLTAGEú11kVú
COMMN_NAMEúMercury 7/4.50 AAC/1350ú
CON_MATERIúAAC/1350ú
CONST_TYPEúAACúPHASESúHV3ú
NO_OF_CABLú3ú STRANDINGú7/4.50?óøz5?ò�
You can see attribute key-value pairs from your screenshot such as:
COMMN_NAME = Mercury 7/4.50 AAC/1350 and
NO_OF_CABL = 3
I tried other text encodings but ISO-Latin-1 seems to point to the best indication of the source.
In Workbench, you can use TextDecoder with these parameters:
Encoding Type = HEX
String to Decode = igds_xattributes{0}.data
Character Encoding for Binary Data: Latin-1
Good luck continuing on from here...
+39@loganj, when I loaded the DGN into Data Inspector, I noticed this attribute has a rather large value:
igds_xattributes{0}.data =
"000001011580A2000001424543584D4C00FF0A0D010000030000301FFA0C4772696666697468
31316B56FA0A696E7374616E63654964FA00FA05786D6C6E73FA3F477269666669746831316B
565F7368705F3336353532323642373237344435363130443641414534443730413036443036313
73738353532412E30312E3030FA0553575F4944FA03464944FA054C4142454CFA0F3936303230
39333A39363032303934FA054445504F54FA0E4772696666697468204465706F74FA0646454544
4552FA0757415232313233FA06524547494F4EFA08536F75746865726EFA06535441545553FA0A
496E2053657276696365FA07564F4C54414745FA0431316B56FA0A434F4D4D4E5F4E414D45FA
174D65726375727920372F342E3530204141432F31333530FA0A434F4E5F4D4154455249FA0841
41432F31333530FA0A434F4E53545F54595045FA03414143FA06504841534553FA03485633FA0A
4E4F5F4F465F4341424CFA0133FA09535452414E44494E47FA06372F342E353003000501110205
03110406020510F3F87A350004020610F281140402071108040209110A04020B110C04020D110E0
4020F11100402111112040213111404021511160402171118040219111A04021B111C04021D111E0
404"
When I copied this into a HEX to ISO-Latin-1 converter, I'd get something garbled text like this:
???¢??BECXML?ÿ
????0úGriffith11kVú
instanceIdú?úxmlnsú?Griffith11kV_shp_3655226B7274D5610D6AAE4D70A06D061778552A.01.00úSW_IDúFIDúLABELú9602093:9602094úDEPOTúGriffith DepotúFEEDERúWAR2123úREGIONúSouthernúSTATUSú
In ServiceúVOLTAGEú11kVú
COMMN_NAMEúMercury 7/4.50 AAC/1350ú
CON_MATERIúAAC/1350ú
CONST_TYPEúAACúPHASESúHV3ú
NO_OF_CABLú3ú STRANDINGú7/4.50?óøz5?ò�
You can see attribute key-value pairs from your screenshot such as:
COMMN_NAME = Mercury 7/4.50 AAC/1350 and
NO_OF_CABL = 3
I tried other text encodings but ISO-Latin-1 seems to point to the best indication of the source.
In Workbench, you can use TextDecoder with these parameters:
Encoding Type = HEX
String to Decode = igds_xattributes{0}.data
Character Encoding for Binary Data: Latin-1
Good luck continuing on from here...
I cannot get the TextDecoder to produce any output with the above parameters for the above data value. I can recreate in an online hex converter. Am I missing a step?
+39Whilst I now have a method that will extract this data for one particular setup of xattributes, it doesn't seem like the correct way to do it. How should this igds_xattributes{}.data (fme-binary) be turned into something useable??
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
