As far as my understanding goes, direct import in GRASS does not work because these global netCDF file include *data points* very near or sometimes at the 90° paralells or the 180° meridian. In GRASS this would result in *grid cells* spanning over these lines, which naturally is not allowed. However this can be fixed in two lines with a netcdf tool like cdo.

cdo sellonlatbox,-179.9,179.9,-89.9,89.9 file.nc file.crop.nc
r.in.gdal input=file.crop.nc

This does practically the same like the scripts I wrote, rendering them useless unless you don’t want to install cdo.

This said, thanks for the link!

Linux-New-Line (LF):
> select replace(field_containing_new_line, x’0A’, ‘ // ‘) from table_containing_field

Windows-New-Line (CR-LF) should be:
> select replace(field_containing_new_line, x’0D0A’, ‘ // ‘) from table_containing_field

Where ” // ” is the replacement-string for the new line.

Also try this script. PDF straight from Gimp
http://registry.gimp.org/node/25677

“It was written for GRASS 6.4 and because of changes in the syntax of some of the functions used by the script, it won’t work in GRASS 7.0.”

but then

“It doesn’t run on GRASS 6.4 unfortunately, although it should be fairly easy to make it so.”

2. The first three commands may behave differently depending on Grass-GIS version. In Grass-GIS 6.4, to achieve the desired outcome – a table containing all boundary categories with left-right information, the following revision was required:
v.category mymap output=mymap2 type=boundary option=add cat=1 step=1
v.db.droptable mymap2 -f
v.db.addtable mymap2
v.db.addcol mymap2 columns=”lleft int, lright int”
v.to.db mymap2 option=sides columns=lleft,lright

But if you need: You can run any GRASS function from R. You need to start R from within GRASS to do that. Having done that, you can use a system call (system(“your grass function call”)) or the execGRASS() function from the spgrass6 package to run GRASS commands. From there is is simple to put those system calls or execGRASS() calls in a loop.