[OSM-dev] GSoC - Travel Time Analysis

[John Robert Peterson]

If somone were finally to solve the problem of matching up traces to ways,
we would be in a position to extend that to identifying some map errors,
such as missing ways, or changed road layouts.

how to present this information in a useful way is a diferent task, but
worth keeping in mind.

Could I sugest splitting your proposal into to distickt projects: track/way
matcher; system to use that data for trafic flow.

JR

On 24 March 2010 23:12, Graham Jones <grahamjones139 at googlemail.com> wrote:

> Hi Lukas,
> I am glad you are interested in contgributing to OpenStreetMap.
> You will see that today there has been quite a bit of discussion on this
> list about collecting and analysing traffic information.  I am sure you
> could make a valuable contribution to such a project.
> You are suggesting basing a project on the suggestion on the ideas list to
> use the GPX files in the osm database.  The analysis method you develop
> could also be used in a more real time application if someone were to
> develop a service to collect and process GPX traces.
> I recommend that you have a look at our application template and start to
> draft an application based on your email.  The main things to develop are
> the scope of the project (to judge success against), and a project
> plan/timeline to convince yourself (and us) that the project is achievable.
> There is a link from our ideas page to a page to store draft proposals for
> comment if you would like to use it.
>
> Regards
>
> ____________________
> Graham Jones
> (from my phone)
>
> On Mar 24, 2010 10:50 PM, "Lukas Kabrt" <lukas at kabrt.cz> wrote:
>
> Hi,
>
> I would like to introduce myself. My name is Lukas Kabrt and I am
> student at the Czech technical university in Prague. I am maping for
> about a year and I'm really enjoying it. Over the past few months I
> participated in import of administrative boundaries and in import of
> address points in the Czech republic. These two projects gave me a lot
> of experience with handling OSM data.
>
> I would like to use the knowledge in the field of artificial
> intelligence I gained during my studies and apply them in the world of
> OSM. I read through the wiki article GSoC Project Ideas 2010 and I
> like the Travel Time Analysis project [1].
>
> I think this project has a great potentioal. As far as I know, routing
> algorithms estimate travel time by using speed limits or curvature of
> the roads. Using GPS traces from real vehicles will allow more
> accurate estimation of travel time, becouse it will take into accout
> other factors (traffic, condition of the road). With enought data
> available it should be even possible to detect rush hours or different
> traffic patterns through the week (weekdays vs. weekend) and give the
> appropriate travel time estimations.
>
> IMO the biggest challange would be to develop an algorithm which will
> match GPX traces to OSM roads. The algorithm has to deal with noisy
> GPS tracks, not-everywhere-accurate OSM map and it would be nice if it
> can handle low-frequency GPS tracks (e.g. 1point / min).
>
> Within the scope of GSoC '10 I'd like to create application, which
> will take an OSM file and bunch of GPS traces, analyze them, try to
> recognize traffic patterns and create the output file with estimated
> travel times for road segments (something like last year's
> Preprocessor to add altitude information to OSM data). If it prooves
> well it can be extended further.
>
> [1]
> http://wiki.openstreetmap.org/wiki/GSoC_Project_Ideas_2010#Travel_Time_Analysis
>
> --
> Lukas Kabrt
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20100325/ad0960be/attachment.html>