Ciao all, If this is yet another copy and paste with minor modifications of a plugin we already have, I am against committing as it is. I would like to see a patch to read this georeferncing as part of the currente geotiff structure. If this code is already doing so, even better just create a jira report with the patch and we'll consider applying it (probably after minor modifications).
Summarising, what I think we should have is: 1> make this contribution work against what we currently have in geotiff, if you need help, just ask 2> create a jira report with the patch Personal observation. As far as I remember we don't hand commit rights to anyone who asks right? We should go through some Q&A cycle and that usually involves patches and the like (especially if we are talking about changes to the what we already have). Ciao, Simone. ------------------------------------------------------- Ing. Simone Giannecchini GeoSolutions S.A.S. Founder - Software Engineer Via Carignoni 51 55041 Camaiore (LU) Italy phone: +39 0584983027 fax: +39 0584983027 mob: +39 333 8128928 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://simboss.blogspot.com/ http://www.linkedin.com/in/simonegiannecchini ------------------------------------------------------- On Thu, Dec 31, 2009 at 11:27 AM, Andrea Aime <[email protected]> wrote: > James Nicolson ha scritto: >> Hello everyone, >> >> I've created a plugin that can read mapinfo tab files that >> "georeference" tif files. At the moment the only projection >> parameters/reference-system it can read are those used by the British >> Ordnance survery (see OSGB36, or EPSG:27700). I plan to extend this to >> other projection/reference-systems. > > Sounds interesting. It's the first time I head about this combination > (tab + tiff). Wondering, is it a full rewrite or does it share any > code with the existing TIFF plugins? > >> I'd like to commit what I have now, if the team will grant me svn access? > > Sure, why not. There are a few formalities to go through before we can > grant you commit access though. > > Did you read the developer guide? > http://docs.codehaus.org/display/GEOT/Home > > Also, do you have any trouble signing the OSGEO contributor agreement? > http://docs.codehaus.org/display/GEOT/1+Contributors > > As far as I remember one has to sign it and send it to OSGEO before > getting commit access. > > Cheers > Andrea > > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
