NAD83(2011)

Waiting for the new geoid to make the move. I imagine there will be a bit of a shift here on the east slope of the cascades but nothing like what those on the west side will see.

Doug

The GEOID issue is a good reason for most folks to hold off for another month or so, but it's only a minor inconvenience from a geodetic control standpoint.

We (County Surveyor & I) started making the transition to NAD83(2011) last summer, so we will have some "GEOID'n" to do this Spring.

Loyal

The few OPUS solutions I have done between the two show 1 - 3cm in the horizontal here in Montana.

hi loyal, we switched to 2011 frame about three months ago. wishing i had a block of time to do the comparisons...

Here's what it looks like for Louisiana:

Solution for 3 Translation, 1 Scale and 3 Rotation Parameters

(Using Variances Only)

DX DY DZ Scale-1 Omega_z Psi_y Epsilon_x
Meters Meters Meters (x10^6) Seconds Seconds Seconds

-0.36 0.12 0.08 0.01 -0.01 -0.01 0.00
Stddev:±0.16 ±0.11 ±0.15 ±0.01 ±0.00 ±0.00 ±0.01

Grrr...Still evaluating all this at the city. Our area has been pretty quiet and things fit but this 'new' thing is just tossing a monkey wrench into a system that was worked since 1996 or such.

Seems to be about 0.09 in the northing and 0.04 (that pesky thing again) in the easting.

0.09 is enough to cause doubts so I hate to say it but maybe we will have to toss in a false northing to match our coordinates when the NGS drops the support for CORS 96. I am not changing ten billion points just because they change the reference frame.

Stop the world. I need to get off.

> Grrr...Still evaluating all this at the city. Our area has been pretty quiet and things fit but this 'new' thing is just tossing a monkey wrench into a system that was worked since 1996 or such.
>
> Seems to be about 0.09 in the northing and 0.04 (that pesky thing again) in the easting.
>
> 0.09 is enough to cause doubts so I hate to say it but maybe we will have to toss in a false northing to match our coordinates when the NGS drops the support for CORS 96. I am not changing ten billion points just because they change the reference frame.
>
> Stop the world. I need to get off.

I've watched your work over the years and you've been an inspiration to some of us. I don't think you should change anything, simply list the metadata and let the next guy worry about 2011. Based on what I've read about your work in the past 10-12 years, it should stand on it's own.

Sit back relax and enjoy the show.

Cheers,
Ralph

I like to keep up, but dang the point to point is the only thing I need. Not some absolute, and changing set of numbers referenced to something we have no idea about.

The point to point stuff hasn't changed with all the realizations (and that cracks me up, realizations)

Quit pushing that little ball in the middle and just stop the sillyness. Some folks have a town to support and we like a stable set of coordinates.

But I will study this.

I used it for one project but didn't check to see the difference from NAD83(CORS96) epoch 2002.00.

Deralski

Hmmmm...that's a little more than I would have “guessed” off the top of my head (for Oklahoma), but then I haven't been monitoring the CORS around Lawton lately either.

We ALL want to have “stable” coordinates on our projects, and it isn't really all that hard to accomplish (with some limitations of course).

IF your area is internally consistent from a NAD83 velocity standpoint (little if any differential movement in the relative sense locally), AND the velocity field model in HTDP appears to model this velocity accurately (which it does in MOST areas of CONUS), then all you have to do is “lose” the State Plane Coordinate moniker, and take control of your projection parameters yourself.

Your Okie NAD83(CORS96) Epoch 2002.0000 North/East coordinate values stay the SAME, but you compute and PUBLISH NAD83(2011) Epoch 2010.0000 Projection Parameters that return the SAME North/East NUMBERS on your bazillion points (aka Lawton_2011). IF the NGS drops another realization on us in say 2015, then you do it again, and PUBLISH Lawton_2015. When the “NEW” Geocentric North American Datum replaces NAD83....ya do it again (Lawton_2022)! Your bazillion points are STILL NAD83(CORS96) Epoch SPCs, but you have built a bridge between realizations of NAD83 (and someday NAD_whatever) so that other folks (and of course yourself) can use the latest realization of the NSRS (and CORS/OPUS_etc.) without reinventing the wheel.

Obviously Lawton_2011 will NOT = Oki_SPC NAD83(2011), but that's the price you pay for using State Plane Coordinates in a modern [dynamic] spatial paradigm. Recompute a couple/three numbers, or recompute a bazillion...the choice is yours.

Loyal

I'm going to run a trial on my "post" in the pasture. I plan to do a less than 2 hours submission to RS. I'll send that both ways. I'll do something like a 6 hour and send to Static. I'll let you know what it looks like.
B Well
Bob in NH