[Proj] EPSG Dataset ver 9.0 released on 15th December 2016

Kristian Evers kreve at sdfe.dk
Tue Dec 20 14:18:28 EST 2016


Don't take that too seriously... It was just my tongue in cheek way of 
referring to Howards proposal. The EPSG database is a fantastic 
starting point and would for the most part cover everyone's needs.

However, I do think that it is a good idea to think in broader terms 
than the EPSG DB when designing a new system.  Something compatible
with the EPSG DB that can also be extended to suit CRS needs not 
covered by the EPSG DB.


> -----Oprindelig meddelelse-----
> Fra: proj-bounces at lists.maptools.org [mailto:proj-
> bounces at lists.maptools.org] På vegne af Martin Desruisseaux
> Sendt: 20. december 2016 16:46
> Til: proj at lists.maptools.org
> Emne: Re: [Proj] EPSG Dataset ver 9.0 released on 15th December 2016
> Le 20/12/2016 à 18:50, Kristian Evers a écrit :
> > +1 on creating a Grand Unified Geodetic Database. That would be a hell
> > of a lot better than what we have now
> >
> I'm not sure what would be the intend of a Grand Unified Geodetic
> Database... But I would not recommend creating a new source of CRS
> definitions. The EPSG database is quite good in my opinion. The problem
> is not EPSG itself, but rather how some software use it. The Proj.4 CSV
> files are oversimplification. Giving to Proj.4 a more complete access to
> EPSG data, with SQLite as proposed by Howard or with whatever storage
> engine achieves the same goal, would be a more effective step I think.
> Of course it does not mean to not support other authorities in addition
> of EPSG, but I would see that as a secondary goal compared to improving
> EPSG support.
>     Martin
> _______________________________________________
> Proj mailing list
> Proj at lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/proj

More information about the Proj mailing list