<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
All<br>
<br>
Just a little background about VDatum, it is a transformation tool
developed collaboratively by several offices at NOAA including: the
Center for Operational Oceanographic Products (CO-OPS) that do tidal
datums, tides and currents; the National Geodetic Survey (NGS) that
do the datums, geoids and transformations; and the Office of Coast
Survey (OCS) that make the nautical charts, do bathymetric surveying
and more. <a moz-do-not-send="true"
href="https://vdatum.noaa.gov/">https://vdatum.noaa.gov/</a> NGS
makes sure to include the most recent NGS transformations into both
VDatum and the NGS Coordinate Conversion and Transformation Tool
(NCAT). <a moz-do-not-send="true"
href="https://geodesy.noaa.gov/NCAT/">https://geodesy.noaa.gov/NCAT/</a><br>
<br>
I have seen a couple questions and comments in this thread and I
wanted to respond to them. <br>
<br>
@ Howard - NGS is participating with several scientists including
myself in the OGC meetings for the deformation grids and developing
the GGXF. We still need to work on getting all the NADCON 5 and
probably the VERTCON 3 grids/transformations incorporated into
EPSG. We have also began working to try to provide our grids in
GeoTiff formats (currently xGEOID20 is the first one I believe) as
well as working to get our tools using GeoTiff grids. The long term
plan is to use GGXF once developed and standardized but to work to
implement GeoTiff until that time.<br>
<br>
@ Greg - Our Chief Geodesist has been significantly involved with
the ISO Geodetic Registry and I believe he has included all of the
datum and transformation parameters and grids from NGS into the
registry. While EPSG is certainly the de facto standard I believe
the desire is to have this registry be the official location for
parameters sometime in the future.<br>
<br>
@ Javier - You are correct that NGS is planning to modernize the
NSRS (NAD 83, NAVD 88). The original plan was to update this by the
end of 2022 but with various delays in data collection and more we
officially announced that it will be delayed. <span lang="EN"><a
href="https://geodesy.noaa.gov/datums/newdatums/delayed-release.shtml"><span
style="color:#1155CC">https://geodesy.noaa.gov/datums/newdatums/delayed-release.shtml</span></a><br>
<br>
If interested there are 3 Blueprint Documents that go into great
detail about the upcoming changes. We have been working on
updating all of the documents and those updates should be
available by the end of February as they are currently in review.
We have been collaborating with the Canadians and actually just
had a meeting with them earlier today.<br>
<a moz-do-not-send="true"
href="https://geodesy.noaa.gov/datums/newdatums/policy.shtml">https://geodesy.noaa.gov/datums/newdatums/policy.shtml</a><br>
</span><br>
Please don't hesitate to email me with any questions.<br>
<br>
Cheers<br>
Brian<br>
<br>
<br>
<div class="moz-cite-prefix">On 12/16/2020 9:04 AM, Javier Jimenez
Shaw wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CADRrdKtNs1tPCukxq28HA8Vs3F03E3A5e3q783v18gMUS1enrw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>CDN is a nice place to store big projects. And it is
actually great that they want to use PROJ "format" to publish
it. However, as Even and Greg mentioned, there are other use
cases where you need it locally in your computer/device. If it
is it planned to be in PROJ-data, maybe I should buy a new
hard drive ;)</div>
<div><br>
</div>
<div>If I am not wrong, NOAA (or other institution) is upgrading
the American horizontal and vertical CRSs in 2022. I could
imagine that they will publish the Tidal Grids referred to the
new ones once published. Am I right?</div>
<div><br>
</div>
<div>I am curious which data is that, that takes 12GB. Can we
see it somewhere?<br>
<br>
</div>
<div>Cheers,</div>
<div>Javier<br>
</div>
<div>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">.___ ._ ..._ .. . ._. .___
.. __ . _. . __.. ... .... ._ .__<br>
Entre dos pensamientos racionales <br>
hay infinitos pensamientos irracionales.<br>
<br>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, 16 Dec 2020 at 15:53,
Howard Butler <<a href="mailto:howard@hobu.co"
moz-do-not-send="true">howard@hobu.co</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
> On Dec 16, 2020, at 8:44 AM, Greg Troxel <<a
href="mailto:gdt@lexort.com" target="_blank"
moz-do-not-send="true">gdt@lexort.com</a>> wrote:<br>
> <br>
> <br>
> Howard Butler <<a href="mailto:howard@hobu.co"
target="_blank" moz-do-not-send="true">howard@hobu.co</a>>
writes:<br>
> <br>
>> IMO, NOAA seeking to put 12gb of specialized shift
files into the CDN<br>
>> is *exactly* what we were hoping to have happen with
the CDN<br>
>> project. They're simply too big to deliver via normal
package, but the<br>
>> convenience the CDN can provide for users of these
grids is<br>
>> substantial. I hope NOAA can close the loop with EPSG
and participate<br>
>> in the OGC standardization effort that is ongoing
with respect to<br>
>> deformation grids and their format as well.<br>
> <br>
> Thanks for explaining. I really meant simply that I did
not understand<br>
> and was thus being careful not to opine if this was ok or
not.<br>
<br>
OK for NOAA to do this or ok for the PROJ project to support
it with its CDN? I don't know about the former either, but the
past NOAA public transition path for this kind of data was to
toss it into the ether in their own format and hope for
implementation. I would hope supporting PROJ and modernizing
their grid deliveries with Cloud Optimized GeoTIFF would be
under their purview.<br>
<br>
As for the CDN, we can put a lot of data up there before
anyone is going to complain. The URL is purposefully the
project's instead of an Amazon one to allow us to gracefully
migrate in case AWS decides supporting us is no longer in
their interest. <br>
<br>
Howard<br>
<br>
_______________________________________________<br>
PROJ mailing list<br>
<a href="mailto:PROJ@lists.osgeo.org" target="_blank"
moz-do-not-send="true">PROJ@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/proj"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/proj</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
PROJ mailing list
<a class="moz-txt-link-abbreviated" href="mailto:PROJ@lists.osgeo.org">PROJ@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/proj">https://lists.osgeo.org/mailman/listinfo/proj</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
*************************************
Brian Shaw
Rocky Mountain Regional Advisor (CO, MT, WY)
NOAA's National Geodetic Survey (NGS)
Cell Phone # 240-988-6363</pre>
</body>
</html>