Hi Rich
regarding the region setting, to adjust the resolution to 3m, use a "-a"
flag ('g.region vect=analytical_area res=3 -pa')
also try to set the region, than re-run any previous steps (like re-import
the raster), to be sure that any operation is being run with the proper
region settings.
C
On Wed, Jul 24, 2019 at 11:44 AM Rich Shepard <rshep...@appl-ecosys.com>
wrote:
> On Wed, 24 Jul 2019, Carlos Henrique Grohmann de Carvalho wrote:
>
> > This might sound silly but have you checked your region? Perhaps the
> > region is not on the same place of your raster? Didi you tried 'zoom to
> > layer' or 'zoom to region'?
>
> Carlos
>
> Not a silly question at all. I tried 'zoom to layer' with no results.
>
> However, there is a mask for the vector map, 'analytical_area', which is
> much smaller the area covered by the DEM. The region is also set to the
> analytical_area map and this might be the issue. Changing the region to the
> raster DEM does not allow the map to display.
>
> While waiting for a solution to the display issue I tried running r.flow on
> the DEM and aspact maps. Grass refused because of a region resolution
> discrepancy between the analytical_area and DEM maps:
>
> DEM resolution: 3 3
> analytical_area resolution: 2.99763360 3.00134608
>
> 'g.region vect=analytical_area res=3 -p' did not change the floating point
> values to integer 3s.
>
> Thanks,
>
> Rich
> _______________________________________________
> grass-user mailing list
> grass-user@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-user
--
Prof. Carlos Henrique Grohmann
Institute of Energy and Environment - Univ. of São Paulo, Brazil
- Digital Terrain Analysis | GIS | Remote Sensing -
http://carlosgrohmann.com
http://orcid.org/0000-0001-5073-5572
________________
Can’t stop the signal.
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user
