The struggle we have is the way Trimble Business Center (TBC) and C3D handles the Join to Point Code (JTP) command. TBC needs a space between the JTP and the point ID that point is joining. C3D requires no space. We use the Join to Point Code (JTP) quite frequently when we are processing survey data. When points are being surveyed in the field, we strive to keep all edits tied to the point with feature coding. This ensures that when the survey is processed, it will automatically draw the features correctly and the user will not have to manually connect features in the different programs we use. Feature lines are automatically drawn in using like features and draws sequentially based on point ID. Any time a point is surveyed outside of the “numerical sequence” you must force the feature lines to connect. This also includes points that were collected on different files on the same data collector, as well as different data collectors all together. Each “job” that the points come from will not continue the feature chain across the separate jobs. We try to alleviate this by making sure the data is surveyed in a way to not try to continue chains, but that is not always the case. The JTP command is the way we force all of these connections. Our current process is to collect the survey data in Trimble access. We import that data into Trimble Business Center and perform any edits to the points to get the feature lines to draw correctly. Once we get the edits complete, we will export out a .CSV with attributes. This .CSV will then be imported into C3D in a survey database. Once the survey database is C3D, we run the extended attribute command to get the attributes to attach to the points. In TBC we would have feature coding that looks like this. EOP EL JTP 50100 C3D the same feature would look like EOP EL JTP50100 Currently this is being handled with taking the .CSV and performing a Find/Replace to get rid of the space and saving the new .CSV. That workflow works. The only issue I have is we still have a .CSV that only works in one program. Many times, we take a .CSV back and forth from one program to the other. A person must keep track of the JTP commands in the file they are working on and ensure they have it configured correctly for the program they are planning to use it in. The downfall arises when someone else uses the file. They need to know which program the file is compatible with in its current state. I believe it just leaves room for error. I would like to see if the JTP command could add a space between the JTP command and the point number it is targeting. Or if we want to come up with a different way of bringing in points and not use the .csv, but I assume it would somehow still use the point codes.
Show More