[GRASS5] nnbathy [was: Re: [bug #4248] (grass) r.surf.contour: Treats 0 as NULL and other archaic problems]

Maciek Sieczka werchowyna at epf.pl
Thu Apr 6 16:03:52 EDT 2006


Hi,

I think I'll separate the nnbathy topic from the bug #4248 thread.

On Thu, 6 Apr 2006 13:42:20 +1200
Hamish <hamish_nospam at yahoo.com> wrote:

> Maciek Sieczka wrote:

> > ---
> > 
> > nn
> > Natural Neighbours interpolation library
> > Version 1.57
> > 
> > C library functions and two utilities for Natural Neighbours
> > interpolation.
> > 
> > Copyright 2000-2005 CSIRO Marine Research
> > GPO 1538 Hobart
> > TAS 7001
> > Australia
> > Please send comments and bugs to Pavel.Sakov at csiro.au
> > 
> > There is no warranty whatsoever.  Use at your own risk.
> > 
> > This code may be freely redistributed under the condition that the
> > copyright notices are not removed. You may distribute modified
> > versions of this code UNDER THE CONDITION THAT THIS CODE AND ANY
> > MODIFICATIONS MADE TO IT IN THE SAME FILE REMAIN UNDER COPYRIGHT OF
> > CSIRO, BOTH SOURCE AND OBJECT CODE ARE MADE FREELY AVAILABLE WITHOUT
> > CHARGE, AND CLEAR NOTICE IS GIVEN OF THE MODIFICATIONS.
> > 
> > ---
> 
> "BOTH SOURCE AND OBJECT CODE ARE MADE FREELY AVAILABLE WITHOUT CHARGE"
> 
> I don't know if that is GPL compatible; you can sell GPL binaries, you
> just have to give your customer the source code if they want it (and
> if the customer wants they can do what they want with it, e.g.
> publish that source on the net for everyone else).
> 
> Also I don't like the fact that any changes I make to the code become
> "property" of CSRIO, even if it is easy enough to keep nn as a
> function in separate file.
> 
> 
> > But the license name is not mentioned if this matters. I will ask
> > author right away.

Here's what Pavel Sakov, the nnbathy author, says:

# Hi Maciek,
# 
# There is no file LICENSE in the nn package; the conditions of use are
# spelled out in README. I think that they are not restrictive at all.
# Basically, I am happy for it to be used anywere as long as the
# copyright is preserved and modifications are made public.
# 
# FYI, quite a few times people who would like to use nn could not do
# so because of the more restrictive license of triangle (the package
# by Jonathan Shewchuk used in nn for underlying triangulation). My
# understanding is that one is allowed to use it freely in a
# non-commercial software.
# 
# One possible way around is to use qhull instead of triangle, which is
# what has been done by plplot team. (It is also a good idea to contact
# Jonathan Shewchuk before you proceed.)
# 
# Good luck,
# Pavel

> Maybe he is happy with a GPL or dual-GPL license agreement with GRASS.

I'll better forward to him.

Pavel,

I hope you don't mind :). Could you please answer Hamish?

Hamish,

Regarding the triangle software which nnbathy uses, it is here:
http://www.cs.cmu.edu/~quake/triangle.html

As to it's license, the triangle README says:

--- triangle README ---

These programs may be freely redistributed under the condition that the
copyright notices (including the copy of this notice in the code
comments and the copyright notice printed when the `-h' switch is
selected) are not removed, and no compensation is received.  Private,
research, and institutional use is free.  You may distribute modified
versions of this code UNDER THE CONDITION THAT THIS CODE AND ANY
MODIFICATIONS MADE TO IT IN THE SAME FILE REMAIN UNDER COPYRIGHT OF THE
ORIGINAL AUTHOR, BOTH SOURCE AND OBJECT CODE ARE MADE FREELY AVAILABLE
WITHOUT CHARGE, AND CLEAR NOTICE IS GIVEN OF THE MODIFICATIONS.
Distribution of this code as part of a commercial system is permissible
ONLY BY DIRECT ARRANGEMENT WITH THE AUTHOR.  (If you are not directly
supplying this code to a customer, and you are instead telling them how
they can obtain it for free, then you are not required to make any
arrangement with me.)

--- triangle README ---

Maciek

--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/




More information about the grass-dev mailing list