| 00:23:18 | CIA-54: | martinl * r37818 /grass/trunk/ ( 5 files in 2 dirs ): minor doxygen updates ( libgis ) |
| 00:24:37 | sigq: | grassfeed: Changeset [37818]: minor doxygen updates ( libgis ) <https://trac.osgeo.org/grass/changeset/37818> |
| 01:02:20 | sigq: | grassfeed: Ticket #638 ( defect created ): Tk interface does not handle mouse wheel events in v.digit <https://trac.osgeo.org/grass/ticket/638> |
| 02:01:10 | aghisla: | hi all, I have trouble in filtering maps by feature type using python bindings, http://osgeo.pastebin.com/m6a686ad8 |
| 02:01:12 | sigq: | Title: osgeo private pastebin - collaborative debugging tool ( at osgeo.pastebin.com ) |
| 02:04:26 | aghisla: | I get the full list using grass.list_grouped( 'vect' )[gisenv['MAPSET']], but when I loop on it to check for point features, the loop ignores some maps |
| 02:53:22 | sigq: | grassfeed: Ticket #478 ( defect closed ): MSYS Console fails to start when installed in Windows at a path with spaces. <https://trac.osgeo.org/grass/ticket/478#comment:2> |
| 02:58:33 | aghisla: | got it.. silly me!! |
| 03:02:02 | aghisla: | in the for loop I remove the nth map if it is not suitable, but the loop continues on the _old_ n+1th element, that is the n+2th in the list without the unsuitable map... |
| 03:27:23 | sigq: | grassfeed: CompileOnWindows edited by hamish <https://trac.osgeo.org/grass/wiki/CompileOnWindows> |
| 04:15:01 | kk: | hi all |
| 04:15:29 | kk: | i have created a tool v.db.appendxls in grass |
| 04:15:31 | kk: | using c |
| 04:15:41 | kk: | now i want use same through web |
| 04:15:55 | kk: | so is there any method to put grass on web |
| 05:03:28 | CIA-54: | martinl * r37819 /grass/trunk/lib/gis/ ( gisrasterlib.dox quant.c quant_rw.c ): libgis: doxygen updates ( quant fns ) |
| 05:04:17 | sigq: | grassfeed: Changeset [37819]: libgis: doxygen updates ( quant fns ) <https://trac.osgeo.org/grass/changeset/37819> |
| 05:47:36 | sigq: | grassfeed: Ticket #639 ( defect created ): Wingrass native r.in.aster doesn't work <https://trac.osgeo.org/grass/ticket/639> |
| 05:55:09 | CIA-54: | glynn * r37820 /grass/trunk/scripts/v.colors/v.colors.py: Use temporary file to avoid deadlock |
| 05:56:24 | sigq: | grassfeed: Changeset [37820]: Use temporary file to avoid deadlock <https://trac.osgeo.org/grass/changeset/37820> |
| 06:23:00 | CIA-54: | glynn * r37821 /grass/trunk/lib/gis/parser.c: Add match_option( ) ( not yet used ) |
| 06:23:36 | sigq: | grassfeed: Changeset [37821]: Add match_option( ) ( not yet used ) <https://trac.osgeo.org/grass/changeset/37821> |
| 06:25:48 | CIA-54: | aghisla * r37822 /grass-addons/vector/v.autokrige2/v.autokrige2.py: |
| 06:25:49 | CIA-54: | added autofit variogram functionality on specific dataset - |
| 06:25:49 | CIA-54: | proof-of-concept. Works! |
| 07:33:18 | CIA-54: | martinl * r37823 /grass/trunk/lib/gis/gisrasterlib.dox: libgis: doxygen update ( gisrasterlib ) |
| 07:35:44 | sigq: | grassfeed: Changeset [37823]: libgis: doxygen update ( gisrasterlib ) <https://trac.osgeo.org/grass/changeset/37823> |
| 07:37:49 | CIA-54: | glynn * r37824 /grass/trunk/lib/gis/parser.c: Improved match_option( ) |
| 07:37:52 | sigq: | grassfeed: Changeset [37824]: Improved match_option( ) <https://trac.osgeo.org/grass/changeset/37824> |
| 07:52:34 | CIA-54: | glynn * r37825 /grass/trunk/lib/gis/parser.c: Use match_option( ) |
| 07:52:39 | sigq: | grassfeed: Changeset [37825]: Use match_option( ) <https://trac.osgeo.org/grass/changeset/37825> |
| 08:15:18 | CIA-54: | martinl * r37826 /grass/trunk/gui/wxpython/ ( 6 files in 3 dirs ): wxGUI: use ElementTree for parsing workspace files |
| 08:15:18 | sigq: | grassfeed: Changeset [37826]: wxGUI: use ElementTree? for parsing workspace files <https://trac.osgeo.org/grass/changeset/37826> |
| 09:35:19 | epifanio: | hi |
| 09:36:07 | epifanio: | do you know if from the grass.py modules it is possible to know the files loaded in the mapdisplay gui ? |
| 09:36:50 | epifanio: | or if the mapdisply saves the layer configuration in something like a file or temp file .. accesible from other python programs ? |
| 09:37:48 | CIA-54: | kyngchaos * r37827 /grass/branches/develbranch_6/macosx/ReadMe.rtf: update ffmpeg build; other 64bit updates |
| 09:38:09 | epifanio: | maybe it is possible to run something like "save workspace" .. and parse it ? |
| 09:38:11 | sigq: | grassfeed: Changeset [37827]: update ffmpeg build; other 64bit updates <https://trac.osgeo.org/grass/changeset/37827> |
| 09:38:42 | CIA-54: | kyngchaos * r37828 /grass/branches/releasebranch_6_4/macosx/ReadMe.rtf: update ffmpeg build; other 64bit updates ( from dev6 r37827 ) |
| 09:39:13 | sigq: | grassfeed: Changeset [37828]: update ffmpeg build; other 64bit updates ( from dev6 r37827 ) <https://trac.osgeo.org/grass/changeset/37828> |
| 09:41:59 | CIA-54: | kyngchaos * r37829 /grass/trunk/macosx/ReadMe.rtf: update ffmpeg build; other 64bit updates ( from dev6 r37827 ) |
| 09:43:28 | sigq: | grassfeed: Changeset [37829]: update ffmpeg build; other 64bit updates ( from dev6 r37827 ) <https://trac.osgeo.org/grass/changeset/37829> |
| 09:59:34 | sigq: | grassfeed: Grass7Planning edited by martinl <https://trac.osgeo.org/grass/wiki/Grass7Planning> |
| 11:56:23 | CIA-54: | martinl * r37830 /grass/branches/releasebranch_6_4/gui/wxpython/gui_modules/ ( nviz_mapdisp.py nviz_tools.py workspace.py ): wxGUI: fix loading workspace ( nviz ) |
| 11:56:58 | sigq: | grassfeed: Changeset [37830]: wxGUI: fix loading workspace ( nviz ) <https://trac.osgeo.org/grass/changeset/37830> |
| 12:10:42 | CIA-54: | martinl * r37831 /grass/trunk/gui/wxpython/gui_modules/ ( nviz_mapdisp.py nviz_tools.py workspace.py ): |
| 12:10:42 | CIA-54: | wxGUI: fix loading workspace ( nviz ) |
| 12:10:42 | CIA-54: | ( merge from relbr64, r37830 ) |
| 12:10:43 | sigq: | grassfeed: Changeset [37831]: wxGUI: fix loading workspace ( nviz ) ( merge from relbr64, r37830 ) <https://trac.osgeo.org/grass/changeset/37831> |
| 12:14:19 | CIA-54: | martinl * r37832 /grass/branches/develbranch_6/gui/wxpython/ ( 8 files in 3 dirs ): |
| 12:14:19 | CIA-54: | wxGUI: use ElementTree for parsing workspace files |
| 12:14:19 | CIA-54: | ( merge from trunk, r37826 & r37831 ) |
| 12:36:21 | sigq: | grassfeed: Ticket #640 ( defect created ): setup.py may use different Python than configured for GRASS <https://trac.osgeo.org/grass/ticket/640> |
| 12:58:37 | CIA-54: | kyngchaos * r37833 /grass/branches/develbranch_6/macosx/app/grass.sh.in: attempt to use same version of Python that wxPython was built for, when bundling wxPython |
| 13:01:30 | CIA-54: | kyngchaos * r37834 /grass/branches/releasebranch_6_4/macosx/app/grass.sh.in: attempt to use same version of Python that wxPython was built for, when bundling wxPython ( from dev6 r37833 ) |
| 13:02:35 | CIA-54: | kyngchaos * r37835 /grass/trunk/macosx/app/grass.sh.in: attempt to use same version of Python that wxPython was built for, when bundling wxPython ( from dev6 r37833 ) |
| 18:52:45 | sigq: | grassfeed: Grass7Planning edited by hamish <https://trac.osgeo.org/grass/wiki/Grass7Planning> || Grass7Planning edited by hamish <https://trac.osgeo.org/grass/wiki/Grass7Planning> |
| 20:34:32 | : | <_rash> i like to do grass development |
| 20:34:57 | : | <_rash> i had done a project using grass gis |
| 20:35:11 | : | <_rash> can anybody help me |
| 20:35:30 | : | <_rash> i don't know where to start development |
| 20:35:57 | : | <_rash> is there anybody to discuss?? |
| 20:50:05 | jachym: | _rash: what is your problem? |
| 20:55:54 | : | <_rash> i had seen grass gui wiki |
| 20:56:06 | : | <_rash> and seen about Data Catalog |
| 20:56:20 | : | <_rash> i had used Arc Catalog in ArcGIS |
| 20:56:30 | : | <_rash> but nothing is there for GRASS GIS |
| 20:56:51 | jachym: | _rash: I have never seen arc gis catalogue, what does it do? |
| 20:57:09 | : | <_rash> It provides like a file explorer |
| 20:57:32 | : | <_rash> which list files of grass such as raster, vector etc.. in groups |
| 20:57:39 | : | <_rash> like a tree structure |
| 20:58:07 | : | <_rash> so users can easily expand trees and select files |
| 20:58:36 | : | <_rash> the root node comes the project under it comes raster, vector and other groups |
| 20:59:11 | : | <_rash> so we can also copy , delete, rename ,add files within gui |
| 20:59:13 | : | <_rash> easily |
| 21:01:31 | : | <_rash> okay |
| 21:02:30 | : | <_rash> currently in GRASS we do copy, rename delete operations using commands |
| 21:02:36 | : | <_rash> no provision in gui |
| 21:03:09 | : | <_rash> i am thinking about developing a module to do operations easily in GUI |
| 21:10:39 | cgs_bob: | _rash: you might like to see how qgis handles grass data with its grass plugin. |
| 21:11:06 | jachym: | _rash: see this video http://gisalaska.com/qgis_movies/qgis_grass_2.html, about 5min55sec |
| 21:11:41 | jachym: | would be nice to have tool like this in grass |
| 21:12:23 | jachym: | go ahead |
| 21:12:30 | : | <_rash> ok |
| 21:12:44 | : | <_rash> can i start my programming in wxpython |
| 21:12:54 | jachym: | _rash: yes, you can |
| 21:13:03 | : | <_rash> where should i submit the code |
| 21:13:45 | jachym: | _rash: since, I assume, you never submitted code before, just prepare some working demo and post link to it do grass-dev mailing list |
| 21:13:56 | jachym: | if you prepare some html page with screenshots, it never harms |
| 21:14:04 | : | <_rash> ok |
| 21:14:16 | jachym: | if people will like it - and I'm sure, they will, you will get access to grass-addons repository first |
| 21:14:38 | jachym: | when people will like it even more, you will get write access to main SVN repository as well |
| 21:14:51 | : | <_rash> so i want to put screen shot in mailing list first. |
| 21:14:57 | jachym: | and so you project will became part of GRASS source |
| 21:15:03 | jachym: | _rash: no |
| 21:15:31 | jachym: | you need to have working code at the first place |
| 21:15:37 | : | <_rash> ok |
| 21:15:59 | : | <_rash> yes, i mean the screen shots of working code |
| 21:16:09 | : | <_rash> to put in mailinglist |
| 21:16:22 | jachym: | yes, what would be a good start |
| 21:17:37 | : | <_rash> so i am starting.. |
| 21:18:01 | jachym: | it should be easy to write module like this, you just have to use standard grass modules ( g.list, g.rename, g.remove, r.info, ... ) |
| 21:18:46 | : | <_rash> yes |
| 21:21:14 | : | <_wolf_> _rash: what are you working on? |
| 21:22:04 | jachym: | openlayers :- ) |
| 21:22:07 | jachym: | sorry |
| 21:22:17 | : | <_rash> no |
| 21:22:18 | jachym: | wrong window |