Pre determined area

Nate The Surveyor

Well-Known Member
Im in the field.
I need to compute an area, by pre determined area, hinge method.
I've monkeyed with it for a while.
Could someone put up some instructions for this?
Thank you
N
 

Matt Johnson

Well-Known Member
5PLS
Did you review the information in the Help screen?

CONTEXT-HELP_20180601-13.16.39.png
 

Matt Johnson

Well-Known Member
5PLS
Also I find that the CoGo Hinge and Parallel functions currently will not provide solutions with concave polygons.
 

Nate The Surveyor

Well-Known Member
Too complex.
The number one rule of cogo, is KISS.
keep It Simple Stupid.
(I solved it with trial and error.)
Go solve it in the hot sun.

Hinge pt-
2nd pt-
Brng-az
Acres
Or
Sq ft.

Create pt-
Desc
Direction defines the geometric figure.
Also, allow overwrite of design pnts. With warning. I had to delete and re-write it.
Then edit the pnt sequence for
 

Nate The Surveyor

Well-Known Member
Oops, posting from phone. Last part didn't make it.
Then edit the pnt sequnce, because deleting a pnt, removed that pnt from the area point sequence.
Trial & error method requires use of a traverse routine, to move a coord, then re run acreage, then move coord with trav. then re run acreage.
Being able to perform this (back and forth) in a simple mechanism is desirable behavior. And, allowing user to overwrite coords, (with warning) is also desirable behaviour.
Anyway, thank you for listening.
N
 

Matt Johnson

Well-Known Member
5PLS
I’m sure I understand what you mean by trial and eror method. Can you share more details about what exactly you are trying to accomplish?
 

Nate The Surveyor

Well-Known Member
I’m sure I understand what you mean by trial and eror method. Can you share more details about what exactly you are trying to accomplish?
Is there a typo in that? Did you leave out the word "not"?
ASSUMING you had a typo, the "Trial and error method" means:
Run the acreage.
Move a coordinate.
Run the acreage.
Move a coordinate.
Repeat, until it's pretty close. Set corner, and go home.
IF you try this, and the coords are Points 1, 2, 3.
It needs to be .45 ac. Hinge is 1. 2 is a fixed point. 3 has to be adjusted, to make it 0.45 ac, along a certain bearing from 2.
You guess at the location of three, at 110' from 2. @ bearing of S 10°05'15"E from 2.
Run acreage. Too big. Move it to be at 109.5. Still too big. (Now, you can see how much the acreage changes, in 1/2 a foot)
Move it to be at 109' That's real close, close enough. Run acreage to confirm, and we are done.
To MOVE pt 3, you have to DELETE it, and re make it, with simple cogo. To recompute the area, you have to EDIT and place pt 3 back in the sequence, because when you deleted it, it was also deleted from the acreage sequence.
This is cumbersome. IF we could simply OVERWRITE that coord, (With a warning) and it did not DELETE it from the Area point sequence it would be easier.
Move coord, and re run acreage. Move coord and re run acreage.

Secondary issue:
I'd also like it if EVERY time you overwrote a coord, in this manner, that it created a file, called over written coords.
So, pt 3 was changed 3 times. Each time, it simply shows a date, and time, and old and new coord.
This would not be needed for rotate and translate, but for simple cogo overwritten points. This way, you could look at that file, if you goofed it, and find an accidentally overwritten coord. and restore an iteration of the coord.
Nate
 

Matt Johnson

Well-Known Member
5PLS
Yes, I meant to say that I didn't understand what you meant by trial and error. There is no need to do this as this is the purpose of the CoGo Hinge function. It can automatically calculate the point that creates the parcel with 0.45 acres remaining.
 

Nate The Surveyor

Well-Known Member
Ok, i need to find (i havent thought of one yet) a work around to work counter clockwise.
Or else, we are back to "trial and error".
Thank you.
 

Nate The Surveyor

Well-Known Member
Ok, so to do it ccw, (counter-clock-wise), we do it backwards. Determine dist from 2nd nodal pt, to new coord.. Then, use traverse, with dist determined from doing it backwards.
Ok...
I would encourage you all to LOOK at the other data collection packages, pick the best, and simplest. Then, add a feature or two, and now this whole discussion can go away.
I'm a big fan of KISS. Simple is good, for cogo.
Nate
 
Top