[GRASS-user] why is v.build.all (and many others) a windows batch file and not an executable?

[Bartolomei.Chris]

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 to update the topography.  I had installed GRASS 
with MSYS from OSGEO4W but that goodness uses the unix-like msys shell as the 
command console - which for what I need is perfect ... I can copy/paste 
commands to test as I write shell scripts to do GIS magic. BUT ... go ahead and 
try to run v.build.all ... and nope - it isn't going to let you. Ends up 
v.build.all (and many other modules) are Windows Batch files !! the msys 
command console won't run the GRASS modules that are Windows Batch files.  I 
was able to work around this a little issue by also installing just the regular 
GRASS 7.0.3 (they install in different directories) and run the v.build.all 
from the Windows cmd console (it is the standard command console that runs with 
"normal" 7.0.3 (not from OSGEO4W) but which won't run any of the code I put 
into a shell script because, well, it's unix shell not DOS - hence the need for 
msys)... I was going to drop a note to the OSGEO4W project about the issue but 
the same thing is part of the current (non-OSGEO4W) package ... look in 
\Program Files\GRASS GIS 7.0.3\bin\ and you'll see many executables (compiled 
python scripts I assume) and quite a few Windows Batch files why is this? 
Should they not all be compiled executables ??
I don't understand this and it makes it really hard to create shell scripts to 
run the modules...
Thanks,
Chris

Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.ch...@ensco.com

The information contained in this email message is intended only for the use of 
the individual(s) to whom it is addressed and may contain information that is 
privileged and sensitive. If you are not the intended recipient, or otherwise 
have received this communication in error, please notify the sender immediately 
by email at the above referenced address and note that any further 
dissemination, distribution or copying of this communication is strictly 
prohibited.

The U.S. Export Control Laws regulate the export and re-export of technology 
originating in the United States. This includes the electronic transmission of 
information and software to foreign countries and to certain foreign nationals. 
Recipient agrees to abide by these laws and their regulations -- including the 
U.S. Department of Commerce Export Administration Regulations and the U.S. 
Department of State International Traffic in Arms Regulations -- and not to 
transfer, by electronic transmission or otherwise, any content derived from 
this email to either a foreign national or a foreign destination in violation 
of such laws.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] where is MSYS in GRASS 7?

[Bartolomei.Chris]

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 
(https://grasswiki.osgeo.org/wiki/Convert_all_GRASS_6_vector_maps_to_GRASS_7) 
only to find out that the module v.build.all looks like it is not compiled in 
their distribution ... there are a whole lot of modules in the 
C:\OSGEO4W64\apps\Grass\Grass-7.0.3\bin folder that are Windows Batch Files and 
not Applications, so when you try to run one of them the returned message is 
that the given module is not found...  Is that the way the distribution should 
be ??? The python code is in C:\OSGEO4W64\apps\Grass\Grass-7.0.3\scripts ...
Thanks for any insight. (should I create a new thread?)
:)
Chris

Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.ch...@ensco.com

From: neteler.os...@gmail.com [neteler.os...@gmail.com] On Behalf Of Markus 
Neteler [nete...@osgeo.org]
Sent: Friday, April 29, 2016 2:38 AM
To: Martin Landa
Cc: Bartolomei.Chris; grass-user@lists.osgeo.org; Helmut Kudrnovsky
Subject: Re: [GRASS-user] where is MSYS in GRASS 7?

On Fri, Apr 29, 2016 at 9:59 AM, Martin Landa  wrote:
> 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 going to be around for a long time then.  :(
>
> it's easy to switch to msys. Install grass and msys from OSGeo4W. Edit
> C:\OSGeo4W/apps/grassX/etc/env.bat.
>
> REM set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe
>
> -> > set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe

Perhaps we should more prominently advertise that?
For now added to
https://urldefense.proofpoint.com/v2/url?u=https-3A__trac.osgeo.org_grass_wiki_Grass7_NewFeatures-23Scripts=CwIBaQ=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY=eSqGGjSXr0YxUswQSfgykYnDrmSPZLd9j9J6SVTJFrQ=IiLOmFa9eu-8VxCQPTFbXKK4alAalbMlwhbc35yi6YI=

Markus

The information contained in this email message is intended only for the use of 
the individual(s) to whom it is addressed and may contain information that is 
privileged and sensitive. If you are not the intended recipient, or otherwise 
have received this communication in error, please notify the sender immediately 
by email at the above referenced address and note that any further 
dissemination, distribution or copying of this communication is strictly 
prohibited.

The U.S. Export Control Laws regulate the export and re-export of technology 
originating in the United States. This includes the electronic transmission of 
information and software to foreign countries and to certain foreign nationals. 
Recipient agrees to abide by these laws and their regulations -- including the 
U.S. Department of Commerce Export Administration Regulations and the U.S. 
Department of State International Traffic in Arms Regulations -- and not to 
transfer, by electronic transmission or otherwise, any content derived from 
this email to either a foreign national or a foreign destination in violation 
of such laws.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] PostgreSQL not in v.out.ogr format options

[Moritz Lennert]

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 having a fully functional GDAL with the OGR
PostgreSQL driver installed and functional, when I pass the following
command:

`v.out.ogr -a -m --verbose input=t_lands type=area
output="PG:dbname=cf_tribal" output_layer=foo format=PostgreSQL`

  the response is:

`ERROR: Value  out of range for parameter 
Legal range:
BNA,CSV,CartoDB,Cloudant,CouchDB,DGN,DXF,ESRI_Shapefile,ElasticSearch,GFT,GME,GML,GPKG,GPSBabel,GPSTrackMaker,GPX,GeoJSON,GeoRSS,Geoconcept,JML,KML,MapInfo_File,Memory,ODS,OGR_GMT,PCIDSK,PDF,PGDUMP,S57,SQLite,Selafin,TIGER,WAsP,XLSX`




What does

ogrinfo --formats | grep PostgreSQL

give you ?

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

Re: [GRASS-user] where is MSYS in GRASS 7?

[Bartolomei.Chris]

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 get 
7.0.3 ... and if you install using the Express Desktop Install, you will need 
to go back and run the installer again, then select Advanced Installation and 
then in the Select Packages window, select msys and install that.
Not difficult nor time-consuming, but if you don't there's no msys on your 
system.

Thanks again!
:)
Chris

Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.ch...@ensco.com

From: Martin Landa [landa.mar...@gmail.com]
Sent: Friday, April 29, 2016 12:59 AM
To: Bartolomei.Chris
Cc: Helmut Kudrnovsky; grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] where is MSYS in GRASS 7?

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 going to be around for a long time then.  :(

it's easy to switch to msys. Install grass and msys from OSGeo4W. Edit
C:\OSGeo4W/apps/grassX/etc/env.bat.

REM set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe

->

set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe

Ma

--
Martin Landa
https://urldefense.proofpoint.com/v2/url?u=http-3A__geo.fsv.cvut.cz_gwiki_Landa=CwIBaQ=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY=59HfvpOtRzPLNaYoyY2ldVu4GUDH7aSFxjWA940iQAo=n54WV3gS2tfvNGL0j02xv7Bv1U6LoPxNfagkq4J_VRc=
https://urldefense.proofpoint.com/v2/url?u=http-3A__gismentors.cz_mentors_landa=CwIBaQ=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY=59HfvpOtRzPLNaYoyY2ldVu4GUDH7aSFxjWA940iQAo=R_sWVv5oRnPNIQma4384DEO9AxguRVmZ3EexvHaARDo=

The information contained in this email message is intended only for the use of 
the individual(s) to whom it is addressed and may contain information that is 
privileged and sensitive. If you are not the intended recipient, or otherwise 
have received this communication in error, please notify the sender immediately 
by email at the above referenced address and note that any further 
dissemination, distribution or copying of this communication is strictly 
prohibited.

The U.S. Export Control Laws regulate the export and re-export of technology 
originating in the United States. This includes the electronic transmission of 
information and software to foreign countries and to certain foreign nationals. 
Recipient agrees to abide by these laws and their regulations -- including the 
U.S. Department of Commerce Export Administration Regulations and the U.S. 
Department of State International Traffic in Arms Regulations -- and not to 
transfer, by electronic transmission or otherwise, any content derived from 
this email to either a foreign national or a foreign destination in violation 
of such laws.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] ASTER satellite imagery

[Nikos Alexandris]

* 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.
https://grass.osgeo.org/grass70/manuals/r.in.aster.html


Forgot to mention:
https://grass.osgeo.org/grass70/manuals/i.aster.toar.html

Markus

PS: https://grass.osgeo.org/grass70/manuals/keywords.html#Terra-ASTER


I sent the following from a "wrong" From address!  Here, the same links
once again plus a shell script.

--%<---

* Grant Boxer  [2016-04-27 11:48:59 +0800]:


As the ASTER satellite data in now available free-of-charge, has
anyone
developed a plug-in or work flow to process this imagery?


Importing and converting to digital numbers to radiance values, are
the basics.  The rest of the steps, of "your" interest, I guess can be
achieved with GRASS' multiple raster and imagery related modules.

Haven't used it for a while, but there is
https://grass.osgeo.org/grass70/manuals/r.in.aster.html.

As well, https://grass.osgeo.org/grass70/manuals/i.aster.toar.html.

For the latter, however, as I had some problem (in the past) I used a
shell script: https://grasswiki.osgeo.org/wiki/User:NikosA#ASTER_L1B

Best, Nikos
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

[GRASS-user] PostgreSQL not in v.out.ogr format options

[Peter Tittmann]

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 PostgreSQL driver installed 
and functional, when I pass the following command:

`v.out.ogr -a -m --verbose input=t_lands type=area output="PG:dbname=cf_tribal" 
output_layer=foo format=PostgreSQL`

 the response is:

`ERROR: Value  out of range for parameter 
Legal range: 
BNA,CSV,CartoDB,Cloudant,CouchDB,DGN,DXF,ESRI_Shapefile,ElasticSearch,GFT,GME,GML,GPKG,GPSBabel,GPSTrackMaker,GPX,GeoJSON,GeoRSS,Geoconcept,JML,KML,MapInfo_File,Memory,ODS,OGR_GMT,PCIDSK,PDF,PGDUMP,S57,SQLite,Selafin,TIGER,WAsP,XLSX`

Thanks in advance for any suggestions.

Peter___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] i.rectify and ground-based photos

[Ken Mankoff]

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 7, but it is easy enough to work in 
6.4 when necessary.

I'm going to look into this more and will write back if I make progress. I 
would appreciate the same from you. Feel free to contact me off list if you 
prefer.

I'm also looking into PRACTISE http://www.geosci-model-dev.net/9/307/2016/ and 
ImGRAFT http://imgraft.glaciology.net/ The latter doesn't work off-the-shelf in 
Octave, but perhaps the former will, which would be a nice solution. These two 
tools work in high-relief terrain, which the Kelly thesis mentions and 
demonstrates also.

  -k.

On 2016-04-29 at 02:49, Blumentrath, Stefan  wrote:
> 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 have to have fairly good estimates of you
> camera angle (roll, pitch, yaw) (and preferably use as much as
> possible down-facing angles) c) according to the manual you need at
> least 16 GCPs, as much as possible evenly distributed over your image,
> and it does not seem to work with less than that at all.
>
> In my case the main problem was c), as I only had a few objects I
> could use for GCPs in my camera viewshed and all of them were more or
> less in the background. So, I was missing elements I could recognize
> in foreground. Therefore I placed colored sheets of paper in the
> camera viewshed, which I measured with GPS, so I can match camera
> coordinate system and geographical coordinate system.
>
> Paul Kelly used a different approach for that task (which I
> unfortunately did not manage to try yet):
> http://www.stjohnspoint.co.uk/work/thesis/
>
>
>
>
> -Original Message- From: grass-user
> [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of Ken Mankoff
> Sent: 28. april 2016 19:49 To: grass-user 
> Subject: [GRASS-user] i.rectify and ground-based photos
>
> Hi list,
>
> Is i.rectify only designed for down-looking aerial photography? Or can
> it be used for highly oblique imagery too, for example photos taken
> side-looking from a plane window, or from a mountain-top covering a
> valley?
>
> Thanks,
>
>   -k.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Cannot launch g.copy from GRASS shell

[Markus Neteler]

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
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] ASTER satellite imagery

[Markus Neteler]

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:
https://grass.osgeo.org/grass70/manuals/i.aster.toar.html

Markus

PS: https://grass.osgeo.org/grass70/manuals/keywords.html#Terra-ASTER
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] r.mapcalc & neighborhood modifiers

[Ken Mankoff]

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.
  
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Unable to install add-ons on fedora23

[Markus Neteler]

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 the officia Fedora SPEC file:

GRASS SPEC file spec: http://pkgs.fedoraproject.org/cgit/rpms/grass.git/
  --> http://pkgs.fedoraproject.org/cgit/rpms/grass.git/tree/grass.spec

> So I'll try to find the culprit piece and report back if anything shows up
> (doubt it though, considering my skills).

... I will be happy to generate a RPM from your updated SPEC file then.

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

Re: [GRASS-user] Missing information in the GRASS 7 NewFeatures/OptionChanges web page

[Markus Neteler]

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:
> https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures#Optionschanges
> I may misunderstand what was intended to be listed in this web page, so 
> please forgive me if this is useless...
> (note that these are just the modules I use in some scripts, I didn't go 
> through every module nor did I list any add--ons)
...

thanks for your detailed list, I have merged in your changes:
https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures?action=diff=395

Full page
https://trac.osgeo.org/grass/wiki/Grass7/NewFeatures

Such contributions are very important for us.

Thanks again,
Markus

-- 
Markus Neteler
http://www.mundialis.de - free data with free software
http://grass.osgeo.org
http://courses.neteler.org/blog
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Unable to install add-ons on fedora23

[Salim Razzaz]

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 
> > grass-devel' and it is there)
> 
> it sounds like broken packaging on Fedora. What is content of
> grass-devel package?
 

usr/include/grass/defs/
usr/include/grass/dgl/
usr/include/grass/iostream/
usr/include/grass/vect/
usr/include/grass/ #headers

usr/lib64/pkgconfig/
usr/lib64/ #libgrass_  .so (51)

usr/share/doc/grass-devel/doc/
usr/share/doc/grass-devel/SUBMITTING
usr/share/doc/grass-devel/TODO

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. So I'll try to find the culprit piece and report 
back if anything shows up (doubt it though, considering my skills). 

Thank you all

S






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

Re: [GRASS-user] Copy an existing location

[Rainer M Krug]

"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
> (https://en.wikipedia.org/wiki/Lossless_compression and
> https://en.wikipedia.org/wiki/Lossy_compression) ... as I briefly
> looked through it just now, it appears gz and zip use a lossless
> algorithm so they should be fine to use. Tar (if I remember right)
> concatenates files into an archive and is not a compression tool.
> It looks like lossy algorithms are used more for music and video and some 
> images according to the articles.
> I was just putting up a yellow flag as a caution to look into it as I
> wasn't sure and I wouldn't want to give someone bad advice.

OK - so we can clarify:

*File Compression* is per definition lossless (zip, gz, 7z, bz,
 ...). Otherwise you would not be able to restore ftom archives.

Compression of *content of the file* can be lossy (mp3, jpeg, ...).

Cheers,

Rainer

>
> Chris Bartolomei P.E.
> Engineer/Scientist
> ENSCO, Inc.
> bartolomei.ch...@ensco.com
> 
> From: Rainer M Krug [rai...@krugs.de]
> Sent: Friday, April 29, 2016 12:35 AM
> To: Bartolomei.Chris
> Cc: Janet Choate; grass list
> Subject: Re: Copy an existing location
>
> "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 references where lossless data
> compression (gz, zip) may cause data loss? Especially tar.gz is used for
> ages in archival and backup?
>
> Rainer
>
>
> [snip (46 lines)]
> --
> Rainer M. Krug
> email: Rainerkrugsde
> PGP: 0x0F52F982
>
> The information contained in this email message is intended only for the use 
> of the individual(s) to whom it is addressed and may contain information that 
> is privileged and sensitive. If you are not the intended recipient, or 
> otherwise have received this communication in error, please notify the sender 
> immediately by email at the above referenced address and note that any 
> further dissemination, distribution or copying of this communication is 
> strictly prohibited.
>
> The U.S. Export Control Laws regulate the export and re-export of technology 
> originating in the United States. This includes the electronic transmission 
> of information and software to foreign countries and to certain foreign 
> nationals. Recipient agrees to abide by these laws and their regulations -- 
> including the U.S. Department of Commerce Export Administration Regulations 
> and the U.S. Department of State International Traffic in Arms Regulations -- 
> and not to transfer, by electronic transmission or otherwise, any content 
> derived from this email to either a foreign national or a foreign destination 
> in violation of such laws.
> ___
> grass-user mailing list
> grass-user@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Copy an existing location

[Bartolomei.Chris]

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 
https://en.wikipedia.org/wiki/Lossy_compression) ... as I briefly looked 
through it just now, it appears gz and zip use a lossless algorithm so they 
should be fine to use. Tar (if I remember right) concatenates files into an 
archive and is not a compression tool.
It looks like lossy algorithms are used more for music and video and some 
images according to the articles.
I was just putting up a yellow flag as a caution to look into it as I wasn't 
sure and I wouldn't want to give someone bad advice.

Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.ch...@ensco.com

From: Rainer M Krug [rai...@krugs.de]
Sent: Friday, April 29, 2016 12:35 AM
To: Bartolomei.Chris
Cc: Janet Choate; grass list
Subject: Re: Copy an existing location

"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 references where lossless data
compression (gz, zip) may cause data loss? Especially tar.gz is used for
ages in archival and backup?

Rainer


[snip (46 lines)]
--
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982

The information contained in this email message is intended only for the use of 
the individual(s) to whom it is addressed and may contain information that is 
privileged and sensitive. If you are not the intended recipient, or otherwise 
have received this communication in error, please notify the sender immediately 
by email at the above referenced address and note that any further 
dissemination, distribution or copying of this communication is strictly 
prohibited.

The U.S. Export Control Laws regulate the export and re-export of technology 
originating in the United States. This includes the electronic transmission of 
information and software to foreign countries and to certain foreign nationals. 
Recipient agrees to abide by these laws and their regulations -- including the 
U.S. Department of Commerce Export Administration Regulations and the U.S. 
Department of State International Traffic in Arms Regulations -- and not to 
transfer, by electronic transmission or otherwise, any content derived from 
this email to either a foreign national or a foreign destination in violation 
of such laws.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] where is MSYS in GRASS 7?

[Martin Landa]

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 going to be around for a long time then.  :(

it's easy to switch to msys. Install grass and msys from OSGeo4W. Edit
C:\OSGeo4W/apps/grassX/etc/env.bat.

REM set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe

->

set GRASS_SH=%OSGEO4W_ROOT%\apps\msys\bin\sh.exe

Ma

-- 
Martin Landa
http://geo.fsv.cvut.cz/gwiki/Landa
http://gismentors.cz/mentors/landa
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] rgrass7 syntax for passing a command

[Blumentrath, Stefan]

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
Sent: 29. april 2016 09:18
To: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] rgrass7 syntax for passing a command

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, 218835), ncol=2),
  proj4string=CRS(paste(execGRASS("g.proj", flags="j", intern=TRUE), collapse=" 
")),
  data=data.frame(x=1))
writeVECT(pt, "outlet")

You could create a temporary text file to read in:

tf <- tempfile()
writeLines("636645, 218835", tf)
execGRASS("v.in.ascii", input=tf, output="outlet1", separator=",",
flags="n")

which is closer to your script but less natural.

Yes, grass-stats is a more appropriate list.
 
Roger




-
Roger Bivand
NHH Norwegian School of Economics, Bergen, Norway
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/rgrass7-syntax-for-passing-a-command-tp5263330p5263427.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] where is MSYS in GRASS 7?

[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 going to be around for a long time then.  :(

Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.ch...@ensco.com

From: grass-user [grass-user-boun...@lists.osgeo.org] On Behalf Of Helmut 
Kudrnovsky [hel...@web.de]
Sent: Friday, April 29, 2016 12:18 AM
To: grass-user@lists.osgeo.org
Subject: Re: [GRASS-user] where is MSYS in GRASS 7?

>  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: 
https://urldefense.proofpoint.com/v2/url?u=http-3A__osgeo-2Dorg.1560.x6.nabble.com_where-2Dis-2DMSYS-2Din-2DGRASS-2D7-2Dtp5263411p5263429.html=CwIGaQ=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY=Tqv_-f6BFBydKWMUnDxwocGFWIum2o634InMCqa5bNw=WNHBoAZ2gMbx9vsNfm6C644WR0BRLeI7wkBp80wiiUI=
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.osgeo.org_mailman_listinfo_grass-2Duser=CwIGaQ=DsZY2bea7iNIzyp-7sZ0t0F2UfNQZUfZhEPCv_2wBI0=O31ltou6ygJL2Y01kQyNJJD2kiILIsbyz2V0Hn4lFUY=Tqv_-f6BFBydKWMUnDxwocGFWIum2o634InMCqa5bNw=5ftPcjPCOYlZKt7Df9RrCF8TNl8dcDCbxsIQAUQHgJQ=

The information contained in this email message is intended only for the use of 
the individual(s) to whom it is addressed and may contain information that is 
privileged and sensitive. If you are not the intended recipient, or otherwise 
have received this communication in error, please notify the sender immediately 
by email at the above referenced address and note that any further 
dissemination, distribution or copying of this communication is strictly 
prohibited.

The U.S. Export Control Laws regulate the export and re-export of technology 
originating in the United States. This includes the electronic transmission of 
information and software to foreign countries and to certain foreign nationals. 
Recipient agrees to abide by these laws and their regulations -- including the 
U.S. Department of Commerce Export Administration Regulations and the U.S. 
Department of State International Traffic in Arms Regulations -- and not to 
transfer, by electronic transmission or otherwise, any content derived from 
this email to either a foreign national or a foreign destination in violation 
of such laws.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Copy an existing location

[Rainer M Krug]

"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 references where lossless data
compression (gz, zip) may cause data loss? Especially tar.gz is used for
ages in archival and backup?

Rainer


[snip (46 lines)]
-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] where is MSYS in GRASS 7?

[Helmut Kudrnovsky]

>  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: 
http://osgeo-org.1560.x6.nabble.com/where-is-MSYS-in-GRASS-7-tp5263411p5263429.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] rgrass7 syntax for passing a command

[Roger Bivand]

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, 218835), ncol=2), 
  proj4string=CRS(paste(execGRASS("g.proj", flags="j", intern=TRUE),
collapse=" ")),
  data=data.frame(x=1))
writeVECT(pt, "outlet")

You could create a temporary text file to read in:

tf <- tempfile()
writeLines("636645, 218835", tf)
execGRASS("v.in.ascii", input=tf, output="outlet1", separator=",",
flags="n")

which is closer to your script but less natural.

Yes, grass-stats is a more appropriate list.
 
Roger




-
Roger Bivand
NHH Norwegian School of Economics, Bergen, Norway
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/rgrass7-syntax-for-passing-a-command-tp5263330p5263427.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] Copy an existing location

[Moritz Lennert]

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
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user

Re: [GRASS-user] v.dissolve on multiple items/controlling the output

[Moritz Lennert]

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 that a SQL statement might help me
out, but I can only use a WHERE clause (not a GROUP BY clause). Maybe it
could help to produce one special concatenated dissolve item before
running v.dissolve, but I was hoping to find a more „elegant“ way.


How about creating a new attribute column which you can populate with a 
code that represents the result of the combination of your criteria. 
Then you can use v.dissolve with that column.




Second, how can I determine if the output of v.dissolve is Multipart or
Singlepart? In my special case, I need both (one for map labeling, one
for area statistics). I could not find an option to set Singlepart or
Multipart.


AFAIK, there is no such thing as multipart or singlepart in the GRASS 
vector format. You can characterize several polygons as representing one 
single entity (and link them to a single line in the attribute table) by 
giving them all the same category number. So, for example, if you have a 
vector with one attribute column containing a code identifying such 
multipart entities, you can create a new vector map with same category 
values (aka id's) for all polygons of the same entity using v.reclass 
(you can actually directly formulate SQL queries in the rules file you 
can feed to v.reclass - see the man page for more info).


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

Re: [GRASS-user] i.rectify and ground-based photos

[Blumentrath, Stefan]

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 have to have fairly good estimates of you camera angle (roll, pitch, 
yaw) (and preferably use as much as possible down-facing angles)
c) according to the manual you need at least 16 GCPs, as much as possible 
evenly distributed over your image, and it does not seem to work with less than 
that at all.

In my case the main problem was c), as I only had a few objects I could use for 
GCPs in my camera viewshed and all of them were more or less in the background. 
So, I was missing elements I could recognize in foreground. Therefore I placed 
colored sheets of paper in the camera viewshed, which I measured with GPS, so I 
can match camera coordinate system and geographical coordinate system.

Paul Kelly used a different approach for that task (which I unfortunately did 
not manage to try yet):
http://www.stjohnspoint.co.uk/work/thesis/

Cheers
Stefan



-Original Message-
From: grass-user [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of Ken 
Mankoff
Sent: 28. april 2016 19:49
To: grass-user 
Subject: [GRASS-user] i.rectify and ground-based photos

Hi list,

Is i.rectify only designed for down-looking aerial photography? Or can it be 
used for highly oblique imagery too, for example photos taken side-looking from 
a plane window, or from a mountain-top covering a valley?

Thanks,

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

Re: [GRASS-user] r.mapcalc & neighborhood modifiers

[Markus Neteler]

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
someone here can suggest a way to do this in grass.
>
> I think the limitation is that I can't use neighborhood modifiers on the
LHS of an r.mapcalc equation like this:
>
> r.mapcalc "down[${r},${c}] = if(fdir == ${dir}, up, down)"
>
> Which means I need to know the upstream cell, which is information I do
not have. Looping through and finding the upstream cell(s) is non-trivial
because there are likely to be multiple, whereas I know there is only 1
downstream cell because I ran r.watershed with "-s".
...

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.

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

Re: [GRASS-user] rgrass7 syntax for passing a command

[Blumentrath, Stefan]

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 coordinates to a temporary file, which you can read in 
v.in.ascii

Cheers
Stefan

From: grass-user [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of 
Veronica Andreo
Sent: 28. april 2016 19:38
To: James Maas (MED) 
Cc: grass-user 
Subject: Re: [GRASS-user] rgrass7 syntax for passing a command

Hello Jim,

Maybe you should write to grass-stats mailing list, too. Perhaps someone there 
can provide useful insights/suggestions for your case

Best,
Vero

2016-04-28 12:53 GMT-03:00 Jim Maas >:
Using GRASS 7.0.3 on Ubuntu Linux,

I'm attempting to recreate the example of r.stream.distance shown at
https://grass.osgeo.org/grass70/manuals/addons/r.stream.distance.html

by passing these comands to GRASS from within an R session.  I can't figure out 
the correct syntax to pass this command to the system and also GRASS, any 
suggestions ?

The original code for GRASS command line in the example is

# Create outlet
echo "636645,218835" | v.in.ascii -n input=- output=outlet separator=","


I've tried lots of combinations of both system() and execGRASS() including this

system(message ("327500.00,523896.55") | "v.in.ascii", input="-", 
output="outlet", separator=",", flags=c("n", "overwrite"))




but have been unsuccessful.

Any suggestions?

Thanks, J

--
Dr. Jim Maas
Norwich Medical School

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

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

Re: [GRASS-user] Copy an existing location

[Blumentrath, Stefan]

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
Stefan

-Original Message-
From: grass-user [mailto:grass-user-boun...@lists.osgeo.org] On Behalf Of 
Markus Neteler
Sent: 28. april 2016 14:35
To: Paulo van Breugel 
Cc: grass list 
Subject: Re: [GRASS-user] Copy an existing location

On Thu, Apr 28, 2016 at 9:54 AM, Paulo van Breugel  
wrote:
> There is also the r.pack function.

Yes,this is a safe way to go (r.pack - r.unpack | v.pack - v.unpack).

Hope this suggestion is addressed one day:

r|v.unpack: add parameter to create new location
https://trac.osgeo.org/grass/ticket/2459

which would be handy for the user receiving the data.

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

[GRASS-user] v.dissolve on multiple items/controlling the output

[Uwe Fischer]

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 out, but I can
only use a WHERE clause (not a GROUP BY clause). Maybe it could help to
produce one special concatenated dissolve item before running v.dissolve,
but I was hoping to find a more "elegant" way.

 

Second, how can I determine if the output of v.dissolve is Multipart or
Singlepart? In my special case, I need both (one for map labeling, one for
area statistics). I could not find an option to set Singlepart or Multipart.


 

Thanks a lot and best regards, Uwe

 

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

[GRASS-user] where is MSYS in GRASS 7?

[Bartolomei.Chris]

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 Windows 7 like it did in 
version 6.4.4. Does anyone have a suggestion on how to get the unix command 
console?
Thanks
:)
Chris


Chris Bartolomei P.E.
Engineer/Scientist
ENSCO, Inc.
bartolomei.ch...@ensco.com

The information contained in this email message is intended only for the use of 
the individual(s) to whom it is addressed and may contain information that is 
privileged and sensitive. If you are not the intended recipient, or otherwise 
have received this communication in error, please notify the sender immediately 
by email at the above referenced address and note that any further 
dissemination, distribution or copying of this communication is strictly 
prohibited.

The U.S. Export Control Laws regulate the export and re-export of technology 
originating in the United States. This includes the electronic transmission of 
information and software to foreign countries and to certain foreign nationals. 
Recipient agrees to abide by these laws and their regulations -- including the 
U.S. Department of Commerce Export Administration Regulations and the U.S. 
Department of State International Traffic in Arms Regulations -- and not to 
transfer, by electronic transmission or otherwise, any content derived from 
this email to either a foreign national or a foreign destination in violation 
of such laws.
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user