Larry Scott, post: 359902, member: 8766 wrote: So, if the POB of an existing parcel was the mid point of the Nevada Utah border? Would that be by latitude? Distance? Slope chaining?
Could you defend a different distance for the north and south halves? if by latitude?
Could you walk to it with RTK?
I'd probably go with the FENCE CORNER(s)!
😀
Loyal
There you have it.
Free range, no fences. Parcel sold. New owner calls for survey to build a fence. Neighbor thinks it the wrong place.
Larry Scott, post: 359912, member: 8766 wrote: There you have it.
Free range, no fences. Parcel sold. New owner calls for survey to build a fence. Neighbor thinks it the wrong place.
Sorry for the delay in getting back to you Scott, been kinda overwhelmed lately.
The very nature of your question makes any reasonable answer impossible.
You are inserting a Cadastral scenario into what was/is intended to be a geometric/geodesy exercise.
Any Land ÛÏboundaryÛ along the Nevada/Utah Border, would of course be constrained by the Official Surveyed (and Monumented) LINE between Utah and Nevada. That ÛÏlineÛ was first surveyed and monumented in 1870, the returns indicating a total length of 345 miles 16 chains. This would put the ÛÏsurveyed midpointÛ at ~ Mile Post 126 + 8 chains. BUT, in 1871, the Survey of the Idaho/Utah Border found that the North Corner of Nevada/Utah was 1 mile 12 chains TOO far north, so a new Corner/Monument was set, and the Original was destroyed. This then put the ÛÏmid-pointÛ at Mile Post 126 + 54 chains! BUT WAIT... in 1901, the Southwest Corner of Utah set in 1870, was found to be 1 mile 31.51 chains TOO far north, so Southwest Corner of Utah moved to the new position. This would put the ÛÏlatestÛ surveyed midpointÛ at ~ Mile Post 127 + 29.757 chains.
Hmmmm...let me do the math, 1870 to 1871 46 chains south, 1871 to 1901 another 55.257 chains South.
Inasmuch as all of the lands situate several miles either way from these points are still Public Domain (BLM), this is pretty much a moot point anywho.
The NGS does have Geodetic Positions at both ends of the [current] ÛÏline,Û which returns an ellipsoidal distance of 344 miles 40.25 chains. Considering that the height of said Line varies from ~2703 ft. to over 9300 ft. and back down to 5238 ft., computing ANY SORT of ÛÏmidpointÛ (in a ÛÏcadastralÛ sense, would be a real PITA. In any case, I'll bet dollars to dog turds that ANY theoretical ÛÏmidpointÛ between these two [end point] Monuments ain't going to FIT the ÛÏsurveyedÛ line (Latitude OR Longitude) fer sour owl $#!?. Not only that, there is some evidence of skipped (and/or) duplicated Mile Post Numbers along the route (line).
Looking at the current USGS Quads involved, it appears that Mile Posts 125, 127 & 128 were recovered by the USGS in 1981...and I see no reason that MP 126 couldn't be recovered. THAT'S were I would start!
I know that you are fishing for a different answer, but I have to stick with some form of RETRACEMENT answer in the scenario you propose.
Loyal
As always, the answer is, it depends.
Back to the original question about midpoint between equator and north pole, a far more complex challenge would be to attempt to actually measure such distance (and divide by two) by selecting a point on land on the equator and heading "north" along the longitudinal line, crossing the least amount of open water possible until reaching the north pole. For example, pick a spot in Kenya to begin. There would be a fairly short water stretch across the Red Sea and a much longer water stretch across the Black Sea. No GPS, strictly total station type measurements allowed. You know, real measurements. Better yet, use a chain everywhere possible.
It wasn't a real cadastral/boundary question. It was in the spirit of defining halfway along a meridian.
Yes the state line has existing history.
I rephrase: a university has a deep space telescope in northern Canada and in southern Mexico, on the same meridian. They want to place a third instrument 1/2 way.
In the spirit of the question, it's a good question. And has different answers under different parameters.