Feel free if I'm wrong but if you're going just to use H2GIS (without 
modifying it), your application does not need to be a GPL licensed. 

The aim of the GPL license for H2GIS was to ensure that code was 
contributed back to the project and help us to build a better extension for 
the community. 

Erwan


Le jeudi 5 février 2015 12:28:22 UTC+1, Sergi Vladykin a écrit :
>
> Erwan,
>
> I can't release software under Apache 2.0 if it contains GPL3 component.
> In this sense they are incompatible and my point is still the same. 
>
> Sergi
>
> 2015-02-05 13:45 GMT+03:00 bocher <erwan....@gmail.com <javascript:>>:
>
>>
>> Just a note : PostGIS the most famous spatial extension is distributed 
>> under the GNU General Public License.
>>
>> Erwan
>>
>> Le jeudi 5 février 2015 11:36:46 UTC+1, bocher a écrit :
>>
>>> Dear Sergi,
>>>
>>> Apache 2.0 is compatible with GPL 3...
>>>
>>> Erwan
>>>
>>> Le mercredi 4 février 2015 23:41:10 UTC+1, Sergi Vladykin a écrit :
>>>>
>>>> My 2 cents:
>>>>
>>>> I'm working on open source Apache licensed software and H2GIS with GPL3 
>>>> is incompatible here as well ;)
>>>> So I'll be happy if alternative GIS extension for H2 with less 
>>>> restrictive license will appear.
>>>>
>>>> Sergi
>>>>
>>>>
>>>>
>>>> On Wednesday, February 4, 2015 at 8:14:10 PM UTC+3, bocher wrote:
>>>>>
>>>>> Hi Steve,
>>>>>
>>>>> Le mercredi 4 février 2015 17:32:56 UTC+1, Steve a écrit :
>>>>>>
>>>>>> Hi Erwan,
>>>>>> there are two issues why I can't use H2GIS.
>>>>>>  
>>>>>> *Issue 1: *
>>>>>> the license - GPL 3 is not an option for us
>>>>>>
>>>>>
>>>>> Oh. Sorry maybe you are working on a proprietary software ;-). In this 
>>>>> case, you are right, H2GIS is not suitable for you.
>>>>>
>>>>>>
>>>>>> *Issue 2: *
>>>>>> We are using a binary format which is different to WKB and we don't 
>>>>>> want to make huge workarounds, which allows us to convert our binary 
>>>>>> format 
>>>>>> to a WKB because that's an unnecessary overhead for us which brings us 
>>>>>> no 
>>>>>> benefit.
>>>>>>
>>>>>
>>>>> I am a bit curious. Is your format compliant with a standard or a 
>>>>> specification ? 
>>>>>
>>>>>>
>>>>>> In addition our binary format supports more geometry types which are 
>>>>>> necessary for our application.
>>>>>>
>>>>>
>>>>> More than the ISO 19107 geometry model ?
>>>>>
>>>>> Erwan.
>>>>>
>>>>>
>>>>> -- 
>>>>> OrbisGIS and H2GIS leader
>>>>> Co-chair of the OGC Symbology Encoding  SWG
>>>>> CNRS FR 2488
>>>>> Institut de recherche en sciences et techniques de la ville
>>>>> École Centrale de Nantes
>>>>> BP 92101
>>>>> 1 rue de la Noë, 44321 NANTES Cedex 3
>>>>> France
>>>>> Tél : 02 40 37 68 67
>>>>> http://www.irstv.fr/
>>>>>
>>>>>  
>>>>>
>>>>>>
>>>>>>
>>>>>> Am Mittwoch, 4. Februar 2015 17:09:44 UTC+1 schrieb bocher:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Dear Steve,
>>>>>>>
>>>>>>> Offer interfaces instead of direct JTS object is a good option. As 
>>>>>>> Nicolas points out, it will be very interesting to extend the 
>>>>>>> geometry model to support OGC Simple Feature Specification for SQL. 
>>>>>>> This idea is in our pipe. We have identified the current constraints to 
>>>>>>> do 
>>>>>>> that and you are welcome to exchange with H2GIS team and H2 guys.
>>>>>>>
>>>>>>> Could you explain what is not relevant to you with H2GIS , because 
>>>>>>> we support all SFS operators, predicates and we have advanced spatial 
>>>>>>> capabilities ?
>>>>>>>
>>>>>>>
>>>>>>> Erwan
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> OrbisGIS and H2GIS leader
>>>>>>> Co-chair of the OGC Symbology Encoding  SWG
>>>>>>> CNRS FR 2488
>>>>>>> Institut de recherche en sciences et techniques de la ville
>>>>>>> École Centrale de Nantes
>>>>>>> BP 92101
>>>>>>> 1 rue de la Noë, 44321 NANTES Cedex 3
>>>>>>> France
>>>>>>> Tél : 02 40 37 68 67
>>>>>>> http://www.irstv.fr/
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Le mercredi 4 février 2015 15:54:38 UTC+1, Nicolas Fortin (OrbisGIS) 
>>>>>>> a écrit :
>>>>>>>>
>>>>>>>> You can't cast a wrapper to a wrapped object, this is why Java 
>>>>>>>> define the interface Wrapper.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>    - -> I understand your intention behind that... currently I do 
>>>>>>>>>    something like that in H2GIS's SpatialResultSetImpl
>>>>>>>>>    
>>>>>>>>>
>>>>>>>> Default implementation means without the presence of H2 jar and JTS 
>>>>>>>> jar. Then at least one implementation of the new Api should be 
>>>>>>>> provided by 
>>>>>>>> h2. You can't ask a user of the database to develop a third party 
>>>>>>>> library 
>>>>>>>> for a feature that are already in h2.
>>>>>>>>
>>>>>>>>>
>>>>>>>>>    - Default Implementation:
>>>>>>>>>    A default implementation itself makes sense because H2 should 
>>>>>>>>>    be able to test their spatial index. Therefore I would suggest to 
>>>>>>>>> implement 
>>>>>>>>>    a H2Envelope, H2Geometry, H2GeometryFactory or we can call it 
>>>>>>>>> JTSEnvelope 
>>>>>>>>>    etc... which uses the JTS framework.
>>>>>>>>>    The default implementation can be provided by a different jar 
>>>>>>>>>    or by H2GIS.
>>>>>>>>>
>>>>>>>>> ​
>>>>>>>>>>
>>>>>>>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "H2 Database" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to h2-database...@googlegroups.com <javascript:>.
>> To post to this group, send email to h2-da...@googlegroups.com 
>> <javascript:>.
>> Visit this group at http://groups.google.com/group/h2-database.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Reply via email to