Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-25 Thread Paul Kelly
On Thu, 21 Aug 2008, Paul Kelly wrote: On Thu, 21 Aug 2008, Glynn Clements wrote: Paul Kelly wrote: AFAICT, the only core GDAL dependencies are the OSR stuff in lib/proj and g.proj, and the vector library's support for v.external. In which case, it really ought to be possible to get a

Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-25 Thread Glynn Clements
Paul Kelly wrote: Also, is there any fundamental obstacle to being able to set the projection information using PROJ parameters without going via OSR? Been thinking about this a bit more and a more fundamental problem than the ellipsoid and datum names is the lack of validation of the

Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-21 Thread Glynn Clements
Paul Kelly wrote: AFAICT, the only core GDAL dependencies are the OSR stuff in lib/proj and g.proj, and the vector library's support for v.external. In which case, it really ought to be possible to get a usable version of GRASS with no GDAL dependency in any of the libraries or core

Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-21 Thread Paul Kelly
On Thu, 21 Aug 2008, Glynn Clements wrote: Paul Kelly wrote: AFAICT, the only core GDAL dependencies are the OSR stuff in lib/proj and g.proj, and the vector library's support for v.external. In which case, it really ought to be possible to get a usable version of GRASS with no GDAL

Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-21 Thread Glynn Clements
Markus Neteler wrote: Null support is missing (r.external records any null value reported by GDAL, but G_get_raster_row() etc ignore it; I suspect that it will treat zero as null due to the absence of a null file). Null support has been added. I have now tested (in my local

Re: [GRASS-dev] some questions about future development

2008-08-20 Thread Maciej Sieczka
Glynn Clements pisze: Markus Neteler wrote: BTW, a r.external would be a great addition. Yes, see: http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_5_4/gips/gip-0002.txt Still not implemented... next GSoC project? It's not that much work. I have attached a first draft

Re: [GRASS-dev] some questions about future development

2008-08-20 Thread Glynn Clements
Glynn Clements wrote: BTW, a r.external would be a great addition. Yes, see: http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_5_4/gips/gip-0002.txt Still not implemented... next GSoC project? It's not that much work. I have attached a first draft patch which

r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-20 Thread Markus Neteler
Glynn, this is excellent! Thanks so much. I have tested it but no success yet: On Wed, Aug 20, 2008 at 1:46 PM, Glynn Clements [EMAIL PROTECTED] wrote: Glynn Clements wrote: BTW, a r.external would be a great addition. It's not that much work. ... Tomorrow, I'll look into creating an

Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-20 Thread Glynn Clements
Markus Neteler wrote: this is excellent! Thanks so much. I have tested it but no success yet: Tomorrow, I'll look into creating an r.external module, adding null support, etc. Okay, done (well, enough to try it out without having to manually hack the files; null support is absent).

Re: [GRASS-dev] some questions about future development

2008-08-20 Thread Glynn Clements
Glynn Clements wrote: Known issues at present: Null support is missing (r.external records any null value reported by GDAL, but G_get_raster_row() etc ignore it; I suspect that it will treat zero as null due to the absence of a null file). Null support has been added. The code which

Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-20 Thread Markus Neteler
On Wed, Aug 20, 2008 at 3:46 PM, Glynn Clements [EMAIL PROTECTED] wrote: Markus Neteler wrote: this is excellent! Thanks so much. I have tested it but no success yet: Tomorrow, I'll look into creating an r.external module, adding null support, etc. Okay, done (well, enough to try it

Re: r.external - was: Re: [GRASS-dev] some questions about future development

2008-08-20 Thread Markus Neteler
On Wed, Aug 20, 2008 at 5:34 PM, Markus Neteler [EMAIL PROTECTED] wrote: On Wed, Aug 20, 2008 at 3:46 PM, Glynn Clements [EMAIL PROTECTED] wrote: Markus Neteler wrote: ... Copied what over? r.external won't work unless the corresponding lib/gis changes have also been incorporated, and lib/gis

Re: [GRASS-dev] some questions about future development

2008-08-19 Thread Hamish
Michael: I haven't calculated the size of the wxPython code base, but when I checked about a year ago, the TclTk code took up over 18,000 lines of code. The many C modules are what makes GRASS 'work' and Martin: Python code: more them 37,000 lines C++ code: almost 30,000 lines

Re: [GRASS-dev] some questions about future development

2008-08-19 Thread Michael Barton
See my suggested enhancements for vector querying (dev mail archives of a couple weeks back and in TRAC). It would make such highlighting much easier. Michael C. Michael Barton, Professor of Anthropology Director of Graduate Studies School of Human Evolution Social

Re: [GRASS-dev] some questions about future development

2008-08-19 Thread Markus Neteler
On Mon, Aug 18, 2008 at 10:30 AM, Paolo Cavallini [EMAIL PROTECTED] wrote: ... BTW, a r.external would be a great addition. Yes, see: http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_5_4/gips/gip-0002.txt Still not implemented... next GSoC project? Markus

Re: [GRASS-dev] some questions about future development

2008-08-19 Thread Glynn Clements
Markus Neteler wrote: BTW, a r.external would be a great addition. Yes, see: http://trac.osgeo.org/grass/browser/grass/branches/releasebranch_5_4/gips/gip-0002.txt Still not implemented... next GSoC project? It's not that much work. I have attached a first draft patch which adds the

[GRASS-dev] some questions about future development

2008-08-18 Thread G. Allegri
Hi to everyone. In the last period I've been working a lot with GRASS for my daily job, and it permitted me to develop a series of wishes for the future... I will share them in the GRASS 7 ideas collection but I would like to ask some questions before: VECTORS 1 - OGR datasources: one important

Re: [GRASS-dev] some questions about future development

2008-08-18 Thread Paolo Cavallini
G. Allegri ha scritto: 1 - OGR datasources: one important GIS functionality in daily work is the possibility to access shapefiles, and other simple feature datas (PostGIS, Oracle Spatial, etc.) directly, without having to import them and/or building the topology. Many times these datas are

Re: [GRASS-dev] some questions about future development

2008-08-18 Thread G. Allegri
v.external? http://grass.itc.it/grass62/manuals/html62_user/v.external.html BTW, a r.external would be a great addition. Hi Paolo, I know v.external, but It's still a bit far from what the user experience is in, let's say, Qgis/uDig/gvSIG/etc. The main restriction is that it's read-only. It

Re: [GRASS-dev] some questions about future development

2008-08-18 Thread Michael Barton
On Aug 18, 2008, at 1:25 AM, [EMAIL PROTECTED] wrote: Date: Mon, 18 Aug 2008 10:25:30 +0200 From: G. Allegri [EMAIL PROTECTED] Subject: [GRASS-dev] some questions about future development To: GRASS developers list grass-dev@lists.osgeo.org Message-ID: [EMAIL PROTECTED] Content-Type

Re: [GRASS-dev] some questions about future development

2008-08-18 Thread Martin Landa
Hi, 2008/8/18 Michael Barton [EMAIL PROTECTED]: 2 - geometry highlighting: when selecting features from the attributes table (wxGUI), it would be nice to make the geometries highlighted in the map window... See next section. in my TODO for next week ;-) Just a note to the development team.

Re: [GRASS-dev] some questions about future development

2008-08-18 Thread Martin Landa
Hi, 2008/8/18 Martin Landa [EMAIL PROTECTED]: [...] C++ code: almost 30,000 lines sorry, I forgot to exclude cpp file generated by swig, then C++ code: about 5,000 lines Time for my towel;-) Martin -- Martin Landa landa.martin gmail.com * http://gama.fsv.cvut.cz/~landa *