Trimble Business Center

Robert Hoy posted 03-03-2022 14:17

What is your purpose of putting a FXL file into civil 3d?   To make a description key out of it?  There are instructions on how to take a civil 3d description key and import it into the Feature Definition Manager to aid in making an FXL file, but I don't know of a way to import something into civil 3d to aid in making a description key.

Tony Edelbrock posted 03-03-2022 14:26

Yes, I should have maybe stated that better. How can I make a description key set out of my fxl file. I can export a .csv out of feature definition manager. But, I believe by default is in a comma delimited format. The person I was speaking with said that in order for C3D to use a .csv it has to be in space delimited? So I opened up my .csv in Excel and exported out a .prn which is space delimited. Saved that and then just changed the .prn extension to a .csv extension. Just not sure if that works on the C3D side as we don't have C3D at all.

ian bissonnette posted 03-04-2022 09:32

i don't know civil 3d well, but we do use an fxl for field work and use the coding to autodraw a full civil 3d drawing. these were provided by our client, so i can't answer your specific question. but i would assume you are headed down the right path and the csv or space delimited file should be able to load into civil, or it might have to be manually done. 
i just have a couple comments:

any symbols from the fxl will not follow in the csv.

civil has it's own line control system associated with certain codes. so you either have to change your fxl to match the civil default codes(this is the approach we took so that anyone that imports the points does not have to change the line control settings in civil) or you have to change the settings in civil to match your fxl. also note: i am almost positive that line control codes like connect point in fxl would be CPN 156 but in civil it would be CPN156. there is a space in fxl but no space in civil. another example for close line: fxl uses CLS 233 and civil would be CLS233. i am not aware of any way to fix this. if others have a solution please let us know.

Robert Hoy posted 03-04-2022 10:24

Civil 3d requires a space between codes and linework code set designators.

ian bissonnette posted 03-04-2022 11:44

interesting robert. i just checked with the woman that runs civil for us and for this client (specific civil template) it requires the space to be removed. perhaps this is embedded in the civil 3d template but she could not find a way to change it(maybe you know the trick). i know the client used to get most data from leica gear, so maybe it comes from that.

sorry we are deviating from the first question, but some of this might be helpful for you.

Robert Hoy posted 03-04-2022 12:00

The default is space.