v.net: turn_uc_layer -> turn_cat_layer (https://trac.osgeo.org/grass/ticket/2409)

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@63720 15284696-431f-4ddb-bdfa-cd5b030d7da7

vector/v.net/args.c

@@ -118,7 +118,7 @@ void define_options(struct opt *opt)
      " The categories are used in turntable. Format: layer number[/layer name]. "
      "Required for operation 'turntable'.");
     opt->tucfield->answer = "4";
-    opt->tucfield->key = "turn_uc_layer";
+    opt->tucfield->key = "turn_cat_layer";
     opt->tucfield->required = NO;
     opt->tucfield->guisection = _("Turntable");
 }

vector/v.net/v.net.html

@@ -83,13 +83,13 @@ The <em>turntable</em> operation creates a turntable
 with the costs for every possible 
 turn on every possible node (intersection, crossroad) in given layer (arc_layer). 
 U-turns are taken in account too.
-Turntable is created in <b>turn_layer</b> and <b>turn_uc_layer</b>.
+Turntable is created in <b>turn_layer</b> and <b>turn_cat_layer</b>.
 Building the turntable allows you to model e.g. trafic code, where some turns 
 may be prohibited.
 If features in analyzed network are changed, the turntable must be created again
 (e.g. it includes v.net connect operation).
 Turntable name consists of output vector map name + "_turntable_" + "t" + "_" + turn_layer +
- "_" + "tuc" + "_" + turn_uc_layer + "_" + "a" + "_" + arc_layer  e. g. roads_turntable_t_3_tuc_4_a_1
+ "_" + "tuc" + "_" + turn_cat_layer + "_" + "a" + "_" + arc_layer  e. g. roads_turntable_t_3_tuc_4_a_1
 
 <p>These modules are able to work with the turntable: 
 <em><a href="v.net.alloc.html">v.net.alloc</a></em>,