Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

26. Sep 2018 06:32 by mark+...@carnildo.com : > On Tue, 25 Sep 2018 08:09:12 +0200 > Florian Lohoff <> f...@zz.de > > wrote: > >> On Wed, Sep 19, 2018 at 11:24:00AM -0700, Mark Wagner wrote: >> > My point is that no such guarantee exists for roads

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Tue, Sep 25, 2018 at 11:34 PM Mark Wagner wrote: > On Tue, 25 Sep 2018 08:09:12 +0200 > Florian Lohoff wrote: > > > On Wed, Sep 19, 2018 at 11:24:00AM -0700, Mark Wagner wrote: > > > My point is that no such guarantee exists for roads without speed > > > limit signs. Yes, the numeric limit

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On 26/09/2018 09:12, Colin Smale wrote: On 2018-09-26 06:32, Mark Wagner wrote: That's not what I said.  To repeat, my point is that, at least locally, ... Sorry Mark, you are wrong. There is no guarantee, signposted or not. I think the key point here is "at least locally".  Certain things

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On 2018-09-26 06:32, Mark Wagner wrote: > That's not what I said. To repeat, my point is that, at least locally, > a signposted speed limit *is* a guarantee that, for an ordinary vehicle > traveling under ordinary conditions, the speed is reasonable. An > unsigned speed limit, on the other

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

In Nederland advisory speed signs are used for this purpose. These do not alter speed limit, but indicate the local safe speed under normal conditions. I do not see how this fact could help with the subject at hand, though. Good luck with that! Op wo 26 sep. 2018 om 06:33 schreef Mark Wagner : >

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Tue, 25 Sep 2018 08:09:12 +0200 Florian Lohoff wrote: > On Wed, Sep 19, 2018 at 11:24:00AM -0700, Mark Wagner wrote: > > My point is that no such guarantee exists for roads without speed > > limit signs. Yes, the numeric limit for something like Glenwood > > Road might be 50 mph, but the

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

> On Sep 25, 2018, at 3:09 PM, Florian Lohoff wrote: > > Sign posted speeds dont are not telling you "this is the speed which is > safe for 100% of the vehicles" but this is the maximum allowed. > You are still required to drive safely. +1 Even variable speed roads (where the signs change

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018 at 11:24:00AM -0700, Mark Wagner wrote: > My point is that no such guarantee exists for roads without speed limit > signs. Yes, the numeric limit for something like Glenwood Road might > be 50 mph, but the road was designed around farm trucks going no more > than 20 mph, and

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Oh, I think you found an error in the default speed limits document. I will go through the table from A to Z within the next few days or even today to correct this at places where the gross vehicle weight is meant instead of the actual weight. I guess then maxspeed:conditional=xx @ (weight >

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

sent from a phone > On 22. Sep 2018, at 23:48, Tobias Zwick wrote: > > What do you mean, what is the difference? > > maxspeed:conditional=xx @ (weight > yy) would be the former or the latter? in German: zulässiges Gesamtgewicht vs. Gewicht ___

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

What do you mean, what is the difference? maxspeed:conditional=xx @ (weight > yy) would be the former or the latter? On 22/09/2018 16:20, Martin Koppenhoefer wrote: > > > sent from a phone > >> On 22. Sep 2018, at 14:22, Tobias Zwick wrote: >> >> But let's look at some other countries for

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wednesday, September 19, 2018, Tobias Zwick wrote: >>> Anyway, for a beginner : is one key even better ? -> should we allow >>> “maxspeed=no_sign” ? Or/and “maxspeed=default” ? >> >> Way too ambiguous to be remotely workable in North America. > > Is it? I think what djakk is arguing for, and

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

You just forgot to mention the table would solve this :-) https://wiki.openstreetmap.org/wiki/Default_speed_limits#The_table And there should be a link to it on these pages : https://wiki.openstreetmap.org/wiki/Speed_limits#Country_code.2Fcategory_conversion_table

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

sent from a phone > On 22. Sep 2018, at 14:22, Tobias Zwick wrote: > > But let's look at some other countries for the default urban speed limit. are these actual weight numbers, or max gross weight? Cheers, Martin ___ Tagging mailing list

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Well said, I agree wholeheartedly. A local, anecdotal view is in itself not enough to produce a data model that works for everyone. On 2018-09-22 14:22, Tobias Zwick wrote: > Tagging an implicit speed limit explicitly for example in town with > maxspeed=50 is straightforward enough for Germany.

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Tagging an implicit speed limit explicitly for example in town with maxspeed=50 is straightforward enough for Germany. It seems natural that no specialist knowledge is required for that kind of thing. For a German. But let's look at some other countries for the default urban speed limit. Spain

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Fri, Sep 21, 2018 at 6:05 PM Martin Koppenhoefer wrote: > > > sent from a phone > > > On 19. Sep 2018, at 21:16, Tobias Zwick wrote: > > > > This is a good argument against tagging an explicit maxspeed=X when > > there is actually no speed limit sign around (X is what the OSM mapper > > by

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

sent from a phone > On 19. Sep 2018, at 22:12, Jérôme Seigneuret > wrote: > > highway:legal_type=urban or highway:legal_type:FR=agglomération I agree with the idea but would use a different tag, something like highway:zone=urban (or whatever you need to distinguish). “legal_type” can

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

sent from a phone > On 19. Sep 2018, at 22:09, Tobias Zwick wrote: > > This is France though. The abutters-key would only need to be used in > the United States in order to infer the default speed limits as only > there, a difference is made between residence districts and business >

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

sent from a phone > On 19. Sep 2018, at 21:16, Tobias Zwick wrote: > > This is a good argument against tagging an explicit maxspeed=X when > there is actually no speed limit sign around (X is what the OSM mapper > by his knowledge about the law thinks should be the default limit here).

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

In Poland legal status of road is very often unrelated to OSM tag of road. For example one may have highway=residential inside legal urban area and outsidelegal urban area. 19. Sep 2018 15:25 by djakk.dj...@gmail.com : > By the way, we should de-correlate the

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018 at 9:31 PM Tod Fitch wrote: > > > On Sep 19, 2018, at 6:59 PM, Paul Johnson wrote: > > > > > > An example of an interstate I would call trunk would be I 70 between I > 68 and I 76, given that those two are the two closest junctions. Motorways > should terminate at an

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

> On Sep 19, 2018, at 6:59 PM, Paul Johnson wrote: > > > An example of an interstate I would call trunk would be I 70 between I 68 and > I 76, given that those two are the two closest junctions. Motorways should > terminate at an interchange with another motorway, not an at-grade >

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018 at 4:51 PM Joseph Eisenberg wrote: > > > Kevin Kenny: > >> >> Not all Interstates *ought* to be tagged as motorways. A case in point >> is Interstate 93 in Franconia Notch, New Hampshire, which *ought* >> to be a trunk (it's a two-lane road with a centre guard rail that was

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

See https://github.com/westnordost/countryboundaries It's per node. Size and supported admin levels depend on the data you stick in there. (Also, the faster the access should be, the bigger the file.) The default data is a geoJson file from the JOSM project which has all the countries, and

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

> > I’m encouraged by this: > >”3. removes superfluous country ISO-code. Country boundaries information >is already available in the OSM > database, data users can just use a >(reverse) geocoder to find where a street is. >(I wrote Java library recently that does this offline in

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Kevin Kenny: > > Not all Interstates *ought* to be tagged as motorways. A case in point > is Interstate 93 in Franconia Notch, New Hampshire, which *ought* > to be a trunk (it's a two-lane road with a centre guard rail that was added > long after the initial construction.) > Amazing! I thought

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018 at 4:34 PM Tobias Zwick wrote: > 2. US interstate in Montana (US-MT): > highway=motorway + source:maxspeed=US-MT:interstate >vs > highway=motorway + maxspeed:signed=no + ref~^I >(maybe ref-starts-with-"I" is not necessary because all interstates > are

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

>> Anyway, for a beginner : is one key even better ? -> should we allow >> “maxspeed=no_sign” ? Or/and “maxspeed=default” ? > > Way too ambiguous to be remotely workable in North America. Is it? I think what djakk is arguing for, and me as well, is to separate the information stored in

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, 19 Sep 2018 at 13:30, Joseph Eisenberg > mailto:joseph.eisenb...@gmail.com>> wrote: > > So on the boundary=administrative admin_level=6 for Rogers > County, we could have something like maxspeed:type:default=45mph Impossible in France, Urban maxspeed area isn't in

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

This is France though. The abutters-key would only need to be used in the United States in order to infer the default speed limits as only there, a difference is made between residence districts and business districts. In France and/or the rest of the world, what about perhaps urban=yes/no?

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

An other example : http://www.mapillary.com/map/im/k43_fyX2AuL594qhVuSY7w/photo abutter=residential and highway:legal_type=rural Le mer. 19 sept. 2018 à 21:41, djakk djakk a écrit : > Sound cool but there may be a gap between the reality and the law : > example : it looks like the countryside

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Sound cool but there may be a gap between the reality and the law : example : it looks like the countryside but legally it is inside the built up area : http://www.mapillary.com/map/im/Dybpz_fHGEmWdLjfG7OMvQ/photo There should be 2 tags : abutters=rural and highway:legal_type=built_up djakk Le

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Okay, so US-American legislation usually differs between "residential district" and "business district" for maxspeed defaults, as opposed to "built-up area" in most other countries. Actually, there is a tag to denote that a street is in a residential district or business district. It comes from

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, 2018-09-19 at 21:16 +0200, Tobias Zwick wrote: > This is a good argument against tagging an explicit maxspeed=X when > there is actually no speed limit sign around (X is what the OSM > mapper > by his knowledge about the law thinks should be the default limit > here). > > Unfortunately,

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

This is a good argument against tagging an explicit maxspeed=X when there is actually no speed limit sign around (X is what the OSM mapper by his knowledge about the law thinks should be the default limit here). Unfortunately, this is still common practice because of the lack of a scheme for

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, 19 Sep 2018 13:54:47 +0200 Tobias Zwick wrote: > This does not present a problem: > > > The first set > > Well, as you write yourself, they may be authorized to set own speed > limits, but they need to signpost it. > > > The second > > So these are the type of regulations I mean

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, 2018-09-19 at 18:04 +0200, Colin Smale wrote: > In many countries in Europe, the "Welcome to XXX" sign as you enter a > town/village has the effect of delineating the "built-up area" for > traffic purposes and introduces a specific speed limit, without any > numbers being mentioned. In the

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018, 10:22 djakk djakk wrote: > Yes Paul, I should not forget the beginners ... > > I am not a beginner anymore but I still found “source:maxspeed=“ for roads > a little confusing, as we should use “source=“ only (?) on the metadata (on > the changeset). > Specific keys that

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

In many countries in Europe, the "Welcome to XXX" sign as you enter a town/village has the effect of delineating the "built-up area" for traffic purposes and introduces a specific speed limit, without any numbers being mentioned. In the countries I know in Northern Europe it means "maxspeed=50

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Yes Paul, I should not forget the beginners ... I am not a beginner anymore but I still found “source:maxspeed=“ for roads a little confusing, as we should use “source=“ only (?) on the metadata (on the changeset). Anyway, for a beginner : is one key even better ? -> should we allow

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Hi, tagging list I just join it. For your information there is part of proposed tagging schema in french subject discuss with @djakk.dj...@gmail.com https://lists.openstreetmap.org/pipermail/talk-fr/2018-September/090189.html Values of legal type can be thinking in specific territory area and

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018, 08:27 djakk djakk wrote: > By the way, we should de-correlate the legal status of an highway from the > highway tag : with the key highway:legal_type, values : business_area or > residential_area or an other local legal classification. A highway=tertiary > could also be

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

By the way, we should de-correlate the legal status of an highway from the highway tag : with the key highway:legal_type, values : business_area or residential_area or an other local legal classification. A highway=tertiary could also be highway:legal_type=residential_area djakk Le mer. 19

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Hello ! There is also speed limit areas, a sign is posted at the entrance of the area. Imagine that a big part of Paris becomes a 30km/h area. Is it possible to create a big polygon tagged with maxspeed=30, each street inside inherits the maxspeed value of the big polygon ? (to escape the

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

This is an interesting idea (inspired by the ongoing discussion about mapping language borders?), but unfortunately it wouldn't work. Sorry for linking to this all the time but it is really necessary in order to understand the big picture: https://wiki.openstreetmap.org/wiki/Default_speed_limits

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018 at 7:18 AM Greg Troxel wrote: > > Philip Barnes writes: > > > And if the default actually applies, or has it been overriden by local > signage. > > > > I am not convinced that a default limit helps, if no speed limit has > been surveyed I would prefer that box not to be

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, Sep 19, 2018 at 7:09 AM Greg Troxel wrote: > Tod Fitch writes: > > >> On Sep 18, 2018, at 6:19 PM, Joseph Eisenberg < > joseph.eisenb...@gmail.com> wrote: > >> > >> So on the boundary=administrative admin_level=6 for Rogers County, we > could have something like

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Philip Barnes writes: > And if the default actually applies, or has it been overriden by local > signage. > > I am not convinced that a default limit helps, if no speed limit has been > surveyed I would prefer that box not to be displayed in my app. > a. It will not give me wrong and possibly

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Colin Smale writes: > A "maximum" speed does not mean an "advised" speed. If you are driving > at an unsuitable speed, below the posted maximum, in Europe you will not > get a ticket for "speeding" as such but you may get one for "dangerous > driving" or something similar. The obligation to

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Tod Fitch writes: >> On Sep 18, 2018, at 6:19 PM, Joseph Eisenberg >> wrote: >> >> So on the boundary=administrative admin_level=6 for Rogers County, we could >> have something like maxspeed:type:default=45mph > > Except that more typically there will be different default speed > limits on

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

This does not present a problem: > The first set Well, as you write yourself, they may be authorized to set own speed limits, but they need to signpost it. > The second So these are the type of regulations I mean with "default speed limits". > The third law As Martin Koppenhoefer stated on

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

> (Incidentally, I think 7 of the 8 Australian states & territories have > the same limits?) Almost. Western Australia and Northern Territory has 110 km/h, Tasmania 100 km/h only on concrete or asphalt surface and 80 km/h otherwise; Northern Territory furthermore sets the speed limit within

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

A "maximum" speed does not mean an "advised" speed. If you are driving at an unsuitable speed, below the posted maximum, in Europe you will not get a ticket for "speeding" as such but you may get one for "dangerous driving" or something similar. The obligation to drive in a safe way overrides all

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

sent from a phone > On 19. Sep 2018, at 08:01, Tod Fitch wrote: > > California, and I suspect most if not all other states, has a reasonable and > prudent clause in the speed statutes too. So depending on conditions, > especially weather conditions, theoretically you can get a speeding

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

And if the default actually applies, or has it been overriden by local signage. I am not convinced that a default limit helps, if no speed limit has been surveyed I would prefer that box not to be displayed in my app. a. It will not give me wrong and possibly costly information. b. It makes it

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

sent from a phone > On 19. Sep 2018, at 03:19, Joseph Eisenberg > wrote: > > So on the boundary=administrative admin_level=6 for Rogers County, we could > have something like maxspeed:type:default=45mph and if your app shows the wrong speed limit you simply have to check additionally all

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Wed, 19 Sep 2018 at 13:30, Joseph Eisenberg wrote: > So on the boundary=administrative admin_level=6 for Rogers County, we > could have something like maxspeed:type:default=45mph Just after crossing over the border into the state of Queensland, you have this sign:

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

> On Sep 18, 2018, at 6:19 PM, Joseph Eisenberg > wrote: > > So on the boundary=administrative admin_level=6 for Rogers County, we could > have something like maxspeed:type:default=45mph Except that more typically there will be different default speed limits on each of the various OSM

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Tue, 18 Sep 2018 20:36:06 +0200 Tobias Zwick wrote: > From your anecdote, it seems, an implicit speed limit tagging scheme > is even more important in the US than for example in the UK In my part of the US, a meaningful implicit speed limit tagging scheme is impossible, due to the three sets

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

So on the boundary=administrative admin_level=6 for Rogers County, we could have something like maxspeed:type:default=45mph On Wed, Sep 19, 2018 at 8:21 AM Paul Johnson wrote: > > > On Tue, Sep 18, 2018 at 1:17 PM Tod Fitch wrote: > >> >> > On Sep 18, 2018, at 10:41 AM, Tobias Zwick wrote: >>

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Tue, Sep 18, 2018 at 1:17 PM Tod Fitch wrote: > > > On Sep 18, 2018, at 10:41 AM, Tobias Zwick wrote: > > > > There is a misunderstanding. > > > > So, there are 597 towns, 77 counties and 2 councils in the state of > > Oklahoma and I understand that you want to say that all these entities >

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Hey, I did not claim that such explanatory signboards are always to be expected at country borders. Just saying that it is at least common in Europe. Anyway, so, in order for data consumers to infer a concrete speed limit from a road that has no explicit speed limit posted, the different road

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

> On Sep 18, 2018, at 10:41 AM, Tobias Zwick wrote: > > There is a misunderstanding. > > So, there are 597 towns, 77 counties and 2 councils in the state of > Oklahoma and I understand that you want to say that all these entities > have authority over defining the default speed limit(s) within

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

There is a misunderstanding. So, there are 597 towns, 77 counties and 2 councils in the state of Oklahoma and I understand that you want to say that all these entities have authority over defining the default speed limit(s) within their borders, right? But if they do set a different default speed

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

18. Sep 2018 01:07 by ba...@ursamundi.org > On Mon, Sep 17, 2018 at 4:42 PM Tobias Zwick <> o...@westnordost.de > > > wrote: >> In order to find an optimal and future proof tagging schema for default >> speed limits, I believe that first

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

17. Sep 2018 16:17 by f...@zz.de : > > Hi, > is it intentional that StreetComplete tags the maxspeed source/type in > maxspeed:type instead of the much more used source:maxspeed? > Yes. See for example https://github.com/westnordost/StreetComplete/issues/492

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

On Mon, Sep 17, 2018 at 4:42 PM Tobias Zwick wrote: > In order to find an optimal and future proof tagging schema for default > speed limits, I believe that first extensive research have to be done to > find out what exists in the world, what has to be considered. Also, for > default speed

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Interesting. But I do think that this person is right. My research so far showed that neither source:maxspeed nor maxspeed:type nor any of the other variants sufficiently cover the topic of default speed limits (see last paragraphs). So, it makes little sense to migrate to a solution that is

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Le 17. 09. 18 à 20:35, Georg Feddern a écrit : > Am 17.09.2018 um 16:17 schrieb Florian Lohoff: >> is it intentional that StreetComplete tags the maxspeed source/type in >> maxspeed:type instead of the much more used source:maxspeed? > > If you search the german forum you will find that it is

Re: [Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Am 17.09.2018 um 16:17 schrieb Florian Lohoff: is it intentional that StreetComplete tags the maxspeed source/type in maxspeed:type instead of the much more used source:maxspeed? If you search the german forum you will find that it is indeed intentional: StreetComplete wird maxspeed:type

[Tagging] maxspeed:type vs source:maxspeed // StreetComplete

Hi, is it intentional that StreetComplete tags the maxspeed source/type in maxspeed:type instead of the much more used source:maxspeed? 1.2 Mio https://taginfo.openstreetmap.org/search?q=source%3Amaxspeed 230K https://taginfo.openstreetmap.org/search?q=maxspeed%3Atype Wiki menttions