Do you have any documents that detail the CMM file formats?
Matt, here's is what I wrote to you on October 23rd.
The LSA file is probably the only thing needing a little help to decipher. The COR and LEV file structures are pretty obvious.
In general, column widths are to be rigidly observed. Point names in CMM (not CEFB) may be be up to 16 characters in length. The dovetailed data collection program, CEFB and its latest incarnations have point names which are restricted to 8 characters in length.
COR files are as Monte described; name, easting, northing; the product of a horizontal least squares adjustment.
LEV files are elevations, noting that the job I grabbed (Job No. 1422) - the last job we set pins on back in July - have only zeros in its LEV file because we weren't concerned with z. LEV files can contain zeros, a single project elevation for all shots or the product of a vertical least squares adjustment with individual elevations for every point matched in the COR file. At export time these two can be married into the single DXF along with all line work and point symbologies.
LSA is really a bit of a stretch for J-Field but with the concepts of LSA's structure and end purpose, there could be a glimmer of hope for Monte. At the top, the first line(s) contains control point(s). The next section are horizontal distances between given points. The next block of lines in the file after the horizontal distances are horizontal angles with the order BS, OCC, FS given in the point names for each line/angle. The next line(s) following the angles contains azimuthal data. At a minimum, each project may have two control points and no azimuths or one control point and one azimuth. Of course there can be more control points and azimuths. The LSA represents the distillation of the OBS file in the horizontal. The observation file's redundant measurements get reduced to the bare bones minimum data through one of the steps along the way that reduce multiple horizontal angles and slope distances to mean values, and some other cool stuff like resections, offsets and such using a behind the scenes program, also written by Ray, OBS2LSA is run. Monte failed to mention another file produced at the same time, the ZZZ file. The ZZZ represents the distillation of the OBS file in the vertical. All of which are incremental steps to the final least squares adjustment.
The purpose of the LSA is to facilitate running LSAQ which then produces the COR and LEV files along with their respective statical reports; ADJ and ZOU respectively. Ray has written Hector the Vector and while I have never gotten into its use, I'm inclined to think that 1) the GFILE export options already afforded in JField (thank you Mr Frame for bringing this into the discussion) + 2) the CMMesque Hector program maybe could play nice together for Monte and other BLMers familiar with Rayware. But inclinations are sometime slippery and I've no experience to add other than we should invite Ray into the conversation. He may be able to just glance at the GFILE export and see how it could be used, probably in some fashion akin to how StarNet is handling it, but in Hector. I'm happy to give him a buzz, just not during Jeopardy!
Although it's a bit dusty with age and your attention span has probably collapsed miles ago, the attached compiled help file may serve you further should you be marginally interested. Originally written for Kurt Wurm's port, Ron Hamilton's version includes this document I wrote in early 1999 just a six months after the BLM was pulled the plug on CMM/CEFB. Some still feel, including myself, that halting CMM's development was tragic and its persistence in use through today I think bears witness to that.
Have fun!
