Gentlemen,

I strongly believe that you should maintain the naming format that has been utilized for almost 2 decades. The name that makes the most sense for your planned adjustment would be NAD 83 (2007). This name falls right into place with your naming practices from past adjustments and it has worked fine throughout the years. The year should be included within the adjustment name to stay consistent with the previous naming and to clearly show when the adjustment was completed.

Wade P. Pettit, RLS
Clark County Surveyor
wade.pettit@co.clark.wi.us
--------------------------------------------------------------------------------------------
I prefer to see the year of the adjustment in the name. Many GIS applications in my area (counties), have performed much work in NAD83(97) with great success. I can easily envision NAD83 (97) going the way of the vertical datum from the 1920s. That is, used extensively for a long time by local units of government, due to the expense of updating.

Reggie Jaquish, RLS

Jaquish Land Surveying LLC

2222 Michael Court

Reedsburg WI 53959

(608) 524-4637

(608) 963-1814 cell

reggie@jaquishlandsurveying.com

--------------------------------------------------------------------------------------------
The web site is good and has been wonderful for tracking progress and for understanding what was happening

It has also been good for understanding what the adjustment meant

In terms of the naming – based on what we are hearing from the parcel people we would suggest a name without a date is better understood and could the name be pronounceable rathehr than just a set of letters

Like GeoRef or BaseRef or BaseGeo of Jersey

Okay – I am grasping at straws here but you have to admit – TIGER worked as a name – we need something that pronounceable since this will be the basis for so much consumer based positioning eventually

Just my opinion, not that of the cad community (NationalCad)

-------------------------------------------------------------------------
Nancy von Meyer
Fairview Industries (http://www.fairview-industries.com)
Phone 864-646-2755 Fax 864-646-2712
Mobile 864-356-6012
PO Box 100
Pendleton SC 29670
-----------------------------------------------------------------------------------------------------
NSRS 2007 (and NSRS 2XXX) appears to be a good naming system.

Robert L. Bragg, Jr.

York County 911

Radio System Administrator

office: (717) 840-2923

cell: (717) 324-4856

--------------------------------------------------------------------------------------------
I suggest using NAD-83(2007) or NAD-83(07).

The datum has not changed, so keep NAD-83.
The pattern used in the past has been to add the date of the readjustment,
I see no reason to change this pattern, unless you want to confuse people
now and in the future. Also, as in previous replies, many states have their
official coordinate systems defined using NAD-83. Changing this would
most likely cause a lot of legislative changes and/or legal problems. I can
envision a circumstance where a surveyor is sued for using a coordinate
system other than NAD-83, even though it actually is the same.

James Jeffreys, PLS
Assistant Locating Engineer
NCDOT, Location & Surveys Unit
Charlotte, NC

--------------------------------------------------------------------------------------------
NAD 83 (2007)


Michael J Romportl
Oneida County Land Information Director
PO Box 400
1 Courthouse Sq
Rhinelander WI 54501
P (715) 369-6179 F 369-6277
lio@co.oneida.wi.us
----------------------------------------------------------------------------------------------
NAD 83 (Adjustment year) seems to be the simplest and conforms to prior naming conventions
----------------------------------------------------------------------------------------------
Tongue in cheek suggestion - NAD83(Final)


Earl F. Burkholder, PS, PE
Global COGO, Inc.
Las Cruces, New Mexico 88003
www.zianet.com/globalcogo/index.html
------------------------------------------------------------------------------------------------
Hello colleagues:
In discussion with a colleague the other day, a reason surfaced for NOT
including the term "NSRS" in the name of the re-adjustment.
The term, NSRS, National Spatial Reference System, is a generic and
important term that is a critical part of NGS' mission. The proposal to
tag one specific adjustment with the same term will cause confusion,
particularly among those who are not all that familiar with our
terminology. Everything in our database is "part of the NSRS" right now,
and the proposed term is intended to identify a sub-set of those stations.
I highly recommend that the NAD83 datum tag for the re-adjustment results
NOT include "NSRS" as part of the name. My preference would be to utilize
the year, as we have done previously, eg, NAD83 (2007). A sentence or two
explaining this new term (adjustment with only CORS for constraints) can
easily and should be added to the "dsdata.txt" file for an explanation of
this new term, as was done for the NAD83 ("HARNyear") term.
Thank you for the opportunity to provide and read others' feedback.
Marti
Ms. Marti Ikehara
National Geodetic Survey
State Geodetic Advisor for CA
(916) 227-7325
---------------------------------------------------------------------------------------------------
It is important that the National Spatial Reference System Readjustment of NAD83 be unmistakably distinguished from previous adjustments and not follow the previous naming convention. In the past, the date of adjustment tags to the NAD83 datum designation were helpful in distinguishing between coordinate values computed at different times using a piecemeal approach and resulting in inconsistency throughout the network. A simultaneous network adjustment, however, eliminates the inconsistency that necessitated the date of adjustment tags.

Although there is consistency in using the CORS network for control, the CORS network is a dynamic system, based on time-dependent positioning. Thus, it is assumed that the Readjustment of NAD83 will be based upon CORS positions for a particular epoch date. It is also assumed that the CORS positions will, at some point, be updated for a new epoch date. Since this anticipated future update will likely also be simultaneous for the entire network, there is not a need to tag the datum designation with a date of adjustment. It is not the date of adjustment tag but the epoch date that becomes important to distinguish the updated position from superseded values. At present, the datasheets for CORS stations do not have a date of adjustment tag for the datum designation. Rather, the epoch date is noted elsewhere on the datasheet.

In my opinion, NAD 83 (NSRS) would be a sufficient datum designation to distinguish the present and future Readjustments of NAD83, based on the CORS stations, from time-tagged datum designations of the past, based on the HARN stations, as long as the term was explained in the dsdata.txt file and the epoch date was addressed elsewhere on the NGS datasheet in the same manner that it is presently addressed for CORS stations.

When reporting metadata, users should add the epoch date to the datum designation to distinguish between different values for different epoch dates (e.g., NAD 83 (NSRS) epoch 2002.00).

Steven E. Weible, PLS
Missouri Department of Natural Resources
Division of Geology & Land Survey
State Parks Survey Crew
P. O. Box 250
Rolla, MO 65402
(573) 368-2304
----------------------------------------------------------------------------------------------------

The less confusion the better. We are used to the format of NAD (some date),(adjustment date),(epoch date). Why not continue in with the same fashion?

Dane Ince, Senior Surveyor , LSIT

Ph: 707.523.1010

daneince@w-and-k.com

495 Tesconi Circle

Santa Rosa, CA 95401

Fx: 707.527.8679

www.w-and-k.com
----------------------------------------------------------------------------------------
Ok,

How about a middle road? Namely NAD83 (NSRS07) - epoch date. This is
similar to NAD83 (CORS96) - epoch date. This should accommodate the people
that want a specific year on the tag and the fact that several years of
communication on the "NSRS" tag have been put out there.

Thomas Taylor, PLS
Chief: Right of Way Engineering
D4 - Right of Way
(510) 286-5294
--------------------------------------------------------------------------------------------------
I like NAD83(NSRS)

State law wll have to be changed if you take the NAD83 out.

DeLane R. Meier
Surveys & Photogrammetry Manager
ND Department of Transportation
Bismarck, ND 58505-0700
----------------------------------------------------------------------------------------------------
The book I am writing on the global spatial data model (GSDM) is nearing completion. For reasons that will make more sense following publication, my suggestion for the name is NAD83(3D). In reality, with all cards on the table, I believe NAD83(07) is the most expedient name at this time.

Earl F. Burkholder, PS, PE
Global COGO, Inc.
Las Cruces, New Mexico 88003
www.zianet.com/globalcogo/index.html

--------------------------------------------------------------------------------------------------------

Greetings kind people!
 
I prefer (NSRS 2007).  The name very clearly references WHAT is it adjusted to and WHEN; two very important details.
 
Thanks for your input request!
 
Mike
 
 
Michael G. Magyar, LSIT
Sr. Survey Analyst
David Evans & Assoc. Inc.
2141 E. Highland Ave.
Ste. 200
Phoenix, AZ 85016

------------------------------------------------------------------------------------------------------------------

I like the NAD83(2007) designation because it is consistent with the older designations and also it designates the year of the adjustment.
 
Thanks,
 

Darryl E. Magnuson,

GPS Specialist

ENGINEERING, INC.

1300 North Transtech Way

Billings, MT 59102

Phone 406/656-5255

Direct 406/869-3335

Mobile 406/670-4762

Fax 406/656-0967

dmagnuson@enginc.com
 -----------------------------------------------------------------------------------------------------------------
Since our state requires NAD83 and the resulting horaw that would occur should we have to request an amendment to the statutes I feel
that we should keep NAD83 and add a parenthetical epoch to define it as the latest adjustment.
 
 
C. Randall Dixon, PLS
Vice President Survey
Krebs, LaSalle, LeMieux Consultants, Inc
3013 27th Street
Metairie, LA 70002
(504) 837-9470
rdixon@kllconsultants.com
-----------------------------------------------------------------------------------------------------------------------
I think that NAD83 with a datum year: NAD83 (2007) would be appropriate
for a readjustment name. This will not be the last readjustment. It is
easier to decipher what it means if the year is added. I can get a
question from 1927 datum and know right away why they are not fitting
1983 datum, by the distance they missed the position. I am not saying
that there will be that large of a difference but knowing the year would
help when holding positions fixed in a GPS Project.



Dick D. Woods
Field Chief
South Carolina Geodetic Survey
5 Geology Road
Columbia, SC 29212

Phone 803-896-7706
Fax: 803-896-7695

Email: dickw@scgs.state.sc.us
SCGS Webpage: www.scgs.state.sc.us
-------------------------------------------------------------------------------------  

NAD83(007)

In agreement with the legal reasons as pertaining to varios states

--
Robert A. Hill, PLS
985.807.6454 (cell)

---------------------------------------------------------------------------------------------------------------------

Hi,

  As a regular user of NGS data, control points and associated data and also having to address and explain the details and differences of the various horizontal and vertical datum available to land surveyors in the Mid-Atlantic, it is my advice that NGS names / designates the new adjustment “NAD’83 / 2006” if that is the year the final adjustment takes place.  Lets be realistic, that is what all land surveyors are going to call it anyway, regardless of what is officially decided. 

 

  Thank you for keeping up the good work. 

 

 

Christopher Chiusano

GPS Sales & Service, Inc.

717-633-7209 (Office)

717-818-3010 (mobile)

888-290-4994 (Fax)

cchiusano@suscom.net

 

 

page 1