Scott Zelenak, post: 384697, member: 327 wrote: I think you can get rid of all those extra DEs and DB 500s in the middle and pack that into 14 lines.
And why fix 500? The LSA will determine its position if that's part of a larger file.
You'd have to look at a minimally constrained network first. Fix one point and an azimuth then fix more points as/if needed.
I'll try that. I was going to fix 500, or 100 for exactly the reason you point out. I need one point fixed. I could choose a corner that's in the network, as it shares two surveys. Then everything else will rotate about it according to my azimuth.
I believe he's using an assumed position. i.e., he has no control. So, fixing one point and one azimuth (minimally constrained) is all he has.
Larry Scott, post: 384766, member: 8766 wrote: I believe he's using an assumed position. i.e., he has no control. So, fixing one point and one azimuth (minimally constrained) is all he has.
That's correct. No locally available control. That's next. I'll either step up to the plate and attempt a 5 mile traverse from "Gulf Stream" NGS mark, or get someone to lend me their old L1 system for a month.:)
Argh. I remember running into this before, but can't remember how I solved it. My astro backsight station "House" is "incorrectly connected to network: Vertical". I've added a line:
E House 1000
To establish a dummy elevation, but that didn't do it. I have no real elevation data for it, and would like to keep the entire upcoming adjustment in 3D if possible.
Should I need more than a B line and an E line?
Try .2d inline command on bs?
well, just figure the azimuth from House to a leg of the net, and hold that bearing fixed. It's exactly the same. House has served its purpose for the multiple astro obs. Now a good az can be determined from House to sta 100. Hold:
b StarryHill-100 ddd-mm-ss !
(However in manual there is discussion of that type of observation. i.e. a natural az mark, off site, without a coord.)
Scott Zelenak, post: 384697, member: 327 wrote: I think you can get rid of all those extra DEs and DB 500s in the middle and pack that into 14 lines.
I ended up doing as Larry suggested (just averaged my dozen angles turned between House and my station mark, but Scott's comment on combining DN lines bothers me.
If I combine these, for example, into fewer groups:
DB 500
DN House 00-00-00
DN 100 68-23-58
DE
DB 500
DN 100 248-23-47
DN House 179-59-42
DE
Like so:
DB 500
DN House 00-00-00
DN 100 68-23-58
DN 100 248-23-47
DN House 179-59-42
DE
How the heck is Starnet supposed to know that 179-00-00 is the same direction as 00-00-00?
I thought that the way the DB, DN, DE statement worked was that it found the difference beween any two directions within one "set".
Um...and just how did it know before my advice?
If you ran that through a converter you probably wouldn't have a problem.
I think, lacking a converter, you'd have to manually reduce that.
Why not assign random coordinates to House and 500 and test it all three ways and see what happens?
Scott Zelenak, post: 384971, member: 327 wrote: Um...and just how did it know before my advice?
If you ran that through a converter you probably wouldn't have a problem.
I think, lacking a converter, you'd have to manually reduce that.Why not assign random coordinates to House and 500 and test it all three ways and see what happens?
Only that I posted the data. It may not have been apparent that it represented D and R directions. Someone here suggested that Starnet could reduce that. I did it manually...no big deal. SurvCE is unable to record just angles, so there's no easy way (using that software) to do a bunch of angles only, and have a converter do the work. I know the Topcon field software can; not sure about MicroSurvey's Field Genius. Right now SurvCe is all I got.
In the mean time, I've taken my Azimuth from 500 to House (derived from astro), and converted it to an azimuth from 500 to another point in my network. It's not ideal, as it's only a couple hundred feet away, but I'll go with it for now and move on to the "grand adjustment". Thanks for the input.
