date:20190125

Re: [GRASS-dev] [GRASS GIS] #3475: r.mapcalc expression does not accept fully qualified map name as an output

2019-01-25 Thread GRASS GIS

#3475: r.mapcalc expression does not accept fully qualified map name as an 
output
--+-
  Reporter:  marisn   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  minor|  Milestone:  7.2.4
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.mapcalc
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by Nikos Alexandris):

 Is there any activity on this? I have the following pending for a recently
 published add-on:

 {{{#!python
 /osgeo/grasstrunk/dist.x86_64-pc-linux-gnu/scripts/r.estimap.recreation
 --overwrite land=land_suitability@examples potential=potential
 syntax error, unexpected '@', expecting '('
 Parse error
 ERROR: parse error
 Traceback (most recent call last):
   File "/osgeo/grasstrunk/dist.x86_64-pc-linux-
 gnu/scripts/r.estimap.recreation", line 4103, in 
 sys.exit(main())
   File "/osgeo/grasstrunk/dist.x86_64-pc-linux-
 gnu/scripts/r.estimap.recreation", line 3631, in main
 r.mapcalc(subset_land)
   File "/osgeo/grasstrunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/pygrass/modules/interface/module.py",
 line 651, in __call__
 return self.run()
   File "/osgeo/grasstrunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/pygrass/modules/interface/module.py",
 line 772, in run
 self.wait()
   File "/osgeo/grasstrunk/dist.x86_64-pc-linux-
 gnu/etc/python/grass/pygrass/modules/interface/module.py",
 line 797, in wait
 module=self.name, errors=stderr)
 grass.exceptions.CalledModuleError: Module run r.mapcalc
 r.mapcalc expression=tmp.5319.8.land_suitability@examples =
 land_suitability@examples region=current ended with error
 Process ended with non-zero return code 1. See errors in the
 (error) output.
 Removing temporary files
 }}}


  Reading Glynn's last comment
 https://trac.osgeo.org/grass/ticket/676#comment:12, do I understand
 correctly that I should take care to strip '@mapset' part at the add-
 on/module level?

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] difference between r.drain and r.path

2019-01-25 Thread Huidae Cho

Hello,

I had the same question before. These two modules are almost the same.
Actually, r.drain is a wrapper for r.path and creates input directions
internally, then just runs r.path. Not sure if it's worth keeping it just
for that extra step.

Best,
Huidae

On Thu, Jan 24, 2019 at 3:29 AM Moritz Lennert 
wrote:

> Hi,
>
> In GRASS 7.6 we have both r.drain and r.path. What is the difference
> between the two ? Should r.drain be declared as deprecated and replaced
> by r.path ?
>
> Moritz
> ___
> grass-dev mailing list
> grass-dev@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/grass-dev

-- 
Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE
Open Source GIS Developer, GRASS GIS Development Team
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [pdal] C API for PDAL now on GitHub

2019-01-25 Thread Luca Delucchi

Hi all,

Could this be useful for pdal integration?

Regards
Luca

-- Forwarded message -
From: Jaime Soto 
Date: ven 25 gen 2019, 16:28
Subject: [pdal] C API for PDAL now on GitHub
To: 

There is now a C API for PDAL available at https://github.com/PDAL/CAPI.
The API exposes PDAL's JSON pipeline functionality just like the Python and
Java bindings available at GitHub. Take a look at the tests for examples on
how to use the API.

A "pdal-c" package is also available for vcpkg and a conda-forge package is
on its way. I hope that this library serves as a useful FFI for other
language bindings. Please submit an issue or pull request at GitHub if you
have any suggestions. Your help will be much appreciated.

Thanks,

Jaime Soto | js...@simverge.com

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

[GRASS-dev] [GRASS GIS] Batch modify: #964, #1356, #2309, #2394, #2754, #3029, ...

2019-01-25 Thread GRASS GIS

Batch modification to #964, #1356, #2309, #2394, #2754, #3029, #3051, #3150, 
#3290, #3314, #290, #1434, #836, #1938, #2336, #3563, #3697, #2762 by martinl:
milestone to 7.6.1

Comment:
Ticket retargeted after milestone closed

-- 
Tickets URL: 

GRASS GIS 

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

[GRASS-dev] [GRASS GIS] Batch modify: #3315, #3323, #3345, #3355, #3378, #3379, ...

2019-01-25 Thread GRASS GIS

Batch modification to #3315, #3323, #3345, #3355, #3378, #3379, #3386, #3404, 
#3413, #3417, #3433, #3437, #3442, #3452, #3468, #3504, #3515, #3518, #3520, 
#3521, #3528, #3529, #3532, #3534, #3535, #3538, #3552, #3559, #3574, #3598, 
#3605, #3614, #3618, #3627, #3633, #3642, #3646, #3647, #3661, #3703, #3706, 
#3707, #3709, #3710, #3711, #3713, #3728, #3729, #3732, #32, #66, #193, #248, 
#320, #401, #446, #487, #517, #558, #578, #619, #645, #733, #794, #804, #977, 
#1002, #1031, #1075, #1144, #1350, #1669, #1906, #1908, #1979, #2049, #2106, 
#2142, #2233, #2620, #2675, #2982, #3005, #3050, #3082, #3111, #3177, #3180, 
#3299, #3312, #3364, #3366, #3375, #3401, #3454, #3512, #3516, #3547, #3678, 
#412 by martinl:
milestone to 7.6.1

Comment:
Ticket retargeted after milestone closed

-- 
Tickets URL: 

GRASS GIS 

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

[GRASS-dev] [GRASS GIS] Batch modify: #2564, #2565, #2566, #2567, #2569, #2570, ...

2019-01-25 Thread GRASS GIS

Batch modification to #2564, #2565, #2566, #2567, #2569, #2570, #2571, #2573, 
#2582, #2587, #2589, #2600, #2609, #2615, #2625, #2637, #2655, #2685, #2715, 
#2739, #2749, #2767, #2768, #2774, #2804, #2816, #2847, #2867, #2874, #2877, 
#2895, #2897, #2898, #2907, #2911, #2924, #2926, #2948, #2953, #2954, #2955, 
#2958, #2963, #2967, #2976, #2977, #2983, #2987, #2990, #3069, #3076, #3077, 
#3080, #3083, #3096, #3099, #3104, #3109, #3110, #3113, #3120, #3125, #3129, 
#3134, #3143, #3145, #3149, #3154, #3157, #3160, #3164, #3166, #3169, #3174, 
#3183, #3188, #3189, #3192, #3195, #3202, #3203, #3217, #3218, #3228, #3241, 
#3250, #3254, #3260, #3261, #3263, #3265, #3271, #3272, #3283, #3286, #3292, 
#3293, #3309, #3310, #3313 by martinl:
milestone to 7.6.1

Comment:
Ticket retargeted after milestone closed

-- 
Tickets URL: 

GRASS GIS 

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

[GRASS-dev] [GRASS GIS] Batch modify: #1453, #1688, #2951, #899, #3487, #179, ...

2019-01-25 Thread GRASS GIS

Batch modification to #1453, #1688, #2951, #899, #3487, #179, #410, #831, 
#1823, #2124, #2485, #2732, #2788, #3024, #3033, #3079, #3255, #3279, #3298, 
#3626, #250, #562, #603, #774, #790, #793, #857, #939, #1033, #1135, #1156, 
#1170, #1219, #1357, #1360, #1466, #1509, #1623, #1627, #1640, #1649, #1659, 
#1673, #1678, #1726, #1755, #1794, #1798, #1811, #1818, #1821, #1852, #1860, 
#1881, #1910, #1922, #1939, #1976, #1998, #2052, #2111, #2112, #2123, #2126, 
#2155, #2203, #2226, #2227, #2232, #2241, #2248, #2249, #2254, #2280, #2282, 
#2296, #2301, #2302, #2307, #2321, #2323, #2328, #2329, #2333, #2345, #2346, 
#2361, #2362, #2376, #2383, #2399, #2402, #2412, #2428, #2446, #2459, #2464, 
#2465, #2487, #2526 by martinl:
milestone to 7.6.1

Comment:
Ticket retargeted after milestone closed

-- 
Tickets 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] #3724: wrong OSGEO4W_ROOT when installing OSGeo4W to different target directory

2019-01-25 Thread GRASS GIS

#3724: wrong OSGEO4W_ROOT when installing OSGeo4W to different target directory
---+---
  Reporter:  martinl   |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  7.4.5
 Component:  Installation  |Version:  svn-trunk
Resolution:|   Keywords:  wingrass, osgeo4w
   CPU:  Unspecified   |   Platform:  Unspecified
---+---

Comment (by martinl):

 See related https://trac.osgeo.org/osgeo4w/ticket/592

-- 
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] #3339: postgis topology: missing relations

2019-01-25 Thread GRASS GIS

#3339: postgis topology: missing relations
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  normal   |  Milestone:  7.8.0
 Component:  LibVector|Version:  unspecified
Resolution:  fixed|   Keywords:  postgis topology
   CPU:  Unspecified  |   Platform:  Unspecified
--+--
Changes (by martinl):

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


Comment:

 In [changeset:"74013" 74013]:
 {{{
 #!CommitTicketReference repository="" revision="74013"
 postgis topology: missing relations, fix #3339
 }}}

-- 
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] #3339: postgis topology: missing relations

2019-01-25 Thread GRASS GIS

#3339: postgis topology: missing relations
--+--
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  LibVector|Version:  unspecified
Resolution:   |   Keywords:  postgis topology
   CPU:  Unspecified  |   Platform:  Unspecified
--+--
Changes (by martinl):

 * milestone:  7.2.4 => 7.8.0


-- 
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] #1684: configure GRASS 6 with X11 support

2019-01-25 Thread GRASS GIS

#1684: configure GRASS 6 with X11 support
+
  Reporter:  martinl|  Owner:  grass-dev@…
  Type:  defect | Status:  closed
  Priority:  major  |  Milestone:  6.4.6
 Component:  Compiling  |Version:  svn-releasebranch64
Resolution:  fixed  |   Keywords:  configure, X11, debian
   CPU:  x86-64 |   Platform:  Linux
+
Changes (by martinl):

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


Comment:

 Seems to be solved.

-- 
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] GSoC 2019 - Call for mentors and ideas

2019-01-25 Thread Helmut Kudrnovsky

Dear OSGeo community,

It is time for *GSoC* [1] this year, so this is our starting information to get 
involved!

If you are willing to act as a mentor [2], fill in this form:

< https://goo.gl/forms/njL27YLWBVensZ3m1 >

If you want to participate proposing ideas, you just need 
to send us (admins:  ) the URL for your project's
ideas page.

Remember that every idea should indicate:

• A title
• A description
• 2 mentors 
• A test for the students to submit to your evaluation. The test aims at 
evaluating if the student is capable for the project, so please design the test 
having in mind the skills required to complete the project.

Time is short, we need to collect all URLs by Feb 4. Here the timeline [3].

Thanks and please forward to your project community.

Your OSGeo GSoC admins

[1] https://summerofcode.withgoogle.com/
[2] https://wiki.osgeo.org/wiki/Google_Summer_of_Code_2019_Administrative
[3] https://summerofcode.withgoogle.com/how-it-works/#timeline
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G 2019 Bucharest Call for Contributions Open

2019-01-25 Thread Moritz Lennert

Who else will come to Bucharest ? Anyone willing to (co-)organise a 
workshop ?


What topics would users find the most useful for a workshop ?

Moritz


 Forwarded Message 
Subject: [OSGeo-Discuss] FOSS4G 2019 Bucharest Call for Contributions Open
Date: Thu, 24 Jan 2019 15:59:23 +0200
From: Codrina Maria Ilie 
To: disc...@lists.osgeo.org, conference_...@lists.osgeo.org

Dear geospatial friend,

We are happy to invite you to come present your work at FOSS4G 2019 
Bucharest! The call for contributions is now open.


You succeeded in overcoming a difficult issue of an open source 
geospatial library and you can’t wait to put it to the test? Or maybe 
you are beginning a new project and you can’t wait to gather ideas 
around it? Or you are keen to share the intermediate results of our 
geospatial endeavors and to see how your peers would deal with the 
foreseen deadlocks? Then FOSS4G 2019 Bucharest is the event where you 
need to be at! Even though the underlying backbone of FOSS4G is strictly 
defined by open source related activities, make no mistake, this is 
where geo-domains leaders, high-end developers, senior and junior users, 
university professors and researchers have been coming for the last 10 
years for their geo-update. Thus, where to best present your work and 
achievements if not at the focal point of the geospatial international 
community?


You can submit three types of contributions[1]: talk[2], workshop[3] and 
academic paper[4]. Do pay special attention when checking the details 
(especially the deadlines!) on each dedicated page.


And don’t forget of our #historicalearlybird offer[5]. If you hurry, you 
just might still catch one of the 100 special T-shirts!..


With confidence for a wonderful FOSS4G 2019 Bucharest program built with 
your contributions,

FOSS4G 2019 Bucharest team

[1] https://2019.foss4g.org/call-for-papers/
[2] https://2019.foss4g.org/call-for-papers/general-sessions/
[3] https://2019.foss4g.org/call-for-papers/workshop-proposals/
[4] https://2019.foss4g.org/call-for-papers/academic-sessions/
[5] https://2019.foss4g.org/register/
___
Discuss mailing list
disc...@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/discuss
--
Département Géosciences, Environnement et Société
Université Libre de Bruxelles
Bureau: S.DB.6.138
CP 130/03
Av. F.D. Roosevelt 50
1050 Bruxelles
Belgique

tél. + 32 2 650.68.12 / 68.11 (secr.)
fax  + 32 2 650.68.30
--
Département Géosciences, Environnement et Société
Université Libre de Bruxelles
Bureau: S.DB.6.138
CP 130/03
Av. F.D. Roosevelt 50
1050 Bruxelles
Belgique

tél. + 32 2 650.68.12 / 68.11 (secr.)
fax  + 32 2 650.68.30
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3733: winGRASS 7.7svn execute command fails

2019-01-25 Thread GRASS GIS

#3733: winGRASS 7.7svn execute command fails
--+---
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.8.0
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  python3, wingrass
   CPU:  Unspecified  |   Platform:  Unspecified
--+---

Comment (by martinl):

 In [changeset:"74010" 74010]:
 {{{
 #!CommitTicketReference repository="" revision="74010"
 winGRASS 7.7svn execute command fails, see #3733
 }}}

-- 
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] Migration to git, use addons as test case?

2019-01-25 Thread Martin Landa

Hi,

pá 25. 1. 2019 v 9:09 odesílatel Stefan Blumentrath
 napsal:
> General structure with regards to code that need hosting (or not): trunk, 
> addonds sandbox, website, …
> Tickets and history

see related ticket [1]. I wanted to setup real testing environment
where we can test trac and git integration (I just need to do the last
step, to restore backup of GRASS trac to sandbox). It could help us to
decide whether to use

* git + trac for issues
* git + issue tracker together (github,. gitlab, ...) -> trac swiched
to read only mode (probably except of wiki)

Ma

[1] https://trac.osgeo.org/grass/ticket/3722

-- 
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] Migration to git, use addons as test case?

2019-01-25 Thread Stefan Blumentrath

Hi Vashek,

Thanks for the valuable info. Agree, that we should start collecting thoughts 
and options on a wiki page as preparation of a decision. I can setup a draft 
tonight (central European time), where I try to extract info from ML-archive.

Such a wiki page could contain the following things:

Relevant aspects to consider independent from platform chosen:

  *   General structure with regards to code that need hosting (or not): trunk, 
addonds sandbox, website, …
  *   Tickets and history
  *   …

A collection of examples and experiences (from other projects (GDAL, QGIS, …) 
and links to ongoing discussions (osgeo-discuss).

Links to latest development / solutions for GRASS code base.

Evaluation of alternative hosting platforms (pros and cons). Maybe also a 
“popular vote” by users for consideration by PSC?

Kind regards,
Stefan


From: Vaclav Petras 
Sent: fredag 25. januar 2019 05:41
To: Luca Delucchi 
Cc: Stefan Blumentrath ; GRASS developers list 

Subject: Re: [GRASS-dev] Migration to git, use addons as test case?



On Thu, Jan 24, 2019 at 3:12 AM Luca Delucchi 
mailto:lucadel...@gmail.com>> wrote:


On Tue, 22 Jan 2019 at 08:09, Stefan Blumentrath 
mailto:stefan.blumentr...@nina.no>> wrote:

Just wondering, regarding migration to git, would it be helpful to use AddOns 
(and possibly sandbox) as a test case?

yes this could be a good idea,

There is couple of different workflows which could be used for Addons besides 
one big repo considering what you can do with Git and Git hosting platforms, 
e.g. submodules. It would be good to collect advantages and disadvantages (e.g. 
on Trac wiki).

I'm not sure if sandbox is that interesting now, because on most platforms, 
even the self-hosted, you will probably have the option of personal repos.

One thing to figure out with both of them is that with Subversion, we you can 
just do `svn cp` to get data from one to the other when you promoting or 
depreciating modules (sandbox->addons->core, core->addons) when you had a 
checkout (svn checkout) of the whole repo (with grass, grass-addons, ...). One 
command, all history preserved. What would be a Git equivalent of this?

but first probably we have to choose which git platform to use. There are many 
possible options right now

There were discussions about this at osgeo-discuss and here probably as well. 
If somebody would be willing to summarize it, it may help us to get started. 
Point of view of occasional contributors would be quite helpful here.

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

Re: [GRASS-dev] [GRASS GIS] #3475: r.mapcalc expression does not accept fully qualified map name as an output

Re: [GRASS-dev] difference between r.drain and r.path

[GRASS-dev] Fwd: [pdal] C API for PDAL now on GitHub

[GRASS-dev] [GRASS GIS] Batch modify: #964, #1356, #2309, #2394, #2754, #3029, ...

[GRASS-dev] [GRASS GIS] Batch modify: #3315, #3323, #3345, #3355, #3378, #3379, ...

[GRASS-dev] [GRASS GIS] Batch modify: #2564, #2565, #2566, #2567, #2569, #2570, ...

[GRASS-dev] [GRASS GIS] Batch modify: #1453, #1688, #2951, #899, #3487, #179, ...

Re: [GRASS-dev] [GRASS GIS] #3724: wrong OSGEO4W_ROOT when installing OSGeo4W to different target directory

Re: [GRASS-dev] [GRASS GIS] #3339: postgis topology: missing relations

Re: [GRASS-dev] [GRASS GIS] #3339: postgis topology: missing relations

Re: [GRASS-dev] [GRASS GIS] #1684: configure GRASS 6 with X11 support

[GRASS-dev] GSoC 2019 - Call for mentors and ideas

[GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G 2019 Bucharest Call for Contributions Open

Re: [GRASS-dev] [GRASS GIS] #3733: winGRASS 7.7svn execute command fails

Re: [GRASS-dev] Migration to git, use addons as test case?

Re: [GRASS-dev] Migration to git, use addons as test case?

16 matches

Site Navigation

Mail list logo

Footer information