[OR Ss4] Survey Data Files - Single big file or separate daily files and Oddities that occur

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

  • I feel your pain as well. I really thought SS4 would be more advanced as a survey product. Maybe even good enough to say it would disrupt our workflows in a good way. Then I woke up from my dream....

    I don't think there is any answer to what you are experiencing. I found the same issues within PowerGeopak. We explored the import options a few years ago. After a lot of experimentation we decided to stay away from processing raw observations in SS4 and Open Roads. Things went well with a single file and went off the rails when adding more raw data. I have had the same experience as you describe. We now process outside of SS4 (StarNET) and import only coordinates with line coding.

    The files I experimented with were: FB raw, rw5,Autodesk FBK and TDS raw.

    The holy grail I was looking for would have a single platform for field to finish work cycles. I'm still looking for that tool.

    Keep us posted. I'd like to see your training documentation when finished, if you can share it.

    Cliff 

  • ODOT's (Ohio) Manual is pretty good. Budgetary constraints are really tying our hands for preparing manuals that do the workflow justice. Right now, ours are assuming no typographic or shot order issues are encountered. The ODOT manual has sections on converting observations to point list and combining figures.

    At the last few firms I worked at, we were successful at processing topo in InRoads Survey for Land Desktop, Civil 3D, GEOPAK as well as InRoads. But they also always used Starnet for generating all of the control points. However, I know of other firms that swear by the Least Squares adjustments done in InRoads Survey.

    The daily files I created do not have any control points in them, except for day 1. But in the TDS RAW, there are records that call out those points and some even include their coordinates. But InRoads Survey, the TIW file tells it to ignore those values. It also tells it to ignore their codes.I wonder if this is why it changes them to Default. But InRoads Survey treats SP records as fixed points. Open Roads seems to require that you give it a list of codes that are control points.


    Charles (Chuck) Rheault
    CADD Manager

    MDOT State Highway Administration

    • MicroStation user since IGDS, InRoads user since TDP.
    • AutoCAD, Land Desktop and Civil 3D, off and on since 1996