-
EPOCHs CSFs and this Dumb Dirt Surveyor
Last week I attended an ALTA/NSPS 2016 standards update presentation by Gary Kent. I returned to the office motivated to start to update my standard drawing template for next year.
Then I came here and saw [USER=10450]@Rich.[/USER] and his brave thread (Plat Opinion) and I was inspired by [USER=6179]@JBrinkworth[/USER] and his posting of a plat for comparison. I decided to steal Johnny’s Basis of Bearing note for my drawing template.
But then I realized that I am just a dumb dirt surveyor, and what the hell do I know about EPOCH’s?
So I sent an e-mail to my friendly neighborhood GPS dealer [USER=1087]@Mark Silver[/USER]. I said,
Happy Friday Mark,
I am polishing up my drawing template and am working on a Basis of Bearings note:
Do you have any advice (1) on the note itself, and (2) how I might readily be able to easily identify the proper info for each survey?
Is there some simple program or such like Corpscon, etc that you recommend?
Do I have to look at the data collector for the EPOCH?
What the ÛÏfront doorÛ is an EPOCH and how in the hell does that info help some future surveyor?
Your friendly neighborhood dumb dirt surveyor, Brad.
And then my pal Mark said, I could make a decent living lecturing about this.
First off, letÛªs be clear that coordinates are accessories to monuments. And coordinates have a relatively low precedence order in the scope of accessories (Distance, Bearing, Natural Calls, Areas, CoordinatesÛ?)
EPOCH: In the United States, all points have some velocity. Areas near the western coast typically have very high velocities, areas like middle of nowhere Oklahoma have relatively small velocities. As you get near the caldera of Yellowstone (like Salt Lake City where I am sitting) the velocities are not negligible.
Because surveyors would like to specify a coordinate and have it remain constant through all times in the future what is done is when you measure a point, you record the coordinate for where the point would have been at some other time. Currently we use Jan 1, 2010 (or 2010.0. For reference, at one second past midnight on December 31st we are at 2015.0 + 364 / 365 = 2015.99726.)
Again, if I go out and record a position in the parking lot, instead of recording the position of the point today, I record the position of where the point would have been on January 1, 2010.
In the future when our kids are surveying, they will be really-really smart and will have really-really good models for translating between EPOCHÛªs (and Frames) and they will think more highly of us for preserving the ÛÏFrame RealizationÛ which is currently ÛÏNAD83 2011Û and the EPOCH date ÛÏ2010.0Û
You can (and should) have your data collector compute a suitable scale factor. You can go to ÛÏEquip: Localization: GPS (tab)Û and check the Grid to Ground checkmark. Then if you are standing in the center of the job, just click on the GPS icon and it will display the correct Grid to Ground scale factor.
If you are OPUS derived, then the position will always be displayed in the current frame (which you can read off). If you are based on a local network, then the network operator can tell you the frame of the network.
If you have already shot a job, you can go to the GG Calculator and compute an average of three or four shots that surround the job, or just use a shot at the center of the job.
In this area it is customary to place GROUND DISTANCES on any plat. To this end, I would suggest that you list ground distances AND grid distances (Carlson will do this for you automatically see: YT link here) Personally I like the Ground on top and the Grid on the bottom in (parentheses). We see a couple of feet per mile between G&G. You however are going to see 0.28Ûª per mile which might not be a big deal most of the time (the distances for 100Ûª courses are going to be the same, right?)
I would specify the EPOCH as ÛÏ2010.0Û not ÛÏ2010.0000Û, but that is nit picking.
I would also write something like: Elevations are GPS derived: A NGS OPUS-STATIC occupation was performed on CP1001. The ellipsoid elevation of CP1001 was reported 631.012 ft and the orthometric elevation was calculated 731.214 feet using GEOID 12B. All other elevations are orthometric heights derived from the ellipsoid height at CP1 using GEOID12B.
Merry Christmas!
Mark
And so I said, I am tempted to post your email text to beer leg to spur some more conversation.
To which my friend Mark said, There will be lots of comments. Hope I don’t get beat up like I did on that shaking video.
Log in to reply.