Re: how to put in octave forge?

[Philip Nienhuis]

shash wrote
> My code is written is c++ and is a wrapper for gdal library. It is not m
> code as Mapping package expect it to be. Also it is not matlab compatible
> at the moment. Should I keep it outside octave forge till it is somewhat
> matlab compatible? Please advise.
> 
> 
> My code is available in https://github.com/shashankkhare/octave-gdal

I had a brief look.

shaperead() is already in the mapping package (in the repo), but as an
.m-file - usually slower. OTOH it can read M and Z (3D) .shp files and
supports clipping (limiting shape features to a rectangular rectangle to be
able to keep shape structs to reasonable limits - some shapefiles are
ridiculously big and make for very slow processing when only a a partial map
is required).

The .tiff file stuff looks promising, I think it would be very nice to have
raster data I/O in the mapping package.

Licensing:
I had a brief look at gnu.org but I cannot assess whether the MIT license
you use is GPL compatible. To me it looks a bit like the BSD license.
Would you be willing to publish your code under the GPL? just asking, AFAICS
the MIT license shouldn't be a showstopper but having several licenses in
one package just complicates things. But there's also the BSD license in the
mapping package anyway (for some geodetic functions).


> I would like to create a new mapping package which uses proj 4, gdal and
> mapserver to provide mapping functionality rather than code everything
> again in m.

If possible it had better go in the mapping package. 
The dominant reason is the need to avoid package fragmentation. later on
that usually leads to a lot of time spent on code reshuffling once small
packages are abandoned.  Code has more changes to live on if it is included
in a "bigger" package.

Philip




--
View this message in context: 
http://octave.1599824.n4.nabble.com/how-to-put-in-octave-forge-tp4671382p4671394.html
Sent from the Octave - Maintainers mailing list archive at Nabble.com.