[GRASS-dev] r.in.wms not by default in winGRASS 7.8.1

[Yann Chemin]

Hi,

I am working on a M$#@%Windows terminal where I have no access/right to
anything.

For my work I need to access :
https://sdi.eea.europa.eu/catalogue/srv/eng/csw-copernicus?SERVICE=CSW=2.0.2=GetCapabilities

is there a possibility to manually make it available somehow?
Thank you
Yann
--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3932: i.vi: NDWI unnecessarily requires red band

[Yann Chemin]

https://github.com/OSGeo/grass/pull/178/commits
--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT



On Tue, 5 Nov 2019 at 13:12, GRASS GIS  wrote:

> #3932: i.vi: NDWI unnecessarily requires red band
> -+-
>  Reporter:  sbl  |  Owner:  grass-dev@…
>  Type:  defect   | Status:  new
>  Priority:  normal   |  Milestone:  7.8.1
> Component:  Imagery  |Version:  git-releasebranch78
>  Keywords:  i.vi |CPU:  All
>  Platform:  All  |
> -+-
>  i.vi requires a red band in any case, even if e.g. NDWI does not need
> one.
>  So, in order to make the module run, a map has to be given also for the
>  red band. That seems like unexpected behavior to me.
>  Maybe better to leave all input bands optional and add a check for the
>  requested VI if required bands are provided...
>
> --
> Ticket URL: <https://trac.osgeo.org/grass/ticket/3932>
> GRASS GIS <https://grass.osgeo.org>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] make vector footprint orientated along track of satellite

[Yann Chemin]

Thank you Markus,
will dig that way...
Cheers,
Yann
--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT



On Wed, 16 Oct 2019 at 16:18, Markus Neteler  wrote:

> (re-adding the list)
>
> On Wed, Oct 16, 2019 at 4:08 PM Yann Chemin 
> wrote:
> >
> > yes Markus that would be nice but the angle is actually changing for
> each point.
> > Only sending the screenshot to you as it is big.
>
> Well, for that probably
>
> https://grass.osgeo.org/grass78/manuals/m.cogo.html  + v.in.ascii?
>
> ... in a Python script which addresses the changing angle.
> Sounds also like a TGRASS topic: points moving in time.
>
> Just some ideas...
>
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] make vector footprint orientated along track of satellite

[Yann Chemin]

Hi all,

I have some OCO2 nc4 files (has points as vectors) and it says the pixel
size should be 2kmx1.3km "along track" oriented.

Is there any GRASS module or trick that can help me generate the polygons
hosts of these data point?

Thank you,
Yann

--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] v.in.ogr Killed by Linux for saturating RAM+SWAP

[Yann Chemin]

Answering to my own question.

I can increase the SWAP size on a running Linux by:

sudo swapoff -a
sudo dd if=/dev/zero of=/swapfile bs=1G count=8
>> 8+0 records in
>> 8+0 records out
>> 8589934592 bytes (8.6 GB, 8.0 GiB) copied, 12.7623 s, 673 MB/s
sudo mkswap /swapfile
>> Setting up swapspace version 1, size = 8 GiB (8589930496 bytes)
>> no label, UUID=x
sudo swapon /swapfile
grep SwapTotal /proc/meminfo
>> SwapTotal:   8388604 kB

--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT



On Mon, 30 Sep 2019 at 14:16, Yann Chemin  wrote:

> Hi devs,
> I am trying to import a vector and it gets killed. Is there a direct way
> to let it not use the whole RAM+SWAP or should I get a bigger RAM system to
> do the manipulation ?
> Thanks,
> Yann
>
> Importing 6146401 features (OGR layer )...
>  100%
> -
> Registering primitives...
> -
> Cleaning polygons
> -
> Breaking polygons...
> Breaking polygons (pass 1: select break points)...
>  100%
> Breaking polygons (pass 2: break at selected points)...
> Killed
>
>
> --
> Dr. Yann Chemin
> +33 7 83 85 5234
> JRC, Ispra, IT
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] v.in.ogr Killed by Linux for saturating RAM+SWAP

[Yann Chemin]

Hi devs,
I am trying to import a vector and it gets killed. Is there a direct way to
let it not use the whole RAM+SWAP or should I get a bigger RAM system to do
the manipulation ?
Thanks,
Yann

Importing 6146401 features (OGR layer )...
 100%
-
Registering primitives...
-
Cleaning polygons
-
Breaking polygons...
Breaking polygons (pass 1: select break points)...
 100%
Breaking polygons (pass 2: break at selected points)...
Killed


--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Try GRASS GIS online: Binder - mybinder.org

[Yann Chemin]

It has been a couple of years already that I am dreaming of an open source
system based on some kind of p2p that will permit people to co-share
processing power and disk space for some interactive teaching/studying...

i.e. I would host MOD13Q1 EU related tiles, from 2001 to 2015
somebody else MOD13Q1 EU related tiles, from 2010 to 2019

all "friends" would have access to the data and processing power on both
the PCs, with only a part of CPUs accessible, and instantly revokable
access by a single button click.

Likewise a meta-access to data could be available in teams
pseudo-libraries/APIs...

the more the merrier, of course.

errrh, just dreaming.

--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT



On Thu, 8 Aug 2019 at 12:22, Stefan Blumentrath 
wrote:

> Hi Yann,
>
>
>
> For courses also: https://cocalc.com/
>
> could be interesting. It does not (yet?) ship GRASS by default though.
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* Yann Chemin 
> *Sent:* torsdag 8. august 2019 10:11
> *To:* Stefan Blumentrath 
> *Cc:* Vaclav Petras ; grass-dev@lists.osgeo.org
> *Subject:* Re: [GRASS-dev] Try GRASS GIS online: Binder - mybinder.org
>
>
>
> Cool stuff !
>
> I can see a whole lot of GIS courses becoming streamlined with that...
>
> +1
>
> --
> Dr. Yann Chemin
>
> +33 7 83 85 5234
>
> JRC, Ispra, IT
>
>
>
>
>
>
>
> On Thu, 8 Aug 2019 at 09:59, Stefan Blumentrath <
> stefan.blumentr...@nina.no> wrote:
>
> Hi Vaclav,
>
>
>
> Sounds really cool to me! Great initiative!
>
> Of course stuff can always be extended if people feel for it, but it seems
> to be more than good enough to promote it as is. Just my impression from
> looking at the third example in Binder.
>
>
>
> Cheers
>
> Stefan
>
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Try GRASS GIS online: Binder - mybinder.org

[Yann Chemin]

Cool stuff !
I can see a whole lot of GIS courses becoming streamlined with that...
+1
--
Dr. Yann Chemin
+33 7 83 85 5234
JRC, Ispra, IT



On Thu, 8 Aug 2019 at 09:59, Stefan Blumentrath 
wrote:

> Hi Vaclav,
>
>
>
> Sounds really cool to me! Great initiative!
>
> Of course stuff can always be extended if people feel for it, but it seems
> to be more than good enough to promote it as is. Just my impression from
> looking at the third example in Binder.
>
>
>
> Cheers
>
> Stefan
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Job position in Thessaloniki university on a h2020 project

[Yann Chemin]

https://dasta.auth.gr/show_news.aspx?sid=2=26214

Please consider applying.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] New Google Scholar profile: "GRASS Development Team"

[Yann Chemin]

amazing the amount of research done by the team ! such diversity !

On Sun, Dec 9, 2018, 11:24 Markus Neteler  Hi,
>
> for  fun, to easily track GRASS GIS related publications I have
> created a new Google Scholar profile:
>
> GRASS Development Team (a virtual team!)
> https://scholar.google.com/citations?user=gJ0ZB0cJ
>
> I have manually scanned some 3k article entires to catch many GRASS
> GIS related papers.
> The profile requires some more maintenance (help welcome!) and for
> sure misses artices (pls tell me).
>
> The "co-authors" on the right side are those who came to mind _and_
> have a Google Scholar profile. If you have one and would like to show
> up, please let me know.
>
> Enjoy,
> Markus
>
> PS: Yes, I got inspired by the virtual "R Development Team" :-)
>
> --
> Markus Neteler, PhD
> http://www.mundialis.de - free data with free software
> http://grass.osgeo.org
> http://courses.neteler.org/blog
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] tygrass, working with GRASS GIS under Terminology

[Yann Chemin]

Nice Nik!



> On 23 Oct 2018, at 12:13, Markus Neteler  wrote:
> 
> On Tue, Oct 23, 2018 at 7:38 AM Nikos Alexandris
>  wrote:
>> 
>> Maybe of your interest,
>> 
>> an approach on rendering maps directly in the Terminology terminal while
>> working interactively or even while running a script:
>> https://gitlab.com/NikosAlexandris/tygrass
>> 
>> an experimental addon:
>> https://gitlab.com/NikosAlexandris/d.tyraster
>> 
>> a series of screencasts:
>> https://archive.org/details/GrassGisUnderTerminology [*]
> 
> Wow, that's fancy!!!
> 
> I just tried on my Fedora box (`dnf install terminology`), works perfectly 
> fine.
> 
> Congrats,
> 
> Markus
> 
>> Nikos
>> 
>> [*] replay is slow, to do: maybe some quality downgrade
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
> 
> 
> 
> -- 
> Markus Neteler, PhD
> http://www.mundialis.de - free data with free software
> http://grass.osgeo.org
> http://courses.neteler.org/blog
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

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

Re: [GRASS-dev] r.patch too many open files ( 432 files )

[Yann Chemin]

Thanks Markus



On Thu, 20 Sep 2018 at 13:00, Markus Neteler  wrote:

> On Thu, Sep 20, 2018 at 10:45 AM Yann Chemin 
> wrote:
> >
> > Hi I have to patch 432 files and it returns “Too many files opened”
> >
> > Is this a limit of my computer or of the code?
>
> You can modify that, see
> https://grass.osgeo.org/grass74/manuals/r.patch.html#notes
>
> HTH
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] r.patch too many open files ( 432 files )

[Yann Chemin]

Hi I have to patch 432 files and it returns “Too many files opened”

Is this a limit of my computer or of the code?

Thanks,
Yann

Dr. Yann Chemin
+33 7 83 85 5234
3 Toulmelin, 56400 Plumergat, FR

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

[GRASS-dev] r.in.wms: decode() is not defined

[Yann Chemin]

Hi

maybe I am missing a library?

/usr/local/grass-7.7.svn/scripts/r.in.wms url=url="
https://tiles.maps.eox.at/wms?; output=sen2cloudless layers=s2cloudless
Traceback (most recent call last):
  File "/usr/local/grass-7.7.svn/scripts/r.in.wms", line
241, in 
sys.exit(main())
  File "/usr/local/grass-7.7.svn/scripts/r.in.wms", line
227, in main
fetched_map = wms.GetMap(options, flags)
  File "/usr/local/grass-7.7.svn/etc/r.in.wms/wms_base.py",
line 212, in GetMap
self._initializeParameters(options, flags)
  File "/usr/local/grass-7.7.svn/etc/r.in.wms/wms_base.py",
line 137, in _initializeParameters
self.proj_srs = decode(self.proj_srs).rstrip('\n')
NameError: global name 'decode' is not defined



--
Dr. Yann Chemin
Freelancer
+33 7 83 85 5234
3 Toulmelin, 56400 Plumergat, FR
https://www.paypal.me/yannchemin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] GRASS GIS ET modules in a new article

[Yann Chemin]

Hi all,

for those interested in ET mapping, Carla has finished her PhD and is now 
finished with article.
Mapping Maize Evapotranspiration at Field Scale Using SEBAL: A Comparison with 
the FAO Method and Soil-Plant Model Simulations
Remote Sens. 2018, 10(9), 1452; https://doi.org/10.3390/rs10091452

Inline: http://www.mdpi.com/2072-4292/10/9/1452
 <http://www.mdpi.com/2072-4292/10/9/1452>PDF: 
http://www.mdpi.com/2072-4292/10/9/1452/pdf 
<http://www.mdpi.com/2072-4292/10/9/1452/pdf>

Cheers,
Yann

Dr. Yann Chemin
+33 7 83 85 5234
3 Toulmelin, 56400 Plumergat, FR



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

Re: [GRASS-dev] pygrass v.import_() strange error

[Yann Chemin]

Great, thanks a lot Pietro !

On Fri, Aug 3, 2018, 07:55 Pietro  wrote:

> Thank you Yann and Vaclav, I was not aware of this issue:
>
> On Thu, Aug 2, 2018 at 5:06 AM, Vaclav Petras 
> wrote:
>
>> >>> a.import()
>>   File "", line 1
>> a.import()
>>^
>> SyntaxError: invalid syntax
>>
>
> I've fixed the the code to support the use of underscore for python
> reserved words and add two doctests in  r73029.
>
> Best regards
>
> pietro
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pygrass v.import_() strange error

[Yann Chemin]

yes in the meantime I am running it with parse_command I believe

#code##
from grass_session import Session
from grass.script import core as gcore
#from grass.pygrass.modules.shortcuts import vector as v
with Session(gisdb="/tmp", location="loc", create_opts="EPSG:4326"):

#v.import_(input=adminfile,output="admin",quiet=True,superquiet=True)

gcore.parse_command("v.import",input=adminfile,output="admin",quiet=True)


On Wed, 25 Jul 2018 at 11:05, Nikos Alexandris 
wrote:

> * Yann Chemin  [2018-07-25 09:34:32 +0200]:
>
> >Hi,
> >(script below)
> >I get this error
> >
> >v.import_(input=adminfile,output="admin",quiet=True,superquiet=True)
> >  File "/usr/lib/grass74/etc/python/grass/pygrass/modules/shortcuts.py",
> >line 47, in __getattr__
> >return self.cls('%s.%s' % (self.prefix, name.replace('_', '.')))
> >  File
> >"/usr/lib/grass74/etc/python/grass/pygrass/modules/interface/module.py",
> >line 530, in __init__
> >raise GrassError(str_err % self.name)
> >grass.exceptions.GrassError: Error running: `v.import.
> >--interface-description`.
> >
> >#SCRIPT
> >from grass_session import Session
> >from grass.pygrass.modules.shortcuts import vector as v
> >adminfile=gadm_FR_2_Morbihan.gpkg
> >with Session(gisdb="/tmp", location="loc", create_opts="EPSG:4326"):
> > v.import_(input=adminfile,output="admin",quiet=True,superquiet=True)
>
> Yann,
>
> does the "typical"
>
> grass.run_command('v.import', input=adminfile, output="admin", quiet=True,
> superquiet=True)
>
> work?
>
> Nikos
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pygrass v.import_() strange error

[Yann Chemin]

yes this is the problem indeed

On Wed, 25 Jul 2018 at 13:21, Vaclav Petras  wrote:

>
>
> On Wed, Jul 25, 2018, 3:34 AM Yann Chemin 
> wrote:
>
>> Hi,
>> (script below)
>> I get this error
>>
>> v.import_(input=adminfile,output="admin",quiet=True,superquiet=True)
>>   File "/usr/lib/grass74/etc/python/grass/pygrass/modules/shortcuts.py",
>> line 47, in __getattr__
>> return self.cls('%s.%s' % (self.prefix, name.replace('_', '.')))
>>   File
>> "/usr/lib/grass74/etc/python/grass/pygrass/modules/interface/module.py",
>> line 530, in __init__
>> raise GrassError(str_err % self.name)
>> grass.exceptions.GrassError: Error running: `v.import.
>> --interface-description`.
>>
>
> It seems that PyGRASS does not support the "underscore at the end when
> Python keyword". It just does it's usual thing which is replacing
> underscores with dots like in r.slope_aspect. So probably a new
> functionality needs to be added to replace import_ with just import.
> Something like name.strip('_'). Please add a test for it.
>
> Best,
> Vaclav
>
>
>
>
>> #SCRIPT
>> from grass_session import Session
>> from grass.pygrass.modules.shortcuts import vector as v
>> adminfile=gadm_FR_2_Morbihan.gpkg
>> with Session(gisdb="/tmp", location="loc", create_opts="EPSG:4326"):
>>  v.import_(input=adminfile,output="admin",quiet=True,superquiet=True)
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] pygrass v.import_() strange error

[Yann Chemin]

Yes I used shortcuts, the Python keyword replacement is forcing pyGRASS to
make v.import_ instead of v.import. However the same "_" scheme is also a
replacement of triple dot separated grass modules 9i.e. r.out.gdal=>
r.out_gdal) and the replacement scheme in running modules assumes that "_"
has to be replaced by a "."  Thus the error ideed
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] pygrass v.import_() strange error

[Yann Chemin]

Hi,
(script below)
I get this error

v.import_(input=adminfile,output="admin",quiet=True,superquiet=True)
  File "/usr/lib/grass74/etc/python/grass/pygrass/modules/shortcuts.py",
line 47, in __getattr__
return self.cls('%s.%s' % (self.prefix, name.replace('_', '.')))
  File
"/usr/lib/grass74/etc/python/grass/pygrass/modules/interface/module.py",
line 530, in __init__
raise GrassError(str_err % self.name)
grass.exceptions.GrassError: Error running: `v.import.
--interface-description`.

#SCRIPT
from grass_session import Session
from grass.pygrass.modules.shortcuts import vector as v
adminfile=gadm_FR_2_Morbihan.gpkg
with Session(gisdb="/tmp", location="loc", create_opts="EPSG:4326"):
 v.import_(input=adminfile,output="admin",quiet=True,superquiet=True)
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] suppress Gtk-WARNING (wxgui.py) in SVN

[Yann Chemin]

Hi
I would like to suppress Gtk-WARNING from the wxgui.py,
any suggestion please?
Using SVN code updated on a daily basis.
Thank you,
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] compile 6S library in GRASS

[Yann Chemin]

a wild guess: specify a raster input option for AOT (alongside other
options), let user find its image source and use it.

Very limited requirement for the GSoC student, most latitude for the the
modules user.

--
Dr. Yann Chemin
Freelancer
+33 7 83 85 5234
3 Toulmelin, 56400 Plumergat, FR
https://www.paypal.me/yannchemin


On Thu, 28 Jun 2018 at 13:35, Moritz Lennert 
wrote:

> On 28/06/18 12:17, Roberta Fagandini wrote:
> > I'm not an expert in MODIS data so if someone wants to give
> > suggestions about how to retrieve the AOT from these data, I will
> > definitely add this option too.
>
> I'm not an expert, and MarkusM can probably provide you with more info,
> but you can already see https://lpdaac.usgs.gov/node/1265.
>
> Moritz
>
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] compile 6S library in GRASS

[Yann Chemin]

On Wed, Jun 27, 2018, 15:25 Markus Metz 
wrote:

>
>
> On Wed, Jun 27, 2018 at 3:06 PM, Roberta Fagandini <
> robifagand...@gmail.com> wrote:
> >
> >
> >
> > 2018-06-27 14:24 GMT+02:00 Markus Metz :
> >>
> >>
> >>
> >> On Wed, Jun 27, 2018 at 2:16 PM, Roberta Fagandini <
> robifagand...@gmail.com> wrote:
> >> >
> >> > I'm trying to create an automatic procedure to retrieve all the input
> parameters for the control file of i.atcorr.
> >> > I need py6S because I want to automatically read and compute AOT at
> 550nm from an AERONET file.
> >>
> >> With AOT you mean aerosol optical thickness right? This is user input
> to i.atcorr. There are various sources for AOT at 550nm, e.g. MODIS.
> >
> >
> > Right!
> >
> >>
> >>
> >>
> >>
> >> Anyway, it is probably much easier to to write your own routine to read
> the AERONET file and get the corresponding formula for AOT than to fight
> with 51821 lines of Fortran source code that is numerically unstable. Maybe
> I can help with getting AOT at 550nm from an AERONET file avoiding the
> Fortran version of 6S.
> >
> >
> > Ok but I'm not able to create this kind of routine on my own. If
> someone, more expert than me, can help me in translating the 6S/Py6S
> functions I can go on in this way otherwise for me it's easier to use the
> fortran source code.
>
> Apparently the AERONET data are simple CSV files. You can import them with
> r.in.xyz or v.in.ascii.
>
> Still, I think it is up to the user to decide on the source of AOT values.
> AERONET is one of many possible sources.
>


+1


> Markus M
>
>
> > Here [0] a link to my Github repository in which you can find the small
> script that I wrote using the Py6S library to compute AOT at 550nm
> >
> > Roberta
> >
> > [0]
> https://github.com/RobiFag/GRASS_clouds_and_shadows/blob/master/read_aeronet.py
> >
> >>
> >>
> >> Markus M
> >>
> >> >
> >> > 2018-06-27 14:01 GMT+02:00 Moritz Lennert <
> mlenn...@club.worldonline.be>:
> >> >>
> >> >> On 27/06/18 13:54, Roberto Marzocchi wrote:
> >> >>>
> >> >>>
> >> >>> Il giorno mer 27 giu 2018 alle ore 13:47 Markus Metz <
> markus.metz.gisw...@gmail.com > ha
> scritto:
> >> >>>
> >> >>> Hi Roberta,
> >> >>>
> >> >>> On Wed, Jun 27, 2018 at 1:20 PM, Roberta Fagandini
> >> >>> mailto:robifagand...@gmail.com>>
> wrote:
> >> >>>  >
> >> >>>  > Hi all!
> >> >>>  > I need to compile the 6S library in GRASS in order to
> install the
> >> >>> python library Py6S [0].
> >> >>>
> >> >>> do you really need Py6S? Can't you use i.atcorr instead?
> >> >>>
> >> >>>
> >> >>> She use Py6S to calculate imput for i.atcorr
> >> >>
> >> >>
> >> >> That seems a bit overkill: why use Py6S to then use i.atcorr ? What
> are you trying to get from Py6S ?
> >> >>
> >> >> Moritz
> >> >>
> >> >
> >
> >
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] compile 6S library in GRASS

[Yann Chemin]

6s was rewritten by Cristo in C++
The code was absorbed in i.atcorr around the beginning of the century.


On Wed, Jun 27, 2018, 13:20 Roberta Fagandini 
wrote:

> Hi all!
> I need to compile the 6S library in GRASS in order to install the python
> library Py6S [0].
> The source code of 6S (v 1.1) is written in Fortran and it seems to be the
> same code used for i.atcorr but I can't see the Fortran source code within
> the GRASS svn [1]. In fact, I can't find the 6S executable on my disk even
> if I installed GRASS.
>
> Thanks in advance!
>
> Roberta
>
> [0]
> http://py6s.readthedocs.io/en/latest/installation.html#alternative-manual-installation
> [1] https://trac.osgeo.org/grass/browser/grass/trunk/imagery/i.atcorr
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] daily windows built lagging, any trouble?

[Yann Chemin]

Hi,

trying to test some r.kappa modification on WinGRASS standalone, but the
nightly built are lagging behind svn.

any worries?
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Issue with double conditional in r.mapcalc (WinGRASS) and real life test of the aconda 7.5dev on Mac

[Yann Chemin]

We had a mix of installations on Windows:
1 - QGIS standalone with GRASS7.2.2. (GRASS could also be run standalone it 
seems)
2 - WinGRASS 7.4.0. mostly direct install, but maybe some from OSGEO4W too.
3 - WinGRASS7.5svn nightly

Windows machines were many times not up to date, we even had some Windows7, but 
mostly Windows 8 and W10.

We tried to use the command prompt to enter the scripts, but it made trouble so 
we tried on the wxGUI Console, and we found it worked mostly, until we started 
entering more complex if statements. But that was after we had to remove quotes 
to enter the r.mapcalc script successfully anyway.

Would that be related to the issues with internationalisation 
(https://trac.osgeo.org/grass/ticket/3500 
)?

> On 18 Feb 2018, at 23:32, Helmut Kudrnovsky  wrote:
> 
>> I conducted a GRASS GIS course this week and we found some bugs on WinGRASS: 
> 
> the subject of this report is _(WinGRASS)_ and _aconda 7.5dev on Mac_ 
> 
> which winGRASS version have you used? 7.4.0? 7.5dev? another version?
> 
> 
> 
> -
> best regards
> Helmut
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[GRASS-dev] Issue with double conditional in r.mapcalc (WinGRASS) and real life test of the aconda 7.5dev on Mac

[Yann Chemin]

I conducted a GRASS GIS course this week and we found some bugs on WinGRASS:

r.mapcalc expression=if(case1,if(case2,Val2True,Val2False),Val1False))

This expression will fail, note that the lack of quote is intentional, as it is 
a requirement to run simpler r.mapcalc statements in WinGRASS.

Also, we found that the use of || and && within a simple conditional statement 
also did not process anything and failed.

We had 25% Mac overall (group of 110 students), we installed the new aconda 
7.5dev and all the above processing worked perfectly. We also had an Ubuntu 
machine (not mine) with Artful default grass install (7.4?) which performed as 
well as the Mac, nothing much to say except from the render.py bug in d.rast 
inside a d.mon (submit ticket last week 
https://trac.osgeo.org/grass/ticket/3497).

We used the tutorial in grass=promo/tuorials/grassstarter, the script at the 
end essentially, running on Spearfish dataset.

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

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

thanks for the constant feed back Zofie, was not possible to make it work
without you guys testing it.
yann

On Aug 6, 2017 12:40 PM, "Stefan Blumentrath" <stefan.blumentr...@nina.no>
wrote:

> Hi again,
>
>
>
> Zofie tested the orthorectification suite in GRASS 7 and just confirmed
> that it works as expected!
>
> Thanks so much, Yann! For me this was the last missing feature for
> completely moving to GRASS 7!
>
>
>
> Cheers
>
> Stefan
>
>
>
>
>
> *From:* grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] *On Behalf
> Of *Blumentrath, Stefan
> *Sent:* tirsdag 21. mars 2017 08.05
> *To:* Yann Chemin <dr.yann.che...@gmail.com>; Luca Delucchi <
> lucadel...@gmail.com>
> *Cc:* GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
> mananpa...@gmail.com>
> *Subject:* Re: [GRASS-dev] Introduction for GSoC 2017
>
>
>
> Hi Yann,
>
>
>
> Thanks so much! Very cool!
>
> I will test the photo2image GUI tool ASAP!
>
>
>
> Cheers
>
> Stefan
>
>
>
> *From:* Yann Chemin [mailto:dr.yann.che...@gmail.com
> <dr.yann.che...@gmail.com>]
> *Sent:* tirsdag 21. mars 2017 07.56
> *To:* Luca Delucchi <lucadel...@gmail.com>
> *Cc:* GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
> mananpa...@gmail.com>; Blumentrath, Stefan <stefan.blumentr...@nina.no>
> *Subject:* Re: [GRASS-dev] Introduction for GSoC 2017
>
>
>
> Hi all,
>
> I have added to SVN trunk one of the two missing gui modules of
> i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
> All other modules but one are operational (still not fully tested though),
> I have already started working on the last one, which is also GUI based.
>
> Cheers,
> Yann
>
>
>
> On Mar 20, 2017 5:25 PM, "Luca Delucchi" <lucadel...@gmail.com> wrote:
>
> On 18 March 2017 at 08:30, Blumentrath, Stefan
> <stefan.blumentr...@nina.no> wrote:
> > Hi,
> >
>
> Hi,
>
> >
> > Could also porting (competition) of the i.ortho.photo modules (and here
> > especially the missing GUI modules around it) to GRASS 7 become scope of
> > this GSoC idea?
> >
>
> I fully support this idea, GUI for i.ortho.photo is the most important
> loss from GRASS 6
>
> >
> >
> > Cheers,
> >
> > Stefan
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

just did using svn mv

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 12 May 2017 at 10:52, Markus Neteler <nete...@osgeo.org> wrote:

> On Fri, May 12, 2017 at 9:33 AM, Luca Delucchi <lucadel...@gmail.com>
> wrote:
> > On 12 May 2017 at 09:28, Moritz Lennert <mlenn...@club.worldonline.be>
> wrote:
> >> On 12/05/17 09:18, Yann Chemin wrote:
> >>>
> >>> Hi Stefan,
> >>>
> >>> the first throw is there in SVN, just update and recompile.
> >>> The two GUI are g.gui.iphoto2image and g.gui.iimage2target.
> >>>
> >>> Finalization of the names are also open to suggestion, so far I just
> >>> concatenated the old module names in v6 and added to g.gui.
> >>
> >> I would suggest
> >>
> >> g.gui.photo2image
> >> g.gui.image2target
> >>
> >> (without the extra i)
> >>
> >
> > +1
>
> +1
>
> If/when renaming, be sure to use "svn mv" for this to keep the history.
> https://trac.osgeo.org/grass/wiki/HowToSVN#SVNusage
> --> at the end of the section
>
> Markus
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

Hi Stefan,

the first throw is there in SVN, just update and recompile.
The two GUI are g.gui.iphoto2image and g.gui.iimage2target.

Finalization of the names are also open to suggestion, so far I just
concatenated the old module names in v6 and added to g.gui.

Please test and if you have a scanned aerial photo with good info about
camera and XYZ of fiducials, please throw it my side too so I can
validate/finalize the output accuracy.

Cheers,
Yann

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 21 March 2017 at 08:31, Yann <dr.yann.che...@gmail.com> wrote:

> Hi Stefan,
>
> please also launch the main menu: i.ortho.photo at the command line, it
> tends to be erratic.
>
> (careful the i.photo.2target is not yet existing)
>
> Ciao,
> Yann
>
>
>
> On 21/03/2017 08:04, Blumentrath, Stefan wrote:
>
>> Hi Yann,
>>
>> Thanks so much! Very cool!
>> I will test the photo2image GUI tool ASAP!
>>
>> Cheers
>> Stefan
>>
>> From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
>> Sent: tirsdag 21. mars 2017 07.56
>> To: Luca Delucchi <lucadel...@gmail.com>
>> Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
>> mananpa...@gmail.com>; Blumentrath, Stefan <stefan.blumentr...@nina.no>
>> Subject: Re: [GRASS-dev] Introduction for GSoC 2017
>>
>>
>> Hi all,
>>
>> I have added to SVN trunk one of the two missing gui modules of
>> i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
>> All other modules but one are operational (still not fully tested though),
>> I have already started working on the last one, which is also GUI based.
>>
>> Cheers,
>> Yann
>>
>> On Mar 20, 2017 5:25 PM, "Luca Delucchi" <lucadel...@gmail.com> ucadel...@gmail.com>> wrote:
>> On 18 March 2017 at 08:30, Blumentrath, Stefan
>> <stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:
>>
>>> Hi,
>>>
>>> Hi,
>>
>> Could also porting (competition) of the i.ortho.photo modules (and here
>>> especially the missing GUI modules around it) to GRASS 7 become scope of
>>> this GSoC idea?
>>>
>>> I fully support this idea, GUI for i.ortho.photo is the most important
>> loss from GRASS 6
>>
>>
>>> Cheers,
>>>
>>> Stefan
>>>
>>>
>> --
>> ciao
>> Luca
>>
>> www.lucadelu.org<http://www.lucadelu.org>
>> ___
>> grass-dev mailing list
>> grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
>> https://lists.osgeo.org/mailman/listinfo/grass-dev
>>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

On Mar 22, 2017 6:01 PM, "Markus Metz" <markus.metz.gisw...@gmail.com>
wrote:
>
>
>
> On Tue, Mar 21, 2017 at 8:31 AM, Yann <dr.yann.che...@gmail.com> wrote:
> >
> > Hi Stefan,
> >
> > please also launch the main menu: i.ortho.photo at the command line, it
tends to be erratic.
> >
> > (careful the i.photo.2target is not yet existing)
>
> you can clone and modify g.gui.gcp to get a wxgui replacement for
i.photo.2target.

Yes started that already.

Essentially you need to replace calls to m.transform with calls to
i.ortho.transform which I wrote a wile ago for this purpose.

I will look into that, I saw that m.transform would need replacement
indeed. Did not know it was ready yet. Thanks.

And some interface to set fiducials is missing (old i.photo.2image) which
would need to be added to the wizard of g.gui.gcp.
>
> Markus M

Thanks Markus
Yann
>
> >
> > Ciao,
> > Yann
> >
> >
> >
> > On 21/03/2017 08:04, Blumentrath, Stefan wrote:
> >>
> >> Hi Yann,
> >>
> >> Thanks so much! Very cool!
> >> I will test the photo2image GUI tool ASAP!
> >>
> >> Cheers
> >> Stefan
> >>
> >> From: Yann Chemin [mailto:dr.yann.che...@gmail.com]
> >> Sent: tirsdag 21. mars 2017 07.56
> >> To: Luca Delucchi <lucadel...@gmail.com>
> >> Cc: GRASS-dev <grass-dev@lists.osgeo.org>; Manan Singh <
mananpa...@gmail.com>; Blumentrath, Stefan <stefan.blumentr...@nina.no>
> >> Subject: Re: [GRASS-dev] Introduction for GSoC 2017
> >>
> >>
> >> Hi all,
> >>
> >> I have added to SVN trunk one of the two missing gui modules of
i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
All other modules but one are operational (still not fully tested though),
I have already started working on the last one, which is also GUI based.
> >>
> >> Cheers,
> >> Yann
> >>
> >> On Mar 20, 2017 5:25 PM, "Luca Delucchi" <lucadel...@gmail.com> wrote:
> >> On 18 March 2017 at 08:30, Blumentrath, Stefan
> >> <stefan.blumentr...@nina.no<mailto:stefan.blumentr...@nina.no>> wrote:
> >>>
> >>> Hi,
> >>>
> >> Hi,
> >>
> >>> Could also porting (competition) of the i.ortho.photo modules (and
here
> >>> especially the missing GUI modules around it) to GRASS 7 become scope
of
> >>> this GSoC idea?
> >>>
> >> I fully support this idea, GUI for i.ortho.photo is the most important
> >> loss from GRASS 6
> >>
> >>>
> >>> Cheers,
> >>>
> >>> Stefan
> >>>
> >>
> >> --
> >> ciao
> >> Luca
> >>
> >> www.lucadelu.org<http://www.lucadelu.org>
> >> ___
> >> grass-dev mailing list
> >> grass-dev@lists.osgeo.org<mailto:grass-dev@lists.osgeo.org>
> >> https://lists.osgeo.org/mailman/listinfo/grass-dev
> >
> >
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org
> > https://lists.osgeo.org/mailman/listinfo/grass-dev
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Introduction for GSoC 2017

[Yann Chemin]

Hi all,

I have added to SVN trunk one of the two missing gui modules of
i.ortho.photo recently: g.gui.iphoto2image at the command line launches it.
All other modules but one are operational (still not fully tested though),
I have already started working on the last one, which is also GUI based.

Cheers,
Yann

On Mar 20, 2017 5:25 PM, "Luca Delucchi"  wrote:

> On 18 March 2017 at 08:30, Blumentrath, Stefan
>  wrote:
> > Hi,
> >
>
> Hi,
>
> >
> > Could also porting (competition) of the i.ortho.photo modules (and here
> > especially the missing GUI modules around it) to GRASS 7 become scope of
> > this GSoC idea?
> >
>
> I fully support this idea, GUI for i.ortho.photo is the most important
> loss from GRASS 6
>
> >
> >
> > Cheers,
> >
> > Stefan
> >
>
>
> --
> ciao
> Luca
>
> www.lucadelu.org
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] extract list of commits from SVN

[Yann Chemin]

OK found it,

svn log --search yourusername

thanks,
Yann

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 11 March 2017 at 14:56, Yann Chemin <dr.yann.che...@gmail.com> wrote:

> Hi,
>
> I'd like to get a list of commits I made to SVN (and maybe to CVS before),
> is there anybody who knows?
>
> Thanks,
> Yann
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] extract list of commits from SVN

[Yann Chemin]

Hi,

I'd like to get a list of commits I made to SVN (and maybe to CVS before),
is there anybody who knows?

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

Re: [GRASS-dev] "add to display" when running module from the SHELL

[Yann Chemin]

yes this is indeed a pickle.

maybe something like:
-> d.mon "get the selected wx display, if none, then d.mon wx0"

if exist and selected:
add output from this module to its "stack" (i.e. set of already run d.*
commands)
-> v.random in=bla.vect out=blaout.vect -a
the -a flag in the module would take the actual selected monitor history of
d.* commands and add one line with the "d.vect blaout.vect" at the end, and
run the new history in it.


?




--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 3 February 2017 at 11:10, Martin Landa <landa.mar...@gmail.com> wrote:

> 2017-02-03 11:04 GMT+01:00 Yann Chemin <dr.yann.che...@gmail.com>:
> > say all raster and imagery and vector modules that generate output
> map(s), I
> > would like this(ese) map(s) to be added to the current stack in the
> current
> > display, the same way it works in the GUI version of the modules (i.e.
> > Check-box "Add created maps to layer tree").
>
> so, something like:
>
> # new flag -a: Add new maps to display automaticaly
> d.mon wx0 -a
> v.random out=p1 n=1000 # new map added to display
>
> ?
>
> But in this case you cannot control display parameters
> (d.vect/d.rast). There is no layer tree to define properties
> afterwards. I am not sure if such flag would make sense.
>
> Now you need:
>
> d.mon wx0
> v.random ...
> d.vect p1 ...
>
> Ma
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] "add to display" when running module from the SHELL

[Yann Chemin]

say all raster and imagery and vector modules that generate output map(s),
I would like this(ese) map(s) to be added to the current stack in the
current display, the same way it works in the GUI version of the modules
(i.e. Check-box "Add created maps to layer tree").


--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 3 February 2017 at 10:52, Martin Landa <landa.mar...@gmail.com> wrote:

> 2017-02-03 10:40 GMT+01:00 Yann Chemin <dr.yann.che...@gmail.com>:
> > I meant a flag in the module.
>
> flag of the module? Which module? Ma
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] "add to display" when running module from the SHELL

[Yann Chemin]

Thanks Martin,

I meant a flag in the module.

Yann

--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 3 February 2017 at 10:11, Martin Landa <landa.mar...@gmail.com> wrote:

> Hi,
>
> 2017-02-03 9:44 GMT+01:00 Yann Chemin <dr.yann.che...@gmail.com>:
> > in the GUI of modules we can select to add to display,
> > is there (or would there be) a possibility to do the same when running
> from
> > the CLI/SHELL?
>
> d.mon wx0
> d.rast ...
> d.vect ...
> ...
>
> Ma
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] "add to display" when running module from the SHELL

[Yann Chemin]

Hi,

in the GUI of modules we can select to add to display,
is there (or would there be) a possibility to do the same when running from
the CLI/SHELL?

Thank you,
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] cannot make it to Genova GFOSS.it 2017

[Yann Chemin]

Hi guys,

sorry cannot make it to Genova gfoss.it,
I'll try to do something over the week-end online though.

Ciao,
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] seg fault of i.atcorr on quickbird

[Yann Chemin]

Hey Markus,

my attempts have been umsuccessful so far, but i cannot yet say if it is my
fault or the module... i have not a good grasp on my dataset yet. will work
on it this week end.

cheers,
yann

On Dec 15, 2016 11:26 PM, "Markus Neteler"  wrote:

> Hi Yann,
>
> On Mon, Nov 28, 2016 at 7:34 PM, Markus Neteler  wrote:
> ...
> > ... the first column got messed up in the reformatting
> > of the CSV file. Fixed in SVN in r69943 (trunk), r69942 (7.2), r69941
> > (7.0).
> ...
> > I have updated the iwave.cpp code accordingly in all 7 branches and
> trunk.
> >
> > Yann, others: Please test.
>
> Does i.atcorr now work ok with Quickbird?
>
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] export vector file as multi-polygon from attribute column value

[Yann Chemin]

Hi,

I have a vector with polygons having same attribute value and would like
export it as multi-polygon according to that attribute column.

v.out.ogr export -m but does not seem to actually do that.

any idea?
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] man error on compilation

[Yann Chemin]

Thanks Vaclav,

the error came when I would not flush all containers from previous build.
If I build with --no-cache, the issue does not come.

Thanks for the check on empty keywords list, I am rebuilding it now.
Yann


--
Yann Chemin
Planetary Scientist
Latest: https://peerj.com/preprints/2124/
-
*JRC:*
https://www.thefreelibrary.com/3628+-+CANHEMON+Remote+sensing+based+forest+canopy+health+monitoring...-a0453990005
*OSGeo: *https://wiki.osgeo.org/wiki/Open_Monitoring_Systems_Working_Group


On 22 November 2016 at 18:58, Vaclav Petras <wenzesl...@gmail.com> wrote:

>
> On Tue, Nov 22, 2016 at 11:12 AM, Yann Chemin <dr.yann.che...@gmail.com>
> wrote:
>
>> I am compiling from SVN inside a docker (Debian testing)
>>
>>
> I'm just doing it with Ubuntu in Docker and I have no issue with r68881
> (docker run ... grass --config revision).
>
>
>> for some reason inside man/ the build_keywords.py bugs at line 63.
>>
>
> This looks like module without keywords or with an empty keyword. Are you
> using something else than code from trunk?
>
>
>>
>> GISBASE="/root/dev/grass_trunk/dist.x86_64-pc-linux-gnu"
>> ARCH="x86_64-pc-linux-gnu" ARCH_DISTDIR="/root/dev/grass_
>> trunk/dist.x86_64-pc-linux-gnu" VERSION_NUMBER=7.3.svn VERSION_DATE=2016
>> python ./build_keywords.py /root/dev/grass_trunk/dist.x86
>> _64-pc-linux-gnu/docs/html
>> Traceback (most recent call last):
>>   File "./build_keywords.py", line 63, in 
>> firstchar = key[0].lower()
>> IndexError: string index out of range
>
>
> r69871 checks for an empty keyword and fail because empty keyword should
> not happen. The error message tells file and line.
>
> Hope this helps,
> Vaclav
>
> https://trac.osgeo.org/grass/changeset/69871
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] man error on compilation

[Yann Chemin]

Hi,

I am compiling from SVN inside a docker (Debian testing)

for some reason inside man/ the build_keywords.py bugs at line 63.

GISBASE="/root/dev/grass_trunk/dist.x86_64-pc-linux-gnu"
ARCH="x86_64-pc-linux-gnu"
ARCH_DISTDIR="/root/dev/grass_trunk/dist.x86_64-pc-linux-gnu"
VERSION_NUMBER=7.3.svn VERSION_DATE=2016 python ./build_keywords.py
/root/dev/grass_trunk/dist.x86_64-pc-linux-gnu/docs/html
Traceback (most recent call last):
  File "./build_keywords.py", line 63, in 
firstchar = key[0].lower()
IndexError: string index out of range
Makefile:113: recipe for target
'/root/dev/grass_trunk/dist.x86_64-pc-linux-gnu/docs/html/keywords.html'
failed
make[1]: ***
[/root/dev/grass_trunk/dist.x86_64-pc-linux-gnu/docs/html/keywords.html]
Error 1
make[1]: Leaving directory '/root/dev/grass_trunk/man'
Makefile:43: recipe for target 'default' failed


thanks for any help,
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Upcoming 7.2.0: review which addons to move to core

[Yann Chemin]

Hi,

added my feelings (biased towards remote sensing, I admit)

+1 => r.streams.*
+1 => r.geomorphon
+0 => i.segment.hierarchical (+1 if manual complete)
+0 => v.class.mlpy
+1 => v.class.ml
+1 => r.randomforest
+1 => i.segment.stats
+1 => r.object.geometry
+0 => v.class.mlR
+0 => i.segment.uspo (but +1 if r.neighborhoodmatrix is included in core)
+1 => i.landsat8.*
+1 => i.spec.sam
+1 => i.edge
+1 => i.histo.match



On 30 September 2016 at 09:19, Moritz Lennert <mlenn...@club.worldonline.be>
wrote:

> On 29/09/16 23:49, Blumentrath, Stefan wrote:
>
>> Hi,
>>
>>
>>
>> This discussion is actually a bit old, but maybe it is not too late to
>> consider adding selected addons to trunk?
>>
>>
>>
>> From my personal user point of view the r.streams.* modules and
>> r.geomorphon are indeed top candidates for inclusion in core!
>>
>>
>>
>> However, also:
>>
>>
>>
>> i.segment.hierarchical (though manual is not yet complete)
>>
>
> I've been working on trying to understand the exact functioning of the
> module and on writing some documentation on this, but this has been
> side-tracked by the many other priorities at work...
>
>
> v.class.mlpy (drawback: requires mlpy library) or v.class.ml and
>>
>> r.randomforest
>>
>> could nicely complement the image classification tools in GRASS.
>>
>
> +1
>
> In the same line, it might be nice to add:
>
> i.segment.stats and r.object.geometry.
>
> And possibly also v.class.mlR and i.segment.uspo...
>
> Moritz
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>



-- 
Yann Chemin
Skype/FB: yann.chemin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] ubuntu gis policy

[Yann Chemin]

+1
same problem been seen more than once

On 16 September 2016 at 13:12, Blumentrath, Stefan <
stefan.blumentr...@nina.no> wrote:

> Hei Martin,
>
> Do you have any chance to influence the naming of the PPAs?
>
> As recently also discussed on the QGIS mailinglist, packages from a
> repository named "unstable" can get blocked by system administrators (who
> not necessarily will take the time to try to understand what is behind all
> applications), regardless if I as a user tell them that "unstable" actually
> means "current release"...
>
> Would be nice to have a more admin-friendly name there...
>
> Cheers
> Stefan
>
> -Original Message-
> From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of
> Martin Landa
> Sent: 16. september 2016 13:03
> To: GRASS users list <grass-u...@lists.osgeo.org>; GRASS developers list <
> grass-dev@lists.osgeo.org>
> Subject: [GRASS-dev] ubuntu gis policy
>
> Hi all,
>
> recently ubuntugis maintainers changed their policy. This means that
> currently is used this workflow:
>
> OSGeoLive nightly --> UbuntuGIS Testing --> UbuntuGIS Unstable -->
> UbuntuGIS Stable
>
> What does it means for GRASS?
>
> 1) experimental packages (like Release Candidates) are uploaded to Testing
> PPA [1]
> 2) final version packages are uploaded to Testing and Unstable [2]
> 3) Stable PPA can contain older version [3]
>
> For user who want to help with testing experimental packages: please use
> Testing PPA otherwise use Unstable (if you prefer up-to-date
> version) or Stable PPA (you prefer stability - slightly older versions).
>
> Martin
>
> [1] https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-testing
> [2] https://launchpad.net/~ubuntugis/+archive/ubuntu/ubuntugis-unstable
> [3] https://launchpad.net/~ubuntugis/+archive/ubuntu/ppa
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.cz/mentors/landa
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>



-- 
Yann Chemin
Skype/FB: yann.chemin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Raster data compression confusion: identical CELL file size

[Yann Chemin]

On 6 September 2016 at 15:23, Markus Metz <markus.metz.gisw...@gmail.com>
wrote:

> On Tue, Sep 6, 2016 at 1:44 PM, Markus Neteler <nete...@osgeo.org> wrote:
> > Hi,
> >
> > since my local drive was filled up again :) I checked raster how data are
> > currently compressed in GRASS GIS 7.2.svn.
> > According to
> >
> > https://grass.osgeo.org/grass72/manuals/r.compress.
> html#used-compression-algorithms
> >
> > all maps are DEFLATE compressed by default:
> >
> > "Raster maps are by default ZLIB compressed.
> > ...
> >
> > Floating point (FCELL, DCELL) raster maps never use RLE compression; they
> > are either compressed with ZLIB, LZ4, BZIP2 or are uncompressed.
> > "
> >
> > Ehm, now how *are* FCELL, DCELL compressed by default? Not quite clear to
> > me! This document needs improvements.
>
> The manual says, as you cited:
> "Raster maps are by default ZLIB compressed."
> What exactly is unclear about this? Should it say "All raster maps ..." ?
>
> >
> > Reality check with Sentinel-2 data (3 different bands, same regional
> > extent):
> >
> > GRASS 7.2.svn (utm37n):~ > r.info -r s2_20151225_B02_10m
> > min=0
> > max=22937
> > GRASS 7.2.svn (utm37n):~ > r.info -r s2_20151225_B04_10m
> > min=0
> > max=18849
> > GRASS 7.2.svn (utm37n):~ > r.info -r s2_20151225_B8A_20m
> > min=0
> > max=17210
> >
> > GRASS 7.2.svn (utm37n):~ >:~ > r.compress s2_20151225_B02_10m -p
> >  is compressed (method 2: ZLIB). Data type:
> > CELL
> >
> > GRASS 7.2.svn (utm37n):~ >:~ > r.compress s2_20151225_B04_10m -p
> >  is compressed (method 2: ZLIB). Data type:
> > CELL
> >
> > GRASS 7.2.svn (utm37n):~ >:~ > r.compress s2_20151225_B8A_20m -p
> >  is compressed (method 2: ZLIB). Data type:
> > CELL
> >
> > So far so nice. Now the suprising part, while the channels are not
> identical
> > (obviously, since covering different spectral parts), the map sizes are
> > identical!
> >
> > GRASS 7.2.svn (utm37n):~ > ls -la
> > ...
> > -rw-r--r--  1 neteler neteler 2539235691 Jun 14 17:14 s2_20151225_B02_10m
> > -rw-r--r--  1 neteler neteler 2539235691 Jun 14 17:19 s2_20151225_B03_10m
> > -rw-r--r--  1 neteler neteler 2539235691 Jun 14 17:25 s2_20151225_B04_10m
> > -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:36 s2_20151225_B05_20m
> > -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:37 s2_20151225_B06_20m
> > -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:39 s2_20151225_B07_20m
> > -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:40 s2_20151225_B11_20m
> > -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:42 s2_20151225_B12_20m
> > -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:43 s2_20151225_B8A_20m
> >
> > I would expect different sizes, compression can hardly lead to identical
> > file sizes.
>
> The default ZLIB compression level was invalid, causing ZLIB to not
> compress at all. Fixed in r69387,8.
>
> Markus M
>
> >
> > Next test: gzip the file
> >
> > GRASS 7.2.svn (utm37n):~/grassdata/utm37n/PERMANENT/cell > ls -la
> > s2_20151225_B03_10m
> > -rw-r--r-- 1 mneteler mneteler 2539235691 Jun 14 17:19
> s2_20151225_B03_10m
> >
> > GRASS 7.2.svn (utm37n):~/grassdata/utm37n/PERMANENT/cell > gzip
> > s2_20151225_B03_10m
> >
> > GRASS 7.2.svn (utm37n):~/grassdata/utm37n/PERMANENT/cell > ls -la
> > s2_20151225_B03_10m.gz
> > -rw-r--r-- 1 mneteler mneteler 1456248453 Jun 14 17:19
> > s2_20151225_B03_10m.gz
> >
> > R
> >> 1456248453/2539235691
> > [1] 0.5734987
> >
> > Quite smaller! So I am not at all convinced that these CELL files are
> > currently ZLIB compressed.
>
> Compressing a whole file instead of compressing each row separately
> (GRASS reads and writes raster data row by row) can lead to higher
> compression ratios.
>

This brings to a long time amount of discussions about parallelization
speed-ups of raster functions being limited by the row-based I/O of GRASS.
Maybe we should look into this for GRASS8...


>
> >
> > From this ticket I would expect something else:
> > https://trac.osgeo.org/grass/ticket/2349
> >
> > Ah, and no specific environment variables are set:
> >
> > GRASS 7.2.svn (utm37n):~ > echo $GRASS_
> > $GRASS_ADDON_BASE   $GRASS_GNUPLOT$GRASS_HTML_BROWSER  $GRASS_PAGER
> > $GRASS_PROJSHARE$GRASS_PYTHON $GRASS_VERSION
> >
> >
> > A bug?
> >
> > Markus
> >
> > ___
> > grass-dev mailing list
> > grass-dev@lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/grass-dev
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>



-- 
Yann Chemin
Skype/FB: yann.chemin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Raster data compression confusion: identical CELL file size

[Yann Chemin]

Hi,

lower level inconsistency is a no-go.
This should be fixed soonest on all 7.x versions IMHO.

Besides, reading the ticket 2349 mentioned, it is remarkable that NULL map
are never compressed by default.

yann

On 6 September 2016 at 13:44, Markus Neteler <nete...@osgeo.org> wrote:

> Hi,
>
> since my local drive was filled up again :) I checked raster how data are
> currently compressed in GRASS GIS 7.2.svn.
> According to
>
> https://grass.osgeo.org/grass72/manuals/r.compress.html#used-compression-
> algorithms
>
> all maps are DEFLATE compressed by default:
>
> "Raster maps are by default ZLIB compressed.
> ...
>
> Floating point (FCELL, DCELL) raster maps never use RLE compression; they
> are either compressed with ZLIB, LZ4, BZIP2 or are uncompressed.
> "
>
> Ehm, now how *are* FCELL, DCELL compressed by default? Not quite clear to
> me! This document needs improvements.
>
> Reality check with Sentinel-2 data (3 different bands, same regional
> extent):
>
> GRASS 7.2.svn (utm37n):~ > r.info -r s2_20151225_B02_10m
> min=0
> max=22937
> GRASS 7.2.svn (utm37n):~ > r.info -r s2_20151225_B04_10m
> min=0
> max=18849
> GRASS 7.2.svn (utm37n):~ > r.info -r s2_20151225_B8A_20m
> min=0
> max=17210
>
> GRASS 7.2.svn (utm37n):~ >:~ > r.compress s2_20151225_B02_10m -p
>  is compressed (method 2: ZLIB). Data type:
> CELL
>
> GRASS 7.2.svn (utm37n):~ >:~ > r.compress s2_20151225_B04_10m -p
>  is compressed (method 2: ZLIB). Data type:
> CELL
>
> GRASS 7.2.svn (utm37n):~ >:~ > r.compress s2_20151225_B8A_20m -p
>  is compressed (method 2: ZLIB). Data type:
> CELL
>
> So far so nice. Now the suprising part, while the channels are not
> identical (obviously, since covering different spectral parts), the map
> sizes are identical!
>
> GRASS 7.2.svn (utm37n):~ > ls -la
> ...
> -rw-r--r--  1 neteler neteler 2539235691 Jun 14 17:14 s2_20151225_B02_10m
> -rw-r--r--  1 neteler neteler 2539235691 Jun 14 17:19 s2_20151225_B03_10m
> -rw-r--r--  1 neteler neteler 2539235691 Jun 14 17:25 s2_20151225_B04_10m
> -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:36 s2_20151225_B05_20m
> -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:37 s2_20151225_B06_20m
> -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:39 s2_20151225_B07_20m
> -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:40 s2_20151225_B11_20m
> -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:42 s2_20151225_B12_20m
> -rw-r--r--  1 neteler neteler  634878630 Jun 14 20:43 s2_20151225_B8A_20m
>
> I would expect different sizes, compression can hardly lead to identical
> file sizes.
>
> Next test: gzip the file
>
> GRASS 7.2.svn (utm37n):~/grassdata/utm37n/PERMANENT/cell > ls -la
> s2_20151225_B03_10m
> -rw-r--r-- 1 mneteler mneteler 2539235691 Jun 14 17:19 s2_20151225_B03_10m
>
> GRASS 7.2.svn (utm37n):~/grassdata/utm37n/PERMANENT/cell > gzip
> s2_20151225_B03_10m
>
> GRASS 7.2.svn (utm37n):~/grassdata/utm37n/PERMANENT/cell > ls -la
> s2_20151225_B03_10m.gz
> -rw-r--r-- 1 mneteler mneteler 1456248453 Jun 14 17:19
> s2_20151225_B03_10m.gz
>
> R
> > 1456248453/2539235691
> [1] 0.5734987
>
> Quite smaller! So I am not at all convinced that these CELL files are
> currently ZLIB compressed.
>
> From this ticket I would expect something else:
> https://trac.osgeo.org/grass/ticket/2349
>
> Ah, and no specific environment variables are set:
>
> GRASS 7.2.svn (utm37n):~ > echo $GRASS_
> $GRASS_ADDON_BASE   $GRASS_GNUPLOT$GRASS_HTML_BROWSER  $GRASS_PAGER
> $GRASS_PROJSHARE$GRASS_PYTHON $GRASS_VERSION
>
>
> A bug?
>
> Markus
>
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
>



-- 
Yann Chemin
Skype/FB: yann.chemin
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] IAU to wkt C code (converted from Trent Hare's Python code)

[Yann Chemin]

Checking with Trent, will report here soon.
On May 5, 2016 7:57 PM, "Markus Neteler"  wrote:

> Hi Yann,
>
> back to this topic:
>
> On Tue, Feb 23, 2016 at 5:26 PM, Yann  wrote:
> ...
> > I have converted the Python script
> > from Trent Hare to generate on the fly PROJCS and GEOCS WKTdescriptions
> for
> > all IAU2000 and IAU2009.
> ...
> > PS: GDAL is also going to insert it.
>
> Did this actually happen?
>
> Because GRASS no longer reads local CSV files and - to my knowledge -
> completely relies on GDAL/PROJ (see
> https://trac.osgeo.org/grass/ticket/2456).
> Hence, your two CSV files iau2000.csv + iau2009.csv and no longer shipped.
>
> Can you confirm that all works fine through GDAL (which version is
> needed to have IAU support?)
> ?
>
> thanks
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Fwd: FOSS4G 2016 Bonn - GRASS GIS Community Sprint

[Yann Chemin]

Would be intérested indeed...
On Nov 2, 2015 3:03 PM, "Markus Neteler"  wrote:

> Hi devs,
>
> please let us know about your interest.
> Guess we should add a new page in our wiki.
>
> Markus
>
>
> -- Forwarded message --
> From: Astrid Emde FOSSGIS e.V. 
> Date: Mon, Nov 2, 2015 at 12:33 PM
> Subject: Re: FOSS4G 2016 Bonn - GRASS GIS Community Sprint
>
> Am 07.10.2015 10:28, schrieb Markus Neteler:
> > Hi Astrid,
> >
> > we are interested to organize a GRASS GIS Community Sprint at the
> > FOSS4G in Bonn.
> [...]
>
> Hi Markus,
>
> here are the dates for the FOSS4G 2016 code sprint
>
> # CodeSprint I: Sun 21.08.2016 12:00 - Tue 23.08.2016 (open end)
> # CodeSprint II: Sat 27.08.2016 - Sun 28.08.2016 12:00 a.m
>
> Maybe you already could estimate how many people will come from your
> community.
>
> --
> Thanks
> Astrid Emde
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-dev
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] sugestions for an interactive 2 points loop gathering

[Yann Chemin]

Hi,

I would like to build an interactive module that would just gather two
points (a center and a peripheric distance) in a loop fashion and add that
to a text file in X1,Y1,X2,Y2.

I am not familiar with the GUI programming as it is to date, but happy to
learn the needed.

Cheers,
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Add support for Python3

[Yann Chemin]

+1

On Fri, Jul 24, 2015 at 4:12 PM Pietro peter.z...@gmail.com wrote:

 Dear devs,

 Next week I would like to start the merge between my local changes and
 trunk to support Python3.
 As reported in the ticket: https://trac.osgeo.org/grass/ticket/2708

 I've tested the changes with python2.6, python2.7 and python3.4.
 So far I've not found regressions in python2.X.

 The status quo for python3 is:
 - the binding of the C GRASS functions is not working;
 - several python modules (~90) are not readable/usable, I've already
 started to port them (~20)

 My idea for the porting is to gradually introduce changes per steps:
 - Monday 27, change only the grass-init and the gunittest;
 - If not new problems connected to previous changes raise, Wendesday
 29 I commit the grass/script stuff
 - If not new problems connected to previous changes raise, I will
 start updating the GRASS modules.

 In the meanwhile I try to get the ctypes working on PY3.

 Are you ok with this schedule?
 Other better options?

 Let me know

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

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

[GRASS-dev] OpenMP 4.0 / gcc5.0

[Yann Chemin]

Hi,

Ubuntu Wily is going towards gcc5.0 as we speak.
anybody following the OpenMP 4.0 integration into gcc 5.0?
it seems there is embedding of heterogeneous computing in it (i.e. ala
OpenCL).

is GRASS code using OpenMP forward compatible with this, or will it need
modification?

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

Re: [GRASS-dev] Next GRASS community sprint

[Yann Chemin]

Have fun guys ! Wish I was there too !

On Sat, Jul 18, 2015 at 6:02 PM Markus Neteler nete...@osgeo.org wrote:

 Hi all,

 today the GRASS GIS community sprint in Como started!

 http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Como_2015

 At time 10 grass-devs are here.

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

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

Re: [GRASS-dev] Fwd: Re: [gdal-dev] Setting NODATA to -nan

[Yann Chemin]

Hi,

it might be that some communication improvement from GRASS-GDAL could be
done?

is there a clear NODATA/NAN definition understood within GDAL that we could
use within r.out.gdal as a target NODATA value whenever anything than a
number is used (i.e. NaN, nan, -nan, helloworld, mynameisbee, etc.)

typically MODIS users are used to -28768 and similar standard NODATA
numbers, but that maybe another story.

0.01c



On Thu, Jul 16, 2015 at 6:34 PM Markus Neteler nete...@osgeo.org wrote:

 Hi devs,

 FWD of an issue with r.out.gdal in G7. Any ideas?

 Markus


 -- Forwarded message --
 From: Even Rouault even.roua...@spatialys.com
 Date: Thu, Jul 16, 2015 at 2:07 AM
 Subject: Fwd: Re: [gdal-dev] Setting NODATA to -nan
 To: nete...@osgeo.org


 Hi Markus,

 Below you'll find the original report about what discussed on the way to
 the
 party tonight, and then my analysis. The GDAL ticket with the dataset is
 https://trac.osgeo.org/gdal/ticket/6036

 I'm not sure there's really an issue in practice on the GDAL side. It is
 just
 that dealing with nan is odd to anybody (and the way Windows and Linux
 displays nan as a string is different).

 Even




 [gdal-dev] Setting NODATA to -nan
 From:   Homme Zwaagstra h...@geodata.soton.ac.uk
 To: gdal-dev gdal-...@lists.osgeo.org
 Date:   Yesterday 11:21:54
 Hello,

 I've got the following raster exported from GRASS using `r.out.gdal`:

 gdalinfo ppp-2015.tif
 Driver: GTiff/GeoTIFF
 Files: ppp-2015.tif
 ppp-2015.tif.aux.xml
 Size is 432017, 216009
 Coordinate System is:
 GEOGCS[WGS 84,
  DATUM[WGS_1984,
  SPHEROID[WGS 84,6378137,298.257223563,
  AUTHORITY[EPSG,7030]],
  AUTHORITY[EPSG,6326]],
  PRIMEM[Greenwich,0],
  UNIT[degree,0.0174532925199433],
  AUTHORITY[EPSG,4326]]
 Origin = (-180.000,90.000)
 Pixel Size = (0.000833300541414,-0.000833298612558)
 Metadata:
AREA_OR_POINT=Area
 Image Structure Metadata:
COMPRESSION=DEFLATE
INTERLEAVE=BAND
 Corner Coordinates:
 Upper Left  (-180.000,  90.000) (180d 0' 0.00W, 90d 0' 0.00N)
 Lower Left  (-180.000, -90.000) (180d 0' 0.00W, 90d 0' 0.00S)
 Upper Right ( 180.000,  90.000) (180d 0' 0.00E, 90d 0' 0.00N)
 Lower Right ( 180.000, -90.000) (180d 0' 0.00E, 90d 0' 0.00S)
 Center  (   0.000,   0.000) (  0d 0' 0.01E,  0d 0' 0.01N)
 Band 1 Block=256x256 Type=Float32, ColorInterp=Gray
NoData Value=nan
Metadata:
  COLOR_TABLE_RULES_COUNT=5
  COLOR_TABLE_RULE_RGB_0=0.00e+00 1.681282e+03 255 255 0 0 255 0
  COLOR_TABLE_RULE_RGB_1=1.681282e+03 3.362563e+03 0 255 0 0 255 255
  COLOR_TABLE_RULE_RGB_2=3.362563e+03 5.043845e+03 0 255 255 0 0 255
  COLOR_TABLE_RULE_RGB_3=5.043845e+03 6.725127e+03 0 0 255 255 0 255
  COLOR_TABLE_RULE_RGB_4=6.725127e+03 8.406408e+03 255 0 255 255 0 0
  Generated_with=GRASS GIS 7.0.0

 As you can see the NoData is set to `nan`.  However, within the data it is
 actually `-nan`:

 gdallocationinfo ppp-2015.tif -wgs84 42.0776 30.9305
 Report:
Location: (266503P,70886L)
Band 1:
  Value: -nan

 I have tried to force the NoData to `-nan` as follows but with no joy:

 gdal_translate -a_nodata '-nan' -of VRT ppp-2015.tif ppp-2015.vrt

 gdalinfo ppp-2015.vrt
 Driver: VRT/Virtual Raster
 Files: ppp-2015.vrt
 /data/data/ppp_v2c_2015/ppp-2015.tif
 Size is 432017, 216009
 Coordinate System is:
 GEOGCS[WGS 84,
  DATUM[WGS_1984,
  SPHEROID[WGS 84,6378137,298.257223563,
  AUTHORITY[EPSG,7030]],
  AUTHORITY[EPSG,6326]],
  PRIMEM[Greenwich,0],
  UNIT[degree,0.0174532925199433],
  AUTHORITY[EPSG,4326]]
 Origin = (-180.000,90.000)
 Pixel Size = (0.000833300541414,-0.000833298612558)
 Metadata:
AREA_OR_POINT=Area
 Image Structure Metadata:
INTERLEAVE=BAND
 Corner Coordinates:
 Upper Left  (-180.000,  90.000) (180d 0' 0.00W, 90d 0' 0.00N)
 Lower Left  (-180.000, -90.000) (180d 0' 0.00W, 90d 0' 0.00S)
 Upper Right ( 180.000,  90.000) (180d 0' 0.00E, 90d 0' 0.00N)
 Lower Right ( 180.000, -90.000) (180d 0' 0.00E, 90d 0' 0.00S)
 Center  (   0.000,   0.000) (  0d 0' 0.01E,  0d 0' 0.01N)
 Band 1 Block=128x128 Type=Float32, ColorInterp=Gray
NoData Value=nan
Metadata:
  COLOR_TABLE_RULES_COUNT=5
  COLOR_TABLE_RULE_RGB_0=0.00e+00 1.681282e+03 255 255 0 0 255 0
  COLOR_TABLE_RULE_RGB_1=1.681282e+03 3.362563e+03 0 255 0 0 255 255
  COLOR_TABLE_RULE_RGB_2=3.362563e+03 5.043845e+03 0 255 255 0 0 255
  COLOR_TABLE_RULE_RGB_3=5.043845e+03 6.725127e+03 0 0 255 255 0 255
  COLOR_TABLE_RULE_RGB_4=6.725127e+03 8.406408e+03 255 0 255 255 0 0
  Generated_with=GRASS GIS 7.0.0

 Even editing the VRT to contain `NoDataValue-nan/NoDataValue` yields a
 positive nan value in gdalinfo.

 This looks like it might be a GDAL bug to me?  Is there a way I can specify
 `-nan` as the NODATA value for 

Re: [GRASS-dev] r.in.proj v.in.proj to trunk

[Yann Chemin]

+1 !

On Tue, Jul 14, 2015 at 11:33 PM Markus Neteler nete...@osgeo.org wrote:

 On Tue, Jul 14, 2015 at 6:02 PM, Martin Landa landa.mar...@gmail.com
 wrote:
  Hi,
 
  I would like to express my wish to copy r|v.in.proj from addons to
  trunk as a core module.

 +1!

  The modules will be still available via addons
  for GRASS 7.0 users. It has one disadvange the code duplication in
  trunk and addons.
 
  What do you think?

 Since it is not subject to heavy changes I don't see this as a real
 problem.

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

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

Re: [GRASS-dev] i.atcorr manual typo

[Yann Chemin]

Thanks Martin

On Sat, Jun 13, 2015 at 2:56 PM Martin Landa landa.mar...@gmail.com wrote:

 Hi,

 2015-06-13 7:04 GMT+02:00 Yann Chemin yche...@gmail.com:
  in manual:
  17 | LandSat 8 | enter month,day,hh.ddd,long.,lat. *  - should be 18

 done r65456. Martin

 --
 Martin Landa
 http://geo.fsv.cvut.cz/gwiki/Landa
 http://gismentors.cz/mentors/landa

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

[GRASS-dev] i.atcorr manual typo

[Yann Chemin]

Hi, I am not able to submit a change now, but there is a small typo in the
i.atcorr manual:

in geomcond.cpp:
case 18: /* Landsat 8* enter month,day,hh.ddd,long.,lat. */

in manual:
17 | LandSat 8 | enter month,day,hh.ddd,long.,lat. *  - should be 18

Thank you,
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Mac Compilation issue (iconv)

[Yann Chemin]

Hi,

facing a little issue with iconv on Mac.
Anybody experienced this before?

YMP:/lib/driver yann$ make
cc -dynamiclib -compatibility_version 7.1 -current_version 7.1 -install_name 
/Applications/GRASS-7.1.app/Contents/MacOS/lib/libgrass_driver.7.1.svn.dylib -o 
/Users/yann/dev/grass_yann/dist.x86_64-apple-darwin14.3.0/lib/libgrass_driver.7.1.svn.dylib
 -L/Users/yann/dev/grass_yann/dist.x86_64-apple-darwin14.3.0/lib 
-L/Users/yann/dev/grass_yann/dist.x86_64-apple-darwin14.3.0/lib -isysroot 
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk
   -L/sw/lib/gcc4.9/lib/gcc/x86_64-apple-darwin14.1.0/4.9.2   
OBJ.x86_64-apple-darwin14.3.0/font2.o 
OBJ.x86_64-apple-darwin14.3.0/set_window.o 
OBJ.x86_64-apple-darwin14.3.0/raster.o 
OBJ.x86_64-apple-darwin14.3.0/text_size.o 
OBJ.x86_64-apple-darwin14.3.0/parse_ftcap.o 
OBJ.x86_64-apple-darwin14.3.0/color.o OBJ.x86_64-apple-darwin14.3.0/text2.o 
OBJ.x86_64-apple-darwin14.3.0/font.o OBJ.x86_64-apple-darwin14.3.0/erase.o 
OBJ.x86_64-apple-darwin14.3.0/font_freetype.o 
OBJ.x86_64-apple-darwin14.3.0/line_width.o OBJ.
 x86_64-apple-darwin14.3.0/path.o OBJ.x86_64-apple-darwin14.3.0/text.o 
OBJ.x86_64-apple-darwin14.3.0/draw.o OBJ.x86_64-apple-darwin14.3.0/box.o 
OBJ.x86_64-apple-darwin14.3.0/graph.o OBJ.x86_64-apple-darwin14.3.0/init.o 
OBJ.x86_64-apple-darwin14.3.0/move.o OBJ.x86_64-apple-darwin14.3.0/get_t_box.o 
OBJ.x86_64-apple-darwin14.3.0/text3.o  -lgrass_gis.7.1.svn -L/sw/lib -lfreetype 
 -liconv  
Undefined symbols for architecture x86_64:
  _iconv, referenced from:
  _draw_main in text3.o
  _iconv_close, referenced from:
  _draw_main in text3.o
  _iconv_open, referenced from:
  _draw_main in text3.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status
../../include/Make/Shlib.make:10: recipe for target 
'/Users/yann/dev/grass_yann/dist.x86_64-apple-darwin14.3.0/lib/libgrass_driver.7.1.svn.dylib'
 failed
make: *** 
[/Users/yann/dev/grass_yann/dist.x86_64-apple-darwin14.3.0/lib/libgrass_driver.7.1.svn.dylib]
 Error 1

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

[GRASS-dev] distributed computing: block access in raster lib

[Yann Chemin]

Hi,

I am looking into distributed processing of raster data in GRASS,

I found this in i.smap/read_block.c

Would that be a good idea to include something similar into the raster lib API?

#include stdlib.h

#include grass/raster.h
#include grass/imagery.h
#include grass/glocale.h

#include bouman.h
#include region.h

int read_block(DCELL *** img,   /* img[band][row[col] */
   struct Region *region, struct files *files)
{
int band, row, col;

for (band = 0; band  files-nbands; band++) {
for (row = region-ymin; row  region-ymax; row++) {
Rast_get_d_row(files-band_fd[band], files-cellbuf, row);
for (col = region-xmin; col  region-xmax; col++)
img[band][row][col] = files-cellbuf[col];
}
}

return 0;
}

Cheers,
Yann___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Next GRASS community sprint

[Yann Chemin]

Wow ! Como ! Would be so fun …

 On Apr 7, 2015, at 10:48 AM, Luca Delucchi lucadel...@gmail.com wrote:
 
 Hi devs,
 
 please consider to add you name to the list [0].
 
 In the next days I'll start to contact owners to find a place where to stay...
 
 Thanks
 
 [0] http://grasswiki.osgeo.org/wiki/GRASS_Community_Sprint_Como_2015#In_person
 
 On 14 March 2015 at 22:58, Markus Neteler nete...@osgeo.org wrote:
 Hi
 
 I'll will be there. And looking forward to it :)
 
 Markus
 
 
 
 -- 
 ciao
 Luca
 
 http://gis.cri.fmach.it/delucchi/
 www.lucadelu.org
 ___
 grass-dev mailing list
 grass-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-dev

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

[GRASS-dev] GRASS GIS spectral analysis status

[Yann Chemin]

Hi Devs,

Just looking at what GRASS does in the spectral domain, as a planetary 
scientist asked me how far GRASS could go to replace ENVI capabilities in that 
matter.

i.spec.unmix
i.spec.sam
i.spectral

is there any other tool that directly relate to spectral analysis?

Thx
Yann

PS: would there be a potential for GSoC or the ESA equivalent?
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] g.mapset a bit more click-friendly (creating G_OPT_M_LOCATION ?)

[Yann Chemin]

Thank you Anna, 

g.mapset is now working as I meant to explain, 
that is that is a gisdbase is given a wrong directory, 
then no Location appears in the location combo box.

Yann

 On Feb 25, 2015, at 6:28 AM, Anna Petrášová kratocha...@gmail.com wrote:
 
 
 
 On Sun, Feb 22, 2015 at 1:00 AM, Yann Chemin yche...@gmail.com 
 mailto:yche...@gmail.com wrote:
 Hi Vaclav,
 
 looking into getting g.mapset module a bit more click-based,
 already gisdbase is selectable with G_OPT_M_DIR.
 
 There is already a G_OPT_M_MAPSET with a combo box, that it cool.
 It would be nice to have a similar combo box for Location selection.
 
 Maybe a G_OPT_M_LOCATION is needed?
 
 Done in r64732 and r64733.
 
 For location we need to have some check done directly on directory selection, 
 or is it OK on running the module?
 
 I am not sure what do you mean?
 
 Anna 
 
 Yann
 ___
 grass-dev mailing list
 grass-dev@lists.osgeo.org mailto:grass-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-dev 
 http://lists.osgeo.org/mailman/listinfo/grass-dev
 

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

Re: [GRASS-dev] Vertical tabs for module's wxGUI interface?

[Yann Chemin]

 On Feb 22, 2015, at 9:06 PM, Pietro peter.z...@gmail.com wrote:
 
 Hi Nikos,
 
 On Sun, Feb 22, 2015 at 3:55 PM, Nikos Alexandris
 n...@nikosalexandris.net wrote:
 where is this screenshot
 http://ncsu-osgeorel.github.io/grass-temporal-workshop/pictures/tregister.png
 coming from?  The vertical arrangement of tabs is awesome!
 
 You can set the vertical tabs in preference, it is my favorite
 arrangement, I thin should be the GRASS default option (imho).
 

+1

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

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

[GRASS-dev] WARNING: No metadata file available more verbose?

[Yann Chemin]

Starting a session I get:
 WARNING: No metadata file available

Can this be including a small hint to fix it.
Yann___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] WARNING: No metadata file available more verbose?

[Yann Chemin]

 On Feb 22, 2015, at 8:28 AM, Vaclav Petras wenzesl...@gmail.com wrote:
 
 
 
 On Sat, Feb 21, 2015 at 9:49 PM, Yann Chemin yche...@gmail.com 
 mailto:yche...@gmail.com wrote:
 Starting a session I get:
 WARNING: No metadata file available
 
 Can this be including a small hint to fix it.
 Yann
 
 I don't know what is the reason for the message. How is your grass7 
 directory? Other circumstances? See the source code here:
 

it is a new compile of svn on Mac, opening a mapset that is few months old. I 
am compiling the add-ons too in it.

 https://trac.osgeo.org/grass/browser/grass/trunk/scripts/g.extension/g.extension.py#L195
  
 https://trac.osgeo.org/grass/browser/grass/trunk/scripts/g.extension/g.extension.py#L195
 
 Vaclav
 
 PS: Which system/terminal emulator is preserving colors when copy pasting 
 from command line? (so I can avoid it :-)
  

Yeah i am struggling with that too… That is the “added benefits” of Mac. :-)

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

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

[GRASS-dev] g.mapset a bit more click-friendly (creating G_OPT_M_LOCATION ?)

[Yann Chemin]

Hi Vaclav,

looking into getting g.mapset module a bit more click-based, 
already gisdbase is selectable with G_OPT_M_DIR.

There is already a G_OPT_M_MAPSET with a combo box, that it cool.
It would be nice to have a similar combo box for Location selection.

Maybe a G_OPT_M_LOCATION is needed?

For location we need to have some check done directly on directory selection, 
or is it OK on running the module?

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

Re: [GRASS-dev] osgeo4w package for GRASS 7

[Yann Chemin]

 On Feb 22, 2015, at 3:48 AM, Helmut Kudrnovsky hel...@web.de wrote:
 
 wenzeslaus wrote
 On Sat, Feb 21, 2015 at 12:17 PM, Martin Landa lt;
 
 landa.martin@
 
 gt;
 wrote:
 
 2015-02-21 17:49 GMT+01:00 Martin Landa lt;
 
 landa.martin@
 
 gt;:
 Except for grass6-dev: does it really make sense to still publish a
 -dev
 version of grass6 ? In my thinking we will be in pure bug fixing mode
 for
 grass6 once grass7 is out. I would actually plead to reduce to one
 grass6
 branch on trac with bug-fixes only for that branch and bug-fix
 releases
 just
 being tags of that branch.
 
 make sense to me. Martin
 
 to summarize OSGeo4W proposal:
 
 * `grass` will be 7.0.0
 * `grass6` will be 6.4.4 (hopefully soon 6.4.5)
 * `grass-svn` will be 7.0.1svn (*)
 * `grass-trunk-svn` will be 7.1svn
 * `grass64-dev` will be removed
 
 Martin
 
 (*) `dev` is really misleading here, so `svn` or `daily` (`svn` sounds
 more technical).
 
 
 I don't like svn in package names. Daily expresses much better what it is.
 It is not the current state of svn, it is a daily build. With leaving out
 the daily builds of current release branch (now 70), it would be just:
 
 * `grass` - latest stable release
 * `grass6` - latest stable release of 6.x series
 * `grass-daily` - daily build of trunk
 
 In my suggestion I suppose that we don't need to package daily builds of
 current release branch (now 70). However, I'm not sure how to deal with
 betas and RCs. Should they be also accessible just through standalone
 installer? Or are they considered as latest stable release and thus for
 example, 7.0.1RC1 would replace 7.0.0 in package `grass`?
 
 ___
 grass-dev mailing list
 
 grass-dev@.osgeo
 
 http://lists.osgeo.org/mailman/listinfo/grass-dev
 
 why not just retire OSGeo4W-grass6 after grass 7.0.1 will be released?
 

+1

 IMHO regarding testing/improving g7 by devs _and_ users, it's better to have
 relbranch7 dailys ready in OSGeo4W than fading out grass6.
 
 
 
 -
 best regards
 Helmut
 --
 View this message in context: 
 http://osgeo-org.1560.x6.nabble.com/osgeo4w-package-for-GRASS-7-tp5189077p5189160.html
 Sent from the Grass - Dev mailing list archive at Nabble.com.
 ___
 grass-dev mailing list
 grass-dev@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/grass-dev

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

Re: [GRASS-dev] WARNING: No metadata file available more verbose?

[Yann Chemin]

ls ../.grass7/
rc  toolboxes

I compile add-ons directly in the tree.

 On Feb 22, 2015, at 9:08 AM, Vaclav Petras wenzesl...@gmail.com wrote:
 
 
 On Sat, Feb 21, 2015 at 10:02 PM, Yann Chemin yche...@gmail.com 
 mailto:yche...@gmail.com wrote:
 
  On Feb 22, 2015, at 8:28 AM, Vaclav Petras wenzesl...@gmail.com 
  mailto:wenzesl...@gmail.com wrote:
 
 
 
  On Sat, Feb 21, 2015 at 9:49 PM, Yann Chemin yche...@gmail.com 
  mailto:yche...@gmail.com wrote:
 
  Starting a session I get:
 
  WARNING: No metadata file available
 
 
  Can this be including a small hint to fix it.
  Yann
 
  I don't know what is the reason for the message. How is your grass7 
  directory? Other circumstances? See the source code here:
 
 
  it is a new compile of svn on Mac, opening a mapset that is few months old. 
  I am compiling the add-ons too in it.
 
 Please try:
 
 $ ls .grass7/
 addons  rc  r.li http://r.li/  toolboxes
 $ ls .grass7/addons/
 bin  docs  etc  modules.xml  scripts
 
 
  https://trac.osgeo.org/grass/browser/grass/trunk/scripts/g.extension/g.extension.py#L195
   
  https://trac.osgeo.org/grass/browser/grass/trunk/scripts/g.extension/g.extension.py#L195
 
 

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

[GRASS-dev] how to relaunch the grass welcome screen

[Yann Chemin]

Hi,

is there a way to (re)launch the GRASS welcome screen manually, i mean 
independently, like a module?

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

[GRASS-dev] forcing a Python version/install when compiling GRASS

[Yann Chemin]

Hi,

I would like to use a different version of Python from the default install in 
the PC,
is there a way to force it in the configure script?

thx
Yann
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] file-new vector

[Yann Chemin]

Hi,

Was looking to create a new vector file to deliniate an area.
I have been repeatedly using qgis up to now (Ctrl+Shift+N) and was looking
in GRASS for a (non-existing) menu entry File-New from some usability
habit from other software.

Maybe this could be useful for users, File-New and/or Ctrl+Shift+N (common
shortcut in many software)

Cheers,
Yann

-- 

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

[GRASS-dev] white splash on trunk

[Yann Chemin]

Hi,

i just rebuilt everything this morning,
Using Linux Mint on 64 bit machine.

just a white splash, nothing shown.

Yann

-- 

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

Re: [GRASS-dev] Planning GRASS GIS 7.0.0RC2

[Yann Chemin]

+1

On 7 February 2015 at 21:52, Markus Neteler nete...@osgeo.org wrote:

 Hi devs,

 I would like to get RC2 out. Even if the updated splash screen is
 perhaps not yet superoptimal in startup timing or whatever some
 (rare?) issues are, please let's go ahead.
 We accumulated important vector fixes which need to get out.

 Can (a wx skilled person/Martin?) please backport the updated welcome
 screen + splash screen? That's the missing issue in
 http://trac.osgeo.org/grass/wiki/Grass7Planning#Planningongoing

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




-- 

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

Re: [GRASS-dev] Planning GRASS GIS 7.0.0RC2

[Yann Chemin]

+1

On 6 February 2015 at 18:58, Martin Landa landa.mar...@gmail.com wrote:

 Hi,

 2015-02-04 10:41 GMT+01:00 Markus Neteler nete...@osgeo.org:
  I don't think that we should start a poll now (voting is happening on
  PSC, for other cases we have no voting infrastructure in place).
  Setting up a proper poll system is not that easy and requires time
  (who can participate, keep poll open for some week(s) etc).
 
  At time it is for RC2 only anyway which we need to get out asap.

 I would like to suggest (facing to RC2, which has been already postponed)
 to:

 1) backport current version of splash screen and startup banner as it's in
 trunk
 2) backport also new version startup screen which has been improved in
 trunk

 Then to release RC2, what do you think? Martin

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




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

+1 (including new version of startup screen). Yann

On 6 February 2015 at 19:00, Martin Landa landa.mar...@gmail.com wrote:

 2015-02-06 14:27 GMT+01:00 Markus Neteler nete...@osgeo.org:
  Despite all the take this take that discussions and a potential extra
  simplified startup it gets into good shape now for RC2.
  Should we consider the backport of these changes?

 +1 (including new version of startup screen). Martin

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




-- 

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

Re: [GRASS-dev] Planning GRASS GIS 7.0.0RC2

[Yann Chemin]

+1 to go ahead, devs will see the difference on their next built. They can
react if needed we decide to change before final.

I am happy about the new splash and the new stylish banner.

PS: I just updated ISIS-GRASS banner too.

On 4 February 2015 at 15:11, Markus Neteler nete...@osgeo.org wrote:

 On Wed, Feb 4, 2015 at 10:10 AM, Luca Delucchi lucadel...@gmail.com
 wrote:
  On 4 February 2015 at 10:03, Martin Landa landa.mar...@gmail.com
 wrote:
  Hi all,
 
 
  Hi all,
 
 
  thanks, the last issue for RC2 which I can see is the new startup
  banner and splash screen. Any objections to backport r64455 and
  r64447. Than we could hopefully move towards RC2 (it's ~20 days since
  RC1 has been released).
 
 
  sorry but should we vote or not?
  Maybe I lost some emails, but I understood that we should vote to
  choose banner and splash screen...

 I don't think that we should start a poll now (voting is happening on
 PSC, for other cases we have no voting infrastructure in place).
 Setting up a proper poll system is not that easy and requires time
 (who can participate, keep poll open for some week(s) etc).

 At time it is for RC2 only anyway which we need to get out asap.

 Is that acceptable?

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




-- 

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

Re: [GRASS-dev] Making start of GRASS GIS easier for newcomers

[Yann Chemin]

It may sound out of place, but would it be possible to call this dialog
anytime during a grass session to manage where you want to work through a
known, unified interface?
On Feb 3, 2015 4:42 AM, Vaclav Petras wenzesl...@gmail.com wrote:


 On Mon, Feb 2, 2015 at 6:34 PM, Michael Barton michael.bar...@asu.edu
 wrote:

  I think that they are equally as informative and the one on the left
 takes up less space. Just my opinion.


 Replacing Warning:  by nothing in r64407. Other changes included as
 well, most notably decreased vertical size at expense of Location and
 Mapset lists which are now as big as in 64. The whole dialog is just little
 bit bigger than in 64, so with smaller banner it will be hopefully smaller.
 I would prefer if it would be possible to make it smaller by dragging but
 it is not (I tried several times but I cannot get it work).

 I also changed the user visible strings, see commit for details but most
 importantly I add numbers to the boxes to make it clear in which order you
 should fill them (and that there is an order).

 Please, see screenshot (40%), commit message and diff for details.

 Vaclav

 http://trac.osgeo.org/grass/changeset/64407


  Michael

  On Feb 2, 2015, at 4:11 PM, Vaclav Petras wenzesl...@gmail.com wrote:



 On Mon, Feb 2, 2015 at 5:33 PM, Markus Neteler nete...@osgeo.org wrote:

  On Mon, Feb 2, 2015 at 11:02 PM, Vaclav Petras wenzesl...@gmail.com
 wrote:
 
  On Mon, Feb 2, 2015 at 4:50 PM, Michael Barton michael.bar...@asu.edu
 
  wrote:
 
  Unfortunately the screenshots are too low resolution for me to read
 them
  here. So I might miss something that is on the screenshot.
 
 
  It's just about layout, don't worry about text. I can of course send
 full
  size if somebody wants.

  Please post at least double size...

  I posted 25%, now posting 50% which is not significantly smaller then
 100% even after optipng, so I can post just one image at a time.

  Here is what you see when you start 64 for the first time and when you
 start current trunk for the first time.


 thanks
 Markus


  startup_old_and_new_error_warning_50.png




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

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

[GRASS-dev] automatically save/open workspace in the Mapset

[Yann Chemin]

Hi,

just a thought, it would be practical to have last maps seen reopen by
having a default mapset being written before closing wxgui, and first
reopened (if exists) on launching the wxgui in the same mapset.

Yann

-- 

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

Re: [GRASS-dev] automatically save/open workspace in the Mapset

[Yann Chemin]

sure, it is there Moritz.
I would find that a nice option to be able to enable in Preferences.

On 2 February 2015 at 14:43, Moritz Lennert mlenn...@club.worldonline.be
wrote:

 On 02/02/15 10:09, Yann Chemin wrote:

 Hi,

 just a thought, it would be practical to have last maps seen reopen by
 having a default mapset being written before closing wxgui, and first
 reopened (if exists) on launching the wxgui in the same mapset.


 You know that you can just save your workspace and open that in order to
 see the same maps displayed as before ? IMHO, this is more than enough and
 having maps displayed automatically each time I open a mapset would be
 counter-productive.

 Moritz




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

is there a way to make a public poll online with the different versions and
send the link on GRASS-dev and GRASS-user MLs, then give a sunday midnight
close of poll?

On 30 January 2015 at 21:23, Martin Landa landa.mar...@gmail.com wrote:

 Hi,

 2015-01-30 15:13 GMT+01:00 Vincent Bain b...@toraval.fr:
  I fear it is an endless discussion anyway. Objectivity is hard to reach
  in that domain of graphic design.

 this is what we need to avoid. RC2 is waiting for a new splash and
 welcome banner. I can see three candidates [1]. Please free add new
 candidates, it would be nice to launch voting during weekend and than
 to move on to RC2 on the beginning of the next week, what do you
 think?

 Martin

 [1] http://grasswiki.osgeo.org/wiki/Talk:Identity

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




-- 

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

Re: [GRASS-dev] Making start of GRASS GIS easier for newcomers

[Yann Chemin]

+1 for a button, but I am not sure sure a data download is that
necessary...
The button might just be a script creating a (several?) empty Location(s?)
in a directory that the user can choose.



On 30 January 2015 at 15:20, Moritz Lennert mlenn...@club.worldonline.be
wrote:

 On 29/01/15 17:43, Vaclav Petras wrote:

 On the MS Windows installer takes care of that by copying demo Location
 to newly created grassdata dir in Documents and creating the rc file. Is
 this enough? If not why? And do we want to do something similar for
 cases when installation is not done by GRASS GIS? If startup detects no
 grassdata it could just create the dir and copy the demo Location there,
 so the only thing needed is to press Start button.


 Don't forget that in many GNU/Linux distributions data is separated from
 applications in the packaging. So, either we have to tell users to install
 a specific data package (e.g. grass-demodata) or the startup screen needs a
 button: Download and unpack demo data.

 Moritz

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




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

still +1 for http://grasswiki.osgeo.org/wiki/File:GRASSGIS_splash5.jpg

On 30 January 2015 at 17:45, Vincent Bain b...@toraval.fr wrote:

 Trying to satisfy everyone's claims, I propose another splash screen :
 - capitalized GRASS GIS (boohhh ;-)) ;
 - centered layout with title underneath logo.

 It is available on the wiki page, it comes with a welcome banner too.

 /Beware that we might progressively turn the result into something quite
 flavourless.../

 Vincent
 (going back to snow blowing)


 Le vendredi 30 janvier 2015 à 12:35 +0100, Markus Neteler a écrit :
  On Thu, Jan 29, 2015 at 2:58 PM, Vincent Bain b...@toraval.fr wrote:
   Le mercredi 28 janvier 2015 à 17:42 +0200, Nikos Alexandris a écrit :
   The ones @
   
 http://grasswiki.osgeo.org/wiki/User:NikosA#Ideas_for_an_alternative_GRASS-Wiki_logogram
 
   are for the Wiki... !?  If anyone is interested.
  
   Sorry Nikos, I missed your suggestion.
   Perhaps it's an opportunity to bet on a similar output, again for
   consistency (see attached file).
 
  While this is nicely evolving, please let's keep GIS/gis in the name.
 
  thanks
  Markus


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




-- 

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

Re: [GRASS-dev] Making start of GRASS GIS easier for newcomers

[Yann Chemin]

Continuing the crazy thoughts,
You could have FFT/wavelet parameters per column of a raster image
hard-coded to create an image on request (that I could do I think). About a
vector, well a set of polygon arcs pairs can easily be stored in code and
(i suppose) imported on the fly as a vector.

On 30 January 2015 at 16:06, Nikos Alexandris n...@nikosalexandris.net
wrote:

 Maybe a crazy idea, but...  if access to internet isn't an option, maybe
 the button can create a Location and Mapset(s), and let a script create
 some artificial vector and raster maps?  So a user can still play along
 with unreal data.

 Nikos

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




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

On 29 January 2015 at 17:57, Michael Barton michael.bar...@asu.edu wrote:

  Thanks again for all this Vicent. I too like the grassy continents in
 green. The white lettering on this is a nice contrast to the dark lettering
 on the startup too. Fira Sans is a good font. It really updates the looks
 of this.

 +1 for http://grasswiki.osgeo.org/w/images/GRASSGIS_splash5.jpg indeed


  Michael

  C. Michael Barton
  Director, Center for Social Dynamics  Complexity
  Professor of Anthropology, School of Human Evolution  Social Change
 Head, Graduate Faculty in Complex Adaptive Systems Science
  Arizona State University

  voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
 fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
  www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu




  On Jan 29, 2015, at 1:30 AM, grass-dev-requ...@lists.osgeo.org wrote:


 * From: *Vincent Bain b...@toraval.fr
  *Cc: *grass-dev grass-dev@lists.osgeo.org
  *To: *Martin Landa landa.mar...@gmail.com
  *Date: *January 28, 2015 at 2:26:42 PM MST
  *Subject: **Re: [GRASS-dev] New splash screen for GRASS GIS 7?*


 Hi Martin, thank you...

 I just updated the wiki page to suggest a font substitution : Fira Sans
 is a very clean sans serif typeface, under the SIL Open Font License. I
 find an intersting contrast with garamond serif.

 Bye,
 V.



 Le mercredi 28 janvier 2015 à 22:16 +0100, Martin Landa a écrit :

 Hi Vincent,

 2015-01-28 15:36 GMT+01:00 Vincent Bain b...@toraval.fr:

 I packed most of the graphical tests I did last week on a wiki page. I
 tried to initiate a place (very rough yet) where we can further set up
 things concerning graphical identity. Hope this helps.

 http://grasswiki.osgeo.org/wiki/Identity


 thanks a lot! The splash screens with grass continents are absolutely
 great!!! I like most [1]. For the startup screen I would choose [2].

 Martin

 [1] http://grasswiki.osgeo.org/w/images/GRASSGIS_splash4.jpg
 [2] http://grasswiki.osgeo.org/wiki/File:GRASSGIS_welcome_banner1.jpg




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




-- 

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

Re: [GRASS-dev] Making start of GRASS GIS easier for newcomers

[Yann Chemin]

Could we have a proposed new banner in trunk too.
It really helps having it on your computer...

Maybe the smallest one makes sense for all screen sizes
http://grasswiki.osgeo.org/wiki/File:GRASSGIS_welcome_banner3.jpg

I wonder if Vincent could make it with GRASS GIS in Fira Sans as in the
splash screen?
Cheers,
Yann

On 29 January 2015 at 18:03, Markus Neteler nete...@osgeo.org wrote:

 On Thu, Jan 29, 2015 at 1:20 PM, Michael Barton michael.bar...@asu.edu
 wrote:
  Is there a place to see a screen shot of what is proposed? I suggested
 some wording changes awhile back but I don't know if they are incorporated
 or not.

 Attached the draft version from trunk (updated 2hs ago). Obviously yet
 with the old logo etc.

 Markus

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




-- 

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

Re: [GRASS-dev] Making start of GRASS GIS easier for newcomers

[Yann Chemin]

+1 Nice !

On 29 January 2015 at 19:15, Vincent Bain b...@toraval.fr wrote:

 Here I put the updated banner:
 http://grasswiki.osgeo.org/wiki/Identity#Proposals_2

 attached is the jpg label.

 Le jeudi 29 janvier 2015 à 14:12 +0100, Vincent Bain a écrit :
  Le jeudi 29 janvier 2015 à 18:19 +0530, Yann Chemin a écrit :
   I wonder if Vincent could make it with GRASS GIS in Fira Sans as in
   the splash screen?
 
  Yes, in a while.
 
  ___
  grass-dev mailing list
  grass-dev@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/grass-dev




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

+1 :D

On 29 January 2015 at 19:28, Vincent Bain b...@toraval.fr wrote:

 Le mercredi 28 janvier 2015 à 17:42 +0200, Nikos Alexandris a écrit :
  The ones @
  
 http://grasswiki.osgeo.org/wiki/User:NikosA#Ideas_for_an_alternative_GRASS-Wiki_logogram
 
  are for the Wiki... !?  If anyone is interested.

 Sorry Nikos, I missed your suggestion.
 Perhaps it's an opportunity to bet on a similar output, again for
 consistency (see attached file).

 Yours,
 Vincent

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




-- 

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

[GRASS-dev] i.spec.unmix: getting end-members with pysptools

[Yann Chemin]

Hi, for info, got an end-member extraction with pysptools

First you need to get a single ENVI formatted file having all spectral
bands in it.
r.out.gdal --o input=M3_mid output=A12_mid format=ENVI type=Float32

Then run the following script in Python adapted from the pysptools tutorials
(deps: python-sklearn, python-cvxopt)

--
import os
import os.path as osp
import numpy as np

import pysptools.util as util
import pysptools.eea as eea

def get_endmembers(data, header, q, path):
print 'Endmembers extraction with NFINDR'
ee = eea.NFINDR()
U = ee.extract(data, q, maxit=5, normalize=True, ATGP_init=True)
ee.plot(path, header)
return U

data_path = '/home/yann/M3/A12'
sample = 'A12.hdr'
data_file = osp.join(data_path, sample)
data, header = util.load_ENVI_file(data_file)
# Maybe needed: Flipping to restore orientation
data = np.fliplr(data)
U = get_endmembers(data, header, 4, result_path)
--


Only issue so far is that the .hdr file should have information about the
wavelength value for each band (here example has 83 bands of Reflectance):

wavelength units = Nanometers (also accepts Micrometers)
z plot titles = {Wavelengths, Reflectance}
band names = {
Band 1, Band 2, Band 3,
Band 4, Band 5, Band 6, Band 7, Band 8, Band 9, Band 10, Band 11,
Band 12, Band 13, Band 14, Band 15, Band 16, Band 17, Band 18, Band 19,
Band 20, Band 21, Band 22, Band 23, Band 24, Band 25, Band 26, Band 27,
Band 28, Band 29, Band 30, Band 31, Band 32, Band 33, Band 34, Band 35,
Band 36, Band 37, Band 38, Band 39, Band 40, Band 41, Band 42, Band 43,
Band 44, Band 45, Band 46, Band 47, Band 48, Band 49, Band 50, Band 51,
Band 52, Band 53, Band 54, Band 55, Band 56, Band 57, Band 58, Band 59,
Band 60, Band 61, Band 62, Band 63, Band 64, Band 65, Band 66, Band 67,
Band 68, Band 69, Band 70, Band 71, Band 72, Band 73, Band 74, Band 75,
Band 76, Band 77, Band 78, Band 79, Band 80, Band 81, Band 82, Band 83}
wavelength = {
 540.84, 580.76, 620.69, 660.61, 700.54, 730.48, 750.44, 770.4, 790.37,
 810.33, 830.29, 850.25, 870.21, 890.17, 910.14, 930.1, 950.06, 970.02,
 989.98, 1009.95, 1029.91, 1049.87, 1069.83, 1089.79, 1109.76, 1129.72,
 1149.68, 1169.64, 1189.60, 1209.57, 1229.53, 1249.49, 1269.45, 1289.41,
 1309.38, 1329.34, 1349.30, 1369.26, 1389.22, 1409.19, 1429.15, 1449.11,
 1469.07, 1489.03, 1508.99, 1528.96, 1548.92, 1578.86, 1618.79, 1658.71,
 1698.63, 1738.56, 1778.48, 1818.40, 1858.33, 1898.25, 1938.18, 1978.10,
 2018.02, 2057.95, 2097.87, 2137.80, 2177.72, 2217.64, 2257.57, 2297.49,
 2337.42, 2377.34, 2417.26, 2457.19, 2497.11, 2537.03, 2576.96, 2616.88,
 2656.81, 2696.73, 2736.65, 2776.58, 2816.50, 2856.43, 2896.35, 2936.27,
 2976.20}

-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

OK maybe we can open a poll somewhere with all these pictures so far, and
ask people to give a vote by sending the link to grass-* ML.

I find the small grass in fore front of the mountain a very sweet picture.
Nice pic Vincent.

On 25 January 2015 at 22:21, Michael Barton michael.bar...@asu.edu wrote:

  The blade of grass with blurred mountain background is pretty and classy.
 But I still think that the one with grass growing into the world map
 conveys the best message, as well as being classy too.

  Michael

  C. Michael Barton
  Director, Center for Social Dynamics  Complexity
  Professor of Anthropology, School of Human Evolution  Social Change
 Head, Graduate Faculty in Complex Adaptive Systems Science
  Arizona State University

  voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
 fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
  www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu




  On Jan 25, 2015, at 7:42 AM, grass-dev-requ...@lists.osgeo.org wrote:

  *From: *Vincent Bain b...@toraval.fr
  *Cc: *Yann Chemin yann.che...@gmail.com, GRASS developers list 
 grass-dev@lists.osgeo.org
  *To: *Markus Neteler nete...@osgeo.org
  *Date: *January 25, 2015 at 7:42:07 AM MST
  *Subject: **Re: [GRASS-dev] New splash screen for GRASS GIS 7?*


 Thank you all for reactions.
 I fear I sort of ran out of spare time to keep making proposals right now.


 Le dimanche 25 janvier 2015 à 08:05 +0100, Markus Neteler a écrit :

 please let's put all the suggestions into a wiki page. And also invite
 grass-user to send suggestions.


 if it can wait till next thursday, I can do that.


On Sat, Jan 24, 2015 at 11:32 PM, Yann Chemin
yche...@gmail.com wrote:
Can you get a libre picture with grass? There are some online
but not good enough. Is some longer grass growing at this time
where you are? Can you take a photo?


 Nope, up here the ground is snow capped all over.
 I have some personal photos but not actually adapted (for the record see
 attached file -- very personal try)

 V.



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




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

Yes the grassy grass is definitely splashy

+1 for your first splash Vincent
On Jan 25, 2015 9:26 AM, Michael Barton michael.bar...@asu.edu wrote:

  I like the grassy one better too. A nice visual metaphor.

  Michael
 
  C. Michael Barton
  Director, Center for Social Dynamics  Complexity
  Professor of Anthropology, School of Human Evolution  Social Change
 Head, Graduate Faculty in Complex Adaptive Systems Science
  Arizona State University

  voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
 fax: 480-965-7671 (SHESC),  480-727-0709 (CSDC)
  www: http://www.public.asu.edu/~cmbarton, http://csdc.asu.edu















  On Jan 24, 2015, at 4:30 PM, Anna Petrášová kratocha...@gmail.com
 wrote:



 On Sat, Jan 24, 2015 at 3:39 PM, Markus Neteler nete...@osgeo.org wrote:

 On Sat, Jan 24, 2015 at 7:50 PM, Vincent Bain b...@toraval.fr wrote:
  Snowy day, stuck at the office : here's my latest attempt to find an
  original solution suitable for your wishes...
 
  http://lesfavrets.fr/telec/grass_splash_4.tar.gz
 
  looks more like a GIS software this way, no ?

 So cool! :)

  Have a good week end ;-)

 Thanks so much for your work,

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



  I still like the first attempt better (grass as background). I don't say
 this one is not interesting or original, but it's not easy to understand,
 especially when the splash screen is not visible long. I don't think we
 have to have something geospatial there.  I added my not very refined
 attempt to not just criticize but I still like the grass background better.

  Anna
  splash.jpg



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

Re: [GRASS-dev] PDF links in modules manuals should be opened externally (OS Web browser)

[Yann Chemin]

Yes Vaclav,

Run I.spec.unmix from grass, then go to the manual tab, the click on PDF,
the link in the reference section, within the gui of the module I find that
problem.

Thanks
Yann
On Jan 25, 2015 10:41 AM, Vaclav Petras wenzesl...@gmail.com wrote:



 On Sun, Jan 25, 2015 at 12:00 AM, Yann Chemin yche...@gmail.com wrote:

 Hi,

 Clicking on the i.spec.unmix PDF link in the module manual tab returns
 the PDF in raw text format (not-human readable) in the same integrated
 viewer.

 Maybe opening it in the OS Web Browser would be an option, or?

 Can you take some screenshots or explain more? I just tried the HTML file
 in source code and it is fine. The link to PDF opens the PDF file in
 browser. I'm using Firefox which uses PDF.js for PDFs.

 If the separate tab should be opened that's different think. People seems
 not to agree what's right. Some say you can use target=_blank some other
 that it is a bad practice almost always and you should leave it completely
 on the user (even non-advanced user can usually go back).

 Vaclav

 PS: The i.spec.unmix manual is not online (generated)?

 http://www.grassbook.org/neteler/papers/neteler2005_IJG_051-061_draft.pdf


 Yann

 --
 

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



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

[GRASS-dev] PDF links in modules manuals should be opened externally (OS Web browser)

[Yann Chemin]

Hi,

Clicking on the i.spec.unmix PDF link in the module manual tab returns the
PDF in raw text format (not-human readable) in the same integrated viewer.

Maybe opening it in the OS Web Browser would be an option, or?

Yann

-- 

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

Re: [GRASS-dev] i.spectral error in trunk

[Yann Chemin]

it does display something with -g flag

On 23 January 2015 at 23:49, Yann Chemin yche...@gmail.com wrote:

 Following the error, launched manually d.mon wx0

 ISIS-GRASS 7.1.svn (M3):~/M3  d.mon wx0
 ISIS-GRASS 7.1.svn (M3):~/M3  i.spectral group=m3@yann coordinates=-23.
 4344978039,-3.00860909257
 ISIS-GRASS 7.1.svn (M3):~/M3 
 GRASS_INFO_WARNING(15380,1): Unsupported command d.linegraph.


 On 23 January 2015 at 23:46, Yann Chemin yche...@gmail.com wrote:

 Hi,

 got this error message when running i.spectral.

 btw, is there a plan to have i.spectral running in the GUI with the other
 tools?

 ---
 i.spectral group=m3@yann coordinates=-23.4344978039,-3.00860909257

 ERROR: Neither MONITOR (managed by d.mon command) nor
 GRASS_RENDER_IMMEDIATE (used for direct rendering) defined
 Traceback (most recent call last):
   File /usr/local/grass-7.1.svn/scripts/i.spectral, line
 241, in module
 main()
   File /usr/local/grass-7.1.svn/scripts/i.spectral, line
 236, in main
 draw_linegraph(what)
   File /usr/local/grass-7.1.svn/scripts/i.spectral, line
 179, in draw_linegraph
 x_title='Bands', y_title='DN Value')
   File
 /usr/local/grass-7.1.svn/etc/python/grass/script/core.py,
 line 375, in run_command
 return handle_errors(returncode, returncode, args,
 kwargs)
   File
 /usr/local/grass-7.1.svn/etc/python/grass/script/core.py,
 line 310, in handle_errors
 returncode=returncode)
 grass.exceptions.CalledModuleError: Module run None
 ['d.linegraph', 'x_title=Bands',
 'x_file=/home/yann/GRASSDATA/M3/yann/.tmp/Yann-
 OK/15217.0/data_x',
 'y_file=/home/yann/GRASSDATA/M3/yann/.tmp/Yann-
 OK/15217.0/data_y_0', 'y_title=DN Value', 'title=Spectral
 signatures', 'y_color=red'] ended with error
 Process ended with non-zero return code 1. See errors in the
 (error) output.



 --
 




 --
 




-- 

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

[GRASS-dev] i.spectral error in trunk

[Yann Chemin]

Hi,

got this error message when running i.spectral.

btw, is there a plan to have i.spectral running in the GUI with the other
tools?

---
i.spectral group=m3@yann
coordinates=-23.4344978039,-3.00860909257
ERROR: Neither MONITOR (managed by d.mon command) nor
GRASS_RENDER_IMMEDIATE (used for direct rendering) defined
Traceback (most recent call last):
  File /usr/local/grass-7.1.svn/scripts/i.spectral, line
241, in module
main()
  File /usr/local/grass-7.1.svn/scripts/i.spectral, line
236, in main
draw_linegraph(what)
  File /usr/local/grass-7.1.svn/scripts/i.spectral, line
179, in draw_linegraph
x_title='Bands', y_title='DN Value')
  File
/usr/local/grass-7.1.svn/etc/python/grass/script/core.py,
line 375, in run_command
return handle_errors(returncode, returncode, args,
kwargs)
  File
/usr/local/grass-7.1.svn/etc/python/grass/script/core.py,
line 310, in handle_errors
returncode=returncode)
grass.exceptions.CalledModuleError: Module run None
['d.linegraph', 'x_title=Bands',
'x_file=/home/yann/GRASSDATA/M3/yann/.tmp/Yann-
OK/15217.0/data_x',
'y_file=/home/yann/GRASSDATA/M3/yann/.tmp/Yann-
OK/15217.0/data_y_0', 'y_title=DN Value', 'title=Spectral
signatures', 'y_color=red'] ended with error
Process ended with non-zero return code 1. See errors in the
(error) output.



-- 

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

Re: [GRASS-dev] Making start of GRASS GIS easier for newcomers

[Yann Chemin]

On 23 January 2015 at 22:18, Anna Petrášová kratocha...@gmail.com wrote:



 On Fri, Jan 23, 2015 at 10:34 AM, Margherita Di Leo direg...@gmail.com
 wrote:

 Hi,

 On Fri, Jan 23, 2015 at 2:10 PM, Markus Metz 
 markus.metz.gisw...@gmail.com wrote:


 That is why I suggested a minimal (minimal information content)
 welcome screen with one OK button and one change button. The OK button
 should be prominently placed, the user must immediately see that all
 is needed to get started is to press OK. This welcome screen could be
 written such that practically nothing but wx needs to be imported,
 which means that the splash screen can go away. Because of the little
 amount of content (text + buttons), there would be enough space for
 graphics even on small screens.

 You could have drop-down boxes for location and mapset to offer a
 choice instead of fixed text.


 Do I understand correctly that such drop-down boxes to change current
 location and mapset are to be found at the stage when GRASS is already
 started? Meaning that you are in a XY empty location and you can choose to
 go directly to a different one without restarting GRASS? If this is your
 proposal, I  think that this would indeed do a huge difference to anyone
 working in grass, not only newcomers, in terms of practicality

 That's already there. I am not sure if it makes such a huge difference.


It is there indeed, but there is here an element of perceived availability
that maybe needed, or maybe perceived focus in the work flow...


 Anna





 --
 Best regards,

 Dr. Margherita DI LEO
 Scientific / technical project officer

 European Commission - DG JRC
 Institute for Environment and Sustainability (IES)
 Via Fermi, 2749
 I-21027 Ispra (VA) - Italy - TP 261

 Tel. +39 0332 78 3600
 margherita.di-...@jrc.ec.europa.eu

 Disclaimer: The views expressed are purely those of the writer and may
 not in any circumstance be regarded as stating an official position of the
 European Commission.

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



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




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

On 23 January 2015 at 22:56, Michael Barton michael.bar...@asu.edu wrote:

  An informal poll of the grad students in my lab this morning. All said
 “Wow”. Very professional!

  I like the idea of GRASS morphing into a map of some kind. Also like
 Vaclav’s tweaks to make the start up a little easier to navigate—2 list
 choice controls with relevant buttons next to them and simplified text.


+1 for those to be implemented, if Vincent is too busy, I can have a throw
at morphing a map in it.


  Michael
 __
  C. Michael Barton
  Director, Center for Social Dynamics  Complexity
  Professor of Anthropology, School of Human Evolution  Social Change
  Head, Graduate Faculty in Complex Adaptive Systems Science
  Arizona State University
  Tempe, AZ  85287-2402
  USA

  voice:  480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
  fax:  480-965-7671(SHESC), 480-727-0709 (CSDC)
  www:  http://csdc.asu.edu, http://shesc.asu.edu
  http://www.public.asu.edu/~cmbarton

  On Jan 23, 2015, at 9:48 AM, grass-dev-requ...@lists.osgeo.org wrote:

  *From: *Markus Neteler nete...@osgeo.org
  *Cc: *GRASS developers list grass-dev@lists.osgeo.org
  *To: *Vincent Bain b...@toraval.fr
  *Date: *January 23, 2015 at 6:41:27 AM MST
  *Subject: **Re: [GRASS-dev] New splash screen for GRASS GIS 7?*


 On Fri, Jan 23, 2015 at 12:45 PM, Vincent Bain b...@toraval.fr wrote:

 A second proposal for splash screen and welcome banner (adapted to dark
 backgrounds) you can pick there :
 http://lesfavrets.fr/telec/grass_splash_2.tar.gz

 The carex image is in the public domain
 http://commons.wikimedia.org/wiki/File:Carexpraegracilis0.jpg

 Fonts are free (see previous post for Exljbris Fontin) or OFL (for the
 exquisite EB Garamond by Georg Duffner).

 Those who wish to trim things on the source file, feel free to ask...
 especially for colors tweaking ;-)


 Thanks for your efforts!
 Do you see a chance to morph the true grass into a map (from left to
 right or so)?

 IMHO we need to somehow communicate that spatial data are involved.

 Markus



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




-- 

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

Re: [GRASS-dev] i.spectral error in trunk

[Yann Chemin]

Following the error, launched manually d.mon wx0

ISIS-GRASS 7.1.svn (M3):~/M3  d.mon wx0
ISIS-GRASS 7.1.svn (M3):~/M3  i.spectral group=m3@yann
coordinates=-23.4344978039,-3.00860909257
ISIS-GRASS 7.1.svn (M3):~/M3 
GRASS_INFO_WARNING(15380,1): Unsupported command d.linegraph.


On 23 January 2015 at 23:46, Yann Chemin yche...@gmail.com wrote:

 Hi,

 got this error message when running i.spectral.

 btw, is there a plan to have i.spectral running in the GUI with the other
 tools?

 ---
 i.spectral group=m3@yann coordinates=-23.4344978039,-3.00860909257

 ERROR: Neither MONITOR (managed by d.mon command) nor
 GRASS_RENDER_IMMEDIATE (used for direct rendering) defined
 Traceback (most recent call last):
   File /usr/local/grass-7.1.svn/scripts/i.spectral, line
 241, in module
 main()
   File /usr/local/grass-7.1.svn/scripts/i.spectral, line
 236, in main
 draw_linegraph(what)
   File /usr/local/grass-7.1.svn/scripts/i.spectral, line
 179, in draw_linegraph
 x_title='Bands', y_title='DN Value')
   File
 /usr/local/grass-7.1.svn/etc/python/grass/script/core.py,
 line 375, in run_command
 return handle_errors(returncode, returncode, args,
 kwargs)
   File
 /usr/local/grass-7.1.svn/etc/python/grass/script/core.py,
 line 310, in handle_errors
 returncode=returncode)
 grass.exceptions.CalledModuleError: Module run None
 ['d.linegraph', 'x_title=Bands',
 'x_file=/home/yann/GRASSDATA/M3/yann/.tmp/Yann-
 OK/15217.0/data_x',
 'y_file=/home/yann/GRASSDATA/M3/yann/.tmp/Yann-
 OK/15217.0/data_y_0', 'y_title=DN Value', 'title=Spectral
 signatures', 'y_color=red'] ended with error
 Process ended with non-zero return code 1. See errors in the
 (error) output.



 --
 




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

... I like that grass, it splashes ...

On 23 January 2015 at 17:15, Vincent Bain b...@toraval.fr wrote:

 A second proposal for splash screen and welcome banner (adapted to dark
 backgrounds) you can pick there :
 http://lesfavrets.fr/telec/grass_splash_2.tar.gz

 The carex image is in the public domain
 http://commons.wikimedia.org/wiki/File:Carexpraegracilis0.jpg

 Fonts are free (see previous post for Exljbris Fontin) or OFL (for the
 exquisite EB Garamond by Georg Duffner).

 Those who wish to trim things on the source file, feel free to ask...
 especially for colors tweaking ;-)

 V

 Le vendredi 23 janvier 2015 à 07:00 +, Michael Barton a écrit :
 
 
   On Jan 22, 2015, at 11:49 PM, grass-dev-requ...@lists.osgeo.org
   wrote:
  
   From: Vincent Bain b...@toraval.fr
  
   To: grass-dev grass-dev@lists.osgeo.org
  
   Date: January 22, 2015 at 11:28:47 PM MST
  
   Subject: Re: [GRASS-dev] New splash screen for GRASS GIS 7?
  
  
  
   I've followed this discussion as closely as I could but might have
   missed some steps..., so to put it in a nutshell:
  
   * Right now, for the release, we propose:
 - a new splash with a neutral/temporary/free banner image (e.g.
   grass);
 - for the welcome screen, I make up a simple banner according to
   Vaclav's suggestion i.e. small GRASS logo+motto on transparent bg
   (or
   white bg to handle dark windows desktop themes).
  
   * Later on I can work on the historical map suggestion --or any
   other
   idea.
  
  
   I can do it between today and sunday.
  
  
 
  Sounds good to me.
 
 
  Michael
  ___
  grass-dev mailing list
  grass-dev@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/grass-dev


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




-- 

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

Re: [GRASS-dev] Making start of GRASS GIS easier for newcomers

[Yann Chemin]

On 23 January 2015 at 16:49, Rainer M Krug rai...@krugs.de wrote:

 Yann Chemin yche...@gmail.com writes:

  On 23 January 2015 at 15:46, Martin Landa landa.mar...@gmail.com
 wrote:
 
  Hi,
 
  2015-01-23 9:20 GMT+01:00 Markus Neteler nete...@osgeo.org:
   my motivation to discuss the current welcome screen is that too many
   potential new users try to launch GRASS, do not get past that screen
 and
   walk away (too difficult). Yes, and they will likely not read the
  manual
   but just take another GIS.
   This is a multiple times reported fact.
 
  I have met a lot of GIS specialists who told me: I tried several times
  to use GRASS in different decades and I end up with the same result, I
  didn't managed to get my data in, so I gave up.
 
  Yes, I also had those experiences told to me.
  Is it possible to open GRASS GIS wxGUI without setting the
  GISDB/Location/mapset yet?
  Then from inside the opened software you will need to go through those
  steps anyway before doing anything...
  Would that make any psychological difference?

 I think this would make a huge difference - especially if the creation
 could be done by triggerd upon import and

 hmm that would be cool !
running r(v).in.* without GISDBASE or Location or mapset could trigger a
wizard to set them up...


 - asking for a directory (for the db),
 - name of the location,
 - name of the mapset, and
 - taking the other parameter (projection, extend) from the data to be
   imported.

 Until a mapset is opened, the non-usable menu items could be greyed
 out.


Sounds like a nice option, as it will direct newbies to modules that import
data (then trigger the creation wizard)



 Rainer

 
 
  It' a sign in my eyes that we should think how to simplify this step ;-)
 
  Martin
 
  --
  Martin Landa
  http://geo.fsv.cvut.cz/gwiki/Landa
  http://gismentors.eu/mentors/landa
  ___
  grass-dev mailing list
  grass-dev@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/grass-dev
 

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




-- 

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

Re: [GRASS-dev] New splash screen for GRASS GIS 7?

[Yann Chemin]

Hi Vincent,

no time at all, unfortunately, please go ahead if you can.

Yann

On 24 January 2015 at 12:11, Vincent Bain b...@toraval.fr wrote:

 This was the idea I had when talking about Cassini's globe but it
 requires a bit of time to set up a correct layout.

 Perhaps an idea with grass texture, let's se if I can do it this
 morning.

 Yann, did you have the time to test map morphing ?

 Le vendredi 23 janvier 2015 à 21:43 +, Michael Barton a écrit :
  I thought about the historical map wrapped around a globe or perhaps
 redone in 3D. But it would probably be too small to make it clear what the
 viewer was seeing.
 
  Michael
  __
  C. Michael Barton
  Director, Center for Social Dynamics  Complexity
  Professor of Anthropology, School of Human Evolution  Social Change
  Head, Graduate Faculty in Complex Adaptive Systems Science
  Arizona State University
  Tempe, AZ  85287-2402
  USA
 
  voice:480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
  fax:  480-965-7671(SHESC), 480-727-0709 (CSDC)
  www:  http://csdc.asu.edu, http://shesc.asu.edu
http://www.public.asu.edu/~cmbarton
 
   On Jan 23, 2015, at 2:23 PM, Markus Neteler nete...@osgeo.org wrote:
  
   On Fri, Jan 23, 2015 at 7:16 PM, Michael Barton 
 michael.bar...@asu.edu wrote:
   If we want to do something from GRASS instead of something historic,
 I bet
   Markus has a LOT of cool maps floating around that we might be able
 to use.
  
   Here is a lot of material:
  
   http://grass.osgeo.org/screenshots/
  
   -- click images to see more or pick from the Gallery menu
  
   Markus
 





-- 

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