Re: [GRASS-dev] [GRASS GIS] #3976: g.manual: say "displays"

[GRASS GIS]

#3976: g.manual: say "displays"
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  trivial  |  Milestone:  7.8.2
 Component:  Docs |Version:  unspecified
Resolution:  fixed|   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by neteler):

 * status:  new => closed
 * resolution:   => fixed
 * milestone:   => 7.8.2


Comment:

 Thanks! Merged.

-- 
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] #3996: Allow multiple --exec's

[GRASS GIS]

#3996: Allow multiple --exec's
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Startup  |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by jidanni):

 Replying to [comment:3 mankoff]:
 > HEREDOCs work in Makefiles.
 >
 > This seems like a bad idea...
 Yup, and that's why I learned perl while the other kids learned python. At
 least good old ";"'s still work.

-- 
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] #3577: Add rename and delete of Location and Mapset in Datacatalog

[GRASS GIS]

#3577: Add rename and delete of Location and Mapset in Datacatalog
-+-
  Reporter:  wenzeslaus  |  Owner:  grass-dev@…
  Type:  | Status:  new
  enhancement|
  Priority:  normal  |  Milestone:  8.0.0
 Component:  wxGUI   |Version:  unspecified
Resolution:  |   Keywords:  datacatalog, location, mapset,
   CPU:  |  rename, delete, move, remove, g.mapset
  Unspecified|   Platform:  Unspecified
-+-

Comment (by jidanni):

 And it is weird that g.mapsets.html mentions
  mapsets can be removed (operation=remove) **from the search path**
 So users wonder ''"So in the world of Grass, being removed from the search
 path means the same as being unlinked from the search path -- means the
 same thing as being unlinked from the file system??" Or else why don't
 they also mention how to remove it for good?"''

-- 
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] #4000: v.import documentation megabug

[GRASS GIS]

#4000: v.import documentation megabug
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 It's bug #4000. Time for my v.import documentation megabug.
 Mainly because apparently v.import calls v.in.org under the hood.

 Anyway, here is the whole mess:
 {{{
 Do not require input=... for v.import -f
 Please do not require the user to have an input file just to use
 v.import -f .
 Or document workaround:
  v.import -f input=/dev/null
 Also
  SYNOPSIS
...
v.import  [-flo]  input=string  ...

 needs to be
v.import  -f #in fact maybe detect and don't allow it to be
 combined with other options
v.import  [-lo]  input=string  ...

 and "[required]" needs to be removed from
  input=string [required]
Name of OGR datasource to be imported
 P.S., change
  The list of actually supported formats can be printed by -f flag.
 to
  The list of actually supported formats can be printed by the -f flag.
 Wait, it seems that v.import is some sort of alias for v.in.org. Well
 the man page should just say so at the top, and the rest left mostly
 blank. (Please don't maintain two sets of almost identical
 documentation. Bad for writers, and bad for readers. In fact you can
 list both aliases in the same SYNOPSIS of a symlinked (or just copied) new
 single page.)
 And in fact one can do
  v.in.ogr -f
 without input=string, so the v.in.ogr man page needs to be fixed too.

 r.in.gdal -f in fact does not require input=... output=...
 The r.in.gdal man page should be fixed to reflect reality:
  SYNOPSIS
r.in.gdal -f #now alone on a separate line
 and "[required]" needs to be removed from these:
  input=name [required]
  output=name [required]

 v.import -f produces jumbled list
 Currently the user must use
  v.import -f | sort -f
 if he wants to read the list produced in any orderly fashion.
 Perhaps this could be done automatically, or at least documented on
 the man page.

 r.in.gdal -f produces jumbled list
 Currently the user must use
  r.in.gdal -f | sort -f
 if he wants to read the list produced in any orderly fashion.
 Perhaps this could be done automatically, or at least documented on
 the man page.

 v.import: combine confusing sentences
 In man v.import we read
  DESCRIPTION
  ...
  If the projection of the input does not match the projection of the
  location, the input is reprojected into the current location. In case
  that the projection of the input map does match the projection of the
  location, the input is imported directly.

 Let's take a second look at that last part:

 
__If_the_projection_of_the_input_does_not_match_the_projection_of_the_location,_the_input_is_reprojected_into_the_current_location.
 
In_case_that_the_projection_of_the_input_map_does_match_the_projection_of_the_location,_the_input_is_imported_directly.

 Let's see if we can combine them to make a single sentence:

  If the projection of the input does not match the projection of the
  location, the input is reprojected into the current location. Else it
  is imported directly.

 Or perhaps simply:

  If the projection of the input does not match the projection of the
  location, the input is reprojected into the current location.

 Wait! Maybe -o needs to be mentioned here too, as further below we see:

  NOTES

  v.import checks the projection metadata of the dataset to be imported
  against the current location's projection. If not identical a related
  error message is shown. To override this projection check (i.e. to use
  current location's projection) by assuming that the dataset has the
  same projection as the current location the -o flag can be used. This
  is also useful when geodata to be imported do not contain any
  projection metadata at all. The user must be sure that the projection
  is identical in order to avoid to introduce data errors.

 Or maybe all this needs to be combined into one paragraph.

 Allow user to do just "v.import datum_trans=-1"
 On man v.import the user sees
  datum_trans=integer
   Index number of datum transform parameters
   -1 to list available datum transform parameters
   Options: -1-100

 OK, he is just curious, and wants to list them.
  $ v.import datum_trans=-1
 alas does not work. He needs to pack on a load of arbitrary junk:
  $ v.import datum_trans=-1 epsg= input=/dev/null output=zzz
 and still just gets
  ERROR: No output format specified, define one of flags -p, -g, -j, or -w
 which by the way do not appear on the v.import man page.
 (My actual test command was
  $ grass --exec v.import datum_trans=-1 epsg= input=/dev/null
 output=zzz

 Wait, man v.in.org says
  An interesting wrapper 

[GRASS-dev] [GRASS GIS] #3999: Mention projection of current location in error message

[GRASS GIS]

#3999: Mention projection of current location in error message
+-
 Reporter:  jidanni |  Owner:  grass-dev@…
 Type:  enhancement | Status:  new
 Priority:  trivial |  Milestone:
Component:  Projections/Datums  |Version:  git-releasebranch78
 Keywords:  |CPU:  Unspecified
 Platform:  Unspecified |
+-
 {{{
 $ grass --exec v.in.ogr -j input=e.geojson
 WARNING: Projection of dataset does not appear to match current location.

  Dataset PROJ_INFO is:
  name: WGS 84
  datum: wgs84
  ellps: wgs84
  proj: ll
  no_defs: defined

  ERROR: proj
 }}}

 OK, it says
 - Dataset PROJ_INFO is:
 so it also should say
 - Current location is:
 even if the result is unknown (say so.) Yes even if the user forgot to run
 it inside grass.

-- 
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] #3996: Allow multiple --exec's

[GRASS GIS]

#3996: Allow multiple --exec's
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Startup  |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mankoff):

 HEREDOCs work in Makefiles.

 This seems like a bad idea https://stackoverflow.com/questions/5873025
 /heredoc-in-a-makefile

-- 
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] #3996: Allow multiple --exec's

[GRASS GIS]

#3996: Allow multiple --exec's
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Startup  |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by jidanni):

 Replying to [comment:1 mankoff]:
 > Somewhat related - you can use HEREDOCs
 Great to know, and **should be documented**.

 (Alas I am mainly doing one-liners in Makefiles.)

-- 
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] #3998: v.out.ascii.html: warn that it doesn't completely export a vector map

[GRASS GIS]

#3998: v.out.ascii.html: warn that it doesn't completely export a vector map
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 v.out.ascii.html says:
v.out.ascii converts a GRASS vector map in binary format to a GRASS
 vector map in ASCII format. Using flag -o v.out.ascii output will be in
 old (version 4) ASCII format.

 OK, but add: Note: attributes are not exported. See v.db.* or db.* ? etc.

-- 
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] #3996: Allow multiple --exec's

[GRASS GIS]

#3996: Allow multiple --exec's
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Startup  |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mankoff):

 Somewhat related - you can use HEREDOCs:

 {{{
 grass -c template.tif ./G --exec 
GRASS GIS 

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

[GRASS-dev] [GRASS GIS] #3997: variables.html: mention not to expect --exec g.gisenv to work

[GRASS GIS]

#3997: variables.html: mention not to expect --exec g.gisenv to work
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 variables.html says
 {{{
 Use g.gisenv within GRASS. This permanently predefines GRASS variables
 in the $HOME/.grass7/rc file.
 }}}
 Yes, "within". However it should mention that that won't work with --exec.

 Mention with --exec a temporary $GISRC is used:
 {{{
 $ grass /.../TC46 --exec env
 GISRC=/tmp/grass7-jidanni-12382/gisrc
 }}}

-- 
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] #3582: Removing a Mapset from inside a GRASS GIS session

[GRASS GIS]

#3582: Removing a Mapset from inside a GRASS GIS session
---+---
  Reporter:  Nikos Alexandris  |  Owner:  grass-dev@…
  Type:  enhancement   | Status:  new
  Priority:  normal|  Milestone:
 Component:  Default   |Version:  unspecified
Resolution:|   Keywords:  mapset, remove, delete, erase
   CPU:  Unspecified   |   Platform:  Unspecified
---+---

Comment (by jidanni):

 Indeed without using the GUI, there is no way to
 - remove locations
 - remove mapsets.

 When one day there finally are, they should be added to the SEE ALSO of
 g.remove.

 And mentioned on grass7.html, which tells one how to create them from the
 command line, but forgets to then add how to remove them!

-- 
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] #3996: Allow multiple --exec's

[GRASS GIS]

#3996: Allow multiple --exec's
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Startup  |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Enhancement idea:

 Even though one can run whole shell scripts,
 how about also allowing more than one "grass --exec"?

 Perhaps allow multiple --exec's using Unix find(1)'s method:

 {{{
 -exec ... ... \; -exec ... ... \;
 }}}

 In fact it one fails, don't run the rest, just like Unix.

-- 
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] #3995: v.out.ascii appends blanks to data upon export

[GRASS GIS]

#3995: v.out.ascii appends blanks to data upon export
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Vector   |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 {{{
 $ grass ... --exec v.out.ascii format=standard input=...
 }}}
 adds a varying number of trailing blanks to each line.

 If there was no blanks when a user imported the data with v.in.ascii then
 there certainly should not be any added upon export.

 Test with

 {{{
  | grep ' $'

 }}}

-- 
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] #3994: Put page name first in s

[GRASS GIS]

#3994: Put page name first in s
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by jidanni):

 * Attachment "2858-8.jpg" added.


-- 
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] #3994: Put page name first in s

[GRASS GIS]

#3994: Put page name first in s
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Idea: Instead of s like
 - GRASS GIS manual: v.edit
 use
 - v.edit - GRASS GIS Manual

 That way the individual titles will still be visible on a bar of tabs
 in the browser.

 In fact the browser always puts its own name at the end too. As seen
 at the very top of the image.

-- 
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] #3994: Put page name first in s

[GRASS GIS]

#3994: Put page name first in s
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by jidanni):

 In fact also standardize on "Manual". Some pages have "manual".

-- 
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] #3993: v.import: document snap=-1

[GRASS GIS]

#3993: v.import: document snap=-1
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 https://github.com/OSGeo/grass/blob/master/scripts/v.import/v.import.html
 mentions

 {{{
  snap=float
  Snapping threshold for boundaries (map units)
  A suitable threshold is estimated during import
  Default: -1
 }}}

 OK, but nowhere on the man page is the meaning of "-1" explained.

-- 
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] #3992: v.import man page should say what -f's ro, rw, and rw+ are

[GRASS GIS]

#3992: v.import man page should say what -f's ro, rw, and rw+ are
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 man v.import -f: document ro, rw, rw+
 {{{
 $ grass --exec v.import -f input=/dev/null 2>/dev/null |\
  perl -nwle '/\(([^)]+)/||die; print $1;'|sort|uniq -c
  40 ro
   2 rw
  47 rw+
 }}}
 OK, but the v.import man page should say what -f's ro, rw, and rw+ are.

 Yes, the user might guess what ro and rw are, but not **rw+**!!.

-- 
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] #3991: m.measure: mention square feet

[GRASS GIS]

#3991: m.measure: mention square feet
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 m.measure man page says
 ''m.measure provides the user with a way to measure the lengths and
 areas of lines and polygons. Areas can be stated in acres, hectares,
 square miles, square meters and square kilometers.''

 OK, but maybe also mention square feet. (Not tested by me.) As one notes:

  ''Options: miles, **feet**, meters, kilometers, acres, hectares''

-- 
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] #3986: Some manual pages lack links to GitHub source

[GRASS GIS]

#3986: Some manual pages lack links to GitHub source
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by jidanni):

 E.g.,
 - https://grass.osgeo.org/grass78/manuals/grass7.html lacks link to
 - https://github.com/OSGeo/grass/blob/master/lib/init/grass7.html

-- 
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] #3990: v.to.db: add a way to control output precision

[GRASS GIS]

#3990: v.to.db: add a way to control output precision
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Database |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 v.to.db could add a way to control precision.
 {{{
 $ grass ...TC46 --exec v.to.db -p map=Qingfu_st
 cat|length
 1|0.157112134436172
 }}}
 e.g., the user might not be interested in nanometers, etc.

-- 
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] #3989: v.to.db -p adds spurious blank line to beginning of output

[GRASS GIS]

#3989: v.to.db -p adds spurious blank line to beginning of output
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Database |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 v.to.db -p adds this leading blank line to output,
 {{{
 $ grass /home/jidanni/grassdata/ruanbikeng/TC46 --exec v.to.db -p
 map=Qingfu_st option=length type=line units=k
 Starting GRASS GIS...
 Cleaning up temporary files...
 Executing  ...
 Reading features...

 cat|length
 1|0.157112134436172
 }}}

-- 
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] #3988: topic_display.html: broken internal link

[GRASS GIS]

#3988: topic_display.html: broken internal link
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  git-releasebranch78
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by jidanni):

 Tools like "linklint" could find all these.

-- 
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] #3988: topic_display.html: broken internal link

[GRASS GIS]

#3988: topic_display.html: broken internal link
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 https://grass.osgeo.org/grass78/manuals/topic_display.html says
 {{{
 See also the corresponding keyword display for additional references.
 }}}
 But that is a broken link.

-- 
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] #3987: Some pages missing from the Full Index

[GRASS GIS]

#3987: Some pages missing from the Full Index
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by jidanni):

 Yes, in https://grass.osgeo.org/grass78/manuals/index.html but not the
 "full" index.

-- 
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] #3987: Some pages missing from the Full Index

[GRASS GIS]

#3987: Some pages missing from the Full Index
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by jidanni):

 * priority:  normal => trivial
 * component:  Default => Docs
 * type:  defect => enhancement


-- 
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] #3987: Some pages missing from the Full Index

[GRASS GIS]

#3987: Some pages missing from the Full Index
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  normal   |  Milestone:
Component:  Default  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 One would think the **Full Index** would contain e.g.,
 - https://grass.osgeo.org/grass78/manuals/variables.html
 Alas,

 {{{
 $ mech-dump --links
 https://grass.osgeo.org/grass78/manuals/full_index.html | grep -c
 variables
 0
 }}}

-- 
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] #3986: Some manual pages lack links to GitHub source

[GRASS GIS]

#3986: Some manual pages lack links to GitHub source
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  git-releasebranch78
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Pages like
 - https://grass.osgeo.org/grass78/manuals/g.gisenv.html
 have a link at the bottom to
 - https://github.com/OSGeo/grass/tree/master/general/g.gisenv

 Alas, pages like
 - https://grass.osgeo.org/grass78/manuals/variables.html
 lack a link at the bottom to
 - https://github.com/OSGeo/grass/blob/master/lib/init/variables.html
 or perhaps to .../tree/master/...

-- 
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] #3985: Read-only operations shouldn't unnecessarily do null edits to sqlite database

[GRASS GIS]

#3985: Read-only operations shouldn't unnecessarily do null edits to sqlite
database
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  enhancement  | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Database |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Even readonly commands,
 {{{
 $ grass /home/jidanni/grassdata/ruanbikeng/TC46 --exec g.gisenv
 Starting GRASS GIS...
 Cleaning up temporary files...
 Executing  ...
 GISDBASE=/home/jidanni/grassdata
 LOCATION_NAME=ruanbikeng
 MAPSET=TC46
 GUI=wxpython
 Execution of  finished.
 Cleaning up default sqlite database ...
 Cleaning up temporary files...
 }}}
 {{{
 cause all this writing
 $ find grassdata/ -mmin -1
 grassdata/ruanbikeng/TC46
 grassdata/ruanbikeng/TC46/sqlite
 grassdata/ruanbikeng/TC46/sqlite/sqlite.db
 }}}
 even e.g.,

 {{{
 $ grass /home/jidanni/grassdata/ruanbikeng/TC46 --exec true
 }}}

-- 
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] #3984: g.gisenv store=mapset ignored if no get=

[GRASS GIS]

#3984: g.gisenv store=mapset ignored if no get=
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Default  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 man g.gisenv says
 {{{
 store=string
 Where GRASS variable is stored
 Options: gisrc, mapset
 Default: gisrc
 }}}
 Bug: if one does just

 {{{
 $ g.gisenv store=mapset
 }}}

 it just does

 {{{
 $ g.gisenv
 }}}

 One needs a
 {{{
 get=var1,..
 }}}
 . to get it to work properly.

-- 
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] #3983: robots.txt unmaintained and lacks sitemaps

[GRASS GIS]

#3983: robots.txt unmaintained and lacks sitemaps
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Website  |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 Google is returning older versions of man pages instead of the current
 (v78) ones.

 This is due to robots.txt not having been updated since 2015,


 {{{
 $ HEAD https://grass.osgeo.org/robots.txt
 Last-Modified: Tue, 20 Jan 2015 11:14:30 GMT

 $ GET https://grass.osgeo.org/robots.txt
 Disallow: /grass61/manuals/
 Disallow: /grass62/manuals/
 Disallow: /grass63/manuals/
 Disallow: /grass65/manuals/
 }}}


 And most importantly, the lack of sitemap entries.
  https://support.google.com/webmasters/answer/156184

-- 
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] #3982: Remove keyword "level1"

[GRASS GIS]

#3982: Remove keyword "level1"
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  defect   | Status:  closed
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  unspecified
Resolution:  wontfix  |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-
Changes (by jidanni):

 * status:  new => closed
 * resolution:   => wontfix


-- 
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] #3982: Remove keyword "level1"

[GRASS GIS]

#3982: Remove keyword "level1"
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by jidanni):

 Oh.
 - https://www.google.com/search?q=level1+gis finds nothing.
 - https://www.google.com/search?q=level1+gis+grass finally does.

-- 
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] #3982: Remove keyword "level1"

[GRASS GIS]

#3982: Remove keyword "level1"
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  defect   | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by sbl):

 `level1` keyword is for modules that also work with vector maps with
 topology level 1 (so, not fullly build topology).
 See: https://grass.osgeo.org/grass78/manuals/vectorintro.html section
 "Vector model and topology".
 I would suggest to close this ticket, or do you have any specific
 suggestions for how to improve the documentation regarding keywords?

-- 
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] #3951: v.in.ascii: add: Note: z= always still needs to be set manually, despite using -z.

[GRASS GIS]

#3951: v.in.ascii: add: Note: z= always still needs to be set manually, despite
using -z.
--+-
  Reporter:  jidanni  |  Owner:  grass-dev@…
  Type:  enhancement  | Status:  new
  Priority:  trivial  |  Milestone:
 Component:  Docs |Version:  unspecified
Resolution:   |   Keywords:
   CPU:  Unspecified  |   Platform:  Unspecified
--+-

Comment (by mmetz):

 Replying to [ticket:3951 jidanni]:
 > In v.in.ascii at
 >
 > {{{
 >z=integer
 >Number of column used as z coordinate (points mode)
 >First column is 1. If 0, z coordinate is not used
 >Default: 0
 > }}}
 >
 > add:
 >
 >  Note: z= always still needs to be set manually, despite using -z.
 >
 > In fact perhaps 3 would be a good default, if -z use is detected...

 If you want to create 3D points when using `v.in.ascii format=point`,
 there is no reason to assume that z coordinates are in column 3, this
 depends on the input data and use case.

 A simplification of the user interface would be to imply `-z` if z > 0.

-- 
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] #3982: Remove keyword "level1"

[GRASS GIS]

#3982: Remove keyword "level1"
-+-
 Reporter:  jidanni  |  Owner:  grass-dev@…
 Type:  defect   | Status:  new
 Priority:  trivial  |  Milestone:
Component:  Docs |Version:  unspecified
 Keywords:   |CPU:  Unspecified
 Platform:  Unspecified  |
-+-
 There is keyword "level1",
 https://grass.osgeo.org/grass79/manuals/keywords.html#level1
 with absolutely nothing saying why it is there.
 Click on the first link (d.vect). No hint there...

-- 
Ticket URL: 
GRASS GIS 

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