Talk:Proposed features/Default Maxspeed

From OpenStreetMap Wiki
Jump to: navigation, search
  • default-maxspeeds normally grouped by vehicle-types and not by waytypes.. so this proposal needs a change.
  • not in my area - it's by way type, then if there are differences for certain vehicle types (hgv, psv) those are explicitly marked with signs. I used my own personal experience when I wrote this. I'll update it to include both possibilities --Cohort 04:22, 25 September 2008 (UTC)
  • default-maxspeeds are attributes of a country not of streets where no speedlimit-signs are. --Cbm 13:03, 12 August 2008 (UTC)
  • They may be attributes of a country, but many locales are allowed to override it. Many times, only by lowering the max limit. State can override country, county can override state, city can override county. --Cohort 10:57, 20 September 2008 (UTC)
  • this feature have no significant value except for people who want to make an electronic map with speed warnings, speed cameras should be tagged with speed limits, so for those types of maps that should be covered. for route planning, a default value of 80 or 100km/h would suffice, as a route planner only should give you the quickest route, and not an estimated travel time. --Skippern 00:46, 15 September 2008 (UTC)
  • I disagree with Skippern, this is relevant information – why shouldn’t a route planner be able to give you an estimated travel time? Even Google Maps does. However, I think the proposal has some problems, such as that borders might not be downloaded with a small area and that it is not generic enough – we should be able to set maxspeeds depending on vehicle, too, and access rights for different vehicles and waytypes, without inventing some completely new tagging. --Tordanik 07:15, 15 September 2008 (UTC)
  • As response to Tordanik, it doesn't mean much difference to expected travel time (unless we talk long jurneys, and then you would need to plan length of breaks as well) if you calculate with 80km/h or 100km/h, besides when passing through populated areas you would expect to see traffic interfearing with planned speed. Anyway, the time you get from a route planner is only an estimate as it contains no or extremely little traffic data. My argument stays valid. --Skippern 01:06, 17 September 2008 (UTC)

Ways to assure that the consumer downloads this tag?

  • there is no way to assure that the user has downloaded such a large area that any part of the surrounding border with this tag is included. --Lulu-Ann 00:33, 15 September 2008 (UTC)
  • I agree that this is an issue and warrants further discussion. And in fact is big enough an issue that it should be a separate discussion. --Cohort 10:52, 20 September 2008 (UTC)

One idea would be to apply the tag to the place (node|way) associated with the area and rely on is_in=* or similar to call on it. The imported TIGER data in the USA already includes a county ref tag on every way, for example. --Cohort 10:52, 20 September 2008 (UTC)

Also see