Re: [GRASS-user] Cannot pull from dev master branch

[Rich Shepard via grass-user]

On Fri, 24 Nov 2023, Maris Nartiss wrote:


If there are no changes you want to keep, just git reset --hard HEAD.


Māris,

Thank you. My use of git is quite simple so there's much I don't know.

Regards,

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

[GRASS-user] PDAL version issue

[Rich Shepard via grass-user]

Installed here is pdal-2.2.0. When I configure the updated source code it
fails at this point:
checking whether to use PDAL... yes
configure: error: *** Unable to locate suitable (>=1.7.1) PDAL library.

The configuration file ends with
--with-pdal=/usr/bin/pdal

and pdal is found in /usr/bin/pdal

Please suggest how I let configure know the installed pdal is >=1.7.1.

TIA,

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

Re: [GRASS-user] Cannot pull from dev master branch [RESOLVED]

[Rich Shepard via grass-user]

On Fri, 24 Nov 2023, Linda Karlovská wrote:


you can do the following in your main branch:


Linda,


git checkout main

$ git checkout main
...
Already on 'main'
Your branch and 'origin/main' have diverged,
and have 81 and 186 different commits each, respectively.
  (use "git pull" to merge the remote branch into yours)


git fetch upstream

$ git fetch upstream
fatal: 'upstream' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Instead,
$ git fetch 
$ git reset --hard

HEAD is now at 8968e9b631 Merge branch 'main' of https://github.com/OSGeo/grass

The log confirms this.

Many thanks,

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

[GRASS-user] Cannot pull from dev master branch

[Rich Shepard via grass-user]

I've not used grass in a long time and want to update my source code to the
current dev status as I've done before. But, there's a merge issue I need to
learn how to resolve. My attempt:
$ git pull
error: Your local changes to the following files would be overwritten by merge:
Dockerfile
contributors.csv
display/d.legend.vect/draw.c
doc/development/submitting/python.md
doc/development/submitting/submitting.md
doc/development/submitting/submitting_c.md
doc/gui/wxpython/example/frame.py
doc/infrastructure.md
doc/python/raster_example_ctypes.py
docker/alpine/Dockerfile
docker/alpine/Dockerfile_alpine_latest
docker/debian/Dockerfile
docker/ubuntu/Dockerfile
docker/ubuntu_wxgui/Dockerfile
gui/wxpython/animation/nviztask.py
gui/wxpython/animation/temporal_manager.py
gui/wxpython/core/gconsole.py
gui/wxpython/core/globalvar.py
gui/wxpython/core/menutree.py
gui/wxpython/core/settings.py
gui/wxpython/core/toolboxes.py
gui/wxpython/core/utils.py
gui/wxpython/core/workspace.py
gui/wxpython/core/ws.py
gui/wxpython/datacatalog/tree.py
gui/wxpython/dbmgr/base.py
gui/wxpython/dbmgr/dialogs.py
gui/wxpython/dbmgr/sqlbuilder.py
gui/wxpython/gcp/manager.py
gui/wxpython/gmodeler/frame.py
gui/wxpython/gmodeler/model.py
gui/wxpython/gui_core/dialogs.py
gui/wxpython/gui_core/forms.py
gui/wxpython/gui_core/gselect.py
gui/wxpython/gui_core/mapdisp.py
gui/wxpython/gui_core/preferences.py
gui/wxpython/gui_core/prompt.py
gui/wxpython/gui_core/pyedit.py
gui/wxpython/gui_core/treeview.py
gui/wxpython/gui_core/vselect.py
gui/wxpython/gui_core/widgets.py
gui/wxpython/iclass/dialogs.py
gui/wxpython/iclass/frame.py
gui/wxpython/iclass/statistics.py
gui/wxpython/iclass/toolbars.py
gui/wxpython/icons/icon.py
gui/wxpython/image2target/ii2t_manager.py
gui/wxpython/iscatt/controllers.py
gui/wxpython/iscatt/core_c.py
gui/wxpython/iscatt/dialogs.py
gui/wxpython/iscatt/frame.py
gui/wxpython/iscatt/iscatt_core.py
gui/wxpython/iscatt/plots.py
gui/wxpython/iscatt/toolbars.py
gui/wxpython/lmgr/frame.py
gui/wxpython/lmgr/giface.py
gui/wxpython/lmgr/layertree.py
gui/wxpython/lmgr/statusbar.py
gui/wxpython/lmgr/workspace.py
gui/wxpython/location_wizard/wizard.py
gui/wxpython/main_window/frame.py
gui/wxpython/mapdisp/frame.py
gui/wxpython/mapdisp/main.py
gui/wxpython/mapswipe/frame.py
gui/wxpython/mapwin/base.py
gui/wxpython/mapwin/buffered.py
gui/wxpython/modules/colorrules.py
gui/wxpython/nviz/mapwindow.py
gui/wxpython/nviz/tools.py
gui/wxpython/nviz/wxnviz.py
gui/wxpython/photo2image/ip2i_manager.py
gui/wxpython/psmap/dialogs.py
gui/wxpython/psmap/frame.py
gui/wxpython/psmap/instructions.py
gui/wxpython/startup/guiutils.py
gui/wxpython/tools/build_modules_xml.py
gui/wxpython/vdigit/mapwindow.py
gui/wxpython/vdigit/toolbars.py
gui/wxpython/vdigit/wxdigit.py
gui/wxpython/vdigit/wxdisplay.py
gui/wxpython/vnet/dialogs.py
gui/wxpython/vnet/vnet_core.py
gui/wxpython/vnet/vnet_data.py
gui/wxpython/vnet/widgets.py
gui/wxpython/web_services/dialogs.py
gui/wxpython/web_services/widgets.py
gui/wxpython/wxgui.py
gui/wxpython/wxplot/base.py
imagery/i.atcorr/geomcond.cpp
imagery/i.atcorr/i.atcorr.html
lib/bitmap/bitmap.c
lib/init/grass.py
lib/vector/Vlib/area.c
lib/vector/Vlib/buffer2.c
lib/vector/Vlib/build.c
lib/vector/Vlib/build_sfa.c
lib/vector/Vlib/close.c
lib/vector/Vlib/copy.c
lib/vector/Vlib/field.c
lib/vector/Vlib/header.c
lib/vector/Vlib/level_two.c
lib/vector/Vlib/line.c
lib/vector/Vlib/net_analyze.c
lib/vector/Vlib/open.c
lib/vector/Vlib/poly.c
lib/vector/Vlib/read.c
lib/vector/Vlib/read_ogr.c
lib/vector/Vlib/simple_features.c
lib/vector/Vlib/write.c
lib/vector/Vlib/write_nat.c
lib/vector/Vlib/write_pg.c
locale/grass_po_stats.py
locale/po/grasslibs_ar.po
locale/po/grasslibs_bn.po
locale/po/grasslibs_cs.po
locale/po/grasslibs_de.po
locale/po/grasslibs_el.po
locale/po/grasslibs_es.po
locale/po/grasslibs_fi.po
locale/po/grasslibs_fr.po
locale/po/grasslibs_hu.po
locale/po/grasslibs_id_ID.po
locale/po/grasslibs_it.po
locale/po/grasslibs_ja.po
locale/po/grasslibs_ko.po

Re: [GRASS-user] Fwd: [GRASS-web] Inclusion of your Website in the Library of Congress Web Archives

[Rich Shepard]

On Wed, 13 Sep 2023, Markus Neteler wrote:


FYI!


Markus,

That's great news. Who would have thought back in the CERL days that so much
could be accomplished by your leadership of the GRASS development team over
the decades?

Best regards,

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

Re: [GRASS-user] agricultural small water reservoir

[Rich Shepard]

On Wed, 26 Jul 2023, Rich Shepard wrote:


Since I'm not at all familiar with the area in which you're working I have
no specific suggestions. I did find a web site that summarizes several
models:
<https://stormwater.pca.state.mn.us/index.php/Available_stormwater_models_and_selecting_a_model>.


Enrico,

One further thought: that web site makes an important point; you have
different modeling needs depending on what needs to be modeled: hydrology
(input to a receiving water body), hydraulics (in-channel flows), or water
quality. Water quality modeling requires different statistical models
because of the characteristics of water chmistry and biota.

Regards,

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

Re: [GRASS-user] agricultural small water reservoir

[Rich Shepard]

On Wed, 26 Jul 2023, bonushenricus wrote:


Do you have any articles or searchable projects on the internet to
recommend the US method?


Enrico,

Since I'm not at all familiar with the area in which you're working I have
no specific suggestions. I did find a web site that summarizes several
models:
.

I've used TR-20 in the past, but every one of my projects has been different
in terms of location, water quality issue, and regulatory requirements.


In addition, I need to learn how to do earthmoving calculations and then
use 3drasters, so if you have any advice on how to do that, I welcome it.


Not sure I understand your need. I've often worked with hard rock quarry
operators to model topographic changes and storm water flows. The base data
is the smallest scale DEM available for that location which is then modified
as needed. I'm an applied ecologist, an environmental scientist, and neither
an engineer nor a geologist.

You may have to invent your own approach and document what you've done to
demonstrate to non-technical decision-makers why it's both technically sound
and legally defensible. Effectively communicating complex environmental
issues to decision-makers can be the most important and difficult of our
job.

Best of luck,

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

Re: [GRASS-user] agricultural small water reservoir

[Rich Shepard]

On Wed, 26 Jul 2023, bonushenricus wrote:


This is a question on the approach to take in order to achieve a
consultancy objective. For two farms I have to give some input on the
possible design of a small water reservoir for agricultural use. I have
this rainfall data: the number of days per month of moderate rainfall (4-6
mm/hr) of at least 4 hours. So, without taking into account extreme
events, which are more interesting for erosion, I was thinking of doing a
r.sim.water calculation for each month of the water depth in the
reservoirs, and at the same time an evaporation calculation, to build up a
yearly report of the potential changes in the amount of water available.
Has anyone ever used GRASS for this type of work? Perhaps for dams?


Enrico,

There are a couple of methods used in the US that might be applicable, but I
suggest you look at precipitation records for the past few years in the
region of the two farms. Given the rate of climate heating and the more
frequent strong weather events everywhere any existing ag pond sizing method
is probably no longer valid.

Depending on the purpose of the pond I would find the most extreme
precipitation events (and the antecedent weather conditions) and add a
safety factor to those. It would be better to oversize them (if that could
be done) than have them overfilled.

It's a changed world and we're all guessing how to advise clients to be
prepared for unpredictable, extreme events.

Good luck,

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

Re: [GRASS-user] v.in.ascii standard format CRS sequence [ANSWERED]

[Rich Shepard]

On Wed, 24 May 2023, Rich Shepard wrote:


The standard format does not use column specifications. Is the standard
format assuming the sequence is easting/northing?


Yep, Found the answer myself.

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

[GRASS-user] v.in.ascii standard format CRS sequence

[Rich Shepard]

In v.in.ascii the point format specifies which data represents easting and
which represents northing by specifying which column is x and which is y,
respectively.

The standard format does not use column specifications. Is the standard
format assuming the sequence is easting/northing?

TIA,

Rich

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

Re: [GRASS-user] v.in.ascii data error

[Rich Shepard]

On Tue, 23 May 2023, Anna Petrášová wrote:


How the data is formatted is wrong, see the example. With standard format,
you need to specify coordinates separated by space. Attributes can't be
used.
B 5
 45.654023 -122.980241 393


Anna,

Oh! I saw the separator option in the parameter list and assumed it applied
to both formats. Didn't pick up the difference looking at the examples.

Thanks for clarifying.

Regards,

Rich

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

Re: [GRASS-user] v.in.ascii data error

[Rich Shepard]

On Tue, 23 May 2023, Anna Petrášová wrote:


Then yes, just include the boundary and run v.centroids. It was unclear
from your first question what it is you actually need.


Anna,

That's what I had done; here are the data file, v.in.ascii command, and
grass' output:

B 5
 45.654023|-122.980241|393|Shop
 45.653931|-122.980315|393|Shop
 45.653960|-122.979910|393|Shop
 45.653856|-122.979831|393|Shop
 45.654023|-122.980241|393|Shop

v.in.ascii -z in=$HOME/projects/oregon/northside-rock/data/shop.txt 
out=maintenance_bldg format=standard sep=pipe cat=0 x=1 y=2 z=3 columns='x 
double precision, y double precision, z integer, label char(4)' --o


v.in.ascii -z in=$HOME/projects/oregon/northside-rock/data/shop.txt 
out=maintenance_bldg format=standard sep=pipe cat=0 x=1 y=2 z=3 columns='x 
double precision, y double precision, z integer, label char(4)' --o

WARNING: Unexpected data in vector header:
 [B 5]
ERROR: Import failed



Looking at the v.in.ascii example 1b I added a 'no header' option to the
command:

v.in.ascii -zn in=$HOME/projects/oregon/northside-rock/data/shop.txt 
out=maintenance_bldg format=standard sep=pipe cat=0 x=1 y=2 z=3 columns='x 
double precision, y double precision, z integer, label char(4)' --o


v.in.ascii -zn in=$HOME/projects/oregon/northside-rock/data/shop.txt 
out=maintenance_bldg format=standard sep=pipe cat=0 x=1 y=2 z=3 columns='x 
double precision, y double precision, z integer, label char(4)' --o

WARNING: Error reading ASCII file: (bad point) [
 45.654023|-122.980241|393|Shop]

Please tell me what I've done incorrectly.

TIA,

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

Re: [GRASS-user] v.in.ascii data error

[Rich Shepard]

On Mon, 22 May 2023, Anna Petrášová wrote:


That's not what I meant. Point format is for points, nothing else. If you
need areas, you need standard format. See the first example in the man
page for importing areas.


Anna,

That's what I thought, and what I had defined in the data file and command.
but with a none-rectangular boundary I don't have the coordinates for a
centroid; although I could just pick a point, I suppose.

Do all standard format boundary data files require me to include a centroid?

Regards,

Rich

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

Re: [GRASS-user] v.in.ascii data error

[Rich Shepard]

On Mon, 22 May 2023, Micha Silver wrote:


Do you actually have the text "Data file:" as part of the header? AFAIK,
You need, at minimum, "VERTI:" in the header.


Micha,

No.

All resolved now. Anna taught me that a boundary/area without an explicit
defined centroid in the source file needs to be imported in point, rather
than standard format.

Regards,

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

Re: [GRASS-user] v.in.ascii data error

[Rich Shepard]

On Mon, 22 May 2023, Anna Petrášová wrote:


Data file:
B 5
  45.654023|-122.980241|393|Shop
  45.653931|-122.980315|393|Shop
  45.653960|-122.979910|393|Shop
  45.653856|-122.979831|393|Shop
  45.654023|-122.980241|393|Shop



you are mixing formats, either use 'standard' or 'point', see the
v.in.ascii manual. Likely you need format=point.


Anna,

I know that lines and points use the point format, but boundaries and areas
use the standard format. Your comment informs me that a boundary or area
without a specified centroid is imported in point format and becomes an area
after v.centroid is applied.

I didn't think of this.

Many thanks,

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

[GRASS-user] v.in.ascii data error

[Rich Shepard]

I've added elevation and a feature name to the standard format v.in.ascii
file. Grass reports an import error; the same error occurs without those two
added columns. I'm not seeing the error, your fresh eyes will see it.

Data file:
B 5
 45.654023|-122.980241|393|Shop
 45.653931|-122.980315|393|Shop
 45.653960|-122.979910|393|Shop
 45.653856|-122.979831|393|Shop
 45.654023|-122.980241|393|Shop

Command:
v.in.ascii -z in=$HOME/projects/oregon/northside-rock/data/shop.txt 
out=maintenance_bldg format=standard sep=pipe cat=0 x=1 y=2 z=3 columns='x 
double precision, y double precision, z integer, label char(4)' --o

Results:
v.in.ascii -z in=$HOME/projects/oregon/northside-rock/data/shop.txt 
out=maintenance_bldg format=standard sep=pipe cat=0 x=1 y=2 z=3 columns='x 
double precision, y double precision, z integer, label char(4)' --o
WARNING: Unexpected data in vector header:
 [B 5]
ERROR: Import failed

I've not calculated a centroid; intend to use v.centroid to add the point to
the bound area.

Help appreciated,

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

Re: [GRASS-user] ps.map: add elevation scale? [RESOLVED]

[Rich Shepard]

On Tue, 16 May 2023, Markus Neteler wrote:


Do you mean in this manual page?
https://grass.osgeo.org/grass-stable/manuals/ps.map.html#colortable

For wording improvements, please (ideally) suggest them here:
https://github.com/OSGeo/grass/blob/main/ps/ps.map/ps.map.html#L214


Markus,

Okay. Earlier today you asked how I would change the colortable name and I
responded in the email. I'll put the same suggestion on the tracking page.

Regards,

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

Re: [GRASS-user] Selecting most appropriate r.resample.* module

[Rich Shepard]

On Tue, 16 May 2023, Markus Neteler wrote:


To me this sounds like
https://grasswiki.osgeo.org/wiki/Interpolation#Resampling_of_raster_maps_to_coarser_resolution

"Resampling of raster maps to coarser resolution"
--> r.resamp.stats


Markus,

Too me, too. The resulting cells were too coarse. Since the source DEM is 9
years old, the two years ago there was another landslide on part of the
site, the original resulution does nicely as a baseline.

Thanks,

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

Re: [GRASS-user] ps.resamp.rst: invalid argument

[Rich Shepard]

On Tue, 16 May 2023, Markus Neteler wrote:


Please report the output of `g.region -p`.


Markus,

It might well have been that the region was set to the vector analysis area map
and not to the raster map.

Regardless, I tried r.resamp.stats and the output was much too coarse so I'm
sticking with the original 1 square foot resolution.

Thanks,

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

[GRASS-user] ps.resamp.rst: invalid argument

[Rich Shepard]

While waiting to learn the uses of the various r.resamp* modules, I tried
r.resamp.rst with this result:
r.resamp.rst in=dem2014 ew_res=10 ns_res=10 elevation=base10ft slope=slope10ft 
aspect=aspect10ft --o
Processing all selected output files will require
129.19 KB of disk space for temp files.
Temporarily changing the region to desired resolution ...
Changing back to the original region ...
Percent complete:
ERROR: Unable to seek: Invalid argument

I'm not seeing the invalid argument. Please show me what I've missed.

TIA,

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

[GRASS-user] Selecting most appropriate r.resample.* module

[Rich Shepard]

I have a DEM with a 1 foot resolution and I want to re-sample it to a 10
foot resolution. Not knowing the mathematics of each option
(r.resamp.bspline, r.resamp.filter, r.resamp.interp, r.resamp.rst,
r.resamp.stats, r.resample) I am asking for advice on selecting one.

The overall elevation difference is about 600 feet. My brief review of the 6
modules leads me to think that r.resamp.rst might be best for my data, But,
that's only a SWAG.

Please advise,

Rich

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

Re: [GRASS-user] ps.map: add elevation scale? [RESOLVED]

[Rich Shepard]

On Tue, 16 May 2023, Markus Neteler wrote:


Please suggest how to improve the documentation to make it more obvious.


Markus,

Reading the colortable manual page shows that it's the raster equivalent of
vlegend. Why not change 'colortable' to 'rlegend' as that's what it
produces?

When I saw 'colortable' I assumed it was a version of r.colors, defining the
map colors, not providing a legend.

Best regards,

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

Re: [GRASS-user] ps.map: add elevation scale? [RESOLVED]

[Rich Shepard]

On Tue, 16 May 2023, Frank David wrote:

colortable  ? : 
https://grass.osgeo.org/grass82/manuals/ps.map.html#colortable


Frank,

Well, I completely missed that one. I used r.colors to set the colors of the
rater to 'elevation' and didn't notice the colortable command in ps.map. I
should have known the code was there someplace and overlooked that one each
time.

Mea culpa!

Many thanks ... close the feature requese please.

Best regards,

Rich


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

Re: [GRASS-user] ps.map: add elevation scale?

[Rich Shepard]

On Mon, 15 May 2023, Rich Shepard wrote:


Since I can add a raster elevation legend using the GUI map window (see
attached), why can't I add in in a .psmap file?


I stopped writing C code >20 years ago so I am not qualified to create a
ps_rlegend.c based on ps_vlegend.c and integrate it into ps.map. It would be
really helpful to be able to put an elevation legend on a map so it better
communicates to non-technical decision-makers.

Could someone quickly create a ps_rlegend.c and make it available to ps.map?

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

[GRASS-user] ps.map: add elevation scale?

[Rich Shepard]

Is there a way to add the elevation color bar for a DEM map to a ps.map?

TIA,

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

Re: [GRASS-user] ps.map: specifying colors

[Rich Shepard]

On Mon, 15 May 2023, Vaclav Petras wrote:


The r:g:b format supports 0-255, not the hexadecimal colors, so that's why
ff does not work. With display commands, you can also use #rrggbb
(#RRGGBB). I would have to check if that works with ps.map or not.


Vaclav,

I should know that. Perhaps need to recaffinate. Yes, the color chart I used
has hexidecimal numbers.

Many thanks,

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

Re: [GRASS-user] ps.map: specifying colors

[Rich Shepard]

On Mon, 15 May 2023, Rich Shepard wrote:


The input file for a ps.map vareas has a color specified as:
color 33:00:00
When I run the ps.map command I'm told this is an invalid color for vareas.


Here's the exact output of one try:
color ff:ff:ff : illegal border color request
color 33:f:0 : illegal color request (vareas)
fcolor 33:f:0 : illegal color request (vareas)

The latter two started as pairs for green and blue, too.

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

[GRASS-user] ps.map: specifying colors

[Rich Shepard]

The input file for a ps.map vareas has a color specified as:
color 33:00:00

When I run the ps.map command I'm told this is an invalid color for vareas.

When I chage it to:
color 3:0:O

I get the same error.

This format worked in the past and according to the ps.map manual page it
should work here. What syntax error do I miss seeing?

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

[GRASS-user] Specifying RBB colors in .psmap file

[Rich Shepard]

The ps.map manual does not specify how to enter RGB colors rather than by
the few recognized names.

In the *.psmap file Would spcifying a color as FF:99:00 be properly
interpreted by grass? And for a border only should I specify fcolor none?

TIA,

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

Re: [GRASS-user] Map production recommendations

[Rich Shepard]

On Sat, 13 May 2023, Eric Patton wrote:


It stands for Generic Mapping Tools. It’s excellent software, but not for
the faint of heart, IMO. Very steep learning curve, but the payoff is
worth it.
https://www.generic-mapping-tools.org/


Eric,

Thanks. I'll take a look.

Regards,

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

Re: [GRASS-user] Map production recommendations

[Rich Shepard]

On Fri, 12 May 2023, Vaclav Petras wrote:


For some use cases, you can consider the m.printws addon. It is an
alternative to ps.map (both GUI and the command line) based on the standard
d-commands.
https://grass.osgeo.org/grass-stable/manuals/addons/m.printws.html


Vaclav,

Thanks for the pointer.


Since we are listing options here, GMT experienced quite some revamp. I
would curious if anyone here has tried it lately.


What's GMT other than the deprecated Greenwich Mean Time?

Regards,

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

Re: [GRASS-user] Map production recommendations

[Rich Shepard]

On Fri, 12 May 2023, Massimiliano Alvioli wrote:


I am not sure what can be done to facilitate the use of ps.map, but I can
tell that browsing GRASS mapsets from QGIS to create nice map figures is
the easiest thing to do. If you browse your "grassdata" folder from the
file explorer in QGIS, you must scroll down until you see GRASS icons for
each location. Then you can navigate to your mapset and display your
raster/vectors in QGIS, and use the map creator (?) tool to prepare
figures.


Massi,

ps.map has always been a low priority for improvements. While it took a lot
of time to produce high quality output, the presention to non-technical
decision-makers was highly satisfying. Now I have several projects needing
such images so I installed qgis and need to learn how to use it for this
purpose.

Your instructions are really helpful and I'll apply them today to produce
the 3 maps needed immediately.

Best regards,

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

[GRASS-user] Map production recommendations

[Rich Shepard]

I've always used ps.map for presentations by writing scripts and using the
GUI to place things. It's a long, tedious process (for me, at least) but
familiar. I've been told that Qgis can produce nice presentation maps and
use grass raster and vector files. I've not used Qgis at all but have just
installed it (I believe, with the grass option) on my ThinkPad.

I would like suggestions to either facilitate ps.map creation or use qgis or
another tool to create 3 presentatoin maps of topography, flowlines and flow
accumulations.

All ideas welcome,

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

Re: [GRASS-user] r.slope.aspect: rejects DCELL precison for map with DCELL precision

[Rich Shepard]

On Wed, 10 May 2023, Anna Petrášová wrote:


It's a typo in "DCELL"


Anna,

Another example of the value of new eyes looking at the situation. I
expected it to be correct so I missed the typo.

Thanks again,

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

Re: [GRASS-user] v.to.rast questions

[Rich Shepard]

On Wed, 10 May 2023, Anna Petrášová wrote:


There is r.surf.contour, so that sounds like the tool you need.


Thank you, Anna. I'll re-do the process.

Best regards,

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

[GRASS-user] r.slope.aspect: rejects DCELL precison for map with DCELL precision

[Rich Shepard]

I don't understand why a raster elevation map with DCELL precision is
rejected by r.slope.aspect. The region was set to the vector analysis area.

r.info tells me this about the elevation map:
++
 | Map:  dem2014Date: Wed May 10 13:47:46 2023|
 | Mapset:   northside_rock Login of Creator: rshepard|
 | Location: Oregon   |
 | DataBase: /data1/grassdata |
 | Title:dem_2014 |
 | Timestamp: none|
 ||
 ||
 |   Type of Map:  raster   Number of Categories: 0   |
 |   Data Type:DCELLSemantic label: (none)|
 |   Rows: 1037   |
 |   Columns:  1056   |
 |   Total Cells:  1095072|
 |Projection: NAD83(CORS96) / Oregon North|
 |N: 224201S: 223164   Res: 1 |
 |E: 2307121.58W:2306066   Res: 0.99960227|
 |   Range of data:min = 240  max = 820   |
 ||
 |   Data Description:|
 |generated by r.surf.contour |
 ||
 |   Comments:|
 |r.surf.contour --overwrite input="baseline_dem" output="dem_2014"   |
 ||
 ++

grass reports (with the module usage redacted):
r.slope.aspect elev=dem2014 slope=dem2014_slope aspect=dem2014_aspect 
format=degrees precision=DCELLl pcurv=dem2014_pcurve dx=dem2014_ew_slope 
dy=dem2014_ns_slope mem=2000 --o
Generates raster maps of slope, aspect, curvatures and partial derivatives from 
an elevation raster map.
 ...

ERROR: Value  out of range for parameter 
Legal range: CELL,FCELL,DCELL

What exactly is out of range?

TIA,

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

Re: [GRASS-user] v.to.rast: advice needed

[Rich Shepard]

On Wed, 10 May 2023, Rich Shepard wrote:


Thanks very much. I'm learning many new things on this project and still
need to meet regulator's deadlines.


Markus,

The wiki page on 'Contour lines to DEM' is what I need.

Best regards,

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

Re: [GRASS-user] v.to.rast: advice needed

[Rich Shepard]

On Wed, 10 May 2023, Markus Neteler wrote:


In addition, here is an overview page:
https://grasswiki.osgeo.org/wiki/Interpolation


Markus,

Thanks very much. I'm learning many new things on this project and still
need to meet regulator's deadlines.

Much appreciated,

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

Re: [GRASS-user] v.to.rast: advice needed

[Rich Shepard]

On Wed, 10 May 2023, Maris Nartiss wrote:


I think you need to interpolate and not simply convert vector lines to
raster lines. Make sure lines have an attribute with elevation (or z
coordinate) and use e.g. v.surf.rst module.


Māris.

Interpolating the vector contour file before rasterizing makes sense to me,
too. Never before having to convert a vector elevation contour file to a
raster file I'd no idea which v.surf.* module to apply.

The vector file has a ContourEle attribute with the elevation values.

I'm taking your advice and will use v.surf.rast.

This project has more topography data issues than any I've encountered since
I started using grass with version 4.0 (all integer, all CLI.)

Very much appreciated,

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

Re: [GRASS-user] v.to.rast questions

[Rich Shepard]

On Wed, 10 May 2023, Rich Shepard wrote:


There are several r.resamp.* modules in the core distribution. Please advise
me which would be most appropriate for my rasterized contour elevation map.


Should I use one of the v.surf.* modules then re-rasterize the resulting
map? If so, please recommend the most appropriate v.surf.* module and
recommended parameters to use.

TIA,

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

Re: [GRASS-user] v.to.rast questions

[Rich Shepard]

On Wed, 10 May 2023, Rich Shepard wrote:


Is there an r.* module to interpolate elevations between the contour lines
so I have cells?


There are several r.resamp.* modules in the core distribution. Please advise
me which would be most appropriate for my rasterized contour elevation map.

TIA,

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

Re: [GRASS-user] v.to.rast questions

[Rich Shepard]

On Wed, 10 May 2023, Anna Petrášová wrote:


Sounds like the vector geometry was already 3D, that's the case when you
use use=z. If the vector would be 2D (see v.info) you would have to use the
attribute table.


Anna,

When I used the 2D file, regardless of which parameter I used or both,
v.to.rast told me the file was not 3D. That's why I converted it. When
'use=z' failed I tried 'attribute_column=ContourEle' with the same result.

Now I have the rasterized contour map (image attached) and need to learn how
to use it to create flowlines, flow accumulations, and more. It does not
have the 1'x1' cells each with a color representing the elevation.

Is there an r.* module to interpolate elevations between the contour lines
so I have cells?

This is all new to me so I appreciate all the help I get.

Regards,

Rich___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] v.to.rast questions

[Rich Shepard]

My current topographic vector data file has a column name for the elevation
data, ContourEle. Reading the v.to.rast page there is a use parameter (with
'z' for elevation) and an attribute_column parmater. Because the vector
map's database table does not have a column named 'z', but the one named
'CountourEle' I put both parameters on the command line.

grass told me that I cannot have both, and that using the named elevation
column was not allowed. So I put 'use=z' in the command and the conversion
worked.

How did v.to.rast know that the column named 'ContourEle' was the z value?

Should the manual page explain that the use and attribute_column cannot be
used together for elevation? And, when the attribute_column would be
appropriate?

Regards,

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

Re: [GRASS-user] v.to.rast: advice needed [RESOLVED]

[Rich Shepard]

On Wed, 10 May 2023, Rich Shepard wrote:


Which v.db* should I use to find the elevation colum associated with each
contour line?


Long ago I used the GUI and it had a menu to examine the vector map's table.
Now, I just leared that v.db.select will work. There're more columns than I
need, but one does have the elevation data. Back to work ...

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

[GRASS-user] v.to.rast: advice needed

[Rich Shepard]

I need to convert a vector contour map to a raster so I can apply the
hydrologic models modules.

Reading the v.to.rast manual page I learned that I needed to add categories
to the input contour map. Running v.category added no categories: "0
features added."

v.info does not tell me anything about the elevation values of the contour
lines. Looking at the v.* modules, and trying v.univar, didn't help. I could
try v.to.3d, but I need information about the vector map's contents.

Which v.db* should I use to find the elevation colum associated with each
contour line?

TIA,

Rich


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

Re: [GRASS-user] v.clip error I don't understand

[Rich Shepard]

On Wed, 10 May 2023, Micha Silver wrote:


Your v.in.ascii command has create a *line* feature, (the L on the first
line) not an area. Even though the lines connect it's not a boundary, and
there's no centroid, which is required for a closed boundary to be
considered a polygon  area. Have another look at the v.in.ascii man page,
and refer to Example 1 a). You'll need to define the list of corners as B
(not L) and also add another few lines for the centroid.


Micha,

Boy howdy! I missed that completely. I'll learn how to define the centroid.

I suspected it was the point file.

Thanks,

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

Re: [GRASS-user] v.in.ascii syntax help needed

[Rich Shepard]

On Tue, 9 May 2023, Markus Neteler wrote:


https://github.com/OSGeo/grass/blob/main/vector/v.in.ascii/v.in.ascii.html


Markus,

Done.

Regards,

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

Re: [GRASS-user] v.in.ascii syntax help needed

[Rich Shepard]

On Tue, 9 May 2023, Markus Neteler wrote:


Please consider to edit the page right away:

https://github.com/OSGeo/grass/blob/main/vector/v.in.ascii/v.in.ascii.html

In the upper right of the page is a pen symbol. Then you can submit it
as a pull request by saving the changes.


Markus,

Shortly, it's only 6:10 AM here. :-)

Also, I'll add a bug report about v.in.ogr that's been present for a long
time and bites me every time I try to import a FileGDB using the CLI (shell
in a v.t.). Full details in the report I'll file.

Regards,

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

Re: [GRASS-user] v.in.ascii syntax help needed

[Rich Shepard]

On Tue, 9 May 2023, Maris Nartiss wrote:


On the first row you have specified a line with 5 coordinates and one
category (L 5 1). You have not provided the last line containing that one
category. Just add „1 1“ (layer 1, cat 1) as a last row and you should be
fine.


Māris.

Thank you. I searched the manual page to learn what the first and last lines
in the example meant, but didn't find what they represent.

So, on the top line 'L' means to draw lines, '5' means 5 data rows, and '1'
means one category. And on the bottom line the layer and category number are
defined.

I'll add a recommendation to add these explanations to the manual page on
the bug/feature request web page.

Best regards,

Rich

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

[GRASS-user] v.in.ascii syntax help needed

[Rich Shepard]

The v.in.ascii manual has an exmple of a standard input file with
elevations. I want to import a rectangle defining the analysis area mask. My
input file has a syntax error and I don't see what it is when I examine the
manual page.

Input file:
L 5 1
2306066.31 224201.00
2307121.58 224201.00
2307121.58 223165.80
2306066.31 223165.80
2306066.31 224401.00

Grass error message:
GRASS Oregon/analysis_area:analyses > v.in.ascii -zn 
in=$HOME/projects/oregon/northside-rock/data/analysis-area.txt out=anal_mask 
format=standard columns='x double precision, y double precision,' x=1 y=2 cat=0 --o
WARNING: End of ASCII file reached before end of categories
ERROR: Import failed

If I remove the cat=0 option I trigger the same error.

TIA,

Rich

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

Re: [GRASS-user] r.in.gdal: geoTIFF file no data?

[Rich Shepard]

On Fri, 5 May 2023, Micha Silver wrote:


This is most probably an RGB color image that GRASS has split into three color 
bands.


Mica,

It could be, but when I look at the little bit that displays it's all grey
tones.


I don't see from the output that each band has the same data. You'd have
to run r.univar on each band to get the statistics (mean, etc)



Can you view the original tif in a graphics program (or QGIS) to see
what's there?


Micha,

Nope. Qgis does nothing when I try to add that .tif file as a raster layer,
and GIMP presents a solid black rectangle.

I'm going to try to load any other geoTIFF files available.

Apparently no one has uncorrupted digital topography for this area. I've
asked the Oregon LiDAR Consortium's GIS manager to see if he can wrangle
something from the one data set he said loaded in his ARC/gis, and I've
asked the USGS National Map Team for help getting usfull data from their
database.

Thanks,

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

[GRASS-user] Vector map appears empty of detail data

[Rich Shepard]

I need help: there's only one digital topographic data set that includes my
client's operational area. That data set imports into grass with v.in.ogr
and has all the expected files in the vector/ subdirectory.

When I view it with d.vect map=usgs_dem display=shape I see a wide screen
filled with solid blue blocks. Zooming in I see no details. I assume this
one file covers a very wide range of 7.5" topograhic quads and I see no
identifying information in them.

The data subdirectory is uploaded to  and I
ask for help in learning if there is information in it that allows me to get
to the one map I need and use those data for hydrologic analyses.

Thanks in advance,

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

Re: [GRASS-user] Is this a bug in 8.3.dev? [RESOLVED]

[Rich Shepard]

On Fri, 5 May 2023, Rich Shepard wrote:


If the re-installation of numpy doesn't fix the problem I build and
install the 8.2.2 source which will replace the development code
installed. I must get hydrological analyses done by Monday so I don't
really care which grass version I run.


Markus, et al.:

To my pleasant surprise, re-building/re-installing python3-numpy-1.22.3
fixed the monitor issue. The only reason that comes to mind is that the
first install was in parallel with python2 and python2-numpy and grass was
still looking for the latter even though it was gond and the laptop
rebooted.

I've run Slackware for 20 years now and haven't had this issue with any
SlackBuilds.org packages before. Regardless I can now meet client
expectations.

Thanks for pointing me in the right direction.

I have a question about a multi-layer FileGDB where each layer has a
different CRS and I'll aske that on gitter.

Regards,

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

Re: [GRASS-user] Is this a bug in 8.3.dev?

[Rich Shepard]

On Fri, 5 May 2023, Markus Neteler wrote:


Still your numpy installation appears to be broken. Perhaps
python3-numpy-1.22.3-x86_64-1.SBo does not match your python version at
binary level?


Markus,

I'm rebuilding python3-numpy and will re-install it. It's not likely to be a
mis-match between the Slackware cord python3 and the SBo numpy because it's
well tested before being added to the repo.

I also have openBLAS installed; it's an optimized BLAS and includes LAPACK.

If the re-installation of numpy doesn't fix the problem I build and install
the 8.2.2 source which will replace the development code installed. I must
get hydrological analyses done by Monday so I don't really care which grass
version I run.

Thanks,

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

Re: [GRASS-user] Is this a bug in 8.3.dev?

[Rich Shepard]

On Thu, 4 May 2023, Markus Neteler wrote:


Are these directories writable?


Markus,

Yes, they are.


Not now, this will not necessarily help.
There is an easy debugging option integrated:

# switch on
g.gisenv set="DEBUG=1"
d.mon wx0


Very interesting:

GRASS NSR_TaxLot/PERMANENT:~ > g.gisenv set="DEBUG=1"
D1/1: G_set_program_name(): g.gisenv
D1/1: G_set_program_name(): g.gisenv
GRASS NSR_TaxLot/PERMANENT:~ > d.mon wx0
D1/1: G_set_program_name(): d.mon
D1/1: Monitor width/height = 720/480
D1/1: Monitor name=wx0, pyfile = 
/data1/grassdata/NSR_TaxLot/PERMANENT/.tmp/caddis.appl-ecosys.com/MONITORS/wx0/render.py
D1/1: Monitor name=wx0, 
envfile=/data1/grassdata/NSR_TaxLot/PERMANENT/.tmp/caddis.appl-ecosys.com/MONITORS/wx0/env
D1/1: Monitor name=wx0, cmdfile = 
/data1/grassdata/NSR_TaxLot/PERMANENT/.tmp/caddis.appl-ecosys.com/MONITORS/wx0/cmd
D1/1: G_set_program_name(): g.gisenv
D1/1: G_set_program_name(): g.gisenv
GRASS NSR_TaxLot/PERMANENT:~ > D1/1: G_set_program_name(): g.gisenv
D1/1: grass.script.core.start_command(): g.gisenv -n
D1/1: G_set_program_name(): g.gisenv
wxnviz.py: This module requires the NumPy module, which could not be imported. 
It probably is not installed (it's not part of the standard Python 
distribution). See the Numeric Python site (http://numpy.scipy.org) for 
information on downloading source or binaries.
D1/1: grass.script.core.start_command(): g.message -v message=Starting map display 
...
D1/1: G_set_program_name(): g.message
D1/1: grass.script.core.start_command(): g.gisenv set=MONITOR_WX0_PID=27366
D1/1: grass.script.core.start_command(): g.gisenv -n
D1/1: G_set_program_name(): g.gisenv
D1/1: grass.script.core.start_command(): g.proj -p
D1/1: grass.script.core.start_command(): g.region -ugpc
D1/1: grass.script.core.start_command(): g.region -ugpc
D1/1: grass.script.core.start_command(): g.region -ugpc
D1/1: grass.script.core.start_command(): g.region -ugpc

D1/1: G_set_program_name(): g.gisenv
D1/1: G_set_program_name(): g.gisenv
GRASS NSR_TaxLot/PERMANENT:~ >

and the GUI window displayed.


# switch off
g.gisenv set="DEBUG=0"


Why are lines repeated?

And, python3-numpy-1.22.3-x86_64-1.SBo is installed.

Thanks,

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

Re: [GRASS-user] Is this a bug in 8.3.dev?

[Rich Shepard]

On Thu, 4 May 2023, Anna Petrášová wrote:


Rich, it would be extremely helpful, if you always show the errors you are
getting, otherwise, it's very difficult for us to help you.


Anna,

My apologies; I do know better.

Here's the session:

GRASS metro100/PERMANENT:~ > g.list type=vect
met100
GRASS metro100/PERMANENT:~ > d.mon start=wx0
ERROR: Monitor  already running
GRASS metro100/PERMANENT:~ > d.mon stop=wx0
WARNING: Unable to open file
 

GRASS metro100/PERMANENT:~ >

When I look for that file the MONITORS subdirectory does not exist:

[rshepard@caddis ~]$ cd 
/data1/grassdata/metro100/PERMANENT/.tmp/caddis.appl-ecosys.com/
[rshepard@caddis caddis.appl-ecosys.com]$ ls
[rshepard@caddis caddis.appl-ecosys.com]$

Re-install grass?

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

Re: [GRASS-user] Is this a bug in 8.3.dev?

[Rich Shepard]

On Wed, 3 May 2023, Michael Barton wrote:


The setup of my Mac is quite different from on Linux of course, but in my
GRASS.sh, GRASS_PYTHON is set to point to the actual file that launches
the correct python.

# set Python
export GRASS_PYTHON="$GISBASE/python.app/Contents/MacOS/python"

Perhaps giving it a path rather than simply calling python3 will help.


Michael,

I had tried pointing grass to /usr/bin/python3 but it didn't like that.
Here, /usr/bin/python3 points to /usr/bin/python3.9. This allows python3
minor version upgrades be found using the same command.

Somehow, the display monitors became FUBAR. Grass tells me that wx? is
running, but doesn't display the GUI, and I cannot stop them. It cannot find
the process ID (the .pid) file because there are no d.mon wx? processes
running. A reboot doesn't clear that clog. If I can get `git pull` to work
I'll rebuild and re-install grass and see if that fixes it.

Thanks,

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

Re: [GRASS-user] Is this a bug in 8.3.dev?

[Rich Shepard]

On Wed, 3 May 2023, Helmut Kudrnovsky wrote:


why not, as Anna already suggested in an earlier reply, _fix_ your
operating system by removing python 2.x from your linux box and keep only
python 3 there.



for a long time now, GRASS GIS 8.x switched to python 3.


Helmut,

I've no idea whether any other applications still require python2.
Regardless, I removed python2 from the laptop. Now GRASS_PYTHON=python3.9.

When I restart grass there's still a monitor issue. When I enter `d.mon
start=wx0` grass tells me it's already running. When I enter `d.mon
stop=wx0` grass tells me there is no wx0 monitor running.

How do I correct this?

Thanks,

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

[GRASS-user] Is this a bug in 8.3.dev?

[Rich Shepard]

I have python3-3.9.16 installed on Slackware64-15.0. I'm building from the
github dev source.

When I used d.mon start=wx0 grass told me it could not find a numpy for
python-2.7.x.

Anna suggested I add GRASS_PYTHON to ~/.bash_profile. I did and learned that
`export GRASS_PYTHON=python3-3.9.16` wasn't accepted by grass, neither was
`export GRASS_PYTHON=python` (which is an alias for python3). What seemed to
work was `export GRASS_PYTHON=/usr/bin/python`.

Starting grass to a location's PERMANENT mapset, g.list type=vect tells me I
have a map named metro100 there.

Unfortunately, I cannot start a monitor:
d.mon start=wx0
GRASS metro100/PERMANENT:~ >   File 
"/usr/local/grass83/gui/wxpython/mapdisp/main.py", line 252
**args,
  ^
SyntaxError: invalid syntax
^C
GRASS metro100/PERMANENT:~ > d.mon start=wx1
GRASS metro100/PERMANENT:~ >   File 
"/usr/local/grass83/gui/wxpython/mapdisp/main.py", line 252
**args,
  ^
SyntaxError: invalid syntax

Is this a bug or something I've done here?

Regards,

Rich

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

Re: [GRASS-user] LiDAR data CRS issue

[Rich Shepard]

On Tue, 2 May 2023, Rich Shepard wrote:


I don't know if QGIS, sagaGIS, or R could read the hdr.adf that grass
cannot.


Just for giggles, I opened qgis-3.30.0, pointed it to the 2014_OLC_Metro
Bare_Earth data setand it opened a window (see attached) that is quite
useless. It also reported that the CRS was unknown.

I've used the Oregon LiDAR data for years on projects across the state where
there is coverage and have not before encounted the problems this quadrangle
has.

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

Re: [GRASS-user] LiDAR data CRS issue

[Rich Shepard]

On Sat, 29 Apr 2023, Rich Shepard wrote:


I've defined a location using NAD83(2011) / Oregon North (ft). But, the
prj.adf file for the data is:
ProjectionLAMBERT
Spheroid  GRS80
Units 3.280839895013123
ZunitsNO
Xshift0.0
Yshift0.0
Parameters
 43  0  0.0 /* 1st standard parallel
 45 30  0.0 /* 2nd standard parallel
-120 30  0.0 /* central meridian
 41 45  0.0 /* latitude of projection's origin
40.0 /* false easting (meters)
0.0 /* false northing (meters)

This is EPSG: 7019, but it's not a CRS, is it?

How do I define a location that will accept these data?


It turns out that all but one of the LiDAR data collections are corrupted;
the hosting agency cannot import them in their $$$ ESRI software. The one they
can import won't import in grass.

I gave the data manager Lat/Lon corner values for coverage that meets my
needs and he'll try to make a Shapefile that covers that area. I should be
able to import the shapefile then run it through v.to.rast with sufficient
accuracy.

I don't know if QGIS, sagaGIS, or R could read the hdr.adf that grass
cannot.

My thanks to all who tried to help,

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

Re: [GRASS-user] Need help importong LiDAR file with r.in.gdal

[Rich Shepard]

On Mon, 1 May 2023, Rich Shepard wrote:


Coordinate System is:
PROJCRS["unnamed",
   BASEGEOGCRS["Unknown datum based upon the GRS 1980 ellipsoid",
   DATUM["Not specified (based on GRS 1980 ellipsoid)",
   ELLIPSOID["GRS 1980",6378137,298.257222101,
   LENGTHUNIT["metre",1]]],
   PRIMEM["Greenwich",0,
   ANGLEUNIT["degree",0.0174532925199433]],
   ID["EPSG",4019]],
   CONVERSION["unknown",
   METHOD["Lambert Conic Conformal (2SP)",
   ID["EPSG",9802]],
   PARAMETER["Latitude of false origin",41.75,
   ANGLEUNIT["degree",0.0174532925199433],
   ID["EPSG",8821]],
   PARAMETER["Longitude of false origin",-120.5,
   ANGLEUNIT["degree",0.0174532925199433],
   ID["EPSG",8822]],
   PARAMETER["Latitude of 1st standard parallel",43,
   ANGLEUNIT["degree",0.0174532925199433],
   ID["EPSG",8823]],
   PARAMETER["Latitude of 2nd standard parallel",45.5,
   ANGLEUNIT["degree",0.0174532925199433],
   ID["EPSG",8824]],
   PARAMETER["Easting at false origin",1312335.95800525,
   LENGTHUNIT["user-defined",0.3048],
   ID["EPSG",8826]],
   PARAMETER["Northing at false origin",0,
   LENGTHUNIT["user-defined",0.3048],
   ID["EPSG",8827]]],
   CS[Cartesian,2],
   AXIS["(E)",east,
   ORDER[1],
   LENGTHUNIT["user-defined",0.3048]],
   AXIS["(N)",north,
   ORDER[2],
   LENGTHUNIT["user-defined",0.3048]]]
Data axis to CRS axis mapping: 1,2
Origin = (672763.500,1467820.500)
Pixel Size = (3.000,-3.000)
Corner Coordinates:
Upper Left  (  672763.500, 1467820.500) (123d 0'19.54"W, 45d44'59.57"N)
Lower Left  (  672763.500, 1421305.500) (122d59'59.58"W, 45d37'20.60"N)
Upper Right (  706054.500, 1467820.500) (122d52'30.33"W, 45d45' 9.33"N)
Lower Right (  706054.500, 1421305.500) (122d52'11.40"W, 45d37'30.34"N)
Center  (  689409.000, 1444563.000) (122d56'15.21"W, 45d41'15.03"N)


If these are valid values why might grass have problems importing the map?

Regards,

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

Re: [GRASS-user] Map not found?

[Rich Shepard]

On Tue, 2 May 2023, Anna Petrášová wrote:


Rich, perhaps you want to consider asking these questions on Gitter?
https://gitter.im/grassgis/community
I think it's better suited for these questions.


Anna,

Okay. I have a question about pulling from the github repo; my syntax is not
working. I'll get an account there and ask there because I didn't see the
answer in the grass wiki.

Regards,

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

Re: [GRASS-user] Map not found? [RESOLVED]

[Rich Shepard]

On Tue, 2 May 2023, Anna Petrášová wrote:


georef doesn't expect a GRASS map, but a georeferenced file.


Anna.

My misunderstanding. Thanks.


ERROR: Unable to read georeferenced file  using GDAL library
GRASS NSR_TaxLot/PERMANENT:~ > v.info map=pernit_area
ERROR: Vector map  not found

it's a typo


Sigh. Missed it.

Thanks again,

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

Re: [GRASS-user] Map not found?

[Rich Shepard]

On Tue, 2 May 2023, Anna Petrášová wrote:


Could you show the exact commands and output? Are you sure it's not a typo?


Anna,

GRASS NSR_TaxLot/PERMANENT:~ > g.mapsets -p
Accessible mapsets:
PERMANENT
GRASS NSR_TaxLot/PERMANENT:~ > g.list type=vect
permit_area
GRASS NSR_TaxLot/PERMANENT:~ > g.proj -g georef=permit_area
ERROR 4: permit_area: No such file or directory
ERROR: Unable to read georeferenced file  using GDAL library
GRASS NSR_TaxLot/PERMANENT:~ > v.info map=pernit_area
ERROR: Vector map  not found

g.list finds the vector file in the PERMANENT mapset so I expected to learn
details using g.proj and v.info.

Regards,

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

[GRASS-user] Map not found?

[Rich Shepard]

I'm working on the command line with the development version.

I have a vector area map called 'permit_area' in the PERMANENT mapset. When I
check using 'g.list type=vect' the map name is displayed. But, when I ask
g.proj or v.info to tell me about that map they tell me 'permit_area not
found.'

What might cause this behavior?

TIA,

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

Re: [GRASS-user] Need help importong LiDAR file with r.in.gdal

[Rich Shepard]

On Mon, 1 May 2023, Markus Neteler wrote:


What does it show in GDAL?


Markus,

I forgot about gdalinfo and the file to which it's applied.

For this data set:
$ gdalinfo hdr.adf
Driver: AIG/Arc/Info Binary Grid
Files: .
   ./prj.adf
   ./w001001.adf
   ./w001001x.adf
   ./sta.adf
   ./metadata.xml
   ./dblbnd.adf
   ./hdr.adf
Size is 11097, 15505
Coordinate System is:
PROJCRS["unnamed",
BASEGEOGCRS["Unknown datum based upon the GRS 1980 ellipsoid",
DATUM["Not specified (based on GRS 1980 ellipsoid)",
ELLIPSOID["GRS 1980",6378137,298.257222101,
LENGTHUNIT["metre",1]]],
PRIMEM["Greenwich",0,
ANGLEUNIT["degree",0.0174532925199433]],
ID["EPSG",4019]],
CONVERSION["unknown",
METHOD["Lambert Conic Conformal (2SP)",
ID["EPSG",9802]],
PARAMETER["Latitude of false origin",41.75,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8821]],
PARAMETER["Longitude of false origin",-120.5,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8822]],
PARAMETER["Latitude of 1st standard parallel",43,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8823]],
PARAMETER["Latitude of 2nd standard parallel",45.5,
ANGLEUNIT["degree",0.0174532925199433],
ID["EPSG",8824]],
PARAMETER["Easting at false origin",1312335.95800525,
LENGTHUNIT["user-defined",0.3048],
ID["EPSG",8826]],
PARAMETER["Northing at false origin",0,
LENGTHUNIT["user-defined",0.3048],
ID["EPSG",8827]]],
CS[Cartesian,2],
AXIS["(E)",east,
ORDER[1],
LENGTHUNIT["user-defined",0.3048]],
AXIS["(N)",north,
ORDER[2],
LENGTHUNIT["user-defined",0.3048]]]
Data axis to CRS axis mapping: 1,2
Origin = (672763.500,1467820.500)
Pixel Size = (3.000,-3.000)
Corner Coordinates:
Upper Left  (  672763.500, 1467820.500) (123d 0'19.54"W, 45d44'59.57"N)
Lower Left  (  672763.500, 1421305.500) (122d59'59.58"W, 45d37'20.60"N)
Upper Right (  706054.500, 1467820.500) (122d52'30.33"W, 45d45' 9.33"N)
Lower Right (  706054.500, 1421305.500) (122d52'11.40"W, 45d37'30.34"N)
Center  (  689409.000, 1444563.000) (122d56'15.21"W, 45d41'15.03"N)
Band 1 Block=256x16 Type=Float32, ColorInterp=Undefined
  Min=11.370 Max=1163.480
  NoData Value=-3.4028235e+38

Yet ARC/gis apparently has no issues with it.

Regards,

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

[GRASS-user] Need help importong LiDAR file with r.in.gdal

[Rich Shepard]

I'm trying to import a LiDAR data set. I've used EPSG:6559 while the data
source manager tells me it imports into ARC/gis using EPSG:6557. I've tried
both and grass doesn't work for me regardless of which code I use.

I create a location:
grass -c EPSG:6557 /data1/grassdata/Metro_LiDAR

Then import the data set (N.B. a copy of the data source tarball is on the
fileconvoy.com web site; see below):
r.in.gdal in=Bare_Earth/be45122f8/hdr.adf out=topo_2010 mem=2000 --o

GRASS returns:
ERROR: Projection of dataset does not appear to match current location.

   Location PROJ_INFO is:
   name: NAD83(2011) / Oregon GIC Lambert (ft)
   datum: nad83_2011
   ellps: grs80
   proj: lcc
   lat_0: 41.75
   lon_0: -120.5
   lat_1: 43
   lat_2: 45.5
   x_0: 39.984
   y_0: 0
   no_defs: defined

   Dataset PROJ_INFO is:
   name: unnamed
   ellps: grs80
   proj: lcc
   lat_0: 41.75
   lon_0: -120.5
   lat_1: 43
   lat_2: 45.5
   x_0: 40
   y_0: 0
   no_defs: defined

   Difference in: datum

   In case of no significant differences in the projection definitions,
   use the -o flag to ignore them and use current location definition.
   Consider generating a new location from the input dataset using the
   'location' parameter.

I added the -o option to r.in.gdal and this is the result:
r.in.gdal -o 
in=$HOME/projects/oregon/northside-rock/data/LDQ-45122F8/2014-OLC-Metro/Bare_Earth/be45122f8/hdr.adf
 out=topo_2010 mem=2000 --o
Over-riding projection check
Importing raster map ...
ERROR 1: Block is corrupt, block size was 21532, but expected to be 16384.
ERROR 1: 
/home/rshepard/projects/oregon/northside-rock/data/LDQ-45122F8/2014-OLC-Metro/Bare_Earth/be45122f8,
 band 1: IReadBlock failed at X offset 15, Y offset 308: Block is corrupt, 
block size was 21532, but expected to be 16384.
ERROR: Unable to read row 4928

If the file loads into ARC/gis why not into grass?

I do not see why this isn't working here. I've uploaded the Bare_Earth
directory to
http://www.fileconvoy.com/dfl.php?id=g4e3d18b830b60bef10004916731ceed9a68e0d28c3.
It's a 474M file.

I need to learn why I have problems importing the data using either EPSG
code, ignoring the data project by override or not.

Regards,

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

Re: [GRASS-user] wxPython cannot find installed module

[Rich Shepard]

On Mon, 1 May 2023, Anna Petrášová wrote:


There is GRASS_PYTHON:
https://grass.osgeo.org/grass82/manuals/variables.html

But I have never used it myself. Note that we don't support Python 2
anymore.


Anna,

Then I wonder why this clean 15.0 installation on the ThinkPad didn't
automatically use python3. Guess I'll add the environmenal variable to my
.bash_profile.

Thanks,

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

Re: [GRASS-user] wxPython cannot find installed module

[Rich Shepard]

On Mon, 1 May 2023, Anna Petrášová wrote:


When you run GRASS, go to terminal, type "python", press Enter and look
what the version of Python you use:


Anna,

It's the 2.7.18 version. Is there a configuration file in which I can
specify python3?

Regards,

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

Re: [GRASS-user] Re-projection fails

[Rich Shepard]

On Mon, 1 May 2023, Micha Silver wrote:


First comment: I think you should not have GRASS map names starting with a 
digit.


Micha,

I should know better. Darn! 

Can you change the above to
output=topo_2010


Done.


The first run of r.proj (with the -g flag) only gives you the target
region settings. You now need to set the region with those settings, and
then run r.proj again (without -g) do actually do the work.



g.region -ap $NSR



r.proj loc=Dixie_Mountain_2010_LiDAR map=PERMANENT in=2010_topo method=lanczos 
mem=2000 output=topo_2010 --o


I wondered about that. I've certainly forgotten a lot of grass since I last
used it.

All fixed now.

Many thanks for your patience, Micha.

Regards,

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

[GRASS-user] Re-projection fails

[Rich Shepard]

I've started a new thread on this issue: it's more specific.

The script that imports the LiDAR topographic map works:

GRASS Dixie_Mountain_2010_LiDAR/PERMANENT:~ > r.in.gdal 
in=$HOME/projects/oregon/northside-rock/data/LDQ-45122F8/2010-USACE-Columbia-River/Bare_Earth/be45122f8/hdr.adf
 out=2010_topo mem=2000 --o
Importing raster map <2010_topo>...
 100%
GRASS Dixie_Mountain_2010_LiDAR/PERMANENT:~ > g.list type=raster
2010_topo

The imported 2010_topo exists in the designated location and mapset.

But, the script to re-project this map fails. I think it has something to do
with how I'm mis-using Micha's suggestion of assigning the re-projected
output to an environmental variable, NSR.

grass /data1/grassdata/Oregon/PERMANENT

g.mapset -c NSR_2010_DEM

GRASS Oregon/NSR_2010_DEM:~ > NSR=`r.proj -g loc=Dixie_Mountain_2010_LiDAR 
map=PERMANENT in=2010_topo method=lanczos mem=2000 --o`
Input map <2010_topo@PERMANENT> in location :
Selected PROJ pipeline:
+proj=pipeline +step +inv +proj=utm +zone=10 +ellps=GRS80 +step +proj=lcc
+lat_0=43.7 +lon_0=-120.5 +lat_1=46 +lat_2=44.3
+x_0=250 +y_0=0 +ellps=GRS80

GRASS Oregon/NSR_2010_DEM:~ > g.list type=rast
GRASS Oregon/NSR_2010_DEM:~ >

There's no output and I'm not seeing why that is.

TIA,

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

Re: [GRASS-user] wxPython cannot find installed module

[Rich Shepard]

On Mon, 1 May 2023, Anna Petrášová wrote:


You are likely using Python 3 already. Why don't you try to see which one
you use as I suggested?



Apparenly so. My Slackware64-15.0 includes python2-2.7.18,
python3-3.9.10, and python3-numpy-1.22.3. No python2-numpy.


Anna, As I wrote: python3-3.9.10 and python3-numpy-1.22.3 are installed,
along with python2 and the last python2-numpy.

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

Re: [GRASS-user] wxPython cannot find installed module

[Rich Shepard]

On Mon, 1 May 2023, Anna Petrášová wrote:


The error comes from this:
from numpy import matrix



Is it possible you have different Python installations on your computer?
Try running a python shell from an active GRASS session and running the
import command and see what it gives you.


Anna,

Apparenly so. My Slackware64-15.0 includes python2-2.7.18, python3-3.9.10, and
python3-numpy-1.22.3. No python2-numpy.

Will GRASS be moving to Python3 some time?

Thanks,

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

Re: [GRASS-user] Region doesn't match EPSG

[Rich Shepard]

On Mon, 1 May 2023, Micha Silver wrote:


GRASS NorthsideRock/PERMANENT:~ > g.region -ap NSR


I guess you're missing the '$' to recognize NSR as a shell variable.


Micha,

I missed that. Mea culpa!

Thanks,

Rich

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

Re: [GRASS-user] Region doesn't match EPSG

[Rich Shepard]

On Sun, 30 Apr 2023, Micha Silver wrote:


What you do is run the r.proj module with the '-g' flag. That gives you
the region settings in the current mapset that would match the region of
the input raster from the other mapset. Then you use those setting as
input to g.region. So:

new_region=`r.proj -g location= mapset= 
input=`


g.region -ap $new_region


Micha,

(Reformatted to fit the scrsen)

It's still not working:
GRASS NorthsideRock/PERMANENT:~ > NSR=`r.proj -g
loc=Dixie_Mountain_2010_LiDAR map=Northside_rock_2010_topo in=2010_DEM
out=2010_topo method=lanczos_f mem=2000 --o`

Input map <2010_DEM@Northside_rock_2010_topo> in location
:

Selected PROJ pipeline:
+proj=pipeline +step +inv +proj=utm +zone=10 +ellps=GRS80 +step +proj=lcc
+lat_0=43.7 +lon_0=-120.5 +lat_1=46 +lat_2=44.3
+x_0=250 +y_0=0 +ellps=GRS80

GRASS NorthsideRock/PERMANENT:~ > g.region -ap NSR
ERROR: Region  not found
GRASS NorthsideRock/PERMANENT:~ > g.list type=raster
GRASS NorthsideRock/PERMANENT:~ >

Regards,

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

Re: [GRASS-user] Region doesn't match EPSG

[Rich Shepard]

On Sun, 30 Apr 2023, Micha Silver wrote:


What you do is run the r.proj module with the '-g' flag. That gives you
the region settings in the current mapset that would match the region of
the input raster from the other mapset. Then you use those setting as
input to g.region. So:

new_region=`r.proj -g location= mapset= 
input=`


g.region -ap $new_region


Thanks again, Micha.

Much appreciated,

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

[GRASS-user] Region doesn't match EPSG

[Rich Shepard]

When I invoke grass using a location and PERMANENT map set, and try to
re-project a raster file to it, grass rejects the action because the map to
be transferred has greater boundaries than the target mapset.

The location was created with EPSG:6884
name: NAD83(CORS96) / Oregon North
ellps: grs80
proj: lcc
lat_0: 43.7
lon_0: -120.5
lat_1: 46
lat_2: 44.3
x_0: 250
y_0: 0
no_defs: defined

Starting grass in that location and the PERMANENT mapset I find this region:
g.region -p
projection: 99 (NAD83(CORS96) / Oregon North)
zone:   0
datum:  ** unknown (default: WGS84) **
ellipsoid:  grs80
north:  1
south:  0
west:   0
east:   1
nsres:  1
ewres:  1
rows:   1
cols:   1
cells:  1

What did I do incorrectly? And, how to I fix it so I can reproject the map
to the project's region?

TIA,

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

Re: [GRASS-user] LiDAR data CRS issue

[Rich Shepard]

On Sat, 29 Apr 2023, Markus Neteler wrote:


PROJCRS["NAD83(2011) / Oregon North
(ft)",BASEGEOGCRS["NAD83(2011)",DATUM["NAD83 (National Spatial
Reference System 2011)",ELLIPSOID["GRS
1980",6378137,298.257222101,LENGTHUNIT["metre",1,ID["EPSG",9001]],ID["EPSG",7019]],ID["EPSG",1116]],ID["EPSG",6318]],CONVERSION["SPCS83
Oregon North zone (International feet)",METHOD["Lambert Conic
Conformal (2SP)",ID["EPSG",9802]],PARAMETER["Latitude of false
origin",43.9,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8821]],PARAMETER["Longitude
of false 
origin",-120.5,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8822]],PARAMETER["Latitude
of 1st standard
parallel",46,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8823]],PARAMETER["Latitude
of 2nd standard
parallel",44.6,ANGLEUNIT["degree",0.0174532925199433,ID["EPSG",9102]],ID["EPSG",8824]],PARAMETER["Easting
at false 
origin",8202099.738,LENGTHUNIT["foot",0.3048,ID["EPSG",9002]],ID["EPSG",8826]],PARAMETER["Northing
at false 
origin",0,LENGTHUNIT["foot",0.3048,ID["EPSG",9002]],ID["EPSG",8827]],ID["EPSG",15351]],CS[Cartesian,2,ID["EPSG",4495]],AXIS["Easting
(X)",east],AXIS["Northing
(Y)",north],LENGTHUNIT["foot",0.3048,ID["EPSG",9002]],ID["EPSG",6559]]

More human readable output you get with `projinfo`:

projinfo EPSG:6559
PROJ.4 string:
+proj=lcc +lat_0=43.7 +lon_0=-120.5 +lat_1=46
+lat_2=44.3 +x_0=250.0001424 +y_0=0 +ellps=GRS80
+towgs84=0,0,0,0,0,0,0 +units=ft +no_defs +type=crs



Note that I just showed an example, it is not necessarily the code you
are hunting for.
Just to illustrate a method.


Markus,

I found that ESPG code yesterday and created a location for it. The problem
is that the prj.adf file does not use that EPSG code:

ERROR: Projection of dataset does not appear to match current location.

   Location PROJ_INFO is:
   name: NAD83(2011) / Oregon North (ft)
   datum: nad83_2011
   ellps: grs80
   proj: lcc
   lat_0: 43.7
   lon_0: -120.5
   lat_1: 46
   lat_2: 44.3
   x_0: 250.0001424
   y_0: 0
   no_defs: defined

   Dataset PROJ_INFO is:
   name: unnamed
   ellps: grs80
   proj: lcc
   lat_0: 41.75
   lon_0: -120.5
   lat_1: 43
   lat_2: 45.5
   x_0: 40
   y_0: 0
   no_defs: defined

   Difference in: datum

I've uploaded the Bare_Earth subdirectory to

where is will stay for 5 days.

There's also a Shapefiles/ directory with several maps. The
OLC_METRO_TAF_7_5_OGIC_2011.prj file contains:

PROJCS["NAD_1983_2011_Oregon_Statewide_Lambert_Feet_Intl",
GEOGCS["GCS_NAD_1983_2011",
DATUM["D_NAD_1983_2011",
SPHEROID["GRS_1980",
6378137.0,298.257222101]],
PRIMEM["Greenwich",0.0],
UNIT["Degree",0.0174532925199433]],
PROJECTION["Lambert_Conformal_Conic"],
PARAMETER["False_Easting",1312335.958005249],
PARAMETER["False_Northing",0.0],
PARAMETER["Central_Meridian",-120.5],
PARAMETER["Standard_Parallel_1",43.0],
PARAMETER["Standard_Parallel_2",45.5],
PARAMETER["Latitude_Of_Origin",41.75],
UNIT["Foot",0.3048]

Should I use that one instead? I see the DEM and vector files using two
different CRS'.

Regards,

Rich

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

[GRASS-user] LiDAR data CRS issue

[Rich Shepard]

I've defined a location using NAD83(2011) / Oregon North (ft). But, the
prj.adf file for the data is:
ProjectionLAMBERT
Spheroid  GRS80
Units 3.280839895013123
ZunitsNO
Xshift0.0
Yshift0.0
Parameters
  43  0  0.0 /* 1st standard parallel
  45 30  0.0 /* 2nd standard parallel
-120 30  0.0 /* central meridian
  41 45  0.0 /* latitude of projection's origin
40.0 /* false easting (meters)
0.0 /* false northing (meters)

This is EPSG: 7019, but it's not a CRS, is it?

How do I define a location that will accept these data?

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

[GRASS-user] wxPython cannot find installed module

[Rich Shepard]

I started grass with the wxGUI. It loaded but the v.t. displayed this
message:

Launching  GUI in the background, please wait... GRASS
Oregon_North_State_Plane_ft/PERMANENT:
~ > wxnviz.py: This module requires the NumPy module, which could not be
imported. It probably is not installed (it's not part of the standard Python
distribution). See the Numeric Python site (http://numpy.scipy.org) for
information on downloading source or binaries.

Installed here: python3-numpy-1.22.3-x86_64-1_SBo

Is there a way to let wxnviz.py know that numpy is installed, or should I
just ignore it?

Rich



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

Re: [GRASS-user] Specify window size when grass invoked

[Rich Shepard]

On Fri, 28 Apr 2023, Micha Silver wrote:


On my system it's ~/.grass8/wx.json, a json formatted config file.


Micha,

Same here. I didn't use more characers, only .grass.

I think you should try to resize with the "handles" on the window corners. 
Then using the menu "Settings->Preferences" check the option "Save current

window layout as default", and click "Save".  That should keep the window
size for next time.


Will do. Thanks again,

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

[GRASS-user] Specify window size when grass invoked

[Rich Shepard]

I'm running grass-8.x on a laptop with a 14" screen. Starting grass within a
virtual terminal opens a GUI window that exceeds the monitor's width and
height. Is there a place where I can define the window's geometry globally?

I don't see a config file, such as ~/.grassrc.

TIA,

Rich

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

Re: [GRASS-user] Shell scripts to define GISDATABASE, location, and mapset; import data

[Rich Shepard]

On Fri, 28 Apr 2023, Micha Silver wrote:


Here's your script with corrections


Micha,

Thanks very much. You've reminded me of what I've forgotten and taught me
things I didn't know. I'll now be quickly back up to speed with grass.

Best regards,

Rich

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

[GRASS-user] Shell scripts to define GISDATABASE, location, and mapset; import data

[Rich Shepard]

I write shell scripts to run modules for analyses, but have always used the
GUI to define locations and/or mapsets before importing data even with starting
grass with the -c option.

What I want to do now when importing project data is to have a script that
defines the location and mapset then imports the data.

I've read the startup program manual page
 several times today
without seeing how to specify the all three parameters to define a location
and mapset and immediately follow that with a data import command; is --exec
really necessary?

An example file is attached. Please correct my format and I'll use this as a
template for all data imports.

TIA,

Rich

quarry-property.sh
Description: Bourne shell script
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Importing LiDAR data

[Rich Shepard]

On Thu, 27 Apr 2023, Maris Nartiss wrote:


Peaking at the file list you provided, you are dealing with already
processed LiDAR data in raster (and shapefile) format. Thus r.in.gdal is
the way to go.

r.in.las (obsolete) and r.in.pdal (the new way to go) deal with raw
point clouds in LAS format. They perform point binning according to
chosen criteria to generate a raster.


Māris,

Thanks very much for confirming what I thought was the case.

Much appreciated,

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

Re: [GRASS-user] Importing LiDAR data

[Rich Shepard]

On Thu, 27 Apr 2023, Rich Shepard wrote:


There are raster LiDAR modules (r.in.gdal, r.in.lidar, r.in.pdal) and the
latter two work with .las files, so I assume that my data use r.in.gdal.
It's been a long time since I've build LiDAR maps and I ask for the proper
command lines to 1) set the location for import and 2) import the data. An
example file tree is 10,008 lines long and downloadable (for 5 days) from:
<https://tinyurl.com/mmkf8pcd>.


For now, I'm interested in only the bare earth data; learning which files to
use for the other data is still valuable.

Regards,

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

[GRASS-user] Importing LiDAR data

[Rich Shepard]

There are raster LiDAR modules (r.in.gdal, r.in.lidar, r.in.pdal) and the
latter two work with .las files, so I assume that my data use r.in.gdal.
It's been a long time since I've build LiDAR maps and I ask for the proper
command lines to 1) set the location for import and 2) import the data. An
example file tree is 10,008 lines long and downloadable (for 5 days) from:
.

TIA,

Rich

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

Re: [GRASS-user] LiDAR files information commands

[Rich Shepard]

On Thu, 27 Apr 2023, Maris Nartiss wrote:


Do you mean `pdal info file.las`?


Maris,

That's helpful. Many thanks.

Regards,

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

Re: [GRASS-user] LiDAR files information commands

[Rich Shepard]

On Thu, 27 Apr 2023, Vincent Bain wrote:


https://github.com/LAStools/LAStools



Hope this helps !


Vincent,

Thank you.

Regards,

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

[GRASS-user] LiDAR files information commands

[Rich Shepard]

A long time ago I learned here the commands to summarize the pertinent
content of LiDAR data files. I can't find it in my mail records. Please
point me to a source of gdal file information.

TIA,

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

Re: [GRASS-user] Building 8.2.1: not finding OpenBLASS

[Rich Shepard]

On Tue, 25 Apr 2023, Huidae Cho wrote:


The easiest fix would be just download the package and install it using
installpkg.
http://www.slackware.com/~alien/slackbuilds/OpenBLAS/pkg64/15.0/OpenBLAS-0.3.12-x86_64-1alien.txz


Huidae,

That fixed the problem. The source configured, built, and installed as it
had always done in the past.

For the past many years I had a copy of the git repo and would pull changes
when I prepared to run grass and rebuilt and reinstalled from a clean source
tree.

I looked at the Download page on the web site but didn't see the dev source
github repo URL in the source code portion. Does one still exist? If so,
I'll make a new clone of it and continue working with the current source and
reporting issues in the infrequent times they bite me.

Thanks again,

Rich

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

Re: [GRASS-user] Building 8.2.1: not finding OpenBLASS

[Rich Shepard]

On Tue, 25 Apr 2023, Huidae Cho wrote:


Checking the OpenBLAS package from
http://www.slackware.com/~alien/slackbuilds/OpenBLAS/pkg64/15.0/, I think
your OpenBLAS installation is somehow broken.


Hĭdae,

Okay. I'll remove the existing SBo OpenBLAS and replace it with ALIEN Bob's
package.

Results to follow.

Thanks,

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

Re: [GRASS-user] Building 8.2.1: not finding OpenBLASS

[Rich Shepard]

On Tue, 25 Apr 2023, Huidae Cho wrote:


I cannot find any support for OpenBLAS in configure. Maybe, you can try
symlinking libopenblas.so to libblas.so. I use Slackware64-15 too, but I
just use BLAS.


Huidae,

I thought that the line, `--with-blas` included OpenBLAS.

I chose OpenBLAS because the SBo SlackBuild page for grass (for a long
out-of-date 7.8.0; the maintainer hasn't responded to my request for an
update) says that OpenBLAS is optimized and includes LAPACK.

Regards,

Rich

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

[GRASS-user] Building 8.2.1: not finding OpenBLASS

[Rich Shepard]

I'm trying to build 8.2.1 on Slackware64-15.0. My configuration file is:
./configure \
--enable-64bit \
--with-libs=/usr/lib64 \
--with-postgres \
--with-postgres-includes=/usr/include/postgresql/server/ \
--with-postgres-libs=/usr/lib64/postgresql/14/lib/ \
--with-sqlite \
--with-sqlite-includes=/usr/include/ \
--with-sqlite-libs=/usr/lib/ \
--with-cairo \
--with-blas \
--with-lapack \
--with-freetype \
--with-freetype-includes=/usr/include/freetype2 \
--with-cxx \
--with-geos \
--with-gdal \
--with-nls \
--with-python3 \
--with-pthread \
--with-proj-share=/usr/share/proj \
--with-wxwidgets \
--enable-largefile \
--with-openmp \
--with-x \
--with-pdal=/usr/bin/pdal \
--with-libLAS

After checking for needed components the script stops telling me it cannot
locate a BLAS library.

Here:
# ls /usr/lib64 | grep blas
libgslcblas.so@
libgslcblas.so.0@
libgslcblas.so.0.0.0*
liblas.so@
liblas.so.2.4.0*
liblas.so.3@
liblas_c.so@
liblas_c.so.2.4.0*
liblas_c.so.3@
liblaszip.so@
liblaszip.so.6@
liblaszip.so.6.0.0*
libopenblas.so@
libopenblas.so.0@
libopenblasp-r0.3.12.so*

What have I done incorrectly?

TIA,

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

Re: [GRASS-user] Development build not finding PDAL version installed

[Rich Shepard]

On Sun, 12 Feb 2023, Maris Nartiss wrote:


Could you check the config.log file for an exact error message?

There was a fix for PDAL as pdal-config enforces C++11 although it
requires C++17:
https://github.com/OSGeo/grass/commit/cb8293e8d40c02857b3a15bac441f703339ba5fd


Māris,

Gzipped log file attached. Pdal issue starts on line 3185; looks to me that
I need to add an configuation option of `-std=c++11 or -std=gnu++11 compiler
options.` (line 3198). Might that be the solution?

Thanks,

Rich

config.log.gz
Description: GNU Zip compressed data
___
grass-user mailing list
grass-user@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Development build not finding PDAL version installed

[Rich Shepard]

On Sat, 11 Feb 2023, Markus Neteler wrote:


Did you install pdal-dev(el)? (the name depends on your Linux distro)


Markus,

Slackware doesn't distribute partial packages. The unmodified kernel and the
complete upstream packages are what we use.

Regards,

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

[GRASS-user] Development build not finding PDAL version installed

[Rich Shepard]

Trying to build source pulled from the repo failed here:
checking whether to use GDAL... yes
checking for gdal-config... /usr/bin/gdal-config
checking whether to use libLAS... no
checking whether to use PDAL... yes
checking for pdal-config... /usr/bin/pdal-config
configure: error: *** Unable to locate suitable (>=1.7.1) PDAL library.

Yet, installed here is pdal-2.0.1-x86_64-1_SBo, which is certainly newer
than 1.7.1.

Please suggest how I make the installed pdal visible to the build process.

Regards,

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

[GRASS-user] Specifying gisdatabase and locations

[Rich Shepard]

I hope that everyone is staying healthy and avoiding the abundant COVID-19
variants running wild in the world.

My overall gisdbase is /data1/grassdata/ and I've reorganized it so all
general locations (different crs/projections) are there, but all my projects
using GRASS are in a projects/ subdirectory. Each project is a distinct
location with its own collection of mapsets. That way I can import data into
its native projection location then reproject it to specific project
locations.

Reading the startup manual page I do not see how to specify a gisdbase as a
subdirectory of grassdata/ and I don't see an example that works if I try,
for example,

$ grass --text /data1/grassdata/projects/my_current_project_location/.

How do I start grass with a three-directory tree for gisdbase rather than
the default two-directory gisdbase?

Regards,

Rich

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

Re: [GRASS-user] Unsubscribe

[Rich Shepard]

On Wed, 27 Apr 2022, David Frederick Davis wrote:


This has turned into a zombie list, I retired several years ago.


David,

Look at the bottom of a message and click on the text telling us that the
message contains mail list information. You'll have the opportunity to
unsubscribe yourself; the process is self-serve.

HTH,

Rich

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