Hi,
I notice a probable problem parsing v.db.connect's -g output. An
extra term containing the layer-name (if present) is added to the
first data column. e.g. if layer 1 had the name "layer_name"
G> v.db.connect -g fields2 fs='|'
1/layer_name|fields2|cat|.../$MAPSET/dbf/|dbf
instead of
1|field
#731: Warming message after removing layer confusing
-+--
Reporter: pvanbosgeo | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority:
#732: Warming message after removing layer confusing
-+--
Reporter: pvanbosgeo | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority:
This is not an issue for gis.m in 6.5. Layer output of v.db.connect
isn't used/parsed, as user's provided layer number is used.
I was not able to find any (easy to spot) way how to name a layer, but
IIRC there are some modules, that add a name to layer during it's
creation.
Maris.
2009/8/24, H
#732: Warming message after removing layer confusing
-+--
Reporter: pvanbosgeo | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: closed
Priority: normal | Milest
Hamish wrote:
Hi,
I notice a probable problem parsing v.db.connect's -g output. An
extra term containing the layer-name (if present) is added to the
first data column. e.g. if layer 1 had the name "layer_name"
...
I am not an expert in these things so I ask: under what conditions
would a v
#733: display lib: support for curveto
-+--
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
Type: enhancement | Status: new
Priority: minor| Milestone: 7.0.0