[OSM-dev] GSoC - Travel Time Analysis (classification aproach of Speedcollector)
marcus.wolschon at googlemail.com
Fri Mar 26 16:00:58 GMT 2010
On Fri, Mar 26, 2010 at 12:21 PM, Aditya Vikram Thoomati
<adivik2000 at hotmail.com> wrote:
> Good to see the talk on Travel Time Analysis i would like you to have a
> look at http://www.wsdot.wa.gov/projects/completed.htm and also check out
> hypercube queuing model to have an elevated idea.
Your links seems to point to a site listing 403 Projects where roads
in the US have been
improved or repaired.
> I'm not saying it's easy. A lot of trail and error adjustments will be needed.
> The main point is that the router already does a lot of the work.
I still think your aproach is flawed.
There should be little trial and error required as you are dealing
with exact meassurements to make a a prediction giving certain
of these meassurements more weight then others based on how
closely they resemble the situation you want to predict.
You start with gpx-traces containing many location- and speed-
information. You also start with a vector map.
But then why divide your traces by timestamp instead of referencing
2 minutes is nothing on a motorway but lets you cross a good part
of a city driving a green wave on a major road.
>such as road maintenance or a car crash that cause
>motorists traveling in both directions to slow down to take a peek.
These events should be filtered out from the start if they do not occur
every day in the same place.
Expected, general travel times and delays due to random events
are 2 different problems.
That there was a car accident last week does not affect the estimate
of how long you are likely to travel by the time you react the start of
a segment now.
The most likely source of information about short time traffic obstructions
is TMC and it usually tells you the expected delay. So this needs different
issue not be addressed now and certainly not here.
More information about the dev