Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It depends on what you want to optimise (you could let the user choose):</p> <p>If you want the shortest route, the cost of an edge is simply the length of the street.</p> <p>If you want the fastest route, the cost would be the expected time to travel the street.</p> <p>If you want the most economical route in terms of fuel consumption, the cost would be `street length / miles per gallon (expected speed)</p> <p>The fuel economy varies by car, but you can assume that the economy (in miles per gallon) grows linearly with speed up until a certain speed, then starts to drop off <sup>[<a href="http://en.wikipedia.org/wiki/File%3aFuel_economy_vs_speed_1997.png" rel="nofollow">Wikipedia</a>]</sup>. As you can always travel slower than the max. speed, assume a constant efficiency. <code>(miles/gallon) / (miles/hour) = (hours/gallon)</code>, so the cost is approximately proportional to time with a speed limit applied at the car's most efficient speed (which could be entered by the user).</p> <p>If you have a source of prepared congestion data, use it to determine the expected car speed. </p> <p>One way to measure the expected time of travel by observing the cars is to take an average over all cars that left the street in the past {interval} (hour? minute? only the very last car? the last ten cars?). However, that doesn't pick up congestion too quickly. You can take the average speed of all cars still present in the speed. However, this will overestimate the effect of traffic lights.</p> <p>You could take the average speed of all cars that <em>entered</em> the street in the last one hour. <code>average(distance traveled/time spent)</code> or <code>average(distance traveled)/average(time spent)</code>. If the street is devoid of life, simply take its speed limit or use a longer measurement interval.</p> <p>Remember the expected speed may be different in both directions (depending on your source of data), so always use pairs of directed edges and measure in each direction separately.</p> <p>[1] <a href="http://en.wikipedia.org/wiki/File:Fuel_economy_vs_speed_1997.png" rel="nofollow">http://en.wikipedia.org/wiki/File:Fuel_economy_vs_speed_1997.png</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload