Re: [GRASS-dev] About the vector changes
Hamish: [...] it would be nice if v.info could work (even partially) for maps without topology built. e.g. massive LIDAR datasets. Try trunk r38644, new -l flag for v.info to open vector map on level 1. Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] About the vector changes
Hamish wrote: Glynn wrote: Vector maps no longer work: $ v.info fields ERROR: Spatial index was written with LFS but this GRASS version does not support LFS. Try to rebuild topology or upgrade GRASS. Hi, I've got nothing to add about that; just while on the subject: it would be nice if v.info could work (even partially) for maps without topology built. e.g. massive LIDAR datasets. It could be useful if more vector modules could support vectors without topology, most importantly all v.surf.* modules. Not a new idea, was mentioned earlier. Markus M ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] About the vector changes
Hamish: Hamish: it would be nice if v.info could work (even partially) for maps without topology built. e.g. massive LIDAR datasets. MMetz: It could be useful if more vector modules could support vectors without topology, most importantly all v.surf.* modules. Not a new idea, was mentioned earlier. AFAIK, they already do. Oops, right. Should v.info calculate bounding box and number of features for level 1? This can take some time because the whole coor file must be read, but I would find it useful to know the extends and number of points (, lines, boundaries, centroids) even for level 1. That helps setting the right region for the v.surf.* modules. Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] About the vector changes
On Fri, Aug 7, 2009 at 10:41 AM, Markus Metz markus.metz.gisw...@googlemail.com wrote: ... Should v.info calculate bounding box and number of features for level 1? This can take some time because the whole coor file must be read, but I would find it useful to know the extends and number of points (, lines, boundaries, centroids) even for level 1. That helps setting the right region for the v.surf.* modules. While I also think that this would be important info to obtain, another option could be to modify v.univar to also work with x, y [,z]. Then the user wouldn't be surprised that it takes time... (v.info is moreover just reading a map header in real time). Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
Re: [GRASS-dev] About the vector changes
Glynn wrote: Vector maps no longer work: $ v.info fields ERROR: Spatial index was written with LFS but this GRASS version does not support LFS. Try to rebuild topology or upgrade GRASS. Hi, I've got nothing to add about that; just while on the subject: it would be nice if v.info could work (even partially) for maps without topology built. e.g. massive LIDAR datasets. thanks, Hamish ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev
