No subject

Tue Nov 10 08:34:52 EST 2015

lution must be to include time dependent coordinates systems and epoch tran=
sformation within the software stack, but that is a far reaching change.  I=
 guess it must start in the definition and conversion software.

In the meantime it is possible to use workarounds such as defining custom c=
oordinate systems for specific epochs,  as in the
l approach.


> -----Original Message-----
> From: proj-bounces at [mailto:proj-
> bounces at] On Behalf Of Greg Troxel
> Sent: Tuesday, 8 March 2016 2:59 p.m.
> To: barronian
> Cc: proj at
> Subject: Re: [Proj] Proj4 and Epoch
> barronian <ian at> writes:
> > Is there support for Epoch in Proj4 ?
> > If so could you please give me a pointer as to how to access the
> > functionality?
> That's a really good question.  I've been on this list for a long time an=
d haven't
> seen any.
> proj4 uses EPSG codes.   I think a question to answer first is how EPSG
> codes represent epoch.
> For example (US centric :-), NAD 83 has many incarnations, but arguably t=
> standard one is "NAD83(2011)":
> However this doesn't talk about epoch at all.  Arguably coordinates in EP=
> 6318 are epoch 2010.0, following:
> But, it's not clear to me how to represent a different epoch, or to talk =
> velocities in EPSG or proj4 at all.
> So, I suspect you have to transform to the standard epoch in some frame,
> and then to another frame, and then to the epoch you want.

This message contains information, which may be in confidence and may be su=
bject to legal privilege. If you are not the intended recipient, you must n=
ot peruse, use, disseminate, distribute or copy this message. If you have r=
eceived this message in error, please notify us immediately (Phone 0800 665=
 463 or info at and destroy the original message. LINZ accepts n=
o responsibility for changes to this email, or for any attachments, after i=
ts transmission from LINZ. Thank You.

More information about the Proj mailing list