Re: [GRASS-dev] [GRASS GIS] #3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes

[GRASS GIS]

#3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes
+-
  Reporter:  saultdon   |  Owner:  grass-dev@…
  Type:  defect | Status:  closed
  Priority:  normal |  Milestone:
 Component:  Compiling  |Version:  svn-releasebranch72
Resolution:  fixed  |   Keywords:
   CPU:  x86-64 |   Platform:  Linux
+-
Changes (by saultdon):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Looks like applying the patch
 
https://trac.osgeo.org/grass/attachment/ticket/3331/ctypesgencore_preprocessor_fix.diff
 from the ticket you mentioned has fixed it - thanks!

--
Ticket URL: 
GRASS GIS 

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

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

[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 possible. Is it really that hard to implement our
>> own download routine of SRTM ?
>>
>
> Agreed. I'm temporarily using the Elevation python package to figure out
> how it is indexing and clipping SRTM tiles from user input coordinate
> boundaries.
>
>
>>
>> I don't know if you have already made a list of target datasets, but I
>> would plead for using global datasets, instead of USA-only datasets,
>> whenever possible.
>>
>
> Double agreed. The initial goal is to create the USGS pipeline as proof of
> concept and apply the framework to broader global data sets and API's.
>
>
>>
>> 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 other
>> interesting global datasets.
>
>
> Definitely good to keep in mind. I've been keeping good documentation of
> my workflow and resources. I hope to spend some time updating the online
> GRASS documentation with that information as I go along.
>
> Please let me know if you have any other thoughts!
>
>
> Zeke
>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Unable to update my project Wiki due to Captcha

[Paul Schrum]

Although it is clearly not yet solved.  When I tried to add a comment to
that ticket I was catcha-challenged (which is not a problem), but when I
answered the challenge with a correct answer it still blocked me.

On Mon, Jun 12, 2017 at 4:10 PM, Paul Schrum  wrote:

> Dr. Neteler,
>
> My problem is in the process of being solved.  I went to the IRC chat
> channel and one of the people there was very willing to help me.  It
> appears to be resolved now, but we are waiting to see if the problem
> returns.
>
> https://trac.osgeo.org/osgeo/ticket/1939#ticket
>
> - Paul
>
>
> On Mon, Jun 12, 2017 at 3:50 PM, Markus Neteler  wrote:
>
>> On Mon, Jun 12, 2017 at 8:20 PM, Markus Neteler 
>> wrote:
>> > On Mon, Jun 12, 2017 at 4:46 PM, Paul Schrum 
>> wrote:
>> >> I attempted to add my Week 2 report to my project wiki page.  When I
>> did
>> >> this, it challenged me with a Captcha Challenge, specifically one with
>> >> simple arithmetic in english words.  I type in the correct answer and
>> it
>> >> thinks my answer fails.
>> >>
>> >> I did this seven or eight times and finally concluded that it has a
>> bug.
>> >
>> > It could be this one:
>> > https://trac.osgeo.org/osgeo/ticket/1672
>>
>> Sorry, that refers to the OSGeo wiki while you have troubles with the
>> trac wiki. The mechanism is different, and managed via
>> https://trac.osgeo.org/grass/admin/spamfilter/monitor
>>
>> (managed by a few GRASS devs). I'll check in a minute.
>>
>> Markus
>>
>
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Unable to update my project Wiki due to Captcha

[Paul Schrum]

Dr. Neteler,

My problem is in the process of being solved.  I went to the IRC chat
channel and one of the people there was very willing to help me.  It
appears to be resolved now, but we are waiting to see if the problem
returns.

https://trac.osgeo.org/osgeo/ticket/1939#ticket

- Paul


On Mon, Jun 12, 2017 at 3:50 PM, Markus Neteler  wrote:

> On Mon, Jun 12, 2017 at 8:20 PM, Markus Neteler  wrote:
> > On Mon, Jun 12, 2017 at 4:46 PM, Paul Schrum 
> wrote:
> >> I attempted to add my Week 2 report to my project wiki page.  When I did
> >> this, it challenged me with a Captcha Challenge, specifically one with
> >> simple arithmetic in english words.  I type in the correct answer and it
> >> thinks my answer fails.
> >>
> >> I did this seven or eight times and finally concluded that it has a bug.
> >
> > It could be this one:
> > https://trac.osgeo.org/osgeo/ticket/1672
>
> Sorry, that refers to the OSGeo wiki while you have troubles with the
> trac wiki. The mechanism is different, and managed via
> https://trac.osgeo.org/grass/admin/spamfilter/monitor
>
> (managed by a few GRASS devs). I'll check in a minute.
>
> Markus
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes

[GRASS GIS]

#3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes
+-
  Reporter:  saultdon   |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:
 Component:  Compiling  |Version:  svn-releasebranch72
Resolution: |   Keywords:
   CPU:  x86-64 |   Platform:  Linux
+-

Comment (by saultdon):

 Yes, the system has gcc 7.1.1 installed.

 When I build against the svn-releasebranch72 it says that the changeset is
 at 71177 - so are those changes already made in this branch or do I have
 to apply them manually to test?

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes

[GRASS GIS]

#3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes
+-
  Reporter:  saultdon   |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:
 Component:  Compiling  |Version:  svn-releasebranch72
Resolution: |   Keywords:
   CPU:  x86-64 |   Platform:  Linux
+-

Comment (by neteler):

 Do you use GCC7?

 If yes, then this is a duplicate of #3331 (proposed fix therein).

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Unable to update my project Wiki due to Captcha

[Markus Neteler]

On Mon, Jun 12, 2017 at 8:20 PM, Markus Neteler  wrote:
> On Mon, Jun 12, 2017 at 4:46 PM, Paul Schrum  wrote:
>> I attempted to add my Week 2 report to my project wiki page.  When I did
>> this, it challenged me with a Captcha Challenge, specifically one with
>> simple arithmetic in english words.  I type in the correct answer and it
>> thinks my answer fails.
>>
>> I did this seven or eight times and finally concluded that it has a bug.
>
> It could be this one:
> https://trac.osgeo.org/osgeo/ticket/1672

Sorry, that refers to the OSGeo wiki while you have troubles with the
trac wiki. The mechanism is different, and managed via
https://trac.osgeo.org/grass/admin/spamfilter/monitor

(managed by a few GRASS devs). I'll check in a minute.

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

Re: [GRASS-dev] [GRASS GIS] #3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes

[GRASS GIS]

#3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes
+-
  Reporter:  saultdon   |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:
 Component:  Compiling  |Version:  svn-releasebranch72
Resolution: |   Keywords:
   CPU:  x86-64 |   Platform:  Linux
+-

Comment (by saultdon):

 Some environment info that may be useful:

 python2-ctypes 1.0.2

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [GRASS GIS] #3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes

[GRASS GIS]

#3354: errors building re: grass/src/grass-7.2.1/lib/python/ctypes
+-
  Reporter:  saultdon   |  Owner:  grass-dev@…
  Type:  defect | Status:  new
  Priority:  normal |  Milestone:
 Component:  Compiling  |Version:  svn-releasebranch72
Resolution: |   Keywords:
   CPU:  x86-64 |   Platform:  Linux
+-
Changes (by saultdon):

 * version:  7.2.1 => svn-releasebranch72


--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Unable to update my project Wiki due to Captcha

[Markus Neteler]

On Mon, Jun 12, 2017 at 4:46 PM, Paul Schrum  wrote:
> I attempted to add my Week 2 report to my project wiki page.  When I did
> this, it challenged me with a Captcha Challenge, specifically one with
> simple arithmetic in english words.  I type in the correct answer and it
> thinks my answer fails.
>
> I did this seven or eight times and finally concluded that it has a bug.

It could be this one:
https://trac.osgeo.org/osgeo/ticket/1672

Please add a note in the ticket.

Markus

> I will seek to add the report to the wiki from a computer with a different
> IP address some time in the future, but for now, this is why it is not
> appearing there
>
> - Paul
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Unable to update my project Wiki due to Captcha

[Paul Schrum]

Thank you.

I have posted me request for help there.

- Paul

On Mon, Jun 12, 2017 at 11:19 AM, Jeff McKenna <
jmcke...@gatewaygeomatics.com> wrote:

> On 2017-06-12 11:46 AM, Paul Schrum wrote:
>
>> I attempted to add my Week 2 report to my project wiki page.  When I did
>> this, it challenged me with a Captcha Challenge, specifically one with
>> simple arithmetic in english words.  I type in the correct answer and it
>> thinks my answer fails.
>>
>> I did this seven or eight times and finally concluded that it has a bug.
>>
>> I will seek to add the report to the wiki from a computer with a
>> different IP address some time in the future, but for now, this is why it
>> is not appearing there
>>
>> - Paul
>>
>>
> Next time you have a problem with the wiki, just let the OSGeo system
> admins know directly through IRC chat (go directly through your Web browser
> at https://webchat.freenode.net/?channels=osgeo-sac)
>
> Regarding this as a 'bug', I doubt that as so many thousands of others use
> the wiki daily; but please do let the admins know and they can 'whitelist'
> you if need be.
>
> Thank you,
>
> -jeff
>
>
>
> ___
> 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] Week 02 Report: GRASS Locations from Public Data

[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 (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...).
>
> Yes, new scenes are (often? always?) now atmospherically corrected by ESA.

I checked with the filter on our S2A maps system (maps.mundialis.de) and
see that atmospherically corrected scenes are provided for Europe only and
since May 2017. No idea of they will enlarge the supported area in future.

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

Re: [GRASS-dev] Unable to update my project Wiki due to Captcha

[Jeff McKenna]

On 2017-06-12 11:46 AM, Paul Schrum wrote:
I attempted to add my Week 2 report to my project wiki page.  When I did 
this, it challenged me with a Captcha Challenge, specifically one with 
simple arithmetic in english words.  I type in the correct answer and it 
thinks my answer fails.


I did this seven or eight times and finally concluded that it has a bug.

I will seek to add the report to the wiki from a computer with a 
different IP address some time in the future, but for now, this is why 
it is not appearing there


- Paul



Next time you have a problem with the wiki, just let the OSGeo system 
admins know directly through IRC chat (go directly through your Web 
browser at https://webchat.freenode.net/?channels=osgeo-sac)


Regarding this as a 'bug', I doubt that as so many thousands of others 
use the wiki daily; but please do let the admins know and they can 
'whitelist' you if need be.


Thank you,

-jeff



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

[GRASS-dev] Unable to update my project Wiki due to Captcha

[Paul Schrum]

I attempted to add my Week 2 report to my project wiki page.  When I did
this, it challenged me with a Captcha Challenge, specifically one with
simple arithmetic in english words.  I type in the correct answer and it
thinks my answer fails.

I did this seven or eight times and finally concluded that it has a bug.

I will seek to add the report to the wiki from a computer with a different
IP address some time in the future, but for now, this is why it is not
appearing there

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

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

[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 about to start
> providing Level 2A data, dunno if they have...).

Yes, new scenes are (often? always?) now atmospherically corrected by ESA.

> MarkusN added support for Sentinel2 in i.atcorr, but I have not tested
> that, so far... Has anyone tested?

Sajid did to my knowledge.

> > Vero, didn't you write a tutorial on this ?
>
> yes and no... MarkusN shared some info/scripts, and I further worked
> on it to create a wiki, but did not finish it... I've been doing some
> simple stuff with S2 recently that could be added... No time right
> now, but definitely a TO-DO for FOSS4G-EU code sprint :)

+1

Markus

> Vero
> ___
> 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] Week 02 Report: GRASS Locations from Public Data

[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 Sentinel2 in i.atcorr, but I have not tested
that, so far... Has anyone tested?

> Vero, didn't you write a tutorial on this ?

yes and no... MarkusN shared some info/scripts, and I further worked
on it to create a wiki, but did not finish it... I've been doing some
simple stuff with S2 recently that could be added... No time right
now, but definitely a TO-DO for FOSS4G-EU code sprint :)

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

Re: [GRASS-dev] grass wiki anti-spam filter

[Luca Delucchi]

On 12 June 2017 at 12:53, Markus Neteler  wrote:

>
> Done

Thanks

> https://grasswiki.osgeo.org/wiki/FOSS4G_Europe_2017
>
> the div tricks are not allowed, so I changed that code part.
>

the div part or the li one?

however it should be allowed...

https://www.mediawiki.org/wiki/Help:Images#Row_of_images_that_will_wrap_to_browser_width

> Markus

-- 
ciao
Luca

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

Re: [GRASS-dev] grass wiki anti-spam filter

[Markus Neteler]

On Mon, Jun 12, 2017 at 12:17 PM, Luca Delucchi  wrote:
> Hi devs,
>
> I'm trying to create a new page but it is blocked by anti-spam filter.
>
> The text is the following, someone with more rights could create the page?

Done
https://grasswiki.osgeo.org/wiki/FOSS4G_Europe_2017

the div tricks are not allowed, so I changed that code part.

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

[GRASS-dev] grass wiki anti-spam filter

[Luca Delucchi]

Hi devs,

I'm trying to create a new page but it is blocked by anti-spam filter.

The text is the following, someone with more rights could create the page?

Thanks

=


[[File:FOSS4G-Europe-2017.png|250px]]
[[File:Grassgis logo colorlogo text
whitebg.png|250px]]


European Conference for Free and Open Source Software for Geospatial,
July 18-22, 2017, Paris, France, http://europe.foss4g.org/2017

== Workshops ==

Conference program link: https://europe.foss4g.org/2017/Workshops

=== TGRASS: temporal data processing with GRASS GIS ===

by Veronica Andreo from University of Twente, Luca Delucchi from
Fondazione Edmund Mach, Markus Neteler from mundialis GmbH & Co. KG

GRASS GIS is a Free and Open Source geographic information system
(GIS) with support for raster, 3D raster and vector data processing.
It provides more than 450 core modules, plus hundreds of Add-ons, to
run any kind of geographical analysis. GRASS GIS offers a useful
graphical interface to work as in any other desktop software. However,
the highest power of GRASS GIS resides in that it can be used also
like a backend tool to run analysis in an automatic way, not only a
personal computer, but also into HPC systems or via web services (WPS
or scripting in several languages). The workshop will show the basics
about GRASS GIS, it will be an intuitive mix of theoretical and
hands-on sections. In the former, we will introduce the participants
to some specific concepts of GRASS GIS, like its database structure,
location, mapset and region and will show how simple the approach
really is. During the hands-on part, the participants will learn how
to use common geographical data formats in GRASS GIS, starting from
simple actions like adding data into the GRASS GIS environment and
displaying it. Finally, the participants will run simple analyses like
map algebra calculations for raster maps and vector buffering and
visualize and export the results.

== Code Sprint ==

General information and sign up is here:

https://wiki.osgeo.org/wiki/FOSS4G-Europe_2017_Code_sprint

[[Category: Conferences]]
[[Category: Workshops]]
[[Category: Code Sprint]]
[[Category: 2017]]




-- 
ciao
Luca

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

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

[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 addition, a few times ago I've played around with GDAL's /vsicurl/
and EU-DEM:

http://www.alectoria.at/content/view/23/30/



-
best regards
Helmut
--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Week-02-Report-GRASS-Locations-from-Public-Data-tp5323780p5323831.html
Sent from the Grass - Dev mailing list archive at Nabble.com.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

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

[Stefan Blumentrath]

Hi Zechariah,

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.

In the blog-post Even demonstrates how to read data directly from web locations 
even when inside zip archives (not sure what performance implications that has, 
but it might help to reduce the amount of local storage needed).

Cheers
Stefan

From: grass-dev [mailto:grass-dev-boun...@lists.osgeo.org] On Behalf Of 
Zechariah Krautwurst
Sent: søndag 11. juni 2017 23.54
To: GRASS developers list (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]
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 data download methods, REST API’s and HTTP protocol
- Reviewed The National Map (TNM) API documentation and tested coordinate 
output methods from g.region as input to TNM API for SRTM ⅓ arc sec NED tiles

NEXT WEEK
- How to import and process subsets of IMG tiles into single layer with TNM API 
through GRASS
- Review wxPython
- Figure out basemap service for user region selection

BLOCKS
- None

[1] https://trac.osgeo.org/grass/wiki/GSoC/2017/GRASSGISLocationsfromPublicData


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

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

[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 other interesting
global datasets.



for example Sentinel data are missing...


I just added first links.

More info on how to treat Sentinel in GRASS would be good.

Vero, didn't you write a tutorial on this ?

Moritz

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

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

[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

>> - Researched USGS data download methods, REST API’s and HTTP protocol
>> - Reviewed The National Map (TNM) API documentation and tested
>> coordinate output methods from g.region as input to TNM API for SRTM ⅓
>> arc sec NED tiles
>
>
> I don't know if you have already made a list of target datasets, but I would
> plead for using global datasets, instead of USA-only datasets, whenever
> possible.
>

+1 also here

> 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 other interesting
> global datasets.
>

for example Sentinel data are missing...

> Moritz
>

-- 
ciao
Luca

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

[GRASS-dev] [GRASS GIS] #3359: Missing/incorrect flag in i.superpixels.slic example

[GRASS GIS]

#3359: Missing/incorrect flag in i.superpixels.slic example
-+-
 Reporter:  jpduffy  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Default  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Hello,

 This help page -
 https://grass.osgeo.org/grass72/manuals/addons/i.superpixels.slic.html has
 an example which shows the following:

 `i.superpixels.slic group=lsat output=segments k=2000`

 `k` is not defined as a flag or a parameter anywhere. I think it should be
 updated to reflect the correct syntax.

 Thanks

 James

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

[Ondřej Pešek]

Hi Maris, Luca,

On 12 June 2017 at 08:11, Maris Nartiss  wrote:
> >
> > I have no idea how much of XML parsing is needed, but implementing an
> > own XML parser never sounds a good idea unless it is a quick hack.
> > Working with XML in a correct way is PITA, unless your parser is
> > really good.
> > Just my 0.02, as I haven't seen teh codez.
> >
>
>
As it's specific xml for SOS and not OSM xml, the converter is needed to
convert the SOS output into something readable for GRASS GIS (to import
data as a layer). And as Luca says, the conversion between this xml () and
GeoJSON was just about 50 lines of code.


2017-06-12 9:51 GMT+02:00 Luca Delucchi :

> they are not much lines of code, however I think this code should be
> added to OWSLib, Ondrej do you think is it possible?
>
>
Good idea. I will ask Tom Kradilis and guys from OWSLib about that.

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

Re: [GRASS-dev] [GRASS GIS] #3331: ctypes: ValueError: invalid literal for int() with base 8: '08420217248550443400745280086994171'

[GRASS GIS]

#3331: ctypes: ValueError: invalid literal for int() with base 8:
'08420217248550443400745280086994171'
--+
  Reporter:  neteler  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.2
 Component:  Python   |Version:  unspecified
Resolution:   |   Keywords:  ctypes, python
   CPU:  Unspecified  |   Platform:  Unspecified
--+

Comment (by brunofriedmann):

 Also +1 for the merge of r68348 in main.

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

[Luca Delucchi]

Hi,

On 12 June 2017 at 08:11, Maris Nartiss  wrote:
> 2017-06-11 20:20 GMT+03:00 Ondřej Pešek :
>> Hi everyone!
>> * I had a problem with xml parser in OWSLib for SOS observations, because it
>> works completely different way than we expected. After few conversations I
>> have decided to work with raw output and write parser by myself.
>
> I have no idea how much of XML parsing is needed, but implementing an
> own XML parser never sounds a good idea unless it is a quick hack.
> Working with XML in a correct way is PITA, unless your parser is
> really good.
> Just my 0.02, as I haven't seen teh codez.
>

they are not much lines of code, however I think this code should be
added to OWSLib, Ondrej do you think is it possible?

>> Regards,
>> Ondrej
>
> Māris.
>

-- 
ciao
Luca

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

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

[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
- Reviewed Python scripting for GRASS documentation and existing GRASS
data import modules
- Wrote SRTM 30 download script using Python Elevation library and GRASS
output


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 ?



- Researched USGS data download methods, REST API’s and HTTP protocol
- Reviewed The National Map (TNM) API documentation and tested
coordinate output methods from g.region as input to TNM API for SRTM ⅓
arc sec NED tiles


I don't know if you have already made a list of target datasets, but I 
would plead for using global datasets, instead of USA-only datasets, 
whenever possible.


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 other 
interesting global datasets.


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

Re: [GRASS-dev] [SoC] GSoC 2017 Weekly Report 2 - SOS tools in GRASS GIS

[Maris Nartiss]

2017-06-11 20:20 GMT+03:00 Ondřej Pešek :
> Hi everyone!
> * I had a problem with xml parser in OWSLib for SOS observations, because it
> works completely different way than we expected. After few conversations I
> have decided to work with raw output and write parser by myself.

I have no idea how much of XML parsing is needed, but implementing an
own XML parser never sounds a good idea unless it is a quick hack.
Working with XML in a correct way is PITA, unless your parser is
really good.
Just my 0.02, as I haven't seen teh codez.

> Regards,
> Ondrej

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