Any guess on when NAD 83(2011) will be adjusted?
I'm going to guess about 2011?
NAD 83(20##)
Bah wiseguy! Don't answer to what I wrote, answer to what I meant...
When will NAD 83 be adjusted again?
NAD 83(2015)
NAD 83(2016)
NAD 83(2017)
Between funding shortages and the NGS having to remeasure the Washington Monument again and again, what is a reasonable time frame for a new build?
NAD 83(20##)
A quick (very quick) perusal of the Ten Year Plan doesn't reveal any date for readjustment. Looks like 2022 is the target for a new reference frame.
> Any guess on when NAD 83(2011) will be adjusted?
There is not likely to be another adjustment of NAD83. The next change will be a whole new datum.
All of the re-adjustments of NAD83 prior to 2011 have been regional in nature or of partial data sets. 2011 was the first comprehensive, national adjustment since 1986.
Geometric Datum 2022 replacing NAD 83(2011)
Dave Doyle gave a workshop at the New Jersey conference on February 5th talking about the new Geometric Datum 2022 to replace NAD83(2011) based on ITRF/IGS. NGS could theoretically switch horizontal datum now, but it will be released at the same time as the new Geopotential Vertical Dautum 2022 based on Grav-D.
As I recall, he said a new ITRF2013 will be released in early 2015. I don't think there will be any future epochs of NAD83(2011)(Epoch 2010.00) before the 2022 switchover.
Geometric Datum 2022 replacing NAD 83(2011)
Thank you all for the responses. 2022 seems so far away but I know better than that. I am trying to describe the movement of control for long term projects that are based on 'network RTK' (quoted because the project is well outside of the network polygon by 20 miles).
I started a different long term project based on passive control before CORS and a MTS CORS (free static) were available in the area. I can either translate it all and hear a large engineering firm groan simultaneously or I can make my own coordinates on the CORS that will work with my current values and play dumb.
I thought I read somewhere in the past (probably here) was that it will be a new coordinate system NAD2011.
> I thought I read somewhere in the past (probably here) was that it will be a new coordinate system NAD2011.
Perhaps you are thinking NAD2022
Adjusting the geometric reference frame (i.e. NAD 83 (2011)) is a MASSIVE undertaking. Given the resources required to perform such a task I would suspect that NGS is not giving any considerations to another adjustment until the release of the new datum in 2022. The only reason NGS performed the 2011 adjustment was because the CORS team undertook an analysis of all CORS data from the beginning of the network (1994) to bring all the stations up to date (- referenced as the Multi-year CORS Solution). Since that effort changed the positions to CORS (in some cases as much as 15 cm) that meant that the GPS passive control had to be adjusted to fit those new coordinates or there would have been serious discontinuities between the passive and active control. That multi-year solution was a tremendous undertaking CORS Multiyear Solution and while I am sure that the CORS team would like to do this every 5-6 years they have fewer personnel resources than before so it's highly unlikely that will occur prior to the new datum release.
Geometric Datum 2022 replacing NAD 83(2011)
It is my understanding that the original group of adjustments to NAD83 were to accommodate better/more observations. Which makes sense given the fact the the original HARNS were established in the days meeting at the bar to start off the day of midnight observations of four or five satellites. While this was fun, it did not result in them most accurate base lines. In Oregon the changes from NAD83[91] to NAD83[98] were quite large and unpredictable. The later adjustments have been primarily to bring the passive marks into alignment with the CORS and to update the reference frame. Hence the lack of need for new observations.
Out here we get a considerable amount of tectonic movement so the local CORS/NRTK network administrators monitor it and readjust individual CORS as needed. It is my understanding that NGS will be doing the same thing but with larger movement thresholds.
If you are worried about network movement over time then HTDP is your friend although I'm not sure how much your area is moving. As long as you are dealing with changes based on actual movement and not just better procedures you can use HTDP to bring the CORS coordinates for epoch 2010 to current. Then process you data as normal. From there you can either shift the results back in time and reference them as NAD83[2011 epoch 2010] or just reference everything to the current epoch.
Good luck
