Re: [GRASS-dev] Object-based image classification in GRASS
On Thu, Oct 31, 2013 at 3:03 PM, Luca Delucchi lucadel...@gmail.com wrote: [0] https://github.com/zarch/i.segment.hierarchical Could I suggest you to use the grass-addons repository ;-) Ok, moved (i.segment.hierarchical) to grass-addons (r58137). Pietro ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] [GRASS GIS] #2124: Browser data in Table Attribute Manager, avoid to load all the dataset
#2124: Browser data in Table Attribute Manager, avoid to load all the dataset ---+ Reporter: zarch | Owner: grass-dev@… Type: enhancement| Status: new Priority: trivial| Milestone: 7.0.0 Component: wxGUI | Version: unspecified Keywords: vector attributes |Platform: Unspecified Cpu: Unspecified| ---+ I would like that the Browser data, start loading in the gui only a chunk of the whole dataset, like the first 250 rows, and then automatically loads another chunk of rows when I'm close to the bottom. You can see an example of what I mean if you open the sqlite database using sqliteman [0]. Do you think that would be feasible do the same thing with the wx? [0] http://sqliteman.com/ -- Ticket URL: http://trac.osgeo.org/grass/ticket/2124 GRASS GIS http://grass.osgeo.org ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
[GRASS-dev] use G_find_raster2() instead of G_find_raster()
Hi Martin and others, I saw r58135. If one function is preferred, manual should state and explain it. I also noticed that there is no find...2 function for 3D rasters. If you understand this topic, please share you knowledge in the manual. Thanks, Vaclav https://trac.osgeo.org/grass/changeset/58135 http://grass.osgeo.org/programming7/find__rast_8c.html http://grass.osgeo.org/programming7/find__vect_8c.html http://grass.osgeo.org/programming7/find__rast3d_8c.html ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] use G_find_raster2() instead of G_find_raster()
Hi Vaclav, to my knowledge, it's already explained in the manual. Note: If the user specifies a fully qualified raster map which exists, then G_find_raster() modifies name by removing the @imapset/i. Martin 2013/11/1 Vaclav Petras wenzesl...@gmail.com: Hi Martin and others, I saw r58135. If one function is preferred, manual should state and explain it. I also noticed that there is no find...2 function for 3D rasters. If you understand this topic, please share you knowledge in the manual. Thanks, Vaclav https://trac.osgeo.org/grass/changeset/58135 http://grass.osgeo.org/programming7/find__rast_8c.html http://grass.osgeo.org/programming7/find__vect_8c.html http://grass.osgeo.org/programming7/find__rast3d_8c.html -- Martin Landa landa.martin gmail.com * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] use G_find_raster2() instead of G_find_raster()
On Fri, Nov 1, 2013 at 10:32 AM, Martin Landa landa.mar...@gmail.comwrote: Hi Vaclav, to my knowledge, it's already explained in the manual. Note: If the user specifies a fully qualified raster map which exists, then G_find_raster() modifies name by removing the @imapset/i. Yes, and also The same as G_find_vector() but doesn't remove the @imapset/i qualification from name, if present. But I'm not able to decide on which occasion I want which function. Someday, I can try to call both functions with different map/mapset combinations but reading from manual would be more effective. Martin 2013/11/1 Vaclav Petras wenzesl...@gmail.com: Hi Martin and others, I saw r58135. If one function is preferred, manual should state and explain it. I also noticed that there is no find...2 function for 3D rasters. If you understand this topic, please share you knowledge in the manual. Thanks, Vaclav https://trac.osgeo.org/grass/changeset/58135 http://grass.osgeo.org/programming7/find__rast_8c.html http://grass.osgeo.org/programming7/find__vect_8c.html http://grass.osgeo.org/programming7/find__rast3d_8c.html -- Martin Landa landa.martin gmail.com * http://geo.fsv.cvut.cz/~landa ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] use G_find_raster2() instead of G_find_raster()
Vaclav Petras wrote: But I'm not able to decide on which occasion I want which function. Someday, I can try to call both functions with different map/mapset combinations but reading from manual would be more effective. Please use G_find_raster2() always (similarly for the other G_find_* functions). G_find_raster() exists for backward compatibility only. Having it modify the map name in-place has been the source of countless bugs. Note that the first argument to G_find_raster() is char *, rather than const char *, so if you have a const string you must use G_find_raster2(). Even if the string isn't explicitly declared const, the fact that it may be modified means that if you need to retain the original value, you have to explicitly copy it. -- Glynn Clements gl...@gclements.plus.com ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
