that worked - yesterday I didn’t make it past the downloads page and so didn’t catch on to the new homebrew pages - may need to add a link on the downloads page.
Thanks for the quick response… Unfortunately that did not cure the problem. You say you are using homebrew - that was my first choice, but I don’t see GRASS in their package list - am I missing something?
A few days ago I upgraded the operating system on my MacBook Pro from 10.11 to 10.13 (High Sierra). Most everything seems to still be working - except GRASS and QGIS. I have been running Barton’s binaries and Kyngs’s frameworks for a number of years without any major problems. I have 3 GRASS versions installed - 6.4.5, 7.3 (py2), and 7.3 (py3). 6.4 gives the most succinct error messages on startup and it’s possible to continue on the command line (no gui):
dyld: Library not loaded: /Applications/GRASS/GRASS-6.4.app/Contents/MacOS/lib/libgrass_gis.6.4.5svn.dylib
Referenced from: /Applications/GRASS-6.4.app/Contents/MacOS/bin/g.gisenv
Reason: image not found
The library in question is still where it’s always been.
7.3 is more verbose, but basically says the same thing:
Starting GRASS GIS…
dyld: Library not loaded: /Applications/GRASS-7.3.app/Contents/MacOS/lib/libgrass_gis.7.3.svn.dylib
Referenced from: /Applications/GRASS-7.3_py3.app/Contents/MacOS/bin/g.gisenv
Reason: image not found
Traceback (most recent call last):
File “/Applications/GRASS-7.3_py3.app/Contents/MacOS/gui/wxpython/gis_set.py”, line 31, in
from core import globalvar
…
grass.exceptions.CalledModuleError: Module run None [‘g.gisenv’, ‘-n’] ended with error
Process ended with non-zero return code -6. See errors in the (error) output.
ERROR: Error in GUI startup. See messages above (if any) and if necessary, please report this error to the GRASS developers.
On systems with package manager, make sure you have the right GUI package, probably named grass-gui, installed.
To run GRASS GIS in text mode use the -text flag.
Exiting…
logout
I tried a fresh installation of 7.3 using macports (grass7) and strangely, had a failure where wxWidgets could not be found:
Macports attempted to fetch wxWidgets from all its sources. But the currently installed (and considered up to date) version is wxWidgets-3.0.3 - strange.
So there does appear to be something unusual going on with wxpython and OS X 10.13
The bad news may be that there is currently no source of a binary version of GRASS for anyone with a new Mac or upgrading their OS. I did get the Macports version of QGIS to install and run - but I need my GRASS to run !
Happy to pursue this further if anyone has any ideas to try …
First problems: lots of warnings like
WARNING: Degenerate island (1 vertices)
WARNING: Feature (cat
): degenerated polygon (1 vertices)
These are invalid geometries in the input
The real cleaning happens only if the snap option is set to > 0.
From the WDPA manual:
“There are many overlapping protected areas in the WDPA. These can be
overlapping areas with
different IUCN categories or the overlap of national protected areas with
designations under
regional or international conventions and agreements.”
Thus I would not regard all overlapping areas as errors. I used a spatial
subset for testing:
v.in.ogr spatial=5.467,43.842,14.3,50.558
that’s the Alps and a bit around.
v.in.ogr suggests a snapping value in the range 1e-5, 1e-13. I started
with
1e-9 and got rid of the warnings like
WARNING: Unable to calculate area centroid
but some incorrect boundaries remained in the output. With snap=1e-8,
these
incorrect boundaries disappeared.
The output contains lots of small areas. According to GIS_AREA in the
attribute table, the smallest areas in the input are larger than 100
square
meters, so I cleaned with v.clean tool=rmarea thresh=100, getting rid of
60% of all areas in the output.
In earlier years, the WDPA was separated into different shapefiles: one
for
marine areas, one for IUCN I-VI, one for all other areas. Now everything
is
in one shapefile / GDB. When importing these data, a spatial and an
attribute filter should be set for v.in.ogr.
thanks for also testing this data set. I’ll add some notes in the wiki about
importing these datasets.
Maybe we should revise the messages provided by v.in.ogr and v.import.
Overlapping polygons are not a problem if polygons are indeed overlapping, as in these and other datasets. The message in v.in.ogr needs to be rephrased accordingly and tests for real topological errors (incorrect boundaries, incorrect centroids) need to be added.
IMHO this is worth a new enhancement ticket, but it should also be discussed in the user ml to get feedback about how to improve v.import and v.in.ogr.
Another problem is that these and other vector datasets provide polygons in one layer that should be (have previously been) provided in separate layers, e.g. different shapefiles. Users need to read the documentation of these datasets (not of GRASS GIS) and then decide what features should be imported.
I’m on Sierra and GRASS from Homebrew worked well for me (tap osgeo to access it). But I recently removed homebrew to switch to MacPorts. GRASS did not work for me from MacPorts. I don’t recall if it was the same wxwidgets error you report above. I now run GRASS and QGIS from fink, co-installed with MacPorts which I use for most of the rest of my *nix tools. The two do play fine together - no problems so far. I needed macports to get the good version of the emacs-mac package.
that worked - yesterday I didn’t make it past the downloads page and so didn’t catch on to the new homebrew pages - may need to add a link on the downloads page.
Thanks for the quick response… Unfortunately that did not cure the problem. You say you are using homebrew - that was my first choice, but I don’t see GRASS in their package list - am I missing something?
A few days ago I upgraded the operating system on my MacBook Pro from 10.11 to 10.13 (High Sierra). Most everything seems to still be working - except GRASS and QGIS. I have been running Barton’s binaries and Kyngs’s frameworks for a number of years without any major problems. I have 3 GRASS versions installed - 6.4.5, 7.3 (py2), and 7.3 (py3). 6.4 gives the most succinct error messages on startup and it’s possible to continue on the command line (no gui):
dyld: Library not loaded: /Applications/GRASS/GRASS-6.4.app/Contents/MacOS/lib/libgrass_gis.6.4.5svn.dylib
Referenced from: /Applications/GRASS-6.4.app/Contents/MacOS/bin/g.gisenv
Reason: image not found
The library in question is still where it’s always been.
7.3 is more verbose, but basically says the same thing:
Starting GRASS GIS…
dyld: Library not loaded: /Applications/GRASS-7.3.app/Contents/MacOS/lib/libgrass_gis.7.3.svn.dylib
Referenced from: /Applications/GRASS-7.3_py3.app/Contents/MacOS/bin/g.gisenv
Reason: image not found
Traceback (most recent call last):
File “/Applications/GRASS-7.3_py3.app/Contents/MacOS/gui/wxpython/gis_set.py”, line 31, in
from core import globalvar
…
grass.exceptions.CalledModuleError: Module run None [‘g.gisenv’, ‘-n’] ended with error
Process ended with non-zero return code -6. See errors in the (error) output.
ERROR: Error in GUI startup. See messages above (if any) and if necessary, please report this error to the GRASS developers.
On systems with package manager, make sure you have the right GUI package, probably named grass-gui, installed.
To run GRASS GIS in text mode use the -text flag.
Exiting…
logout
I tried a fresh installation of 7.3 using macports (grass7) and strangely, had a failure where wxWidgets could not be found:
Macports attempted to fetch wxWidgets from all its sources. But the currently installed (and considered up to date) version is wxWidgets-3.0.3 - strange.
So there does appear to be something unusual going on with wxpython and OS X 10.13
The bad news may be that there is currently no source of a binary version of GRASS for anyone with a new Mac or upgrading their OS. I did get the Macports version of QGIS to install and run - but I need my GRASS to run !
Happy to pursue this further if anyone has any ideas to try …