That's reassuring, thanks Markus.
Incidentally, since HTML housekeeping is such a boring
chore but so crucial: Do you guys think it would make
sense to have a "man page improvement day", similar to
a code sprint, but with the whole community dedicating
perhaps a day to finding problems in man pages and fixing
them?
I am not just talking about correcting errors, but also
rephrasing things that are hard to understand or elaborating
on aspects that aren't explained verbosely enough.
Ben
----- Original Message -----
On Thu, Jan 13, 2011 at 10:03 PM, Benjamin Ducke
<benjamin.ducke@oxfordarch.co.uk> wrote:
> The HTML manual page for v.surf.bspline
> says:
>
> "A raster output map ("raster=") of more than 2000x2000 (4 mill)
> cells is not allowed. If an output map would exceed this size,
> an error message is generated."
>
> But there is nothing in the source code which suggests such
> a limitation. I tried interpolating a 5000x4000 raster and it
> worked just fine.
>
> Am I missing something or has this limitation fallen?
>
Right, this limitation has been removed, the maximum number of cells
depends now on LFS and the amount of available system memory.
Additionally, one bug has been removed:
"At this time, sparse vector input can only be used with interpolation
from 3D vector z-coordinates"
is no longer true, z values are collected either from 3D points or
from the attribute table.
The manual has been updated correspondingly in all branches.
Markus M
------
Files attached to this email may be in ISO 26300 format (OASIS Open Document Format). If you have difficulty opening them, please visit http://iso26300.info for more information.
On Tuesday, January 18, 2011, Benjamin Ducke wrote:
That's reassuring, thanks Markus.
Incidentally, since HTML housekeeping is such a boring
chore but so crucial: Do you guys think it would make
sense to have a "man page improvement day", similar to
a code sprint, but with the whole community dedicating
perhaps a day to finding problems in man pages and fixing
them?
I am not just talking about correcting errors, but also
rephrasing things that are hard to understand or elaborating
on aspects that aren't explained verbosely enough.
Ben
Excellent idea! I would participate.
Dylan
----- Original Message -----
> On Thu, Jan 13, 2011 at 10:03 PM, Benjamin Ducke
> <benjamin.ducke@oxfordarch.co.uk> wrote:
> > The HTML manual page for v.surf.bspline
> > says:
> >
> > "A raster output map ("raster=") of more than 2000x2000 (4 mill)
> > cells is not allowed. If an output map would exceed this size,
> > an error message is generated."
> >
> > But there is nothing in the source code which suggests such
> > a limitation. I tried interpolating a 5000x4000 raster and it
> > worked just fine.
> >
> > Am I missing something or has this limitation fallen?
> >
> Right, this limitation has been removed, the maximum number of cells
> depends now on LFS and the amount of available system memory.
>
> Additionally, one bug has been removed:
>
> "At this time, sparse vector input can only be used with interpolation
> from 3D vector z-coordinates"
>
> is no longer true, z values are collected either from 3D points or
> from the attribute table.
>
> The manual has been updated correspondingly in all branches.
>
> Markus M
------
Files attached to this email may be in ISO 26300 format (OASIS Open Document
Format). If you have difficulty opening them, please visit
http://iso26300.info for more information.
_______________________________________________
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
--
Dylan Beaudette
Soil Resource Laboratory
http://casoilresource.lawr.ucdavis.edu/
University of California at Davis
530.754.7341
On Wed, Jan 19, 2011 at 12:37 AM, Dylan Beaudette
<debeaudette@ucdavis.edu> wrote:
On Tuesday, January 18, 2011, Benjamin Ducke wrote:
That's reassuring, thanks Markus.
Incidentally, since HTML housekeeping is such a boring
chore but so crucial: Do you guys think it would make
sense to have a "man page improvement day", similar to
a code sprint, but with the whole community dedicating
perhaps a day to finding problems in man pages and fixing
them?
I am not just talking about correcting errors, but also
rephrasing things that are hard to understand or elaborating
on aspects that aren't explained verbosely enough.
Ben
Excellent idea! I would participate.
Me, too.
Also the sphinx'ization (http://trac.osgeo.org/grass/ticket/151) comes to mind.
Markus
On Wed, 2011-01-19 at 08:51 +0100, Markus Neteler wrote:
On Wed, Jan 19, 2011 at 12:37 AM, Dylan Beaudette
<debeaudette@ucdavis.edu> wrote:
> On Tuesday, January 18, 2011, Benjamin Ducke wrote:
>> That's reassuring, thanks Markus.
>> Incidentally, since HTML housekeeping is such a boring
>> chore but so crucial: Do you guys think it would make
>> sense to have a "man page improvement day", similar to
>> a code sprint, but with the whole community dedicating
>> perhaps a day to finding problems in man pages and fixing
>> them?
>>
>> I am not just talking about correcting errors, but also
>> rephrasing things that are hard to understand or elaborating
>> on aspects that aren't explained verbosely enough.
>>
>> Ben
>
> Excellent idea! I would participate.
Me, too.
Also the sphinx'ization (http://trac.osgeo.org/grass/ticket/151) comes to mind.
Me too!
I have created a wiki page
http://grass.osgeo.org/wiki/Man_Pages_Improvement_Sprint
to collect ideas and organise the event.
Edits welcome!
cheers
Anne
--
http://wiki.osgeo.org/wiki/User:Aghisla
On Wed, Jan 19, 2011 at 9:14 AM, Anne Ghisla <a.ghisla@gmail.com> wrote:
On Wed, 2011-01-19 at 08:51 +0100, Markus Neteler wrote:
On Wed, Jan 19, 2011 at 12:37 AM, Dylan Beaudette
<debeaudette@ucdavis.edu> wrote:
> On Tuesday, January 18, 2011, Benjamin Ducke wrote:
>> That's reassuring, thanks Markus.
>> Incidentally, since HTML housekeeping is such a boring
>> chore but so crucial: Do you guys think it would make
>> sense to have a "man page improvement day", similar to
>> a code sprint, but with the whole community dedicating
>> perhaps a day to finding problems in man pages and fixing
>> them?
>>
>> I am not just talking about correcting errors, but also
>> rephrasing things that are hard to understand or elaborating
>> on aspects that aren't explained verbosely enough.
>>
>> Ben
>
> Excellent idea! I would participate.
Me, too.
Also the sphinx'ization (http://trac.osgeo.org/grass/ticket/151) comes to mind.
Me too!
Me too. It seems I started something here by forgetting to remove a
paragraph. I always wanted to update the lidar tools man pages but
never got around to do it...
Markus M