Connection-aware routing when using CHRouter (trac #303)

[behrisch]

Routers (DUAROUTER/JTRROUTER) consider vehicle types when choosing an edge during route computation. Still, they do not know whether a vehicle can actually reach an edge - because it's predecessor is only connected by a link outgoing from a lane where the vehicle's class is not allowed.

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

{
    "status": "reopened", 
    "changetime": "2015-02-23T12:18:24Z", 
    "description": "Routers (DUAROUTER/JTRROUTER) consider vehicle types when choosing an edge during route computation. Still, they do not know whether a vehicle can actually reach an edge - because it's predecessor is only connected by a link outgoing from an edge where the vehicle's class is not allowed.\n", 
    "reporter": "junghans", 
    "cc": "", 
    "resolution": "", 
    "_ts": "1424693904951061", 
    "component": "routing (DUAROUTER)", 
    "summary": "Connection-aware routing when using CHRouter", 
    "priority": "minor", 
    "keywords": "", 
    "time": "2010-05-07T08:55:31Z", 
    "milestone": "1.1.0", 
    "owner": "behrisch", 
    "type": "defect"
}

[behrisch]

• @behrisch changed milestone from "0.12.0" to "0.12.1"
• @behrisch changed version from "0.11.1" to "SVN"

[behrisch]

@lbieker changed milestone from "0.12.1" to "1.0.0"

[behrisch]

• @lbieker changed milestone from "1.0.0" to "0.13.0"
• @lbieker changed owner from "" to "behrisch"
• @lbieker changed status from "new" to "assigned"

[behrisch]

@behrisch changed milestone from "0.13.0" to "1.0.0"

[behrisch]

@namdre committed a5c53e2 (aka r17921):
connection aware routing. refs #303. needs some more tests

[behrisch]

• @namdre committed e56e5d8 (aka r17926):
  added test. fix Connection-aware routing when using CHRouter (trac #303) #303
• @namdre changed resolution from "" to "fixed"
• @namdre changed status from "assigned" to "closed"

[behrisch]

• @namdre commented:

The issue is still open when using CH. Fixing this would require a large rewrite of internal data structures since it currently isn't detailed enough to represent lane-level routing information.
The suggested work-around is to use CHWrapper instead.

• @namdre changed component from "routing (DFROUTER, JTRROUTER)" to "routing (DUAROUTER)"
• @namdre changed milestone from "1.0.0" to "1.1.0"
• @namdre changed priority from "major" to "minor"
• @namdre changed resolution from "fixed" to ""
• @namdre changed status from "closed" to "reopened"

[behrisch]

@namdre changed summary from "Connection-aware routing" to "Connection-aware routing when using CHRouter"

[behrisch]

@namdre committed 54726af (aka r17947):
flagging know bug refs #303