On 30/09/13 09:45, Štěpán Turek wrote:
Hi,
working on integration of turns support into GRASS 7 I see two
possibilities how to integrate creation of the turntable.
New module v.net.turntable can be added,which will manage creation of
the turntable.
There already exists v.net module which is doing maintenance and
preparation of a network for a network analysis. Creation of the
turntable can be considered also like preparation of network for
analysis. Also in future it would be good to add into connect operation
support for modification of the turntable. And this will require
extension of the v.net interface for the turntable support.
Suggestion of interface changes of v.net module:
operation=turntable - create turntable (what v.net.turntable do)
tlayer and tuclayer - two layers where information about turns is stored
(for description see [1])
- these two parameters would need to be added into v.net even if
v.net.turntable would exist in order to be the connect operation able to
adjust the turntable. Adding of these parameters could be avoided if
another connect method would be implemented into v.net.turntable, but it
would be probably quiet confusing for user.
-t flag if this flag would be attached, the connect method would work
with the turntable support
On the other hand v.net module interface will become even more complex
and it can become difficult to use by some users.
Even if the complexity might be increased (I don't find v.net _that_
complex at this point), I would go for the integration of turntables in
v.net. It seems the logical place for everything concerning network
preparation and maintenance. If complexity really becomes a problem,
there is always the option of creating wrapper scripts which hide some
of the complexity.
Moritz
_______________________________________________
grass-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/grass-dev
