I still have a problem, since my DEMs have a very high resolution. I tried
to run r.basin using a lower resolution of the DEMs, but I do get an error.
any reason why not use the original DEM resolution?
AFAIK as the underlying modules (r.watershed, r.stream.*) are sensitive to
region and resolution settings (please see their manuals regarding this).
resolution resampling may introduce some artefacts which may be some issues
for these modules.
B) Run r.basin using a lower resolution DEM
B1) I changed the resolution of the computational region
I’m running 7.1 svn 67037M (Barton binary) on OS X Yosemite - mostly flawlessly - except r.in.gdal (or ‘import raster data’ as it’s now known).
The import dialog window is not functioning correctly - the ‘options’ section is dead / missing (see below) - Stretching the window doesn’t help.
I can import this file ok with GRASS 6.4 and then it’s available to process in 7.1. 7.0 running on another similar machine does not have this ‘feature’…
On Wed, Apr 13, 2016 at 11:07 AM, Stuart Edwards <sedwards2@cinci.rr.com>
wrote:
Hi -
I'm running 7.1 svn 67037M (Barton binary) on OS X Yosemite - mostly
flawlessly - except r.in.gdal (or 'import raster data' as it's now known).
The import dialog window is not functioning correctly - the 'options'
section is dead / missing (see below) - Stretching the window doesn't help.
I can import this file ok with GRASS 6.4 and then it's available to
process in 7.1. 7.0 running on another similar machine does not have this
'feature'....
Thanks for any assistance.
Stu
I tested compiled GRASS on Yosemite (version 67669) and I don't have that
problem. I am using wxPython 3.0.2.0. Maybe this was already fixed.
I'm trying to work with some vector data that is in the 'WGS_1984_Web_Mercator_Auxiliary_Sphere' projection - an apparently popular web mapping projection. I want to re-project it to a state plane co-ordinate system (ohio-north us survey ft).
The EPSG code for the raw data is (reportedly) 3857, but GRASS gives the following error messages when trying to import to a location set to this projection:
'Projection of following layers do not match with projection of current location' ....... the layers will be re-projected.
This fails and the console shows the following error: ERROR 6: No translation for Mercator Auxiliary Sphere to PROJ.4 format is known.
The data import to an x,y location with an ERROR 6 message, but otherwise seems intact including attributes (just crazy co-ordinates).
Re-projecting to the SPC location fails with: v.proj --overwrite location=OHxy mapset=PERMANENT input=PCR_Local output=ohPCR WARNING: <PROJ INFO> file not found for location <OHxy>
With some minor aggravation my wife's arcgis was able to figure this out - but any suggestions on how to proceed in GRASS would be much appreciated.
I'm trying to work with some vector data that is in the 'WGS_1984_Web_Mercator_Auxiliary_Sphere' projection - an apparently popular web mapping projection. I want to re-project it to a state plane co-ordinate system (ohio-north us survey ft).
The EPSG code for the raw data is (reportedly) 3857, but GRASS gives the following error messages when trying to import to a location set to this projection:
'Projection of following layers do not match with projection of current location' ....... the layers will be re-projected.
This fails and the console shows the following error: ERROR 6: No translation for Mercator Auxiliary Sphere to PROJ.4 format is known.
The data import to an x,y location with an ERROR 6 message, but otherwise seems intact including attributes (just crazy co-ordinates).
Re-projecting to the SPC location fails with: v.proj --overwrite location=OHxy mapset=PERMANENT input=PCR_Local output=ohPCR WARNING: <PROJ INFO> file not found for location <OHxy>
With some minor aggravation my wife's arcgis was able to figure this out - but any suggestions on how to proceed in GRASS would be much appreciated.
This is a very difficult projection system to deal with, to the point that many agencies have banned it.
