MS Field Genuis F-F

I used it for a couple months but had trouble with the screen locking up picking points on screen, while in point staking ,they may have fixed this by now . The other deal that bothered me was that thier automapping only works with thier cad software . meaning if you wanted to automap in the data collector and then download it to say carlson it would not work unless you forgo the line creation method in the data collector and collect with begin codes and such that work with Carlson. I wish it would allow you to collect the data with the MS survey way, but then write a rw5 file with the begin and end codes in it so Carlson can automap in the program. you can always send out a dxf but then you will not be able to process the rw5 file and get automapping . If you use MS Cad then its probably a no brainer.

Other than that it a top notch program .

Thanks Michael,

I'll give those guys a shout.

In the multi set routine Field Genius has a bug which messes up the target heights. Take good notes when using field genius.

I use Microsurvey for a cogo program which it is pretty good at. But in my humble opinion Carlson has a much more robust and powerful field to finish capability. If it was me and my money I would go with Carlson. Also Carlson knows how an area inverse list should look but that may be a personal preference thing.

Keep your eye on the ball (and the money), if you run Leica gear, I would expect this to work good, better and best as time goes on since they are now owned by the same parent company. In addition, I believe at least one person who used to work for Leica in Atlanta support is now working for them in Canada. To me as a causal observer, I would say that with Leica now owning MS that there will be rapid development to any perceived short falling to the competitors.

SHG

MS Field Genuis F-F

I thought this post was going to be about me!:-D

Just kidding, I couldn't resist.

I don't think that it is a bug.
You have to recheck your set-up info because you are doing a new 'routine'.
We do multi-sets fr control points , so the instrument is always re-leveled and therun the BS check.
But I like how you can 'freewheel' your shots in the multisets.

Robby it is good. But as others eluded to what PC software are you using?

Also beware even with Microsurvey (any version even 2013) there is a missing link between both applications.
For egs 3D linework in Fg doesn't come into Microsurvey attached to the points. (2D does, not all 3D stuff) That's fine so long as you don't do any shift, rotate, scale etc inside MSCAD.
You can create DTM's in FG but that involves careful scrutiny on screen.
Points can be set not to be used in the modeling, but MSCAD doesn't honour that.
Also AutoMAP (point coding and linework) in FG works well but again there are some mismatches in MSCAD.
Now that doesn't mean anything if you use another software.

Linework is so easy in FG but that's not all there is to data collection.

FG creates a dxf file of all linework. And FG will export ASCCI file of points.
So you have that option of using the dxf and points to bring into the other program.

Also FG creates a dbf file that has all the attributes of your field points. It is time stamped if you turn it on ie.

I would say you could, given good field procedures, get an output that requires very little if any reprocessing.
That is provided you don't have to rotate, shift etc.

Rotate, shift and scale can be achieved in FG but on a small screen then its a pain. Also its easy to muck up and NOT all points get treated so some get missed and then its a nightmare.

Hope that helps. Field to Finish is really only as good as the operator and the software combined. FG wont make it for you on its own.

Also the free application offered by Microsurvey - MSDX may get you across some hurdles.
Haven't used that yet so can't comment.

I haven't actually used field genius but my co-worker does.

If you look in the raw data (similar to TDS RW5) you will see a target record with the correct HI/HR but the backsights and foresights will have the same HR. This is because the raw data also has the HR on the line with the angles and distances. I can't remember but I think it copies the backsight HR onto the foresight HR although the correct foresight HR was entered.

There could be some step that is being missed.

Field Genius allows sights to be collected in any order but personally I think good set collection procedure calls for matched shots so that drift (if any) can be detected.