Error - There are unconnected sub-nets in the network

You have two separate networks in your project. Split them up into two projects.

If they're not connected, they can't be adjusted together, and they won't influence each other anyways, so it won't make any difference.

It's an irritating but minor quirk of TBC.

sorry,

but the client need it to be adjusted on one complete network he reject to be more than one network

if u know another software can do the same result and to performe the report with least square adjustment it will be more useful for me .

It sounds like there are no (or insufficient) measurements to connect one set of points to the other set of points.

If client wants it all on one network then perform measurements to tie the two individual networks together. If not it doesnƒ??t matter what software you have if there is no tie from one to another then they are independent of each other. ?ÿStarnet can do this or atleast it did many years ago. But it still doesnƒ??t change the fact they have little to no ties between them. If you have a base and rover rtk this could be done very easily by setting up the base on one side and then rover to other side. Or static or traverse between the two. Can you post a screenshot of what you have in TBC with the vectors and or total station data turned on. Maybe have background imagery turned on and the experts here could probably tell you what observations need to be made to solve the issue. Could be as simple as doing a resection between a few points or like stated above. ?ÿ Rtk base and rover or network rtk.?ÿ

Posted by: @olemanriver

Starnet can do this or atleast it did many years ago. But it still doesnƒ??t change the fact they have little to no ties between them.

This is the correct answer. While StarNET makes it convenient to adjust two separate networks at the push of a button, it doesn't change the fact that those two networks are not connected and thus have zero relationship to each other.

The results will be the same in a single StarNET project as they will be in two separate TBC projects. No connection? No influence.

If the two networks are part of the same project, do the job right and connect them. If not, it doesn't matter whether you adjust them in the same project or not.

It used to be that in Trimnet you could have unconnected subnets IF you turned off the transformation parameters (latitude/longitude tilts, azimuth rotation, and scale). Not sure why they changed that in TBC. There are many cases where I have had small unconnected subnets in a project. A workaround is to connect them together via a CORS tie (i.e. include vectors to one or more common CORS)

Other least squares packages that I use (Geolab and Star*Net) will do just fine with those.?ÿ

@john-hamilton I almost totally forgot about GeoLab. Geezers. ?ÿYes sometimes especially years ago sub nets or independent work was more common. ?ÿWith rtk base and rover and or network rtk itƒ??s almost unnecessary to not have everything connected. Even if you gain a new project next door and want to tie them together you can do it so easy now. Using CORS stations is also a good way. Then one report for all. In a perfect world with technology today I try and tell people establish a few control points way off the site its to easy and when the dozers and such come in and clear a site it will not matter if you lose most of your control you can pop it back in with ease very quickly. ?ÿIf done correctly in the front end.

Here's all I could find on the web concerning sub nets:

Unconnected sub networks is likely a VRS aka nRTK (network RTK). Did you use base and rover RTK and VRS?

if just VRS, possibly more than one base station was used during VRS survey.?ÿ

basically you have 2 points used as a base station that have no GNSS observation between them