Max codes per point

Pretty sure it's in the tiw file.  Although this variable is set to look into a certain folder, it doesn't show the correct tiw files.

Has anyone had any luck get codes and linking codes to work in a trimble collector, being able to draw lines on the map and being able to download correctly in openroads?  Specifically IDOT standards?

I have got it to work, but not using the IDOT standards. I work for USACE and am setting up the survey stuff for my district and all seems to be going ok for now.

You will need to go into the survey settings and ensure that the linking codes in ORD are the same as it is in Trimble.

668 being edge of pavement

Trimble's need to be: "668 B" for begin line.  I'd also like to be able to multicode up to 4 items on one shot but haven't figured out the tiw file for this yet.  Feel free to contact me offline.

Open Roads only permits one alpha or numeric code per survey point stored.

If you dual code (or more) it creates points with sequence numbers - 801, 801_1, 801_2, etc.

The link codes are even trickier. Some allow one code per shot, others allow more than one. Once used in a survey, they are split into two groups - link vs control. I forget which is which, but the codes to start and modify figures - Start, StartPC, PC, PT, NonTangentPC, NonTangentPT, etc are the one per shot per alpha code. The ones like JoinPoint, Rectangle, Distance can be used with more than one per point. You can also tell the one code per point codes as they permit numeric coding. The more than one codes do not.

This may read clear as mud, but I am not on a PC with the software loaded, so I have no reference other than memory.

Lucas,

See the attached files and let me know if this is what you are after.

Thanks,

Gerald Piotrowski

DiscussionGroup_TEST.dgn

Line Code Check - Copy.csv