Hi Marcus, I refer to your previous post: <<< I suggest a service that collects the following data:
collection: * vehicly-category (car,bike,foot,ship,other) * vehicle-type (String, freely chosen with some presets) ** vehicly-subtype (flow, normal, fast) ** used metric (String, freely chosen, presets: fastest, shortest, efficient, scenic, mapping) * average speed in km/h * way-ID, startNode, endNode * day = (weekday,weekend,holiday) * time = (night,morning,afternoon) ** sub-time = (early,mid,late) example: car-fast, 123-456 on way 789 with 78km/h at early morning >>> When I read your post, I just wonder how you store those information above into current data model (node/way/relation)? I though OSM is going to introduce new data model (routing node) to store above information You wrote: <<< (I still am not convinced that having such a thing is a good idea for everyone but you. But you are free to add whatever relation you like to the map and use it yourself. The voting on the page you mentioned has not a single PRO-vote but a lot of CONs. Thus I see it as "declined".) Let`s use another topic or even better the talk-page on your wiki-page to discuss this. It seems to have no immediate relevance to crownsourced metrics. >>> ---> My mistake, sorry for disturb your guys. Please ignore all my posts. Regards, _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing -- View this message in context: http://www.nabble.com/Crowdsourced-costing-tp20798329p20808710.html Sent from the OpenStreetMap - Routing mailing list archive at Nabble.com. _______________________________________________ Routing mailing list [email protected] http://lists.openstreetmap.org/listinfo/routing
