#2632: option in context menu to export vector attribute table
--------------------------+-------------------------
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.3
Component: Vector | Version: unspecified
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mlennert):
I added a second patch that puts the (IMHO) main options of v.db.select
(map, column separator, output file) into a "Main choices" tab. I think
this should be enough to make exporting attributes easier, without having
to code a separate simplified GUI. Not sure if "Main choices" is the best
choice of names for that tab, though. Any better ideas are more than
welcome.
On Tue, Dec 22, 2015 at 3:47 PM, GRASS GIS <trac@osgeo.org> wrote:
#2632: option in context menu to export vector attribute table
--------------------------+-------------------------
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.3
Component: Vector | Version: unspecified
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mlennert):
I added a second patch that puts the (IMHO) main options of v.db.select
(map, column separator, output file) into a "Main choices" tab. I think
this should be enough to make exporting attributes easier, without having
to code a separate simplified GUI. Not sure if "Main choices" is the best
choice of names for that tab, though. Any better ideas are more than
welcome.
Thanks. Unfortunately, I am not sure how to apply/test that patch, is there
a description / grass wiki page somewhere that explains?
On Tue, Dec 22, 2015 at 3:47 PM, GRASS GIS <trac@osgeo.org
<mailto:trac@osgeo.org>> wrote:
#2632: option in context menu to export vector attribute table
--------------------------+-------------------------
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.3
Component: Vector | Version: unspecified
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mlennert):
I added a second patch that puts the (IMHO) main options of
v.db.select
(map, column separator, output file) into a "Main choices" tab. I
think
this should be enough to make exporting attributes easier, without
having
to code a separate simplified GUI. Not sure if "Main choices" is
the best
choice of names for that tab, though. Any better ideas are more than
welcome.
Thanks. Unfortunately, I am not sure how to apply/test that patch, is
there a description / grass wiki page somewhere that explains?
For the GUI part (export_attributes.patch) you can also copy the changes manually into gui/wxpython/lmgr/layertree.py in your GRASS installation directory (GISBASE).
For the v.db.select change you need to patch (or apply manually - there are not that many changes) and then recompile the module.
On Tue, Dec 22, 2015 at 5:26 PM, Moritz Lennert <
mlennert@club.worldonline.be> wrote:
On 22/12/15 16:09, Paulo van Breugel wrote:
On Tue, Dec 22, 2015 at 3:47 PM, GRASS GIS <trac@osgeo.org
<mailto:trac@osgeo.org>> wrote:
#2632: option in context menu to export vector attribute table
--------------------------+-------------------------
Reporter: pvanbosgeo | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.0.3
Component: Vector | Version: unspecified
Resolution: | Keywords:
CPU: Unspecified | Platform: Unspecified
--------------------------+-------------------------
Comment (by mlennert):
I added a second patch that puts the (IMHO) main options of
v.db.select
(map, column separator, output file) into a "Main choices" tab. I
think
this should be enough to make exporting attributes easier, without
having
to code a separate simplified GUI. Not sure if "Main choices" is
the best
choice of names for that tab, though. Any better ideas are more than
welcome.
Thanks Moritz, this works perfectly. This is really a very welcome
addition, I hope this can be incorporated.
Thanks. Unfortunately, I am not sure how to apply/test that patch, is
there a description / grass wiki page somewhere that explains?
For the GUI part (export_attributes.patch) you can also copy the changes
manually into gui/wxpython/lmgr/layertree.py in your GRASS installation
directory (GISBASE).
For the v.db.select change you need to patch (or apply manually - there
are not that many changes) and then recompile the module.
Thanks. My problem was that I didn't recognized the format.. which looked
suspiciously as html. Which it was, I accidentally saved the webpage of the
patch instead of the patch file itself.
For the GUI part (export_attributes.patch) you can also copy the changes
manually into gui/wxpython/lmgr/layertree.py in your GRASS installation
directory (GISBASE).
For the v.db.select change you need to patch (or apply manually - there
are not that many changes) and then recompile the module.
Thanks. My problem was that I didn't recognized the format.. which looked
suspiciously as html. Which it was, I accidentally saved the webpage of the
patch instead of the patch file itself.
I have updated the Wiki page yesterday and now, adding among other
stuff the new section:
On Wed, Dec 23, 2015 at 12:47 PM, Markus Neteler <neteler@osgeo.org> wrote:
On Wed, Dec 23, 2015 at 10:50 AM, Paulo van Breugel
<p.vanbreugel@gmail.com> wrote:
> On Tue, Dec 22, 2015 at 5:26 PM, Moritz Lennert
>> On 22/12/15 16:09, Paulo van Breugel wrote:
>>> Thanks. Unfortunately, I am not sure how to apply/test that patch, is
>>> there a description / grass wiki page somewhere that explains?
>>
>> https://grasswiki.osgeo.org/wiki/Patches
>>
>> For the GUI part (export_attributes.patch) you can also copy the changes
>> manually into gui/wxpython/lmgr/layertree.py in your GRASS installation
>> directory (GISBASE).
>>
>> For the v.db.select change you need to patch (or apply manually - there
>> are not that many changes) and then recompile the module.
>
> Thanks. My problem was that I didn't recognized the format.. which looked
> suspiciously as html. Which it was, I accidentally saved the webpage of
the
> patch instead of the patch file itself.
I have updated the Wiki page yesterday and now, adding among other
stuff the new section: