let ptlines2flows.py deal with unordered stops (trac #3444)

[behrisch]

• add option for generating stop pois for each line to help finding ordering problems.

  • same color for each line
  • poi ids should take the form 1_a 2_a 3_a (for line with ref a)

• add option for warning if successive stops have (airline) distance above a specified threshold

• add option for fixing out of order stops automatically

  • at least if two stops on the same edge and misordered this should be easy to detect and fix
  • simple 2-stop inversions could also be detected based on distance comparisons.

• ensure that the output flows are valid for intermodal routing

  • if the simulation of trips.trips.xml generates errors concerning stops that cannot be used, the corresponding should be commented out in the resulting output flow file

Migrated from http://sumo.dlr.de/ticket/3444

{
    "status": "new", 
    "changetime": "2017-09-18T08:04:52Z", 
    "description": "- add option for generating stop pois for each line to help finding ordering problems.\n  - same color for each line\n  - poi ids should take the form 1_a 2_a 3_a (for line with ref a)\n\n- add option for warning if successive stops have (airline) distance above a specified threshold\n\n- add option for fixing out of order stops automatically\n  - at least if two stops on the same edge and misordered this should be easy to detect and fix\n  - simple 2-stop inversions could also be detected based on distance comparisons.\n\n- ensure that the output flows are valid for intermodal routing\n  - if the simulation of trips.trips.xml generates errors concerning stops that cannot be used, the corresponding <stop> should be commented out in the resulting output flow file\n\n", 
    "reporter": "namdre", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1505721892287117", 
    "component": "tools (python)", 
    "summary": "let ptlines2flows.py deal with unordered stops", 
    "priority": "major", 
    "keywords": "", 
    "time": "2017-09-18T07:19:55Z", 
    "milestone": "1.0.0", 
    "owner": "laemmel", 
    "type": "enhancement"
}

[behrisch]

@namdre changed description from:

• add option for generating stop pois for each line to help finding ordering problems.

  • same color for each line
  • poi ids should take the form 1_a 2_a 3_a (for line with ref a)

• add option for warning if successive stops have (airline) distance above a specified threshold

• add option for fixing out of order stops automatically

  • at least if two stops on the same edge and misordered this should be easy to detect and fix
  • simple 2-stop inversions could also be detected based on distance comparisons.

to:

• add option for generating stop pois for each line to help finding ordering problems.

  • same color for each line
  • poi ids should take the form 1_a 2_a 3_a (for line with ref a)

• add option for warning if successive stops have (airline) distance above a specified threshold

• add option for fixing out of order stops automatically

  • at least if two stops on the same edge and misordered this should be easy to detect and fix
  • simple 2-stop inversions could also be detected based on distance comparisons.

• ensure that the output flows are valid for intermodal routing

  • if the simulation of trips.trips.xml generates errors concerning stops that cannot be used, the corresponding should be commented out in the resulting output flow file

[namdre]

could be more urgent due to urban_mobility requirements but the analysis has not been done yet.