[MetaCRS] [Proj] Common SQLite-based dictionaries
Even Rouault
even.rouault at spatialys.com
Mon Aug 3 14:21:24 PDT 2015
On Monday 03 August 2015 22:46:41 Martin Desruisseaux wrote:
> Le 03/08/15 22:37, Sebastiaan Couwenberg a écrit :
> > I can envision a project that takes the EPSG database and with a
> > collection of SQL scripts (patches) creates the database for proj, gdal
> > & friends. That would be compatible with the compromise when you apply
> > it to data instead of software. The EPSG ToS is just not very explicitly
> > about being allowed to distribute changes.
>
> I think that the intend of EPSG term of use is to make sure that
> "EPSG:something" is understood in the same way by everyone. Applying
> patches with SQL scripts compromise this goal in the same way than
> modifying the data directly, unless we make clear that this is not
> anymore EPSG definitions.
Let's say we distribute a SQLite version of the PostgreSQL scripts unmodified
(or within the allowed modifications). If the *software* that use it return an
"incorrect" definition when querying EPSG:4326 (for example a WKT with AXIS
stripped), that has nothing to do with the data being distributed. It is a
bug/feature in the way the software interprets the data.
And if this database includes an extra proj.4 dedicated table with records
like '4326', '+proj=longlat +datum=WGS84 +no_defs' or '4322', '+proj=longlat
+ellps=WGS72 +towgs84=0,0,4.5,0,0,0.554,0.2263 +no_defs' that doesn't modify
the original dataset.
>
> Martin
>
> _______________________________________________
> MetaCRS mailing list
> MetaCRS at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/metacrs
--
Spatialys - Geospatial professional services
http://www.spatialys.com
More information about the MetaCRS
mailing list