Tag Info

New answers tagged


Step 1 Make bit rasters for each of the unique classes. This can be a 1-band rasters for each class, or a single raster with a band for each class (e.g. GeoTIFF). If using GTiff, you can use the creation option NBITS=1 to conserve space. You may also want to consider twobit rasters to store three-valued logic where the third (e.g. 2) is NODATA, which would ...


Raster data is only as sharp as the grid size that you are using. To try and represent something like a Road or River as a Raster would be be faulty as is it will give the raster value to the entire grid where as the entire grid may not actually be that value (Say you are using 10m raster grids, and 51% of the grid is a type of soil, that will cause the ...


According to the docs thinning is for line features. Remember to select "area" as the feature type in r.to.vect.


It seems that you final goal is to total raster values for each vector polygon. It's worth pointing out that the GRASS module v.rast.stats does just that.


I think gdal_polygonize might help you. It will convert a raster to vector format (GML, shapefile, etc). By default it connects the cell that have same values, but from your description, it should not be a problem. This text comes from the official site: This utility creates vector polygons for all connected regions of pixels in the raster sharing a ...

Top 50 recent answers are included