Good evening and happy weekend!
I am (still) upgrading from 6.4.4 to 7.0.3 and I discovered that the vector
topography of all my data is not upwards compatible so per the instructions at
https://grasswiki.osgeo.org/wiki/Convert_all_GRASS_6_vector_maps_to_GRASS_7 I
am (trying) to us v.build.all
Good evening ... I've downloaded the OSGEO4W GRASS GIS 7.0.3 and msys ... and
that works, but as I am trying to test my scripts the vector topology is no
longer compatible (oh joy) so I am trying to use the steps provided on
On 29/04/16 18:00, Peter Tittmann wrote:
All,
Using GRASS7. I would like to write to postgis from a GRASS vector file,
and would like to be able to append to a table as opposed to create new.
I see that the `-a` flag is not implemented yet in v.out.postgis so I
turned to v.out.ogr. Despite
Whew! ... thank you - that worked.
Just a couple notes: the C:\OSGeo4W/apps/grassX/etc/env.bat file did not have
the GRASS_SH line in it so I just added it as you typed out and it works.
Also for anyone else trying this:
When installing GRASS from OSGEO4W, even if you select 7.0.4RC1 you still
* Markus Neteler [2016-04-29 16:16:23 +0200]:
On Thu, Apr 28, 2016 at 3:19 PM, Markus Neteler wrote:
r.in.aster - Georeference, rectify, and import Terra-ASTER imagery and
relative DEMs using gdalwarp.
All,
Using GRASS7. I would like to write to postgis from a GRASS vector file, and
would like to be able to append to a table as opposed to create new. I see that
the `-a` flag is not implemented yet in v.out.postgis so I turned to v.out.ogr.
Despite having a fully functional GDAL with the OGR
Hi Stefan,
Thanks for the links. From reading the threads and other links below (and links
therein) it seems like your summary is correct. Except the Kelly thesis and the
Neteler (2005) paper show oblique photos (extreme oblique in the thesis). It is
a shame this doesn't seem present in GRASS
On Mon, Apr 11, 2016 at 9:38 AM, roy roy wrote:
...
>
> Also the NOTES section of the g.copy manual page describe something
> that seems to not happen at all, maybe it needs to be updatet ...(?)
Good hint, cleaned up now.
Markus
On Thu, Apr 28, 2016 at 3:19 PM, Markus Neteler wrote:
> r.in.aster - Georeference, rectify, and import Terra-ASTER imagery and
> relative DEMs using gdalwarp.
> https://grass.osgeo.org/grass70/manuals/r.in.aster.html
Forgot to mention:
Hi Marcus,
On 2016-04-29 at 03:17, Markus Neteler wrote:
> Would the eval() function of r.mapcalc be of use? In order to hold the
> interim values? Just guessing, I did not study your need in details.
Yes that does solve it. Thank you for pointing out this solution.
-k.
On Fri, Apr 29, 2016 at 11:50 AM, Salim Razzaz wrote:
...
> So yeah. Make went missing like Markus said. It exists in the __src.rpm
> though. and
> it shows in BUILD after packaging. So I guess it's the spec file. I'm a
> newbie, but a
> curious one.
Great :-)
Here is
Chris,
On Thu, Apr 28, 2016 at 9:35 AM, Bartolomei.Chris
wrote:
> I'm upgrading some scripts to run in GRASS 7.1 (from GRASS 6.4.4) and just
> wanted to point out some missing information on the Changes page:
>
On Thu, Apr 28, 2016 at 01:52:31PM +0200, Martin Landa wrote:
> 2016-04-28 12:03 GMT+02:00 Salim Razzaz :
> > There isn't any directory called 'include' in /usr/lib64/grass-7.0.3/ when
> > I checked. And grass-devel is installed (I ran 'dnf list installed
> >
"Bartolomei.Chris" writes:
> Hi Rainer,
> I had stated that I wasn't 100% sure and just to look into it - I had
> recalled reading about lossy and lossless data some time ago.
> For a quick look into it, Wikipedia has a decent article
>
Hi Rainer,
I had stated that I wasn't 100% sure and just to look into it - I had recalled
reading about lossy and lossless data some time ago.
For a quick look into it, Wikipedia has a decent article
(https://en.wikipedia.org/wiki/Lossless_compression and
Hi,
2016-04-29 9:52 GMT+02:00 Bartolomei.Chris :
> Oh no that is really really bad (for me) ... does this mean all of my
> shell (sh) scripts have to be rewritten in python?
> That may be a ridiculous amount of work ... So much for "upgrading".
> I hope 6.4.4 is
Hi again,
On a second look I tried:
execGRASS("v.in.ascii", flags="n", input="-", output=" outlet1",
Sys_input="636645|218835")
That worked for me on Ubuntu...
Cheers
Stefan
-Original Message-
From: grass-user [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of Roger
Bivand
Oh no that is really really bad (for me) ... does this mean all of my
shell (sh) scripts have to be rewritten in python?
That may be a ridiculous amount of work ... So much for "upgrading".
I hope 6.4.4 is going to be around for a long time then. :(
Chris Bartolomei P.E.
Engineer/Scientist
"Bartolomei.Chris" writes:
[snip (4 lines)]
> The reason I say this is the file
> compression I suggested may cause some data loss ... look into
> lossless data compression algorithms and you'll see what I'm talking
> about.
Could you please elaborate and give some
> I can't find any settings anywhere to get GRASS 7.0.4 to start with a
>unix (shell) command console in Windows 7 like it did in version 6.4.4.
AFAIK msys was dropped in winGRASS 7.
-
best regards
Helmut
--
View this message in context:
Simply, don't.
execGRASS() is for executing single GRASS commands, not a drop-in
replacement for bash.
Try something like creating the point in R with the correct projection, and
write that vector object to your mapset:
library(sp)
library(rgrass7)
pt <- SpatialPointsDataFrame(matrix(c(636645,
On 29/04/16 08:34, Blumentrath, Stefan wrote:
Yes, and maybe allowing for multiple input would be nice for such use cases as
well!?
For rasters this could possibly be done by adding the option to pack a
group.
Moritz
___
grass-user mailing list
On 29/04/16 08:20, Uwe Fischer wrote:
Hello list,
I have two questions concerning v.dissolve. As far as I can see, there
can be only one single column be specified as dissolve item. But I need
to dissolve polygons using several items (up to 6) in one stroke. I
checked out v.extract, too, hoping
Hi Ken,
I have been working on (and struggling with) this as well and did not succeed
yet:
For more info and relevant links see:
https://lists.osgeo.org/pipermail/grass-user/2015-August/072881.html
My lessons so far are that one
a) needs to use i.ortho.* modules from GRASS 6.4 for this
b) you
Hi Ken,
On Apr 6, 2016 6:29 PM, "Ken Mankoff" wrote:
...
> Now, I'd like to do something similar, which is route all stream water 1
grid cell downstream. I can't figure out how to do this. Perhaps this is
beyond the ability of r.mapcalc, or reasonable bash scripting? Hopefully
Hi Jim,
Although this does not solve you pipe issue (you might need to use pipe or fifo
(run: help(pipe) in R for more info) :
If you just want to create a map with one point you could also use “v.edit» in
non interactive mode (I guess), meaning, create a map and add a point.
Or you write your
Yes, and maybe allowing for multiple input would be nice for such use cases as
well!?
Another possibly useful enhancement may be a kind of wrapper script (let`s call
it m.pack/unpack) which would even allow for packing (and unpacking) raster and
vector maps together in one archive...?
Cheers
Hello list,
I have two questions concerning v.dissolve. As far as I can see, there can
be only one single column be specified as dissolve item. But I need to
dissolve polygons using several items (up to 6) in one stroke. I checked out
v.extract, too, hoping that a SQL statement might help me
Hi folks,
I'm upgrading to 7.0.4 from 6.4.4 ... I used to be able to starts GRASS with
MSYS unix console but now I don't get that option and the command console is a
Windows "cmd" window... I can't find any settings anywhere to get GRASS 7.0.4
to start with a unix (shell) command console in
29 matches
Mail list logo