Re: [GRASS-user] [GRASS-dev] ASF - OGC - OSGeo code sprint - Feb 17-19, 2021

[Luca Delucchi]

On Thu, 11 Feb 2021 at 16:28, Anna Petrášová  wrote:
>
> Hi Vero,
>
Hi all,

> we registered for this, we probably won't participate 100% of the time, but 
> hope to see other GRASS devs there.
>

I also registered myself!

> Anna & Vaclav
>

-- 
ciao
Luca

www.lucadelu.org
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.contour

[Maris Nartiss]

Hello Dave,
r.contour should be working just fine. Your posted Warning is
harmless. Please try to run it in a pure GRASS session and not through
QGIS – in case of failure, it will be possible to get a reasonable
error message.

As for upgrading of GRASS – be ware – LiDAR tools depend on libLAS
that has been deprecated and is not shipped in most of recent Linux
distributions. Thus working with LAS files might be impossible at all.
There are planned new LiDAR tools based on PDAL in GRASS 8.

Māris.


2021-02-11 23:38 GMT+02:00, Dave Marshall <43carn...@gmail.com>:
> Hello,
>
> I do a lot of work with UK LIDAR data and one of the most frequently used,
> and useful, GRASS routines for my work is r.contour. I am currently using
> GRASS through QGIS 3.4.12 and the associated version of GRASS is 7.6.1. I
> have made a couple of attempts to upgrade my QGIS version to a more recent
> one but this always results in a different version of GRASS which does not
> allow r.contour to work with the LIDAR files.
>
> QGIS 3.4 opens LIDAR tif files directly using EPSG:27700 as the CRS. Later
> versions of QGIS seem to require, or at least suggest, a transformation to
> an alternative CRS. Whether I use one of these transformations or not, the
> initial error I receive when running r.contour is "WARNING: Datum
>  not recognised by GRASS and no
> parameters found". Other errors follow and finally there is a message to
> say that the routine has failed. I think that all the versions of GRASS
> which have generated this error are 7.8.
>
> I would like to upgrade my version of QGIS to a later version but am stuck
> with 3.4 because of my need for a functioning r.contour. QGIS contains a
> similar contour-drawing option but it does not allow the specification of
> upper and lower height limits and so can take a very long time to run on
> large files.
>
> Any help or advice will be much appreciated,
>
> Dave Marshall
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.futures.demand

[Anna Petrášová]

On Thu, Feb 11, 2021 at 3:14 PM Mitchell Meads 
wrote:

> Hi Anna,
>
> Thank you for the helpful information! I suppose I was somewhat confused
> as to what exactly should all be in the parameters for the
> r.futures.potential submodel. I've made the changes you've suggested above,
> but I'm still getting some type of "Unable to select cursor" error. Below
> is the command output with its errors, if you could help me pin down what
> I'm doing wrong, that would be great! Also on a side note, unfortunately,
> I'm not experienced in R and and somewhat relying on the futures modeling
> in GRASS to complete my task. Thanks again for your help!
>
> (Thu Feb 11 13:11:21 2021)
>
> r.futures.potential --overwrite input=sampling_f_km@PERMANENT
> output=potential_f_km.csv
> columns=devclip_2016,block_rast,county_rast,devpress_0_5_2016,dist_to_evac_km,dist_to_pp_km,dist_toh20_2001_km,dist_toh20_2004_km,dist_toh20_2006,dist_toh20_2008_km,dist_toh20_2011_km,dist_toh20_2013_km,dist_toh20_2016_km,per_forest_2001,per_forest_2004,per_forest_2006,per_forest_2008,per_forest_2011,per_forest_2013,per_forest_2016,urban_change_01_16
> developed_column=devclip_2016 subregions_column=county_rast min_variables=5
> max_variables=10
> Computing model...
> WARNING: fixed-effect model matrix is rank deficient so dropping 2 columns
> / coefficients
> Error in pwrssUpdate(pp, resp, tol = tolPwrss, GQmat = GQmat, compDev =
> compDev,  :
> pwrssUpdate did not converge in (maxit) iterations
> Calls: glmer ...  ->  -> stopifnot -> fn ->
> pwrssUpdate
> In addition: Warning message:
> Some predictor variables are on very different scales: consider rescaling
> Execution halted
> WARNING: fixed-effect model matrix is rank deficient so dropping 2 columns
> / coefficients
> Error in pwrssUpdate(pp, resp, tol = tolPwrss, GQmat = GQmat, compDev =
> compDev,  :
> pwrssUpdate did not converge in (maxit) iterations
> Calls: glmer ...  ->  -> stopifnot -> fn ->
> pwrssUpdate
> In addition: Warning message:
> Some predictor variables are on very different scales: consider rescaling
> Execution halted
> ERROR: Running R script failed, check messages above
> (Thu Feb 11 13:11:25 2021) Command finished (3 sec)
>
> (Thu Feb 11 14:09:43 2021)
>
> r.futures.potential -d --overwrite input=sampling_f_km@PERMANENT
> output=potential_f_km.csv
> columns=devclip_2016,devpress_0_5_2016,dist_to_evac_km,dist_to_pp_km,dist_toh20_2016_km,per_forest_2016,
>
>

looks like you have an extra comma after per_forest_2016? What
is devclip_2016?


> developed_column=urban_change_01_16 subregions_column=county_rast
> min_variables=2 max_variables=6
> DBMI-SQLite driver error:
> Error in sqlite3_prepare():
> SELECT devclip_2016,devpress_0_5_2016,dist_to_evac_km,dist_t
> o_pp_km,dist_toh20_2016_km,per_forest_2016,,urban_change_01_
> 16,county_rast FROM sampling_f_km WHERE devclip_2016 IS NOT
> NULL AND devpress_0_5_2016 IS NOT NULL AND dist_to_evac_km
> IS NOT NULL AND dist_to_pp_km IS NOT NULL AND
> dist_toh20_2016_km IS NOT NULL AND per_forest_2016 IS NOT
> NULL AND  IS NOT NULL AND urban_change_01_16 IS NOT NULL AND
> county_rast IS NOT NULL
> near ",": syntax error
> DBMI-SQLite driver error:
> Error in sqlite3_prepare():
> SELECT devclip_2016,devpress_0_5_2016,dist_to_evac_km,dist_t
> o_pp_km,dist_toh20_2016_km,per_forest_2016,,urban_change_01_
> 16,county_rast FROM sampling_f_km WHERE devclip_2016 IS NOT
> NULL AND devpress_0_5_2016 IS NOT NULL AND dist_to_evac_km
> IS NOT NULL AND dist_to_pp_km IS NOT NULL AND
> dist_toh20_2016_km IS NOT NULL AND per_forest_2016 IS NOT
> NULL AND  IS NOT NULL AND urban_change_01_16 IS NOT NULL AND
> county_rast IS NOT NULL
> near ",": syntax error
> ERROR: Unable to open select cursor
> Traceback (most recent call last):
>   File "/Users/mitchellmeads/Library/GRASS/7.8/Modules/scrip
> ts/r.futures.potential", line 221, in 
> sys.exit(main())
>   File "/Users/mitchellmeads/Library/GRASS/7.8/Modules/scrip
> ts/r.futures.potential", line 181, in main
> gscript.run_command('v.db.select', map=vinput,
> columns=columns, separator='comma', where=where,
> file=TMP_CSV)
>   File "/Applications/GRASS-7.8.app/Contents/Resources/etc/p
> ython/grass/script/core.py", line 441, in run_command
> return handle_errors(returncode, returncode, args,
> kwargs)
>   File "/Applications/GRASS-7.8.app/Contents/Resources/etc/p
> ython/grass/script/core.py", line 342, in handle_errors
> raise CalledModuleError(module=None, code=code,
> grass.exceptions.CalledModuleError: Module run None
> v.db.select map=sampling_f_km@PERMANENT columns=devclip_2016
> ,devpress_0_5_2016,dist_to_evac_km,dist_to_pp_km,dist_toh20_
> 2016_km,per_forest_2016,,urban_change_01_16,county_rast
> separator=comma where=devclip_2016 IS NOT NULL AND
> devpress_0_5_2016 IS NOT NULL AND dist_to_evac_km IS NOT
> NULL AND dist_to_pp_km IS NOT NULL AND dist_toh20_2016_km IS
> NOT NULL AND per_forest_2016 IS NOT NULL AND  IS NOT NULL
> AND urban_change_01_16 IS NOT NULL AND county_rast 

[GRASS-user] v.surf.idw Not Working

[Michaela Lobato]

Hello,

I have recently been struggling with an issue in GRASS. I am a new GRASS
user and recently downloaded version 7.8.5 for my MacBook (macOS
Catalina).  I converted this sample dataset
 to a shapefile. I am able to
load and visualize the file and set the region to be the loaded set of
points. When I run v.surf.idw, I get the following error:

v.surf.idw input=coal_test@PERMANENT output=coal_test_tested
Input vector map  is 2D - using categories to
interpolate
WARNING: No record for point (cat = 1)
WARNING: No record for point (cat = 2)
WARNING: No record for point (cat = 3)
.
.
.
WARNING: No record for point (cat = 96)
0 points loaded
ERROR: No points found

I have tried to use v.surf.idw with different datasets as well and am
still getting the same error. I've also tried re-installing GRASS GIS to no
avail. I'd appreciate any help you can provide!

Thanks,
Michaela
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] r.contour

[Dave Marshall]

Hello,

I do a lot of work with UK LIDAR data and one of the most frequently used,
and useful, GRASS routines for my work is r.contour. I am currently using
GRASS through QGIS 3.4.12 and the associated version of GRASS is 7.6.1. I
have made a couple of attempts to upgrade my QGIS version to a more recent
one but this always results in a different version of GRASS which does not
allow r.contour to work with the LIDAR files.

QGIS 3.4 opens LIDAR tif files directly using EPSG:27700 as the CRS. Later
versions of QGIS seem to require, or at least suggest, a transformation to
an alternative CRS. Whether I use one of these transformations or not, the
initial error I receive when running r.contour is "WARNING: Datum
 not recognised by GRASS and no
parameters found". Other errors follow and finally there is a message to
say that the routine has failed. I think that all the versions of GRASS
which have generated this error are 7.8.

I would like to upgrade my version of QGIS to a later version but am stuck
with 3.4 because of my need for a functioning r.contour. QGIS contains a
similar contour-drawing option but it does not allow the specification of
upper and lower height limits and so can take a very long time to run on
large files.

Any help or advice will be much appreciated,

Dave Marshall
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.futures.demand

[Mitchell Meads]

Hi Anna,

Thank you for the helpful information! I suppose I was somewhat confused as
to what exactly should all be in the parameters for the r.futures.potential
submodel. I've made the changes you've suggested above, but I'm still
getting some type of "Unable to select cursor" error. Below is the command
output with its errors, if you could help me pin down what I'm doing wrong,
that would be great! Also on a side note, unfortunately, I'm not
experienced in R and and somewhat relying on the futures modeling in GRASS
to complete my task. Thanks again for your help!

(Thu Feb 11 13:11:21 2021)

r.futures.potential --overwrite input=sampling_f_km@PERMANENT
output=potential_f_km.csv
columns=devclip_2016,block_rast,county_rast,devpress_0_5_2016,dist_to_evac_km,dist_to_pp_km,dist_toh20_2001_km,dist_toh20_2004_km,dist_toh20_2006,dist_toh20_2008_km,dist_toh20_2011_km,dist_toh20_2013_km,dist_toh20_2016_km,per_forest_2001,per_forest_2004,per_forest_2006,per_forest_2008,per_forest_2011,per_forest_2013,per_forest_2016,urban_change_01_16
developed_column=devclip_2016 subregions_column=county_rast min_variables=5
max_variables=10
Computing model...
WARNING: fixed-effect model matrix is rank deficient so dropping 2 columns
/ coefficients
Error in pwrssUpdate(pp, resp, tol = tolPwrss, GQmat = GQmat, compDev =
compDev,  :
pwrssUpdate did not converge in (maxit) iterations
Calls: glmer ...  ->  -> stopifnot -> fn ->
pwrssUpdate
In addition: Warning message:
Some predictor variables are on very different scales: consider rescaling
Execution halted
WARNING: fixed-effect model matrix is rank deficient so dropping 2 columns
/ coefficients
Error in pwrssUpdate(pp, resp, tol = tolPwrss, GQmat = GQmat, compDev =
compDev,  :
pwrssUpdate did not converge in (maxit) iterations
Calls: glmer ...  ->  -> stopifnot -> fn ->
pwrssUpdate
In addition: Warning message:
Some predictor variables are on very different scales: consider rescaling
Execution halted
ERROR: Running R script failed, check messages above
(Thu Feb 11 13:11:25 2021) Command finished (3 sec)

(Thu Feb 11 14:09:43 2021)

r.futures.potential -d --overwrite input=sampling_f_km@PERMANENT
output=potential_f_km.csv
columns=devclip_2016,devpress_0_5_2016,dist_to_evac_km,dist_to_pp_km,dist_toh20_2016_km,per_forest_2016,
developed_column=urban_change_01_16 subregions_column=county_rast
min_variables=2 max_variables=6
DBMI-SQLite driver error:
Error in sqlite3_prepare():
SELECT devclip_2016,devpress_0_5_2016,dist_to_evac_km,dist_t
o_pp_km,dist_toh20_2016_km,per_forest_2016,,urban_change_01_
16,county_rast FROM sampling_f_km WHERE devclip_2016 IS NOT
NULL AND devpress_0_5_2016 IS NOT NULL AND dist_to_evac_km
IS NOT NULL AND dist_to_pp_km IS NOT NULL AND
dist_toh20_2016_km IS NOT NULL AND per_forest_2016 IS NOT
NULL AND  IS NOT NULL AND urban_change_01_16 IS NOT NULL AND
county_rast IS NOT NULL
near ",": syntax error
DBMI-SQLite driver error:
Error in sqlite3_prepare():
SELECT devclip_2016,devpress_0_5_2016,dist_to_evac_km,dist_t
o_pp_km,dist_toh20_2016_km,per_forest_2016,,urban_change_01_
16,county_rast FROM sampling_f_km WHERE devclip_2016 IS NOT
NULL AND devpress_0_5_2016 IS NOT NULL AND dist_to_evac_km
IS NOT NULL AND dist_to_pp_km IS NOT NULL AND
dist_toh20_2016_km IS NOT NULL AND per_forest_2016 IS NOT
NULL AND  IS NOT NULL AND urban_change_01_16 IS NOT NULL AND
county_rast IS NOT NULL
near ",": syntax error
ERROR: Unable to open select cursor
Traceback (most recent call last):
  File "/Users/mitchellmeads/Library/GRASS/7.8/Modules/scrip
ts/r.futures.potential", line 221, in 
sys.exit(main())
  File "/Users/mitchellmeads/Library/GRASS/7.8/Modules/scrip
ts/r.futures.potential", line 181, in main
gscript.run_command('v.db.select', map=vinput,
columns=columns, separator='comma', where=where,
file=TMP_CSV)
  File "/Applications/GRASS-7.8.app/Contents/Resources/etc/p
ython/grass/script/core.py", line 441, in run_command
return handle_errors(returncode, returncode, args,
kwargs)
  File "/Applications/GRASS-7.8.app/Contents/Resources/etc/p
ython/grass/script/core.py", line 342, in handle_errors
raise CalledModuleError(module=None, code=code,
grass.exceptions.CalledModuleError: Module run None
v.db.select map=sampling_f_km@PERMANENT columns=devclip_2016
,devpress_0_5_2016,dist_to_evac_km,dist_to_pp_km,dist_toh20_
2016_km,per_forest_2016,,urban_change_01_16,county_rast
separator=comma where=devclip_2016 IS NOT NULL AND
devpress_0_5_2016 IS NOT NULL AND dist_to_evac_km IS NOT
NULL AND dist_to_pp_km IS NOT NULL AND dist_toh20_2016_km IS
NOT NULL AND per_forest_2016 IS NOT NULL AND  IS NOT NULL
AND urban_change_01_16 IS NOT NULL AND county_rast IS NOT
NULL file=/Volumes/Extreme
SSD/grassdata/forecast2/PERMANENT/.tmp/Mitchells-MacBook-
Pro.local/49600.0.csv ended with error
Process ended with non-zero return code 1. See errors in the
(error) output.
(Thu Feb 11 14:09:44 2021) Command finished (0 sec)




Cheers,
Mitchell Meads, PhD Student
Texas A University at Galveston

Re: [GRASS-user] r.futures.demand

[Anna Petrášová]

Hi Mitchell,

looking at your command there are several things to fix. Parameter columns
should have only the predictors, so for example remove county_rast and
urban_change_01_16. Parameter developed_column should be the response
variable, so I suppose urban_change_01_16 is the one to use here. Lastly,
without the dredge mode only use combination of predictors that are not
correlated and don't represent the same info, for example, do not include
dist_toh20_2001_km,dist_toh20_2004_km,dist_toh20_2006,dist_toh20_2008_km,dist_toh20_2011_km,dist_toh20_2013_km,dist_toh20_2016_km,
since these all represent the same variable (I suppose). Without the dredge
mode, all provided predictors will be used in the model, with the dredge
mode, it will try different combinations and return the best model.

Note r.futures.potential is basically just a wrapper around R glmer (lme4)
function, so if you are familiar with R, you can experiment with finding a
model directly in R if you need more flexibility etc.

Please keep the conversation on this mailing list which is archived, so
that others can add to it or benefit from it later.

Best,
Anna

On Thu, Feb 11, 2021 at 2:12 PM Mitchell Meads 
wrote:

> Hi Anna,
>
> I've revisited the r.futures.potential submodel for the futures modeling
> and I still can't get the r.futures.potential submodel to run. I've
> rescaled my variables so they all should be on a similar scale but the
> program is telling me that the variables are still not in appropriate scale
> along with some other error messages that I have copied below. Please let
> me know what you think I'm doing wrong.
>
> (Thu Feb 11 13:11:21 2021)
>
> r.futures.potential --overwrite input=sampling_f_km@PERMANENT
> output=potential_f_km.csv
> columns=devclip_2016,block_rast,county_rast,devpress_0_5_2016,dist_to_evac_km,dist_to_pp_km,dist_toh20_2001_km,dist_toh20_2004_km,dist_toh20_2006,dist_toh20_2008_km,dist_toh20_2011_km,dist_toh20_2013_km,dist_toh20_2016_km,per_forest_2001,per_forest_2004,per_forest_2006,per_forest_2008,per_forest_2011,per_forest_2013,per_forest_2016,urban_change_01_16
> developed_column=devclip_2016 subregions_column=county_rast min_variables=5
> max_variables=10
> Computing model...
> WARNING: fixed-effect model matrix is rank deficient so dropping 2 columns
> / coefficients
> Error in pwrssUpdate(pp, resp, tol = tolPwrss, GQmat = GQmat, compDev =
> compDev,  :
> pwrssUpdate did not converge in (maxit) iterations
> Calls: glmer ...  ->  -> stopifnot -> fn ->
> pwrssUpdate
> In addition: Warning message:
> Some predictor variables are on very different scales: consider rescaling
> Execution halted
> WARNING: fixed-effect model matrix is rank deficient so dropping 2 columns
> / coefficients
> Error in pwrssUpdate(pp, resp, tol = tolPwrss, GQmat = GQmat, compDev =
> compDev,  :
> pwrssUpdate did not converge in (maxit) iterations
> Calls: glmer ...  ->  -> stopifnot -> fn ->
> pwrssUpdate
> In addition: Warning message:
> Some predictor variables are on very different scales: consider rescaling
> Execution halted
> ERROR: Running R script failed, check messages above
> (Thu Feb 11 13:11:25 2021) Command finished (3 sec)
>
> Cheers,
> Mitchell Meads, PhD Student
> Texas A University at Galveston
> Marine & Coastal Management Sciences; CTBS 
> Email: mitchell.me...@tamu.edu
>
>
>
>
> On Sat, Jan 23, 2021 at 9:54 PM Anna Petrášová 
> wrote:
>
>> Hi Mitchell,
>>
>> On Fri, Jan 22, 2021 at 3:23 PM Mitchell Meads 
>> wrote:
>>
>>> Hi all,
>>>
>>> I'm getting an error when running r.futures.demand that says "Number of
>>> development raster maps doesn't not correspond to the number of observed
>>> times". I thought that a fix for this would be to make sure my input
>>> population csv had years that matched the input raster maps in the first
>>> column but this didn't change the error. If you could let me know what you
>>> think I'm doing wrong, that would be greatly appreciated!
>>>
>>
>> The error means the number of raster maps in the development parameter
>> does not match the number of years in the observed_population CSV. So for
>> example, if you specify development=urban_2001,urban_2006,urban_2011 (3
>> maps) then the observed_population file should look like this (header + 3
>> lines):
>>
>> year,37037,37063,...
>> 2001,19860,10980,...
>> 2006,20760,12660,...
>> 2011,21070,13090,...
>>
>> If you can't see any obvious mistake with your data, I would have to see
>> the r.futures.demand command you are trying to execute and the input CSV
>> file.
>>
>>
>>>
>>>
>>> Cheers,
>>> Mitchell
>>>
>>>
>>> ___
>>> grass-user mailing list
>>> grass-user@lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/grass-user
>>> 
>>>
>>
___

Re: [GRASS-user] Creating a png file with multiple vector maps

[Chris Bartolomei via grass-user]

 Good morning Anna,It took quite a while of trial and error but I worked out a 
method that kindof works:First off - unless someone says otherwise, you can't 
use the PNG driver (d.mon) method to overlay more than one polygon vector. 
Sorry - it just doesn't work. You CAN use the ps.map method - that works really 
well generating the image however it by default assumes you are printing on an 
A4 piece of paper so there's all sorts of white space.  The image is centered 
at the top of this fictional piece of paper. In your postscript rules file you 
can use the "maploc" command to position the image elsewhere on the page. This 
is necessary because the next trick changes the paper dimensions but it assumes 
the origin is the lower left corner and therefore clips anything that is above 
the new dimensions. Back to postscript commands in the rules file first though 
... the ps.map maploc command uses inches (why?? it should be points) so an A4 
page is 8.27" x 11.69"  points are 1/72 of an inch thus 595p x 842p - it also 
has a default 36p margin (0.5 inch). You'll need those numbers later. maploc 
also lets you set the size of your image box:  maploc {x offset from left edge} 
{y offset from top} {width of box} {height of box} Note: this is all done via a 
BASH script with GRASS 7.4 on Linux (RHEL 7), not python. This is my postscript 
rules file:
maploc 0.1 6.815 6.5 4.875 #468p x 351p map box moved down towards the bottom 
of the page# note that if you push it too far down to where the box would run 
off the bottom, the image is# resized to fit on the page so do some testing to 
come up with the correct values# also I found the computational region controls 
the aspect ratio so although I say 
# 6.5 x 4.875 with the above maploc command, I got a 6.5 x 3.8 inch box.border 
y # add a border to the map frame (box)  color 81:81:81 # shade of gray  end # 
end the border controlsvareas admin_area # top vector layer to display  layer 1 
# attribute table to use  rgbcolumn area_color # name of column holding R:G:B 
values to fill the polygons  color 153:153:153 #boundary color  end # end the 
admin_area controlsvareas Country # this is the bottom vectors to display  
color 210:210:210 #boundary color  fcolor 153:153:153 #fill color for all 
polygons  end # end the Country controls
Here's the command to run to generate the postscript file:
ps.map input=$HOME/ps_rules.txt out=$HOME/color_admin.ps --overwrite
To convert the postscript to PNG I had to use ghostscript - there are other 
tools you can use though.
gs -dSAFER -dBATCH -dNOPAUSE -sDEVICE=png16m -r300 -dTextAlphaBits=4 
-dGraphicsAlphaBits=4 -dDEVICEWIDTHPOINTS=473 -dDEVICEHEIGHTPOINTS=276 
-dFIXEDMEDIA -dPSFitPage -sOutputFile=$HOME/color_admin.png -c "<> setpagedevice" -f $HOME/color_admin.ps
So the above line needs some explaining 
(http://www.ghostscript.com/doc/9.27/Use.htm) but in a nutshell, the parameters 
to play with are first the Pageoffset [x y] values. They are in points not 
inches ... 1/72 inch = 1 point ... remember the 1/2" margins? the -34 gives me 
2 points of white space to the left edge of the map frame, the 78 I had to play 
with to push the map frame down to the right spot.Next is the DEVICEWIDTHPOINTS 
and DEVICEHEIGHTPOINTS ... again in points ... this "trims" the paper to height 
and width ... set something then run it and view the results. Adjust and run 
again until you get it correct.
It's a royal pain but it seems to work this way. It would sure be nice to 
create a GRASS workspace file and just say "convert this workspace to an image" 
with everything all laid out nicely - like Arc does exporting their mxd map 
files...
I hope this helps someone !:)
Chris

On Wednesday, February 10, 2021, 11:08:00 PM EST, Anna Petrášová 
 wrote:  
 
 

On Tue, Feb 9, 2021 at 4:41 PM Chris Bartolomei  wrote:

 Hi Anna - thank you for the suggestion - I tried it but alas, still it only 
outputs a single vector map (layer). I can get either the Country vector or the 
admin_areas vector, but not both overlaid.:(Chris


I realized you are using both environmental variables and d.mon, that might 
cause some issues, you use one or the other. So try to remove the lines 
starting with d.mon.
Hope that helps,Anna 

On Tuesday, February 9, 2021, 1:20:52 PM EST, Anna Petrášová 
 wrote:  
 
 Hi,
On Tue, Feb 9, 2021 at 10:25 AM Chris Bartolomei via grass-user 
 wrote:

Good morning :)I'm using GRASS 7.4.1 on a Linux cluster so I only have 
command-line capability. I have two vector layers (a country boundary polygon 
and part of an administrative area map - also polygons). I am trying to 
automate creating a PNG file of the admin areas overlaying the country boundary 
therefore all work has to be command-line (in a bash script). I've tried this 
two ways - using the d.mon start=png method and also the ps.map method as 
described below. The d.mon method appears to generate the image with only one 
vector map (not both) and only colors the borders - 

Re: [GRASS-user] [GRASS-dev] ASF - OGC - OSGeo code sprint - Feb 17-19, 2021

[Anna Petrášová]

Hi Vero,

we registered for this, we probably won't participate 100% of the time, but
hope to see other GRASS devs there.

Anna & Vaclav

On Thu, Feb 11, 2021 at 9:16 AM Veronica Andreo 
wrote:

> Hello everyone :)
>
> Shall we join the 2021 Joint ASF – OGC – OSGeo Code Sprint [0]?
>
> AFAIU, the focus is on OGC standards implementation. Is anyone in the
> GRASS community currently working on that and wishes to participate? They
> have created a repo with further details [1] in case you are interested.
>
> Best,
> Vero
>
> [0] https://portal.ogc.org/public_ogc/register/20210217_code_sprint.php
> [1] https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021
> ___
> grass-dev mailing list
> grass-...@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] ASF - OGC - OSGeo code sprint - Feb 17-19, 2021

[Veronica Andreo]

Hello everyone :)

Shall we join the 2021 Joint ASF – OGC – OSGeo Code Sprint [0]?

AFAIU, the focus is on OGC standards implementation. Is anyone in the GRASS
community currently working on that and wishes to participate? They have
created a repo with further details [1] in case you are interested.

Best,
Vero

[0] https://portal.ogc.org/public_ogc/register/20210217_code_sprint.php
[1] https://github.com/opengeospatial/joint-ogc-osgeo-asf-sprint-2021
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user