For a long time, the standard workflow here has been to combine all data files (in our case, TDS RAW files) into a single behemoth. This dates back to early software where preprocessing was required before bringing in an ICS file of the full Survey. When they converted to using InRoads Survey, they carried that workflow forward. Many of the consultants doing work for us did not follow this approach but brought in each file in sequence.
As we are preparing our training materials, I want to introduce this workflow, but I did not have real daily files, so I made my own from a behemoth file. One thing I am noticing is that as certain setups are brought in, it is supposed to recall and reuse the control points of the initial file. But in the process, it is changing their Feature to Default. In some instances, it is even complaining of duplicate points and wants to rename or ignore.
Is this normal? Is there any way to prevent these from occuring?
In my experience the control points have always been in a separate file "Point List" from the Raw Data. Each Brand of Survey Software treats it slightly different, I can see trying to break out a large file to represent a daily file could wreck some havoc. We tried to process the files at the end of each day. Mainly to make it easier to find any busts and fix them. nothing worse than trying to renumber or edit codes on 12,000+ points. Good Luck I feel your Pain
Idaho Red