![]() This lack of functionality causes me to have to use an external workflow with Excel, but in my mind this is unacceptable as TBC is supposed to be the definitive resource for processing, adjusting, and reporting all of my field survey needs. The whole reason I use TBC is so I can marry job files from different sources and guarantee a consistent geospatial reference frame. ![]() This is very frustrating because I don't always have physical possession of the Data Collector used, and if there's even the slightest mismatch in control or coordinate system settings the exported CSV will not be reliable. I would really like to know if there are any intentions of supporting SonarMite data in a future release of TBC? I spoke with my local distributor back in 2017 and they told me this was a topic of discussion, but it still doesn't seem possible to properly process sonar data in TBC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |