Survey File using Text Import Wizard

Cory, a couple things:

1. You can definitely do what your describing
2. I don’t understand what you’re doing when you say: “I add an extra column for the field code as a general point (PNT) so I could set up the element template, feature definition and feature symbologies…” You don’t need to do that to import a field Note that part of a previously established Feature Code, unless you are saying that you created a specific code PNT for them to use in the field for their various shots that have Notes.
3. I also don’t understand what you’re doing here: “Inside the text wizard, I have put it under "Note" and "Attribute Name…” Are you also collecting field code Attributes?
4. Yes, when using the Text Import Wizard the NOTE equates to the DESCRIPTION once it’s imported into ORD
5. When imported properly, the NOTE absolutely shows up in the Properties as the DESCRIPTION. … but it depends on what you are selecting in ORD. If you select a Code in the Field Book, it won’t show up there because the software isn’t designed that way. If you select the Feature in the DGN file and look at its Properties it will show up. You’ll also see the DESCRIPTION (NOTE) in the Survey Details. And you’ll also see it when you toggle on the Description Decorator.
6. When setting up the Annotation Text Favorite, the Properties (and hence the Description) can definitely be accessed.

But the “how to” on all of this is too much to describe here. I don't like mentioning this on Bentley's Forum, but my ORD Survey book takes 18 pages just to describe setting up basic Survey Annotation. And please, please don’t take this the wrong way, (and maybe someone else will be willing to burn their free time, or company time paid for by someone else, to help you out in more detail), but dude, sorry, you need some good training. This software is NOT intuitive no matter what anyone says…. And management just throws this software on peoples computers without realizing that they don’t know how to use it. There’s no easy button here.... just frustration if you don't know what you're doing.

I hope you don't get upset by this post, I just get a little cranked up when users get thrown into new software like this without providing them training first.

Feel free to contact me on the side if you want to chat further about this. … or hope that someone else chimes in here to fill in the technical gaps.

No offense at all. We were used to InRoads and had all our preferences set up to how we like. We are trying to switch over to Open Roads but like you said there is no easy button. I am the front runner for trying to learn this so I can share and train the rest of our group when the time comes. My biggest issue is that after all the training I've done, and all the videos I watch, they all seem to say just click the button and its magic. But, none of them explain how to change the small things (preferences, settings etc.). I've gone through an entire project and completed it but now I am trying to go back and fix all the work arounds I had to do.

For what I am trying to do here, is that I didn't want to make a feature definition for every "Code". I am on the design side so the surveyors have their own field codes they use and most of the time they are not consistent. So my thought process was to make a FD, FS, ET, for this so when I import the points they all come in on the same level, symbol, and label the same way. What I am trying to do is make every point come in as a "X", and when I annotate it will show me the point name (or number in my case), description (or note), and the elevation.

My understanding is that if I wanted the surveyor text files to work as intended, I would have to create the FD, FS, ET for every unique code. But, I do not need every code to have a different symbol or annotation, hence my process of creating a general point "PNT" to make them all the same.

The only problem I was having is that even after importing and putting the description column (ex. APPROACH LIGHT) as "Note" in the heading, when I click on the points in the file the description is still blank. But your comment #5 makes sense and may have been the problem. I will have to test it later this afternoon.

But the technical stuff I have figured out (I think). From your last answer on my other post I was able to follow your video on YouTube and set all that up inside our dgnlib. I will have to go double check that file this afternoon as well. 

I much appreciate your help so far, you have been the most clear on answers that I have seen.

No offense at all. We were used to InRoads and had all our preferences set up to how we like. We are trying to switch over to Open Roads but like you said there is no easy button. I am the front runner for trying to learn this so I can share and train the rest of our group when the time comes. My biggest issue is that after all the training I've done, and all the videos I watch, they all seem to say just click the button and its magic. But, none of them explain how to change the small things (preferences, settings etc.). I've gone through an entire project and completed it but now I am trying to go back and fix all the work arounds I had to do.

For what I am trying to do here, is that I didn't want to make a feature definition for every "Code". I am on the design side so the surveyors have their own field codes they use and most of the time they are not consistent. So my thought process was to make a FD, FS, ET, for this so when I import the points they all come in on the same level, symbol, and label the same way. What I am trying to do is make every point come in as a "X", and when I annotate it will show me the point name (or number in my case), description (or note), and the elevation.

My understanding is that if I wanted the surveyor text files to work as intended, I would have to create the FD, FS, ET for every unique code. But, I do not need every code to have a different symbol or annotation, hence my process of creating a general point "PNT" to make them all the same.

The only problem I was having is that even after importing and putting the description column (ex. APPROACH LIGHT) as "Note" in the heading, when I click on the points in the file the description is still blank. But your comment #5 makes sense and may have been the problem. I will have to test it later this afternoon.

But the technical stuff I have figured out (I think). From your last answer on my other post I was able to follow your video on YouTube and set all that up inside our dgnlib. I will have to go double check that file this afternoon as well. 

I much appreciate your help so far, you have been the most clear on answers that I have seen.