[GRASS-dev] [GRASS GIS] #3281: region boundaries rendering

[GRASS GIS]

#3281: region boundaries rendering
---+-
 Reporter:  vincent|  Owner:  grass-dev@…
 Type:  enhancement| Status:  new
 Priority:  normal |  Milestone:
Component:  wxGUI  |Version:  svn-trunk
 Keywords:  g.region, map display  |CPU:  Unspecified
 Platform:  Unspecified|
---+-
 In order to better warn novice users about region settings importance,
 could we imagine a way to instantly know whether or not the current region
 extent fits with the area one ''pretends'' working on?

 In the map display it could be done by greying out the area outside the
 current region. Compared to the current red frame, if the map display does
 not show any region border, you could anyhow see if you are inside or
 outside the region extent. I attached an illustration of this idea in
 #3279 :
 https://trac.osgeo.org/grass/attachment/ticket/3279/region_display.png

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] github / travis sync - push file to grass-gis/homebrew-grass-dev repo when grass-gis is synsed to svn?

[Vaclav Petras]

On Thu, Feb 9, 2017 at 4:25 PM, Rainer M Krug  wrote:

> Would it be possible to push a file containing e.g. the time to
> grass-gis/homebrew-grass-dev?
>
> The content of the file does not matter, but e.g. the time would be
> fine.
>

That would be a big workaround IMO. I think using daily cron jobs on travis
is a better option (if it works). I enabled them and now we need to wait to
see if that works (Travis CI has currently large backlog on Mac builds,
https://www.traviscistatus.com/).

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

Re: [GRASS-dev] v.in.osm

[Štěpán Turek]

Hi,




I incline to clean up the data as a default. The module should behave in a 
user-friendly way therefore expected behavior should be the default one.




I guess that most users would expect to import the data in topologically 
correct format. If the topology is wrong, a user can get totally misleading 
results (wrongly assuming they are correct) from various vector modules 
which is not very nice.




Stepan




-- Původní zpráva --
Od: Moritz Lennert 
Komu: Luca Delucchi , GRASS-dev 
Datum: 9. 2. 2017 13:47:49
Předmět: Re: [GRASS-dev] v.in.osm

"On 09/02/17 10:20, Luca Delucchi wrote:
> Hi,
>
> I did a change in v.in.osm adding a c flag to cleanup the data and
> create a GRASS GIS network topological correct, this is done by
> default now. I attached a diff.
>
> The flag could be also the opposite, so don't cleanup the data.
>
> What do you think?

I would not make it the default. You cannot be sure that users want to 
clean in the same way you do, so better to provide it as an 
(well-documented) option.

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

[GRASS-dev] github / travis sync - push file to grass-gis/homebrew-grass-dev repo when grass-gis is synsed to svn?

[Rainer M Krug]

Hi

Would it be possible to push a file containing e.g. the time to
grass-gis/homebrew-grass-dev?

The content of the file does not matter, but e.g. the time would be
fine.

I have just created a travis-ci test for the homebrew-grass-dev repo and
if it would be possible to push a file to this repo whenever the github
grass-gis/grass-ci is updated, we would have tests of the Mac build via
homebrew which is separate from the test for Linux.

Cheers,

Rainer

-- 
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982


signature.asc
Description: PGP signature


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

Re: [GRASS-dev] [GRASS GIS] #3279: Add Region tab to the main GUI

[GRASS GIS]

#3279: Add Region tab to the main GUI
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  major   |  Milestone:  7.4.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:  g.region, extent, resolution,
   CPU:  |  novice, beginner, user-friendliness
  Unspecified|   Platform:  Unspecified
-+-

Comment (by wenzeslaus):

 Replying to [comment:3 mlennert]:
 > Replying to [ticket:3279 wenzeslaus]:
 > > Problems:
 > > * How many of these tabs do we what to add (allowed to be added)
 there?
 > >  * Spatial Database, Location, Mapset
 > >  * Thing related to Map Display, Vector Digitizer, ... (as for 3D
 view)
 > >  * General preferences which needs to be changed often (Map Display
 color, font, projection statusbar settings)
 > >  * Documentation (Doc, Man)
 > >  * R, Jupyter Notebook, ...
 > I think we should not overdo it with these tabs [...] the idea should
 not be to put all of GRASS GIS into wxGUI tabs

 Agreed. And there is more danger... Workspace(s)/Projects, Mask

 > or we should allow activating/desactivating (some of them).

 That's possible for some: ''Settings > Preferences > General > Hide 'X'
 tab'' where ''X'' is ''Modules'' or ''Python''. The ''Data'' tab should be
 in this list as well and same for ''Region''. We can even consider hiding
 the ''Console'' tab and show it automatically when an error is printed.
 And of course ''3D view'' is there already only when needed.

--
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] #3280: r.terraflow requires all output options to be given

[GRASS GIS]

#3280: r.terraflow requires all output options to be given
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  closed
  Priority:  normal   |  Milestone:  7.4.0
 Component:  Raster   |Version:  svn-trunk
Resolution:  fixed|   Keywords:  r.terraflow
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by martinl):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:  7.2.1 => 7.4.0


Comment:

 Replying to [comment:3 annakrat]:
 > The ticket is 'enhancement' ticket, so I would suggest not to backport
 it.

 OK, changing milestone.

--
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] #3280: r.terraflow requires all output options to be given

[GRASS GIS]

#3280: r.terraflow requires all output options to be given
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.2.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.terraflow
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by martinl):

 Replying to [comment:3 annakrat]:
 > Have you committed it? I don't see it. The ticket is 'enhancement'
 ticket, so I would suggest not to backport it.

 yes, there is something bad with trac which currently shows as the last
 commit r70514 (see timeline). But it's not the last svn commit:

 {{{
 svn up
 Updating '.':
 At revision 70516.
 }}}

--
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] #3279: Add Region tab to the main GUI

[GRASS GIS]

#3279: Add Region tab to the main GUI
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  major   |  Milestone:  7.4.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:  g.region, extent, resolution,
   CPU:  |  novice, beginner, user-friendliness
  Unspecified|   Platform:  Unspecified
-+-

Comment (by wenzeslaus):

 Replying to [comment:3 mlennert]:
 > As we are speaking about this: It would be great if the computational
 extent and resolution dialog would allow drawing the region extent
 interactively. I guess this would probably mean some call to OSM or
 similar in order to display a meaningful map at different zooming levels.

 This may be better discussed in a separate ticket. There is a lot of
 details to discuss. The ''Region'' tab is integrated in GUI, so using Map
 Display seems to be the most straightforward option.

--
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] #3279: Add Region tab to the main GUI

[GRASS GIS]

#3279: Add Region tab to the main GUI
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  major   |  Milestone:  7.4.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:  g.region, extent, resolution,
   CPU:  |  novice, beginner, user-friendliness
  Unspecified|   Platform:  Unspecified
-+-

Comment (by wenzeslaus):

 Replying to [comment:2 vincent]:
 > Replying to [ticket:3279 wenzeslaus]:
 > > This may raise awareness of new users about computational region and
 encourage all users to remember it before running modules.
 > In the same scope, what about greying out the space around the region
 extent ?

 Please, create a separate ticket for it.

--
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] #3280: r.terraflow requires all output options to be given

[GRASS GIS]

#3280: r.terraflow requires all output options to be given
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.2.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.terraflow
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by annakrat):

 Have you committed it? I don't see it. The ticket is 'enhancement' ticket,
 so I would suggest not to backport it.

--
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] #3280: r.terraflow requires all output options to be given

[GRASS GIS]

#3280: r.terraflow requires all output options to be given
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.2.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.terraflow
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by martinl):

 If no objections I will do backport for GRASS 7.2.1.

--
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] #3280: r.terraflow requires all output options to be given

[GRASS GIS]

#3280: r.terraflow requires all output options to be given
--+-
  Reporter:  martinl  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  7.2.1
 Component:  Raster   |Version:  svn-trunk
Resolution:   |   Keywords:  r.terraflow
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by martinl):

 Implemented in r70516. In trunk you can now run eg.

 {{{
 r.terraflow elevation=elevation100 filled=o1
 }}}

 The module also also much less verbose than before.

--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3280: r.terraflow requires all output options to be given

[GRASS GIS]

#3280: r.terraflow requires all output options to be given
-+-
 Reporter:  martinl  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  normal   |  Milestone:  7.2.1
Component:  Raster   |Version:  svn-trunk
 Keywords:  r.terraflow  |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Currently user needs to specify all output options of G72:r.terraflow even
 he/she is interested only about one of them.

 {{{
 r.terraflow elevation=elevation100 filled=o1 direction=o2 swatershed=o3
 accumulation=o4 tci=o5
 }}}

--
Ticket URL: 
GRASS GIS 

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

Re: [GRASS-dev] v.in.osm

[Moritz Lennert]

On 09/02/17 10:20, Luca Delucchi wrote:

Hi,

I did a change in v.in.osm adding a c flag to cleanup the data and
create a GRASS GIS network topological correct, this is done by
default now. I attached a diff.

The flag could be also the opposite, so don't cleanup the data.

What do you think?


I would not make it the default. You cannot be sure that users want to 
clean in the same way you do, so better to provide it as an 
(well-documented) option.


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

Re: [GRASS-dev] [GRASS GIS] #3275: wxGUI: encoding error when saving workspace

[GRASS GIS]

#3275: wxGUI: encoding error when saving workspace
--+--
  Reporter:  mlennert |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.1
 Component:  wxGUI|Version:  svn-trunk
Resolution:   |   Keywords:  wxGUI workspace encoding
   CPU:  Unspecified  |   Platform:  Unspecified
--+--

Comment (by mlennert):

 Replying to [comment:1 mlennert]:
 > Vaclav made me realize that I did have a non-ascii character in my
 display: u'\u20ac' is a Euro sign.

 This does not make this less an error, though. I suppose this is linked to
 the GSoC cartography work trying to save more elements of the current map
 display ?

--
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] #3279: Add Region tab to the main GUI

[GRASS GIS]

#3279: Add Region tab to the main GUI
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  major   |  Milestone:  7.4.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:  g.region, extent, resolution,
   CPU:  |  novice, beginner, user-friendliness
  Unspecified|   Platform:  Unspecified
-+-

Comment (by mlennert):

 Replying to [ticket:3279 wenzeslaus]:
 > I suggest to add another tab to the Layer Manager which would handle
 (and show) all things related to the (current) computational region.
 [...]
 > This may raise awareness of new users about computational region and
 encourage all users to remember it before running modules. There can be
 even a short explanation what does it do.
 >


 Nice idea !

 As we are speaking about this: It would be great if the computational
 extent and resolution dialog would allow drawing the region extent
 interactively. I guess this would probably mean some call to OSM or
 similar in order to display a meaningful map at different zooming levels.

 >
 > Problems:
 >
 > * Name: ''Region'' is not completely clear, but we decided to go with
 one word, so ''Computational Region'' is not an option. ''g.region'' would
 be less readable for novices and inconsistent.
 > * Although for English there is still space even when ''3D view'' is
 active, we may be running out of space for some languages.
 > * How many of these tabs do we what to add (allowed to be added) there?
 >  * Spatial Database, Location, Mapset
 >  * Thing related to Map Display, Vector Digitizer, ... (as for 3D view)
 >  * General preferences which needs to be changed often (Map Display
 color, font, projection statusbar settings)
 >  * Documentation (Doc, Man)
 >  * R, Jupyter Notebook, ...

 I think we should not overdo it with these tabs, or we should allow
 activating/desactivating (some of them). IMHO, the idea should not be to
 put all of GRASS GIS into wxGUI tabs ;-)

--
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] #3224: broken links to source code and history in add-ons user manuals

[GRASS GIS]

#3224: broken links to source code and history in add-ons user manuals
--+-
  Reporter:  Veronica Andreo  |  Owner:  martinl
  Type:  defect   | Status:  reopened
  Priority:  normal   |  Milestone:  7.2.1
 Component:  Addons   |Version:  svn-releasebranch72
Resolution:   |   Keywords:  add-ons, links, user manual
   CPU:  x86-64   |   Platform:  Linux
--+-

Comment (by martinl):

 Replying to [comment:11 Veronica Andreo]:
 > Reopening this ticket since links to source code and history in
 r.modis.* and r.green.* modules (apparently those belonging to a group)
 are still broken.
 >
 > This is the message I get in trac:
 >
 > Trac Error
 > No node grass-addons/grass7/raster/r.green.biomassfor.legal at revision
 70410

 Should be fixed in trunk (r70514). Testing welcome.

--
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] #717: Vector digitizer tool in wx-Python GUI crashes after changing mapsets.

[GRASS GIS]

#717: Vector digitizer tool in wx-Python GUI crashes after changing mapsets.
---+-
  Reporter:  voncasec  |  Owner:  grass-dev@…
  Type:  defect| Status:  new
  Priority:  normal|  Milestone:  6.4.6
 Component:  wxGUI |Version:  6.4.0 RCs
Resolution:|   Keywords:  g.mapset
   CPU:  x86-64|   Platform:  Linux
---+-
Changes (by martinl):

 * status:  assigned => new
 * cc: grass-dev@… (removed)
 * owner:  martinl => grass-dev@…


--
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] #725: wxGUI: bind ctrl-q to exit

[GRASS GIS]

#725: wxGUI: bind ctrl-q to exit
--+--
  Reporter:  hamish   |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  normal   |  Milestone:  6.5.0
 Component:  wxGUI|Version:  svn-develbranch6
Resolution:   |   Keywords:  menu
   CPU:  All  |   Platform:  All
--+--
Changes (by martinl):

 * status:  assigned => new
 * cc: grass-dev@… (removed)
 * owner:  martinl => grass-dev@…


--
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] #2626: v.out.ogr does not suggest db.connect and db.login when not set

[GRASS GIS]

#2626: v.out.ogr does not suggest db.connect and db.login when not set
--+---
  Reporter:  wenzeslaus   |  Owner:  martinl
  Type:  defect   | Status:  assigned
  Priority:  normal   |  Milestone:  7.2.1
 Component:  Vector   |Version:  svn-trunk
Resolution:   |   Keywords:  PostgreSQL, postgres, PostGIS
   CPU:  Unspecified  |   Platform:  Linux
--+---

Comment (by martinl):

 Still the issue in GRASS 7.2.1svn?

--
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] #2460: v.out.postgis doesn't export attribute table

[GRASS GIS]

#2460: v.out.postgis doesn't export attribute table
--+---
  Reporter:  martin   |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  normal   |  Milestone:  7.2.1
 Component:  Default  |Version:  svn-trunk
Resolution:   |   Keywords:  v.out.postgis
   CPU:  x86-64   |   Platform:  Linux
--+---

Comment (by martinl):

 In [changeset:"70513" 70513]:
 {{{
 #!CommitTicketReference repository="" revision="70513"
 vlib: copy areas - turn is_isle() into debug message (see #2460)
 }}}

--
Ticket URL: 
GRASS GIS 

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

[GRASS-dev] v.in.osm

[Luca Delucchi]

Hi,

I did a change in v.in.osm adding a c flag to cleanup the data and
create a GRASS GIS network topological correct, this is done by
default now. I attached a diff.

The flag could be also the opposite, so don't cleanup the data.

What do you think?

-- 
ciao
Luca

www.lucadelu.org
Index: grass7/vector/v.in.osm/v.in.osm.py
===
--- grass7/vector/v.in.osm/v.in.osm.py  (revision 70510)
+++ grass7/vector/v.in.osm/v.in.osm.py  (working copy)
@@ -49,6 +49,12 @@
 #%end
 
 #%flag
+#% key: c
+#% label: Cleanup data
+#% description: Execute v.split and v.build.polylines to create a GRASS GIS 
network topological correct
+#%end
+
+#%flag
 #% key: l
 #% label: List available OGR layers in data source and exit
 #%end
@@ -126,28 +132,29 @@
 except CalledModuleError:
 grass.fatal(_('%s failed') % 'v.in.ogr')
 
-try:
+
+if flags['c']:
 grass.debug('Step 2/3: v.split...', 2)
-grass.run_command('v.split',
- quiet=True,
- input=self.getTmp('ogr'),
- output=self.getNewTmp('split'),
- vertices=2
-)
-except CalledModuleError:
-grass.fatal(_('%s failed') % 'v.split')
+try:
+grass.run_command('v.split',
+ quiet=True,
+ input=self.getTmp('ogr'),
+ output=self.getNewTmp('split'),
+ vertices=2
+)
+except CalledModuleError:
+grass.fatal(_('%s failed') % 'v.split')
+try:
+grass.debug('Step 3/3: v.build.polylines...', 2)
+grass.run_command('v.build.polylines',
+ quiet=True, overwrite=grass.overwrite(),
+ input=self.getNewTmp('split'),
+ output=options['output'],
+ cats='same'
+ )
+except CalledModuleError:
+grass.fatal(_('%s failed') % 'v.build.polylines')
 
-try:
-grass.debug('Step 3/3: v.build.polylines...', 2)
-grass.run_command('v.build.polylines',
- quiet=True,
- input=self.getNewTmp('split'),
- output=options['output'],
- cats='same'
- )
-except CalledModuleError:
-grass.fatal(_('%s failed') % 'v.build.polylines')
-
 if __name__ == "__main__":
 options, flags = grass.parser()
 
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev

Re: [GRASS-dev] [GRASS GIS] #3279: Add Region tab to the main GUI

[GRASS GIS]

#3279: Add Region tab to the main GUI
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  major   |  Milestone:  7.4.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:  g.region, extent, resolution,
   CPU:  |  novice, beginner, user-friendliness
  Unspecified|   Platform:  Unspecified
-+-

Comment (by vincent):

 Replying to [ticket:3279 wenzeslaus]:
 > This may raise awareness of new users about computational region and
 encourage all users to remember it before running modules.
 In the same scope, what about greying out the space around the region
 extent ?

--
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] #3279: Add Region tab to the main GUI

[GRASS GIS]

#3279: Add Region tab to the main GUI
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  major   |  Milestone:  7.4.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:  g.region, extent, resolution,
   CPU:  |  novice, beginner, user-friendliness
  Unspecified|   Platform:  Unspecified
-+-
Changes (by vincent):

 * Attachment "region_display.png" added.

 greying out the space around region extent

--
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] #3279: Add Region tab to the main GUI

[GRASS GIS]

#3279: Add Region tab to the main GUI
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  major   |  Milestone:  7.4.0
 Component:  wxGUI   |Version:  svn-trunk
Resolution:  |   Keywords:  g.region, extent, resolution,
   CPU:  |  novice, beginner, user-friendliness
  Unspecified|   Platform:  Unspecified
-+-

Comment (by martinl):

 Replying to [ticket:3279 wenzeslaus]:
 > I suggest to add another tab to the Layer Manager which would handle
 (and show) all things related to the (current) computational region. The
 name I suggest for the tab is ''Region'' and the order:

 strong +1

--
Ticket URL: 
GRASS GIS 

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