Re: Seeking clarification on PROJ support for temporal transformations
Nyall Dawson <[email protected]>
| Newsgroups | gmane.comp.gis.proj-4.devel |
|---|---|
| Message-ID | <CAB28AsiCf11i_y19jMoQE6z1NTDYtkG4Yd8m++bmcV_KtSamHA@mail.gmail.com> |
On Wed, 28 Aug 2019 at 01:26, Even Rouault <[email protected]> wrote: > > > But, if I understand correctly, WKT2:2018 would be the ultimate answer > > to this, in that it would allow us to specify the epoch of a dataset > > as an integral part of the data's CRS definition (which it is). > > Not sure to understand your "what it is", but pedantically, the epoch of the > dataset is not part of the CRS definition. Anyway... Well -- I think it IS a fundamental part of the definition, of equal importance to other parameters such as false easting/northing. Without the epoch information the coordinate data becomes meaningless, and it's required in order to accurately position them. While it would theoretically be possible to store this information somewhere else in a dataset's metadata, it's such an integral part of the CRS that shoving it right into the CRS definition is the right way forward... Nyall > > -- > Spatialys - Geospatial professional services > http://www.spatialys.com _______________________________________________ PROJ mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/proj