[GRASS-dev] [GRASS GIS] #517: v.net.iso loses or does not create a database connection for resulting vector map

#517: v.net.iso loses or does not create a database connection for resulting
vector map
-----------------------+----------------------------------------------------
Reporter: effilc36 | Owner: grass-dev@lists.osgeo.org
     Type: defect | Status: new
Priority: minor | Milestone: 6.4.0
Component: default | Version: 6.4.0 RCs
Keywords: v.net.iso | Platform: MacOSX
      Cpu: OSX/Intel |
-----------------------+----------------------------------------------------
Dataset: nc_spm_08

Input:

v.net.iso input=streets_net output=streets_net_iso ccats=1-100000 nlayer=2
\
costs=200,400,600,800 afcolumn=navcost

v.category streets_net_iso option=report (works as expected)

Results:

Adding streets_net_iso to the GIS Manager and classifying by cat=1
produces "database connection not defined" error.

"Show attribute columns" in GIS Manager produces the same results

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/517&gt;
GRASS GIS <http://grass.osgeo.org>

#517: v.net.iso loses or does not create a database connection for resulting
vector map
--------------------------+-------------------------------------------------
  Reporter: effilc36 | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: new
  Priority: minor | Milestone: 7.0.0
Component: default | Version: svn-trunk
Resolution: | Keywords: v.net.iso
  Platform: All | Cpu: All
--------------------------+-------------------------------------------------
Changes (by mlennert):

  * platform: MacOSX => All
  * version: 6.4.0 RCs => svn-trunk
  * type: defect => enhancement
  * cpu: OSX/Intel => All
  * milestone: 6.4.0 => 7.0.0

Comment:

Reclassifying this as a wish instead of a bug since this is a feature of
the current version of v.net.iso: all line segments are given the category
number of the distance class they belong to. Thus they cannot be linked to
the table of the original input file, as the segment identifiers have
changed and do not correspond to the original attribute table key field
anymore.

However, I do agree that it might be desirable to implement (some of) the
following:

1) at least create an attribute field containing the min and max distances
of the class. Otherwise, you might forget which distances you used to
create the map and then the cat values are useless for anything else but
ordinal logic.

2) keep the old category values of the input map and create a new column
in the table in which you enter the distance class (preferrably in the
form "min-max") for each line segment. This way one could connect to the
table of the input map if so desired

3) add a flag which would allow to do 2) by updating the table of the
input map instead of creating a new map. No need really to use up disk
space for a map which only contains distance classes if you can just as
easily integrate them into the existing attribute table. Even more
relevant now that Markus' work allows to use quite large networks.

Moritz

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/517#comment:1&gt;
GRASS GIS <http://grass.osgeo.org>

#517: v.net.iso: change output
--------------------------+-------------------------------------------------
  Reporter: effilc36 | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: new
  Priority: minor | Milestone: 7.0.0
Component: default | Version: svn-trunk
Resolution: | Keywords: v.net.iso
  Platform: All | Cpu: All
--------------------------+-------------------------------------------------
Changes (by mlennert):

  * summary: v.net.iso loses or does not create a database connection for
              resulting vector map => v.net.iso: change
              output

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/517#comment:2&gt;
GRASS GIS <http://grass.osgeo.org>

#517: v.net.iso / v.net.alloc: keep original cat values or change output to field
in attribute table instead of new map
--------------------------+-------------------------------------------------
  Reporter: effilc36 | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: new
  Priority: minor | Milestone: 7.0.0
Component: default | Version: svn-trunk
Resolution: | Keywords: v.net.iso
  Platform: All | Cpu: All
--------------------------+-------------------------------------------------
Changes (by mlennert):

  * summary: v.net.iso: change output => v.net.iso / v.net.alloc: keep
              original cat values or change output to field
              in attribute table instead of new map

Comment:

Replying to [comment:1 mlennert]:

> However, I do agree that it might be desirable to implement (some of)
the following:

Just brainstorming here: the same can be said for v.net.alloc.

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/517#comment:3&gt;
GRASS GIS <http://grass.osgeo.org>

#517: v.net.iso / v.net.alloc: keep original cat values or change output to field
in attribute table instead of new map
--------------------------+-------------------------------------------------
  Reporter: effilc36 | Owner: grass-dev@lists.osgeo.org
      Type: enhancement | Status: new
  Priority: minor | Milestone: 7.0.0
Component: Vector | Version: svn-trunk
Resolution: | Keywords: v.net.iso
  Platform: All | Cpu: All
--------------------------+-------------------------------------------------
Changes (by martinl):

  * component: default => Vector

--
Ticket URL: <http://trac.osgeo.org/grass/ticket/517#comment:4&gt;
GRASS GIS <http://grass.osgeo.org>