Lieca LGO + Move3 Least Squares Plug-in vs. StarNet

I have used the adjustment module of LGO. In 2012. I am also a long term user of StarNet. I understand that the Move3 algorithm is better than StarNet's when the project extent becomes very large, as in several counties (or large Pacific island, as the case may be). But how many of us do that?

You can edit the input data in LGO but it isn't real slick. You are going to place a high priority on having data come in from the field without needing even the most minor corrections.

Forget about using data from anything other than Lieca data collectors.

There is no "Run" button as there is with StarNet. You add data, or make an edit, and the results are updated instantly. Which is sort of cool. Except that it doesn't always work. Which is dangerous. Perhaps they have fixed that by now.

The adjustment report is HTML, which is fine for examining on the screen but not so good for printing out. I like to print a copy for the files.

Over all, I prefer StarNet. But I could live with LGO. If you are fully committed to Leica I can see why you would prefer to go that way.

Mark Mayer, post: 362055, member: 424 wrote: I understand that the Move3 algorithm is better than StarNet's when the project extent becomes very large, as in several counties (or large Pacific island, as the case may be). But how many of us do that?

Star*Net performs its adjustment on a user-selected grid, so attempting to adjust measurements that extend beyond the grid system boundary will introduce errors corresponding to the limits of the grid system formulas. Move3 and some others (e.g. Grafnet, Columbus, TGO/TBC) aren't subject to this restriction, as I understand it.

Starnet is less expensive, easier to learn and use, good but not as robust as move3.

move3 / LGO is more costly, difficult to learn, and immensely powerful: the user can process GNSS data, leveling, and total station data all in the same platform. least squares adjustments can be handled simultaneously also.

i agree with jim and mark, as a network grows in size, so would the benefit to use a process like move3, as it has a true 3d geodetic quality to it. starnet is closer to a 2d plus 1d processor, for lack of a better phrase. if you are using move3, but are also thinking to switch to starnet, i would suggest you stick with move3 for its versatility and power

Moe Shetty, post: 362062, member: 138 wrote: the user can process GNSS data, leveling, and total station data all in the same platform. least squares adjustments can be handled simultaneously also.

Those things are true of StarNet as well.

One of the limitations of StarNet is the lack of intelligent converters. As it is purely a LSA engine, it doesn't provide F2F features - no user lines, text, and symbols. But I love StarNet as it processes fast and quiet. Easier to troubleshoot too.

Any idea of the price of LGO+Move3?

Thank you guys!

Mark Mayer, post: 362067, member: 424 wrote: Those things are true of StarNet as well.

good. i didn't know starnet processes GNSS data. i was under the impression that it will adjust an already processed vector (from some other source of software) by way of the VCV matrix. our starnet license may be a couple years old, so that's good for them

amdomag, post: 362077, member: 1683 wrote: One of the limitations of StarNet is the lack of intelligent converters. As it is purely a LSA engine, it doesn't provide F2F features - no user lines, text, and symbols. But I love StarNet as it processes fast and quiet. Easier to troubleshoot too.

Any idea of the price of LGO+Move3?

Thank you guys!

i think LGO is re-branded as Infinity now, the guts of the computations are probably very similar to move3. my guess would be $10000 USD, but some of the user options can change the price.

Moe Shetty, post: 362083, member: 138 wrote: i didn't know starnet processes GNSS data.

It doesn't, it does adjustment only. I think Mark was referring to its ability to *adjust* data from all those observation sources.

Moe Shetty, post: 362083, member: 138 wrote: good. i didn't know starnet processes GNSS data. i was under the impression that it will adjust an already processed vecto

StarNet does not resolve vectors. Neither does the Move3 (Adjustment) module of LGO. The static vector resolution module of LGO is a separate purchase.

amdomag, post: 362077, member: 1683 wrote: Any idea of the price of LGO+Move3

I don't recall exactly, but I know that the prices for all these modules stack up pretty fast. By the time you have the static resolution module, the Move3 module, the drawing module, yadda, yadda, you are going to be into it several thousand dollars. And I expect that you are still going to need some other CAD.