Just checking...is anyone at MicroSurvey following this thread? It is interesting to note that this very topic was posted for months on the Feedback Forum without a single reply. I guess that avenue is not all that well traveled by MicroSurvey customers. Anyone else like to chime in?

Richard,
I'm not an experienced Excel user but I tried what you suggested. None of the GIS info appeared in the Excel file. I'm still surprised so few comments on this issue. Perhaps full blown topos are not common anymore.
Thanks,
Ed

It seems to me that if you developed a feature table you would be able to tell which features create the dtm and which do not. When you import the file to MSCAD the features should follow along and then you could sort your point table by feature and set all non dtm features to a zero elevation. MSC...

I agree with Richard. If you are confident of the elevation difference and which points were affected, a simple elevation shift in MSCAD or whatever software you are using, would be in order. However, I would also check to another point or so to see if the vertical error is consistent before applyin...

The Feature file sounds interesting and worth exploring. I've played around a little bit with them but have not implemented one. My guess is I would nedd an identical AutoMap file. The biggest problem with topo points is that I may want points with the same descriptor both in and out of the DTM. For...

Richard, thank you for these excellent points. The idea of copying the job and then deleting points has a lot of merit because if the tin goes completly haywire we can easily and confidently start over. Although it is a pity we have to resort to such methods It's great to hear from colleagues who th...

I posted on the FieldGenius Feedback Forum but received zero response so I'll try here. How do you keep track of topo points from field to office? I for one am always scrambling with inconvenient methods to keep track of which points to include or not include in the DTM that I will build back at the...

Glen is correct (as usual), freeze the image or unload it before saving. Always zoom extents prior to saving or you'll pay the price. The strange thing is that my computer seems to crash more readily now than when I first installed 2010..it seems to "learn to be bogus"

Yes it is. However, 2008 has issues handling the .tif files that are created from MrSid. I'm told these issues will be resolved with the next service patch. At this point version 2005 works much better.

I must agree. One common problem is performing a coordinate file rotation late in the drawing process. Example: Once lines have been labelled with bearings and distances, these values are often moved to a more suitable location along the desired line. Also, the text value may be edited to change the...

Thanks for listening. :D I agree with Chis L. The calculator is a great touch but using it to add angles to bearings or azimuths is cumbersome and somewhat error prone. Try the commonly used procedure of traversing from a known point by way of an angle added to the back azimuth. I think you will und...

In FieldGenius XG we could save the "as staked " position of a point (ie N,E, H, cut and\or fill) in a text file without actually creating a new point. This was very handy because we could retain as staked results without cluttering up the data collector screen with more point numbers. Can we still ...

Thanks Jason, MicroSurvey support is why we are here.
I followed your suggestion and all is well. I think all users would be interested in this info which, correct me if I'm wrong, is not in print elsewhere.