If I had to create data collection files for students to use, and was
doing it often enough, I might just create a program to prompt for
each field situation and write out the .RW5 format. Another perhaps
more convoluted solution would be to write a conversion from the CEFB
.OBS file into a .RW5 file. CEFB running on the PC with manual input
allows you to key in the data to create the .OBS file, well possibly
one step removed the binary FF file which can is converted to the OBS file.
The basic concept in both is that you have a
setup at a point,
you backsight something, may or may not shoot a distance, HI's may or
may not be recorded and read the horizontal and vertical plates
you foresight something, may or may not shoot a distance, HI's may or
may not be recorded and read the horizontal and vertical plates
The post processing software has to decide what to do with the data
so all you have to do is create all those fields.
It might be possible to build a spreadsheet to do it, but there are
multiple lines of output per setup so I think it would be easier to program.
CEFB has similar data to TDS. What constitutes a new setup may be
more explicit in CEFB than TDS, but I have not walked it all through.
You're right though, it's something you might expect someone else to
have done at least as a conversion.
- jlw