[MetaCRS] [Proj] Common SQLite-based dictionaries

[Norman Barker]

I appreciate that ESPG is an Access database and hence there is a schema
for most of the existing CRS definitions, however it does seem limiting to
other uses. A Key-Value store (such as leveldb) would enable the the
CRS_CODE->VALUE_DEFINITION without a schema. The value can be a GML/XML
doc, JSON whatever the calling application can understand.

I looked to use leveldb with the GDAL couchdb driver but opted for GPKG
since this was already well understood in the code base. However for
something like CRS I can see a schema model being restrictive.

Norman

On Mon, Aug 3, 2015 at 8:00 AM, Martin Desruisseaux <
martin.desruisseaux at geomatys.com> wrote:

> Le 03/08/15 15:32, Sebastiaan Couwenberg a écrit :
> > (...snip...) the ToS
> > is incompatible with the Debian Free Software Guidelines and the Open
> > Source Definition. The ToS discriminates against field of endeavor and
> > limits derived works via parameter modification restrictions.
>
> I'm not sure that those restrictions on modifications are incompatible
> with Open Source Definition. Apache 2 is an Open Source license, despite
> that it has a yet stronger restriction on modification:
>
> http://www.apache.org/foundation/license-faq.html#Name-changes
>
> In short: if you modify an Apache software, you are not allowed to call
> your modified software "Apache" (but you can said "based on Apache").
> The EPSG terms of use seems actually more flexible since it describe the
> changes that you are allowed to do and still keep the "EPSG" codespace.
>
>     Martin
>
> _______________________________________________
> MetaCRS mailing list
> MetaCRS at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/metacrs
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/metacrs/attachments/20150803/6a37e979/attachment.html>