On Wed, 3 Dec 2008 10:15:55 +0200, "Jaak Laineste" <[EMAIL PROTECTED]> wrote: > Hi, > > Wouldn't it be too complicated to have proper coverage? Some of the data, > like average speed, is also very hard easy to estimate without really good > experiences or specialist analysis. And average speed is most important > data > for fastest way calculation, it would be too easy to get garbage-in > garbage-out situation.
This is indeed a risk. However for the "proper coverage"-argument I can offer the gravefull degration by having vehicle-types and times grouped and ignoring single parameters untill a proper number of meassurements exist for an answer. It will at all times be the best answer that can be given but seldomly (it ever) be for the exact case that was asked for. It can not hurt to collect these. I think about gathering the average speed from navigation-software and mapping-software running on a device in the driving vehicle and averaged over a complete way until the vehicle leaves the way. Maybe we should indeed filter out meassurements over distances that are too short to be meaningfull. Do you agree? > I would suggest to have live traffic event data, collectable mostly using > mobile devices from the road. The events could be: > a) road temporarily blocked. No routing over here. > b) road speed disturbance (e.g. traffic jam). Calculate extra time for > routing. > c) other traffic-related events: e.g. mobile speed trap. Notify user, > perhaps does not affect routing. This sounds like an excellent separate service using the same meassurement. Such data can be centrally collected and merged with data about road-construction -sites and published traffic-diversions/jams. Programs that can make use of it can then either request the current state from a central server (if they have internet at the moment) or even exchange such data among each other in the (very seldom) case that 2 such vehicles pass within wifi-distance. While one could host both services on one location I don`t think we should join them as they are usefull for different situations (metrics can be used on a website without actually driving) and require somewhat different data to be collected. > With mobile data collection it should be very easy, possible to be entered > while driving (click "mark traffic event to current location", select type > from short list, OK), so any extra data (like estimated duration of event) > should be optional. Maybe for block duration is essential: it could be 3 > month roadworks, or just 30 minutes due to an accident. > > Technically, the "mark" event is then attached to certain road segment, > which is found automatically from user's current GPS location. This sounds like an excellent idea. Do you offer to implement a prototype of it or specify a protocoll or user-interface for it? I would really like to see such a thing happen. Marcus _______________________________________________ Routing mailing list Routing@openstreetmap.org http://lists.openstreetmap.org/listinfo/routing
