[PROJ] NOAA VDatum Tidal Grids and PROJ CDN

[Javier Jimenez Shaw]

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 ;)

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?

I am curious which data is that, that takes 12GB. Can we see it somewhere?

Cheers,
Javier
.___ ._ ..._ .. . ._.  .___ .. __ . _. . __..  ... .... ._ .__
Entre dos pensamientos racionales
hay infinitos pensamientos irracionales.



On Wed, 16 Dec 2020 at 15:53, Howard Butler <howard at hobu.co> wrote:

>
>
> > On Dec 16, 2020, at 8:44 AM, Greg Troxel <gdt at lexort.com> wrote:
> >
> >
> > Howard Butler <howard at hobu.co> writes:
> >
> >> IMO, NOAA seeking to put 12gb of specialized shift files into the CDN
> >> is *exactly* what we were hoping to have happen with the CDN
> >> project. They're simply too big to deliver via normal package, but the
> >> convenience the CDN can provide for users of these grids is
> >> substantial. I hope NOAA can close the loop with EPSG and participate
> >> in the OGC standardization effort that is ongoing with respect to
> >> deformation grids and their format as well.
> >
> > Thanks for explaining.  I really meant simply that I did not understand
> > and was thus being careful not to opine if this was ok or not.
>
> 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.
>
> 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.
>
> Howard
>
> _______________________________________________
> PROJ mailing list
> PROJ at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/proj
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/proj/attachments/20201216/06d2d581/attachment.html>