Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Zechariah Krautwurst
Forgot to include GRASS-dev on this. Keep the good ideas coming! On Mon, Jun 12, 2017 at 8:49 AM, Zechariah Krautwurst wrote: > Moritz, > > Thank you for your feedback. > > >> IMHO, I think it would be better if we avoided additional outside >> dependencies as much as

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Markus Neteler
On Jun 12, 2017 2:32 PM, "Markus Neteler" wrote: > On Jun 12, 2017 2:27 PM, "Veronica Andreo" wrote: > > > > Hello > > > > [rest skipped] > > > > > More info on how to treat Sentinel in GRASS would be good. > > > > Once you managed to get to Level 2A

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Markus Neteler
Hi On Jun 12, 2017 2:27 PM, "Veronica Andreo" wrote: > > Hello > > [rest skipped] > > > More info on how to treat Sentinel in GRASS would be good. > > Once you managed to get to Level 2A (from TOA to BOA), the rest is > similar to other imagery datasets (I think ESA was

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Veronica Andreo
Hello [rest skipped] > More info on how to treat Sentinel in GRASS would be good. Once you managed to get to Level 2A (from TOA to BOA), the rest is similar to other imagery datasets (I think ESA was about to start providing Level 2A data, dunno if they have...). MarkusN added support for

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Helmut Kudrnovsky
>If you do not know GDALs /vsizip and /vsiurl capabilities, I would recommend having a look at this >blog-post from Even Rouault: > >http://erouault.blogspot.no/2012/05/new-gdal-virtual-file-system-to-read.html > >These GDAL features might be relevant for importing external data. a small

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Stefan Blumentrath
] On Behalf Of Zechariah Krautwurst Sent: søndag 11. juni 2017 23.54 To: GRASS developers list (grass-dev@lists.osgeo.org) <grass-dev@lists.osgeo.org> Subject: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data WEEK 02 REPORT: JUNE 05 - JUNE 09 GRASS GIS Locations from Public Data [1] Zec

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Moritz Lennert
On 12/06/17 11:14, Luca Delucchi wrote: On 12 June 2017 at 09:48, Moritz Lennert wrote: You can check the wiki page on global data sets for inspiration: https://grasswiki.osgeo.org/wiki/Global_datasets Also don't hesitate to update this page if you come by any

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Luca Delucchi
On 12 June 2017 at 09:48, Moritz Lennert wrote: > Hi Zechariah, > Hi, > > IMHO, I think it would be better if we avoided additional outside > dependencies as much as possible. Is it really that hard to implement our > own download routine of SRTM ? > +1 >> -

Re: [GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-12 Thread Moritz Lennert
Hi Zechariah, Thanks for your report ! I have two remarks which should probably better be discussed at this stage of the project: On 11/06/17 23:53, Zechariah Krautwurst wrote: WEEK 02 REPORT: JUNE 05 - JUNE 09 GRASS GIS Locations from Public Data [1] Zechariah Krautwurst ACCOMPLISHED -

[GRASS-dev] Week 02 Report: GRASS Locations from Public Data

2017-06-11 Thread Zechariah Krautwurst
WEEK 02 REPORT: JUNE 05 - JUNE 09 GRASS GIS Locations from Public Data [1] Zechariah Krautwurst ACCOMPLISHED - Reviewed Python scripting for GRASS documentation and existing GRASS data import modules - Wrote SRTM 30 download script using Python Elevation library and GRASS output - Researched USGS