Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow visualizing, modifying and creating TAZ #3425

Closed
behrisch opened this issue Sep 13, 2017 · 4 comments

Comments

@behrisch
Copy link
Contributor

commented Sep 13, 2017

new editing mode TAZ

TAZ Frame Functions:

  • create TAZ: create new taz in the same way as a polygon (attributes: id, shape, color) ,
    • checkbox: useEdgesInShape
  • Edit TAZ (Frame active after clicking on a TAZ):
    • show current taz id (no editor of attributes here, this is done in inspect mode)
    • Edges
      • Button: select edges (changes current selection so that all edge of the TAZ are selected)
      • Button: used selected (changes TAZ edges to current selection) - default weight 1
        • when switching from TAZ-Mode to select-mode and back, the currently edited TAZ must be remembered
      • used edges in shape (see edgesInDistrict.py)
  • Weights
    • color mode (depart, arrival, default) - sets current edge coloring mode, reset when leaving TAZ mode,
    • attributes departWeight, arrivalWeight
    • clicking on an edge shows its current taz-edge values . Editing the value updates it for that edge and all edges of the current taz that are currently selected
    • Button: normalize weights byLength

new objects:

  • GNETAZ (id, color, shape, edges)
  • GNETAZEdge (departWeight, arrivalWeight)

@behrisch behrisch added this to the 2.0.0 milestone Oct 28, 2017

@namdre namdre modified the milestones: 2.0.0, 1.1.0 May 16, 2018

@palvarezlopez palvarezlopez self-assigned this Sep 4, 2018

@palvarezlopez palvarezlopez added the branch label Sep 4, 2018

@palvarezlopez palvarezlopez changed the title allow visualizing, modifying and creating TAZ (trac #3425) Allow visualizing, modifying and creating TAZ Sep 4, 2018

@palvarezlopez

This comment has been minimized.

Copy link
Contributor

commented Oct 8, 2018

@namdre Can we considerate TAZ as the first GNERoute Element in Netedit?

@namdre

This comment has been minimized.

Copy link
Contributor

commented Oct 9, 2018

A taz can be the first or the last element of a route definition. Actualy in this case it would be a trip rather than a route because a vehicle can only use it after filling in the missing edges with a router (using DUAROUTER or SUMO).

@palvarezlopez

This comment has been minimized.

Copy link
Contributor

commented Oct 9, 2018

With GNERoute I mean the following hierarchy:

GNERouteElement
|
|-> GNERoute
|-> GNEVehicle
|-> GNEVehicleType
|-> GNETAZ
|-> GNETAZEdge
....

@namdre

This comment has been minimized.

Copy link
Contributor

commented Oct 9, 2018

If GNERouteElement is meant to encapsulate elements of a route file than no. (Also, I would call it GNERouteFileElement in this case).

TAZ and TazEdge are part of the static input which is always loaded from an additional file (not incremental like a route file). A vehicle definition may reference a TAZ by its ID.
Thus, when loading and saving, TAZ are handled like additional elements.

Since their manipulation is more complex than that of other additionals, they can get their own mode. (Similar to how crossings get their own edit mode).

palvarezlopez added a commit that referenced this issue Oct 10, 2018
palvarezlopez added a commit that referenced this issue Oct 11, 2018
palvarezlopez added a commit that referenced this issue Oct 11, 2018
palvarezlopez added a commit that referenced this issue Oct 16, 2018
palvarezlopez added a commit that referenced this issue Oct 16, 2018
palvarezlopez added a commit that referenced this issue Oct 17, 2018
palvarezlopez added a commit that referenced this issue Oct 17, 2018
palvarezlopez added a commit that referenced this issue Oct 17, 2018
palvarezlopez added a commit that referenced this issue Oct 18, 2018
palvarezlopez added a commit that referenced this issue Oct 18, 2018
palvarezlopez added a commit that referenced this issue Oct 18, 2018
palvarezlopez added a commit that referenced this issue Oct 18, 2018
palvarezlopez added a commit that referenced this issue Oct 19, 2018
palvarezlopez added a commit that referenced this issue Oct 29, 2018
palvarezlopez added a commit that referenced this issue Nov 2, 2018
palvarezlopez added a commit that referenced this issue Nov 5, 2018
palvarezlopez added a commit that referenced this issue Nov 5, 2018
palvarezlopez added a commit that referenced this issue Nov 6, 2018
palvarezlopez added a commit that referenced this issue Nov 7, 2018
palvarezlopez added a commit that referenced this issue Nov 7, 2018
palvarezlopez added a commit that referenced this issue Nov 7, 2018
palvarezlopez added a commit that referenced this issue Nov 7, 2018
palvarezlopez added a commit that referenced this issue Nov 8, 2018
palvarezlopez added a commit that referenced this issue Nov 8, 2018
palvarezlopez added a commit that referenced this issue Nov 8, 2018
palvarezlopez added a commit that referenced this issue Nov 9, 2018
palvarezlopez added a commit that referenced this issue Nov 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.