Re: [GRASS-dev] An applicant for GSoC 2024

familiarizing myself with the source code of Grass GIS. I hope I am on the > right track. If you have any comments or suggestions, please feel free to > let me know. Thanks a lot! > > Best, > > Chung-Yuan > > On Mon, Apr 1, 2024 at 10:20 PM Huidae Cho wrote: > >>

Re: [GRASS-dev] An applicant for GSoC 2024

formance computing and machine learning to advance > geospatial applications and research. > > Last week, at the AWRA 2024 GWTC conference, I met Prof. Huidae Cho, who > introduced me to the Google Summer of Code (GSoC) program. Inspired by our > conversation, I am writing to expre

Re: [GRASS-dev] [GRASS-user] [EXTERNAL] vector patching frustration

2 > > Yours, > V. > > Le vendredi 15 mars 2024 à 09:51 -0600, Huidae Cho a écrit : > > Michael, > > > > Just confirmed your issue. > > > > v.random tmp100 npoints=100 seed=100 > > v.db.addtable tmp100 col="id varchar(20)" > > v.db.updat

Re: [GRASS-dev] [EXTERNAL] vector patching frustration

ense.com/v3/__https://openmodelingfoundation.github.io/__;!!IKRxdwAv5BmarQ!dv7XjZX6-VnNpFbpXP6R1XYWkuaA4Y-gDR4RvL3bWazWUkLfURuKDMWqiBFqBS6jlNSHDKZCo02GJKjauaAJ-pCVvuAToIA$> > ) > Director, Network for Computational Modeling in Social & Ecological > Sciences (https://comses.net > <

Re: [GRASS-dev] [release planning] GRASS GIS 8.3.2

+1 Huidae -- Huidae Cho, Ph.D., GISP GRASS GIS Developer https://idea.isnew.info/ Sent from my phone On Wed, Mar 6, 2024, 8:17 AM Anna Petrášová via grass-dev < grass-dev@lists.osgeo.org> wrote: > +1 > > Anna > > On Wed, Mar 6, 2024 at 9:54 AM Martin Landa > wrote: &

Re: [GRASS-dev] GRASS Teams on GitHub

ome (grass-addons-subversion-committers -> > grass-addons-write) but I guess this is for another and much more > contentious discussion. > ___________ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/l

[GRASS-dev] Contents for FOSS4G Asia 2023

Dear All, I'm currently working on slides for FOSS4G Asia 2023 next week. If I missed any important things, please let me know or feel free to create PRs. Any help would be appreciated! https://github.com/HuidaeCho/grass-gis-talk-foss4g-asia-2023 Best, Huidae -- Huidae Cho, Ph.D., GISP, /hidɛ

Re: [GRASS-dev] Candidate modules for OpenMP parallelization

C 2021, there are not that many > modules left that could be described as "low hanging fruit". Do you have > any suggestions? > > The proposal is due very soon. > > Thanks, > Anna > -- Huidae Cho, Ph.D., GISP, /hidɛ <http://ipa-reader.xyz/?text=hi

Re: [GRASS-dev] [GRASS-user] Fwd: [OSGeo-Discuss] GSoC 2023: OSGeo Accepted as Mentor Organization | Form for Mentors

GSoC Admins > ___ > Discuss mailing list > disc...@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/discuss > ___ > grass-user mailing list > grass-u...@lists.osgeo.org > http

[GRASS-dev] Transifex Migration to OSGeo Weblate for GRASS Translation

OSGeo account is set up, go to https://weblate.osgeo.org/projects/grass-gis/ to start translating on the new platform. Please let us know if you have any questions about this migration: https://lists.osgeo.org/mailman/listinfo/grass-translations Best Regards, Huidae -- Huidae Cho, Ph.D., GISP, /hidɛ

Re: [GRASS-dev] [release planning] GRASS GIS 8.0.1

z/gwiki/Landa > http://gismentors.cz/mentors/landa > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., GISP, /hidɛ <http://ipa-reader.xyz/?

Re: [GRASS-dev] GRASS + WSL

Windows desktop! It's a bit surreal. > > Best Regards, > -Brad > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., GISP, /hidɛ <http://i

Re: [GRASS-dev] [GRASS-PSC] difficult to get GRASS source code package

e should all remember to post > links to zip as well as .tar.gz etc on our main download pages. > > -jeff > > > > > > -- > Jeff McKenna > GatewayGeo: Developers of MS4W, MapServer Consulting and Training > co-founder of FOSS4G > http://gatewaygeo.com/ >

Re: [GRASS-dev] strange problem using v.out.ogr

C), 480-727-0709 (CSDC) > www: http://shesc.asu.edu, https://complexity.asu.edu, > http://www.public.asu.edu/~cmbarton > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.

Re: [GRASS-dev] Python and script header definitions for modules

gt; # % required: output,-e > # %end > """ # noqa: E501 > > Links: > > https://github.com/OSGeo/grass/pull/1446 > https://www.flake8rules.com/rules/E265.html > https://www.flake8rules.com/rules/E501.html > http://pylint-messages.wikidot.com/messages:c0111 > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大 GRASS GIS Developer https://idea.isnew.info/ ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] Parallelization of existing modules for GRASS GIS

__ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大 GRASS GIS Developer https://idea.isnew.info/ ___ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] GRASS GIS single layout (GSoC 2021)

window GUI makes a sound use case and it would be nice > to keep it reasonably accessible. > > -- > Denis Ovsienko > _______ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., GISP,

[GRASS-dev] Google Summer of Code (GSoC) 2021

, please feel free to discuss those with your potential mentors. Please check [3] and let us [4] know if you have any questions. Looking forward to your applications! Best Regards, Huidae Cho [1] https://summerofcode.withgoogle.com/ [2] https://trac.osgeo.org/grass/wiki/GSoC/2021 [3] https

Re: [GRASS-dev] Next Tasks For The GSoC Project

end another email to the mailing list, not focusing > on GSoC, but really for general discussion, to see what people expect from > this and how they think your idea would work. This can help you define for > the proposal what you are aiming at in your project. Then, for the > proposal

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

Petrášová wrote: > > > On Wed, Feb 17, 2021 at 11:51 AM Huidae Cho wrote: > >> Anna, >> >> Thanks! I just updated the wiki and filled out the form. Will I receive >> further communications from OSGeo (e.g., rejected, accepted, how to >> proceed...)? &

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

Anna, Thanks! I just updated the wiki and filled out the form. Will I receive further communications from OSGeo (e.g., rejected, accepted, how to proceed...)? Regards, Huidae On Wed, Feb 17, 2021 at 11:29 AM Anna Petrášová wrote: > > > On Tue, Feb 16, 2021 at 2:37 PM Huidae C

Re: [GRASS-dev] Need a mentor for GSoC parallelization topic

ar, OSGeo is not even accepted yet. If you are > interested, please also fill this form [2]. > > Thank you for considering this, > > Anna > > [1] > https://trac.osgeo.org/grass/wiki/GSoC/2021#Parallelizationofexistingmodules > [2] https://forms.gle/9Na1vzGX3ESxqgpj9 >

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

:19 PM Moritz Lennert < > > >mlenn...@club.worldonline.be> wrote: > > >> > > >> > > >> > > >> Am 29. Januar 2021 20:54:06 GMT+00:00 schrieb Markus Metz < > > >markus.metz.gisw...@gmail.com>: > >

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

e difficult because apparently C++ standards > are not fully backwards compatible. We had corresponding problems with C++ > code in GRASS previously and fixed these problems when they arose. > > Markus M > > > On Thu, Jan 28, 2021 at 3:33 PM Huidae Cho wrote: > >> Nic

Re: [GRASS-dev] Min. req. of programming language standard support, GRASS GIS 8

t regards, > Nicklas > > > > [1] https://github.com/OSGeo/grass/issues/1241 > [2] https://github.com/OSGeo/grass/issues/1247 > [3] https://github.com/OSGeo/grass/pull/1256 > ___________ > grass-dev mailing list > grass-dev@

Re: [GRASS-dev] [GRASS GIS Elections 2020] Voting phase closed, presentation of results

Dear the GRASS community, Thank you for your support and I am honored to be elected for the PSC. I am excited that I can contribute to the community in a different way. We will all make GRASS a better GIS! Best Regards, Huidae Cho On Mon, Jan 25, 2021 at 7:31 AM Chief Return Officer (CRO

[GRASS-dev] Statement Huidae Cho

example, I hope to support and mentor GSoC developers. I am very excited about the future of GRASS. Best Regards, Huidae -- Huidae Cho, Ph.D., GISP, /hidɛ t͡ɕo/, 조희대, 曺喜大 GRASS GIS Developer https://idea.isnew.info ___ grass-dev mailing list grass-d

Re: [GRASS-dev] Bugs in r.stream.extract

>>> > r.stream.extract. Why the stream from r.stream.extract did not follow >>> > flow accumulation results? And how to fix this problem? >>> >>> Is there any chance you can share the raster that includes this region >>> so I can examin

Re: [GRASS-dev] Error in GRASS GUI startup

Great! Just to make sure. That was the official daily build, right? Thanks for testing. -- Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE Open Source GIS Developer, GRASS GIS Development Team https://idea.isnew.info Sent from my phone On Fri, Dec 27, 2019, 6:05 PM Bergquist, Kiersten L

Re: [GRASS-dev] Error in GRASS GUI startup

rom:* Maris Nartiss > *Sent:* Sunday, December 22, 2019 4:41 AM > *To:* Huidae Cho > *Cc:* Bergquist, Kiersten L ; GRASS > developers list > *Subject:* Re: [GRASS-dev] Error in GRASS GUI startup > > [EXTERNAL EMAIL ALERT]: Verify sender before opening links or attachments. >

Re: [GRASS-dev] Error in GRASS GUI startup

f, there > is no such thing as over-explaining it to me! Thank you very much in > advance. > > > > -- > Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html > ___________ > grass-dev mailing list > grass-dev@l

Re: [GRASS-dev] Try GRASS GIS online: rollApp - rollapp.com

Ah! /tmp works. Thanks! On Fri, Dec 20, 2019 at 9:35 PM Vaclav Petras wrote: > > > On Fri, Dec 20, 2019, 3:42 PM Huidae Cho wrote: > >> Vaclav, >> >> rollApp looks good, but it's read-only without a plan. I can start the >> GUI, but I cannot create a new lo

Re: [GRASS-dev] Try GRASS GIS online: rollApp - rollapp.com

s as a secondary one in > case we want to favor an open source platform). In any case, I would like > to find a place on the new website to have rollApp listed as one option for > using GRASS GIS online. > > Let me know what you think, > Vaclav > _

Re: [GRASS-dev] any special reason why choice of raster compression method is done via environmental variable ?

anging the env variable, run r.compress, then change > the variable back to the value one wishes generally to use as default. > > Obviously, you can always just export as tiff and share that, but that > just feels less elegant. Anyway, this is probably somewhat of a luxury &g

Re: [GRASS-dev] load_env() issues in startup

OK.. Tried to work around this limitation by adding spaces and $HOME is now expanded into the location directory. Hmm... I kind of see why we're doing this. Maybe, better to fix load_env()? Huidae On Tue, Oct 29, 2019 at 8:59 PM Huidae Cho wrote: > Hi, > > Currently, .gras

[GRASS-dev] load_env() issues in startup

les instead of just writing out all these lines into .bashrc in the mapset and letting bash handling everything? Is it by design or a bug? Regards, Huidae -- Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE Open Source GIS Developer, GRASS GIS Development Team __

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

Are you sure you did git add? -a just adds "all changes". I remember add & -m only worked for me on Windows (msys2 git). Regards, Huidae -- Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE Open Source GIS Developer, GRASS GIS Development Team https://idea.isnew.info Sent from my phon

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

the notifications: >> https://help.github.com/en/articles/watching-and-unwatching-repositories >> > > > Then please all promise to subscribe to the repo notifications and look at > them :) > > Thanks > Markus > > PS: with "lost" I meant that nobody car

[GRASS-dev] Merging PRs

yes, my name) 2. master => feature1 3. master => feature2 4. merge feature1 and feature2 into "hcho" 5. compile "hcho" To be honest, it's a lot of work :-(. Any suggestions or hints would be very welcome. Best Regards, Huidae -- Huidae Cho, Ph.D., GISP, PE

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

Markus, I don't think that list has PR notifications. That's only for actual merges, not everything, if I'm not wrong. Best, Huidae On Fri, Jul 12, 2019 at 9:58 AM Markus Neteler wrote: > Hi, > > On Fri, Jul 12, 2019 at 6:12 AM Huidae Cho wrote: > > > > Markus, &

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

at 11:39 PM Huidae Cho wrote: > And, maybe, this question is related. I don't receive any notifications > for my own PRs. PRs from other devs are OK. Is that normal? > > Thanks, > Huidae > > > On Thu, Jul 11, 2019 at 6:43 PM Markus Neteler wrote: > >> Hi, >> &g

Re: [GRASS-dev] GitHub: how to fwd pull requests to this list?

this list? > > They tend to get lost: > https://github.com/OSGeo/grass/pulls > https://github.com/OSGeo/grass-addons/pulls > > thanks > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/ma

Re: [GRASS-dev] wingrass builds status (git recover)

g 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

Re: [GRASS-dev] wingrass builds status (git recover)

Hello, I experienced the exact same issue on Windows. One of my PRs should fix it. Regards, Huidae -- Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE Open Source GIS Developer, GRASS GIS Development Team https://idea.isnew.info Sent from my phone On Sun, Jul 7, 2019, 3:53 PM Helmut Kudrnovsky

Re: [GRASS-dev] Switching addon manual pages to point to grass76 ?

> > ping again ... > > I can easily switch it on the server but I am not sure if that would be > enough? > > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listin

Re: [GRASS-dev] [GRASS-SVN] r73995 - grass/trunk/scripts/v.db.addtable

r74043 works. Thanks, Huidae On Wed, Jan 30, 2019 at 4:20 AM Markus Metz wrote: > > > On Wed, Jan 30, 2019 at 9:42 AM Markus Metz > wrote: > > > > > > > > On Tue, Jan 29, 2019 at 11:37 PM Huidae Cho wrote: > > > > > > Just for our re

Re: [GRASS-dev] [GRASS-SVN] r73995 - grass/trunk/scripts/v.db.addtable

, Jan 29, 2019 at 5:16 PM Huidae Cho wrote: > I just did a quick search and found that these modules (i.segment.stats, > r.mwprecip, v.in.geopaparazzi, v.link.precip, v.out.gps, v.ply.rectify, > v.unpack) create/copy new tables themselves without the index and invoke > v.db.connect. For no

Re: [GRASS-dev] [GRASS-SVN] r73995 - grass/trunk/scripts/v.db.addtable

On Tue, Jan 29, 2019 at 4:12 PM Huidae Cho wrote: > Yes. Like you said, v.db.connect followed by v.db.connect -d gives me the > same pg errors and grass warning. I agree with you that the preferred > solution would be to create the index in v.db.addtable, not in v.db.connect > "if

Re: [GRASS-dev] [GRASS-SVN] r73995 - grass/trunk/scripts/v.db.addtable

x. Huidae On Tue, Jan 29, 2019 at 3:51 PM Markus Metz wrote: > > > On Tue, Jan 29, 2019 at 4:12 PM Huidae Cho wrote: > > > > You're right. It was a warning with PostgresSQL error messages (attached > below), not a fatal error. But I don't think there should be any warnin

Re: [GRASS-dev] [GRASS-SVN] r73995 - grass/trunk/scripts/v.db.addtable

here WARNING: Values in column will be overwritten Reading features... 100% Updating database... 100% Huidae On Tue, Jan 29, 2019 at 9:37 AM Markus Metz wrote: > > > On Sun, Jan 27, 2019 at 11:21 AM Markus Metz < > markus.metz.gisw...@gmail.com> wrote: > > > >

Re: [GRASS-dev] [GRASS-SVN] r73995 - grass/trunk/scripts/v.db.addtable

Or maybe, to be more flexible... 1. v.db.addtable doesn't create unique index 2. v.db.connect creates unique index "only if" there is no unique index Just my 2 cents On Sat, Jan 26, 2019 at 8:50 AM Huidae Cho wrote: > Markus, > > If there is a linked table, v.db.addtabl

Re: [GRASS-dev] [GRASS-SVN] r73995 - grass/trunk/scripts/v.db.addtable

rass.warning(_("Unable to create index on table <%s>") > % table) > > -pass > > - > > # connect the map to the DB: > > if schema: > > table = '{schema}.{table}'.format(schema=schema, table=table) > > just a concept

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

> 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:/

Re: [GRASS-dev] v.delaunay3d error

I tried static_cast, but it didn't work (not sure why). C-style casting and reinterpret_cast worked though. Huidae On Tue, Dec 25, 2018 at 5:16 PM Markus Neteler wrote: > On Thu, Dec 20, 2018 at 6:39 PM Huidae Cho wrote: > > Hello Martin, > > > > I'm getting this erro

[GRASS-dev] v.delaunay3d error

(points.begin(), points.end()); Maybe, simple type casting, but I'm not a C++ expert. Any idea? Regards, Huidae -- Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE Open Source GIS Developer, GRASS GIS Development Team ___ grass-dev mailing list grass-dev

Re: [GRASS-dev] Exclusive rule between '--o' and another custom flag

-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

Re: [GRASS-dev] [GRASS-SVN] r73769 - grass/trunk/locale/po

Sure, no problem. It was just faster to do Korean only for testing. Huidae On Sat, Dec 8, 2018 at 7:10 AM Markus Neteler wrote: > On Fri, Dec 7, 2018 at 5:14 PM Huidae Cho wrote: > > > > Yes, I did use the transifex_merge script (changed -a to -l ko). > > Feel free to jus

Re: [GRASS-dev] [GRASS-SVN] r73769 - grass/trunk/locale/po

ate this using the transifex_merge script? > > Otherwise the work may get lost until we have "tx push" working. > > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/list

Re: [GRASS-dev] PO file error?

me. > > Note: since r73517 has not been backported so far I also didn't touch > relbranch76. > > Markus > -- Huidae Cho, Ph.D., GISP, PE (MD), CFM, M.ASCE Open Source GIS Developer, GRASS GIS Development Team ___ grass-dev mailing li

[GRASS-dev] PO file error?

uot;), backrow_layer, backcol_layer); #: ../raster/r.spreadpath/main.c:161 #, fuzzy, c-format msgid "eading the input map -%s- and -%s- and creating some temporary files..." I have no idea what happened? A bug in any of our scripts? Best, Huidae -- Huidae Cho, Ph.D., GISP, PE (MD

Re: [GRASS-dev] [GRASS-SVN] r73627 - grass/trunk/raster/r.stream.extract

Thanks Markus! Regarding merging messages from transifex, do we have a designated developer who does that or can anyone merge and check in translations to svn? Best, Huidae -- Huidae Cho, Ph.D., P.E., M.ASCE, CFM, GISP Open Source GIS Developer, GRASS GIS Development Team https

Re: [GRASS-dev] [GRASS-SVN] r73627 - grass/trunk/raster/r.stream.extract

he .po files need that update add I have done last time as > well. > Then no translation will be broken. > > Markus > > Huidae Cho schrieb am Mi., 31. Okt. 2018, 15:06: > >> Hmm... I never thought about backporting these changes... So just G76 >> should be fine

Re: [GRASS-dev] [GRASS-SVN] r73627 - grass/trunk/raster/r.stream.extract

t; grass-commit mailing list > > > > grass-com...@lists.osgeo.org > > > > https://lists.osgeo.org/mailman/listinfo/grass-commit > > > > > > > > > > > > -- > > > Martin Landa > > > http://geo.fsv.cvut.cz/gwiki/Landa > >

Re: [GRASS-dev] Mixing vector and Raster input maps for a module

I much appreciate your thoughts. > > Nikos > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP Open Source GIS Developer, GRASS GIS Development Team __

Re: [GRASS-dev] [GRASS GIS] #3600: m.nviz.image doesn't produce any output

Test run for the NC sample dataset. g.region rast=elevation m.nviz.image elevmap=elevation output=elev format=tif persp=10 --o On Sun, Jul 22, 2018 at 1:43 AM, Huidae Cho wrote: > For anyone who wants to try this patch on macOS. > > -- Forwarded message -- > From

[GRASS-dev] Fwd: [GRASS GIS] #3600: m.nviz.image doesn't produce any output

For anyone who wants to try this patch on macOS. -- Forwarded message -- From: Huidae Cho Date: Sun, Jul 22, 2018 at 1:41 AM Subject: Re: [GRASS-dev] [GRASS GIS] #3600: m.nviz.image doesn't produce any output To: Michael Barton Michael, Please try this patch. cd grass_trunk

Re: [GRASS-dev] [GRASS GIS] #3600: m.nviz.image doesn't produce any output

Maybe, we can try the same thing I did for Windows. Create and hide a real window and draw to it? -- Huidae Cho, Ph.D., P.E. (MD), M.ASCE, CFM, GISP Sent from my phone On Fri, Jul 20, 2018, 1:15 PM Huidae Cho wrote: > Michael, one thing weird is with no changes to the Mac code, it wor

Re: [GRASS-dev] [GRASS GIS] #3600: m.nviz.image doesn't produce any output

Michael, one thing weird is with no changes to the Mac code, it worked on my 10.12 Sierra VM yesterday. Maybe, VM vs. real hardware? Regards, Huidae -- Huidae Cho, Ph.D., P.E. (MD), M.ASCE, CFM, GISP Sent from my phone On Fri, Jul 20, 2018, 1:07 PM Michael Barton wrote: > Unfortunat

Re: [GRASS-dev] [GRASS GIS] #3600: m.nviz.image doesn't produce any output

set/72986 > https://trac.osgeo.org/grass/changeset/72987 > https://trac.osgeo.org/grass/changeset/72990 > https://trac.osgeo.org/grass/changeset/72997 > > > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.

Re: [GRASS-dev] [GRASS-SVN] r72948 - grass/trunk/misc/m.nviz.image

t; return GS_write_ppm(name); > > the return code of GS_write_ppm is 1 when it fails, so there shouldn't be > the negation? > > Anna > > >> ___ >> grass-commit mailing list >> grass-com...@lists.osgeo.org >> https://lists.osgeo.org/mailman/listinfo/grass-commit > > > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP Senior Geospatial Engineer, MapAnything 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] New addon r.accumulate calculates weighted flow accumulation using a flow direction map

this module many years ago for GRASS 6, but I almost forgot about it until I read this question: https://gis.stackexchange.com/questions/280813/compute-flow-accumulation-only-from-flow-direction Thanks. Huidae -- Huidae Cho, Ph.D., PE, M.ASCE, CFM, GISP Senior Geospatial Engineer, MapAnything Open

Re: [GRASS-dev] a proposal to rename "location"

aphic or projected coordinates. How can I > reflect this difference between "files" that actually depict exactly the > same area? My answer to this has been always the spatial reference > system. > > I.e. a "Europe/" GRASS GIS data base with the following l

Re: [GRASS-dev] New dev team on github for initial tests

a/ > [1] https://git.osgeo.org/gitea/osgeo/todo/issues > [2] https://git.osgeo.org/gitea/lucadelu/gci_analyst > > -- > ciao > Luca > > www.lucadelu.org > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > htt

Re: [GRASS-dev] New dev team on github for initial tests

we are relatively flexible in choosing the platform. > > Just my 0.02 cents, > Markus > ___ > grass-dev mailing list > grass-dev@lists.osgeo.org > https://lists.osgeo.org/mailman/listinfo/grass-dev > -- Huidae Cho, Ph.D., PE,

Re: [GRASS-dev] New dev team on github for initial tests

Great! Thanks, Markus! -- Huidae Cho, Ph.D., P.E., M.ASCE, CFM, GISP Sent from my phone On Thu, Apr 12, 2018, 4:51 PM Markus Neteler <nete...@osgeo.org> wrote: > Huidae, > > On Wed, Mar 28, 2018 at 2:57 PM, Huidae Cho <gras...@gmail.com> wrote: > > Markus, &g

Re: [GRASS-dev] New dev team on github for initial tests

Markus, You can add me: https://github.com/HuidaeCho Thanks. Huidae On Mon, Mar 19, 2018 at 10:48 AM, Markus Neteler wrote: > On Mon, Mar 19, 2018 at 11:01 AM, Pietro wrote: > > On Sat, Mar 17, 2018 at 6:27 PM, Markus Neteler >

Re: [GRASS-dev] lib/python/ctypes compilation errors

Status: Processing description list. Warning: Member "def" of Struct "Option" has been renamed to "_def" because it has the same name as a Python keyword. Status: Writing to OBJ.x86_64-pc-linux-gnu/vector.py. Status: Wrapping complete. Thanks. Huidae On Sun, J

[GRASS-dev] lib/python/ctypes compilation errors

Hello, I'm trying to compile the trunk on a new machine and getting these errors when compiling lib/python/ctypes. I searched this mailing list and found that /usr/include/GL/gl.h.. Syntax error at '\n' is normal (?), but what about the others? Regardless of these errors, make reports No errors

Re: [GRASS-dev] [GRASS-SVN] r70710 - in grass/branches/releasebranch_7_2: lib/vector/vedit raster/r.timestamp raster/r.to.vect raster/r.topidx raster/r.topmodel scripts/v.db.addtable vector/v.build.po

8:16 AM, Huidae Cho <gras...@gmail.com> wrote: > Ah! Sorry for the huge comment and I forgot to copy log messages. > Backporting is always difficult for me ;) > > On Wed, Mar 1, 2017 at 7:51 AM, Martin Landa <landa.mar...@gmail.com> > wrote: > >> 2017-03

Re: [GRASS-dev] [GRASS-SVN] r70710 - in grass/branches/releasebranch_7_2: lib/vector/vedit raster/r.timestamp raster/r.to.vect raster/r.topidx raster/r.topmodel scripts/v.db.addtable vector/v.build.po

Ah! Sorry for the huge comment and I forgot to copy log messages. Backporting is always difficult for me ;) On Wed, Mar 1, 2017 at 7:51 AM, Martin Landa wrote: > 2017-03-01 13:31 GMT+01:00 Martin Landa : > > please *explain* your changes in log

Re: [GRASS-dev] [GRASS-SVN] r70632 - grass/trunk/scripts/v.report

sure. usually, I don't backport, but I'll check the wiki. Thanks. On Mon, Feb 20, 2017 at 3:11 AM, Martin Landa <landa.mar...@gmail.com> wrote: > Hi, > > 2017-02-20 8:58 GMT+01:00 Huidae Cho <gras...@gmail.com>: > > no problem, I'll backport it. > > ok, than

Re: [GRASS-dev] [GRASS-SVN] r70632 - grass/trunk/scripts/v.report

no problem, I'll backport it. Thanks. On Mon, Feb 20, 2017 at 2:39 AM, Martin Landa wrote: > Hi, > > are you planning to backport bugfixes to relb72? Thanks, Ma > > 2017-02-20 1:15 GMT+01:00 : > > Author: hcho > > Date: 2017-02-19 16:15:14 -0800

Re: [GRASS-dev] [GRASS-SVN] r68061 - grass/trunk/lib/gis

Hi Martin, This fix only affects the history, not its behavior. "v.info -h n" gives you: COMMAND: v.edit map="n" layer="1" type="point,line,boundary,centroid" tool="delete" threshold=-1,0,0 where="" snap="no" Without this fix, you'll see: COMMAND: v.edit map="n" layer="1"

Re: [GRASS-dev] Fwd: Re: [GRASS-SVN] r68240 - grass/trunk/scripts/v.report

I don't think we have a consensus yet... -- Sent from my phone On Apr 12, 2016 11:01 AM, "Markus Neteler" <nete...@osgeo.org> wrote: > On Mon, Apr 11, 2016 at 3:57 PM, Huidae Cho <gras...@gmail.com> wrote: > ... > > 11 scripts use \r\n and 5 use os.linesep. g

Re: [GRASS-dev] usage of os.linesep (was: Re: [GRASS-SVN] r68240 - grass/trunk/scripts/v.report_

. Or simply just use \r\n for reading and os.linesep for writing? -- Sent from my phone On Apr 11, 2016 10:58 AM, "Martin Landa" <landa.mar...@gmail.com> wrote: > Hi Huidae, > > {I took liberty to move discussion to ML} > > 2016-04-11 15:54 GMT+02:00 Huidae Cho <gras.

[GRASS-dev] Fwd: Re: [GRASS-SVN] r68240 - grass/trunk/scripts/v.report

Forgot to reply all... -- Sent from my phone -- Forwarded message -- From: "Huidae Cho" <gras...@gmail.com> Date: Apr 11, 2016 9:54 AM Subject: Re: [GRASS-dev] [GRASS-SVN] r68240 - grass/trunk/scripts/v.report To: "Martin Landa" <landa.mar...@gmail.co

Re: [GRASS-dev] [GRASS-SVN] r68127 - grass/trunk/lib/gis

<wenzesl...@gmail.com> wrote: > > On Wed, Mar 23, 2016 at 11:29 PM, Huidae Cho <gras...@gmail.com> wrote: > >> Vaclav, that script completely removes tabs and I didn't want to >> introduce a big revision for no reason other than changing those two >> options t

Re: [GRASS-dev] [GRASS-SVN] r68127 - grass/trunk/lib/gis

Vaclav, that script completely removes tabs and I didn't want to introduce a big revision for no reason other than changing those two options to match the rest of the file. On Wed, Mar 23, 2016 at 10:59 PM, Vaclav Petras wrote: > > On Wed, Mar 23, 2016 at 5:29 PM,

Re: [GRASS-dev] [GRASS-SVN] r66772 - in grass/trunk: db/drivers db/drivers/dbf db/drivers/mysql db/drivers/odbc db/drivers/ogr db/drivers/postgres db/drivers/sqlite lib/db/dbmi_driver lib/db/stubs

I can also confirm this. I had to copy dbstubs.h to dist.../include/grass, but I'm not sure what brought those changes in the above revision. If we have to keep this revision, adding dbstubs.h in include/ should address this issue... On Wed, Nov 11, 2015 at 11:54 AM, Vaclav Petras

Re: [GRASS-dev] Return value from g.copy is one when --overwrite - bug or feature?

r66775 adds a warning for non-vector elements as well. On Mon, Nov 9, 2015 at 6:20 AM, Glynn Clements wrote: > > Markus Neteler wrote: > > > It should probably not silently fail. > > > > The code in question is in > > lib/manage/do_copy.c > > M_do_copy() returns a

Re: [GRASS-dev] Return value from g.copy is one when --overwrite - bug or feature?

Rainer, I cannot seem to replicate your issue: G srorg6630/tmp ~> g.version GRASS 7.1.svn (2015) G srorg6630/tmp ~> g.list region tmp tmp.d.rast.edit.6753 tmp1 G srorg6630/tmp ~> g.copy region=tmp,tmp1 --overwrite Copy region definition to current mapset as G srorg6630/tmp ~> echo

Re: [GRASS-dev] [GRASS-SVN] r65981 - grass-addons/grass7/raster/r.wateroutlet.lessmem

Markus, Yes, it does work. I had to do the following: svn propset svn:keywords Date r.wateroutlet.lessmem.html Thanks. Huidae On Mon, Aug 24, 2015 at 6:22 PM, Markus Neteler nete...@osgeo.org wrote: Just FYI On Fri, Aug 21, 2015 at 9:04 AM, svn_gr...@osgeo.org wrote: Author: hcho

Re: [GRASS-dev] [GRASS-SVN] r65307 - grass/trunk/lib/init

Landa landa.mar...@gmail.com wrote: Hi, 2015-07-08 18:31 GMT+02:00 Huidae Cho gras...@gmail.com: I think the following change has to be reverted because it breaks aliases and custom prompts defined in ~/.grass7/bashrc. Currently, only NAME=VALUE lines are parsed from this file

Re: [GRASS-dev] [GRASS-SVN] r65307 - grass/trunk/lib/init

Martin, I think the following change has to be reverted because it breaks aliases and custom prompts defined in ~/.grass7/bashrc. Currently, only NAME=VALUE lines are parsed from this file in load_env(). Regards, Huidae On Thu, May 21, 2015 at 5:45 PM, svn_gr...@osgeo.org wrote: Author:

Re: [GRASS-dev] inconsistency between G_OPT_V_INPUT and G_OPT_R_INPUT

description to label as the primary one or making both mandatory. See also *Standard options label vs description* from Huidae Cho: http://lists.osgeo.org/pipermail/grass-dev/2014-June/069313.html http://osgeo-org.1560.x6.nabble.com/Standard-options-label-vs-description-td5144023.html Vaclav

Re: [GRASS-dev] [GRASS-SVN] r65249 - grass/trunk/raster/r.topidx

Hi, Thanks for pointing me to the script. I just manually adjusted several lines to make them 80 columns. Based on the script, it looks like couple options were dropped (-ts8, -ut) and new ones were added (-npro, --no-tabs). On Fri, May 15, 2015 at 1:22 PM, Vaclav Petras wenzesl...@gmail.com

Re: [GRASS-dev] module header definitions add: text/multiline and latex support?

On Thu, Jan 15, 2015 at 2:46 AM, Glynn Clements gl...@gclements.plus.com wrote: Requiring raster OR vector is possible already. #%rules #% requires: raster, vector #%end This should be required (at least one of the options must be given). If you want exactly one option to be given,

Re: [GRASS-dev] module header definitions add: text/multiline and latex support?

On Wed, Jan 14, 2015 at 3:42 AM, Pietro peter.z...@gmail.com wrote: Dear devs, sometimes I would like to add some multiline text on the module GUI to help to understand the meaning of the parameter, and/or understand the logic of the module. Do you think that would be possible to have a

Re: [GRASS-dev] group does not update REF file upon g.remove raster file

Yann, Please be more specific. What is the group REF file and how can I replicate your issue? And what do you expect to happen? Regards, Huidae -- Sent from my phone On Dec 15, 2014 3:49 AM, Yann Chemin yche...@gmail.com wrote: Hi, did g.remove a raster, and the group REF file referencing

Re: [GRASS-dev] Custom GRASS command line prompt

Mine looks like this (bash shell): grass_ps(){ echo G `g.gisenv LOCATION_NAME`/`g.gisenv MAPSET` } export PS1=\[\033]0;\$(grass_ps) \w\007\]\$(grass_ps) \w The prompt gets updated dynamically since grass_ps() is called every time you hit enter. Huidae On Mon, Dec 15, 2014 at 6:15 AM,

  1   2   3   >