Re: [GRASS-dev] C code indented

On Tue, 13 Sept 2022 at 09:33, Vaclav Petras wrote: > > Formatting needs to be enforced in the CI. This can be done with something > like re-indent followed by git diff. > > Maybe something like this could be used? https://github.com/marketplace/actions/clang-format-check Note that it doesn't ac

Re: [GRASS-dev] Fwd: [OSGeo-Discuss] FOSS4G Community Sprint 2022

Hello all, For the FOSS4G community sprint we have a sign up sheet here . I'm not there physically, but I'd still love to work together on the weekend. I'm planning on working more on the command line stuff I've been looking at r

Re: [GRASS-dev] Community sprint at FOSS4G 2021

Ugh. I give up. Perl and I just agreed to go our separate ways :P --Wolf *-- * * ^.___* *( ,__// / Wolf Bergenheim* On Sat, 2 Oct 2021 at 12:01, Wolf Bergenheim wrote: > Hey Vaclav, > > Sure, perl is by no means an area I know much about, but looks quite

Re: [GRASS-dev] Community sprint at FOSS4G 2021

Hey Vaclav, Sure, perl is by no means an area I know much about, but looks quite simple :) *-- * * ^.___* *( ,__// / Wolf Bergenheim* On Sat, 2 Oct 2021 at 10:23, Vaclav Petras wrote: > > > > On Fri, Oct 1, 2021 at 10:31 AM Wolf Bergenheim > wrote: > >>

Re: [GRASS-dev] Community sprint at FOSS4G 2021

European morning works for me. Will be in and out, though. Mainly I'm looking for opportunities to contribute after 10 years away :P --Wolf *-- * * ^.___* *( ,__// / Wolf Bergenheim* On Fri, 1 Oct 2021 at 09:31, Ondřej Pešek wrote: > Ciao, > > st 29. 9. 2021 v 23:04 ode

Re: [GRASS-dev] Introduction and GSoC

On Fri, Mar 23, 2012 at 22:04, Eric Momsen wrote: > On Fri, Mar 23, 2012 at 2:41 PM, Wolf Bergenheim > wrote: > > Hi Eric! > > > > It might help us in trying to classify you if you could tell a bit about > > your programming experience. What languages are you co

Re: [GRASS-dev] Fwd: [OSGeo-Discuss] OSGeo has been accepted at Google Summer of Code!

show/google/gsoc2012/osgeo > [1] > http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Administrative > [2] http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Ideas > [3] http://wiki.osgeo.org/wiki/Google_Summer_of_Code_2012_Improvements > > All the best! > > Anne Ghisla, Wolf Be

Re: [GRASS-dev] Introduction and GSoC

Hi Eric! It might help us in trying to classify you if you could tell a bit about your programming experience. What languages are you comfortable with? I see that you are interested in data mining, which is unfortunately something I know very little about... Did you see any ideas which interested

Re: [GRASS-dev] GSOC: ideas

Hi Luca, Glad to hear you are thinking of applying :). On Wed, Mar 30, 2011 at 13:23, Luca Delucchi wrote: > 2) from the GRASS GSOC ideas WMS and/or TiledMapService and/or WMS-T > layer support, is there someone interested to do the mentor? > > I like this idea, and would be interested in metori

Re: [GRASS-dev] r.sun and pj_do_proj() calls

On Thu, Jun 10, 2010 at 09:10, Seth Price wrote: > Which came from here: > http://newtrac.osgeo.org/grass/log/grass-addons/r.sun_horizon/r.sun2/rsunlib.c?rev=25783 > > The comments say it came from JRC, but what is that? The JRC seems to be the European Commission Joint Research Centre http://ec.

[GRASS-dev] Re: [SoC] Weekly reports #2 wxNviz

Martin, I think you forgot the links ;) --Wolf ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Soc - wxNviz proposal

_SoC_2010 > > -- > Martin Landa * http://gama.fsv.cvut.cz/~landa > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev > -- <8 ) Wolf Bergenheim ( 3>

[GRASS-dev] Re: google soc

ady > > http://grass.osgeo.org/wiki/GRASS_SoC_Ideas > > I think we need to eventually remove the sections that don't have any ideas > listed - > or to reformulate to e.g. "student ideas welcome" > > Helena -- <8 ) Wolf Bergenheim ( 3> _

Re: [GRASS-dev] Doubt regarding r.lake

7;m willing to test it. --Wolf -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [R-sig-Geo] [Report #2] Kriging with GRASS and R: v.autokrige port to wxPython and more

d R using automap… > > Sure it will! I'll have a look at how to add this functionality in the > next weeks. I think there is a function in SWIG so that your module will have the same commandline behaviour as other GRASS modules. Martin, you know better than I do how to enn

Re: [GRASS-dev] GRASS and C++

e implicit %.o: %.cpp rule though...) %.o: %.cpp $(CXX) -c $(CXXFLAGS) $< -o $@ CMD_OBJS = $(subst .cpp,.o,$(wildcard *.cpp)) Before you include include $(MODULE_TOPDIR)/include/Make/Module.make --Wolf -- Wolf Bergenheim (wolf+gr...@bergenheim.net)

Re: [GRASS-dev] v.buffer

which use the old syntax. Aren't we supposed to be more or less backwards compatible within a major version? However distance is a more "proper" name for the parameter IMHO. So keep it as distance in 7 maybe? --Wolf -- <:3 ) Wolf Bergenheim ( 8:>

Re: [GRASS-dev] Google Summer of Code mentors

el Barton : >> I've received a LOT of chatter on the SoC list since re-upping as potential >> mentor, but have not noticed anything about GRASS. Maybe I've just missed it >> in all the other stuff. > > me too, I just remember one student speaking about OpenMP int

Re: [GRASS-dev] call for volunteers - urgent need for Windows Vista binaries

__ > grass-dev mailing list > grass-dev@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/grass-dev -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

[GRASS-dev] Re: [GRASS-user] v.generalize for area boundaries?

ould use the douglas method to reduce the number of points. I'll see if I can whip up an example for you. --Wolf -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Add GMP library to GRASS

I know how to do it and I can provide the fixed version to someone who can commit to trunc. Just add it as a separate file in your addons directory. It can be merged to develbranch_6 and trunk from there. Thanks, --Wolf -- <:3 ) Wolf Berge

Re: [GRASS-dev] How to create union of areas with isles

kwise). This will create bridges to the islands. Those are removed with a call to Vect_remove_bridges(); so I guess you don't need to worry about them. Markus, Glynn, Hamish, is that right? Is there no way to create islands without creating bridges? --Wolf -- <:3 ) Wolf Berge

Re: [GRASS-dev] terminology issues in grass7

Yes, that would conform more with the terminology of most other GIS:es out there. Especially the vector layer is very confusing for people who switch to GRASS. The renaming the layer parameters might need a lot of manual work, or maybe we can device a script to do it. --Wolf -- <:3 ) Wolf B

Re: [GRASS-dev] A0-A10 paper size calculations

it is available for purchase. A mandatory wikipedia reference (yes I realize wikipedia is very unreliable blabla...) which also references Moritz' first source ;) http://en.wikipedia.org/wiki/ISO_216 --Wolf -- <:3 ) Wolf Bergenheim ( 8:> __

[GRASS-dev] Re: [GRASS-user] New proposal web site

On 21.06.2008 19:40, Martin Landa wrote: Hi, 2008/6/21 Paul Kelly <[EMAIL PROTECTED]>: Note there already is an experimental Drupal site at http://grass-dev.osgeo.net/. not working now, -> "Address Not Found" (?) Martin Yes it is [worksforme] ;) --Wolf -- <:3

Re: [GRASS-dev] proper v.parallel behavior on strange input

ld allow for all kinds of interesting buffer shapes. --Wolf -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] proper v.parallel behavior on strange input

s-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev -- <:3 ) Wolf Bergenheim ( 8:> <>___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [SoC] Status Report: Reimplementation of v.voronoi and v.delaunay in GRASS GIS

@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Contributing code to GRASS?

I forgot to add the link to the programmer's manual. Here it is: http://download.osgeo.org/grass/grass6_progman/ --Wolf On 22.05.2008 00:00, Wolf Bergenheim wrote: On 12.05.2008 11:56, Tomas Ukkonen wrote: Hi, I'm working at Finnish Geodetic Insitute where we have developed so

Re: [GRASS-dev] Contributing code to GRASS?

ile I'll be happy to help you in case you have any more questions. --Wolf -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] d.labels

Hamish, I know you are busy and all, but I'd like to know whether you are ok with this approach or not. I'd like to start moving forward.. :) --Wolf On 27.04.2008 17:26, Hamish wrote: Wolf Bergenheim wrote: I have a patch to d.labels that I intend to apply. This patch adds s

Re: [GRASS-dev] GRASS 7 development started

ts to: find . -type f -name '*.c' | xargs indent find also has the nice -exec switch, which will allow you to have find exec indent. It's probably a bit faster. find . -type f -name '*.c' -exec indent {} \; I can do that, I have a 10 Mb connection. --Wolf -- <

Re: [GRASS-dev] Small tcltk fonts used in gis.m gui

/grass-dev -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS 7 development started

you can easily make a tar ball of your code. Thanks. --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] d.labels

code in place I'm ready to call this almost done, and think we can start merging the two. Especially if you'll accept my NONE patches ;) Man, it's great to find a few minutes to hack on GRASS again! :D --Wolf -- <:3 ) Wolf Bergenheim ( 8:>

Re: [GRASS-dev] d.labels

I have the patch for ps.map too. (attached). Please comment on it too, if you want. --Wolf On 27.04.2008 14:18, Wolf Bergenheim wrote: Hi! I have a patch to d.labels that I intend to apply. This patch adds support for positioning the label _exactly_ on the co-ordinated given in the labels

[GRASS-dev] d.labels

exactly on that point. Feel free to comment on the patch. Next I need to look at how ps.map positions labels... Please see [1] for example screenshots. --Wolf [1] http://wolf.bergenheim.net/src/GRASS/v.label.sa -- <:3 )---- Wolf Bergenheim ( 8:> Index: do_la

Re: [GRASS-dev] GSoC, Reimplementing v.buffer and adding features

ndeed quite a while since it has worked properly. Elliptical buffers will come in handy I'm pretty sure. I hope you'll have fun working on it! --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev

[GRASS-dev] Character glyphs

tter). Thanks for your time, --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GSoC, reimplementation of modules v.voronoi and v.delaunay

of a better name. Anybody else have some idea? Another way to handle it would be to make two modules, but re-use that 70% by having it in a library or something. --Wolf On Thu, Apr 24, 2008 at 5:57 AM, Wolf Bergenheim <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

Re: [GRASS-dev] 6.3.0 is out! please prepare binaries...

Glynn! I have backported fixed Makefile to releasebranch_6_3. I am afraid we need to tag 6.3.0 again(?) *Can* we redo 6.3.0? Or go directly for 6.3.1? Markus ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-de

Re: [GRASS-dev] Building a new module for GRASS6.2.3

On 03/29/2008 08:14 PM, Markus Neteler wrote: I have started a trac Wiki page for collecting such things: http://trac.osgeo.org/grass/wiki/HowToProgram Please extend this page. Very nice. This page will be really handy for SoC students :) --Wolf -- <:3 )---- Wolf Bergenheim

Re: [GRASS-dev] Google Summer of Code 2008

17:41:42 +0200 From: Wolf Bergenheim <[EMAIL PROTECTED]> Subject: Re: [GRASS-dev] Google Summer of Code 2008 To: Hamish <[EMAIL PROTECTED]> Cc: GRASS developers list Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Wolf, I emailed in

Re: Re[GRASS-dev] ady to help with GRASS graphics

best solution seems to be 24x24. Is it acceptable from i/ coding (TclTk, wxpython) ii/ general Grass layout point of view? I think 24x24 icons are good, as they seem to be used. Better yet, make them in SVG so we can later render them into different sizes. --Wolf -- <:3 )---- Wolf Bergenh

Re: Re[GRASS-dev] ady to help with GRASS graphics

for GIS users but original and uniform template. Time schedule depending on my time and your comments. Robert -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Google Summer of Code 2008

rt color values into the DB. What I'd love to see is a GUI tool to create these files (and queries). --Wolf -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Google Summer of Code 2008

R script. this is related to the R integration threads. Definitely a very weak point of GRASS currently. I think we need to have really good kriging ASAP. I think it would be better to maybe focus on some sort of integration tool to the existing good Kriging tools out there. --Wolf --

Re: [GRASS-dev] Google Summer of Code 2008

On 03/09/2008 03:25 AM, Hamish wrote: Wolf Bergenheim wrote: * displaced symbols. Create a module to place map symbols on a map, so that the feature and other overlap information is minimized (NP-Complete problem). The map symbol should be referenced to their original location, by

Re: [GRASS-dev] Google Summer of Code 2008

nswer questions, either per email or in the #GRASS channel in IRC. --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: Re[GRASS-dev] ady to help with GRASS graphics

o much easier to remember an icon then to read a menu entry... --Wolf -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Re: [GRASS-user] Interpolation with faultlines?

, depending on the student. These would maybe be a natural extension. So step one would be to add support to v.surf.rst and then continue with the others. --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osg

Re: [GRASS-dev] Google Summer of Code 2008

h the list and indicate which projects they would feel comfortable mentoring. The PSC should also go through the list of mentors and rubber stamp the ones they approve of. --Wolf [1] http://grass.gdf-hannover.de/wiki/GRASS_SoC_Ideas -- <:3 )---- Wolf Bergenheim

[GRASS-dev] Google Summer of Code 2008

ing an Idea won't require any commitment. I think it is more important to get more ideas, later we will see who can mentor what. (I suspect that we will have sround 2 slots this year for GRASS) --Wolf -- <:3 ) Wolf Bergenheim ( 8:>

Re: [GRASS-dev] GRASS in a usability review

. If you are willing and able to serve as a technical contact even better. Everybody else seems to be too busy ;) I might also be able to help out. --Wolf PS. You might want to update your address book for the mailinglist address. ;) -- <:3 )

Re: [GRASS-dev] GRASS in a usability review

than 2 levels deep and that menu item names should be shorter. This was difficult to do, given GRASS's complexity. But having done it, I think it helped usability a lot. Yes, I agree. It is a lot better, but I believe it could be made even be

Re: [GRASS-dev] GRASS in a usability review

the means. I'm always interested in talking about usability for GRASS. Hope we get some more interest then in the past... --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://list

Re: [GRASS-dev] Autoconf 2.13

automake to cmake, and I think it was a good success (*much* less bloody than I expected). Now compilation is way smoother and faster. Would it be reasonable to do the same for GRASS? All the best. pc -- <:3 )---- Wolf Bergenheim ( 8:> ___

Re: Fwd: [GRASS-dev] 6.3.0RC4 on Gentoo

27;ll give it to the admin and see if they can get it installed. Thanks! --Wolf -- <:3 ) Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] cvs>svn?

ur MS thesis. --W -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS Drupal web site

A voice: 480-965-6262; fax: 480-965-7671 www: http://www.public.asu.edu/~cmbarton On Jan 16, 2008, at 10:00 AM, [EMAIL PROTECTED] wrote: Date: Wed, 16 Jan 2008 10:19:37 +0200 From: Wolf Bergenheim <[EMAIL PROTECTED]> Subject: [Fwd: Re: [GRASS-dev] cvs>svn?] To: GRASS developers list Me

[Fwd: Re: [GRASS-dev] cvs>svn?]

s familiar with code can edit a page and post a message to the mailing lists via the web interface. --Wolf -- <:3 ) Wolf Bergenheim ( 8:> -- |Humpty Dumpty sat on a wall (o< --|Humpty Dumpty had a great fall //\ |All the king's horses and all the king's m

Re: [GRASS-dev] cvs>svn?

ccessing a version control repository trough Drupal, a bit like webVC. Don't be afraid of the new installation, just go in there and get your hands dirty! Send me an email if you need / want editing rights. --Wolf -- <:3 )---- Wolf Bergenheim ( 8:>

Re: [GRASS-dev] cvs>svn?

and even wysiwyg editors. > > Having said that I am all for lowering barriers to entry to allow more > helpers to contribute. But raw HTML is not very hard, and Markus's nice > CSS setup ensures a consistent and pretty look. > Well that is what Drupal does too. --Wolf -- <

[GRASS-dev] Re: [GRASS-user] measuring line sinuosity in GRASS

values and then an update with the value calculated in the script. Anyway, I have just committed changes to the SVN, and so maybe it will be merged to the next release? Anyway I've attached the diff for your convenience. I hope you enjoy it :) --Wolf -- <:3 ) Wolf Berg

[GRASS-dev] Re: [GRASS-web] GRASS website migration - content types

On 11.01.2008 00:33, Wolf Bergenheim wrote: Hi! On Saturday I have scheduled time to make the http://grass-dev.osgeo.org/ website ready for access to GRASS developers. Hello, sorry for cross post, but I think this might be interesting to a larger crowd then just the web list... I have now

[GRASS-dev] 6.3.0RC4 on Gentoo

Hi gang, Could anyone here be so kind as to provide a gentoo package for the most recent 6.3.0RC4 release? --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/li

Re: [GRASS-dev] Message standardization

exceptions that can create > maps in other mapsets or new locations] --HB > FWIW I think that using @mapset should be limited to cases where mapset is not the current mapset. And should *always* be used in that case whether the input came from the user or not. --Wolf -- <:3 )

Re: [GRASS-dev] remove v.generalize/v.path.obstacles from grass add-ons

On 12.12.2007 12:04, Martin Landa wrote: > Hi all, > > I guess v.generalize and v.path.obstacles can removed from > grass-addons (now in main source tree as v.generalize and > v.net.visibility). > Yes. I'll do it (to test my SVN access) --Wolf -- <:3 )--

[GRASS-dev] where= and cats= to all vector commands

the result to only cats in the given list? Or output a warning that where takes precedence over cats? --Wolf -- <:3 )---- Wolf Bergenheim ( 8:> ___ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev