Re: [Tagging] Suggestion: ref:mobile_payment for amenity=parking

> I already have trouble imagining that there are mobile apps so badly > made that it asks the user to transcribe the parking ref instead > of finding it by geolocation They do geolocation and suggest the ref. However, in some cases they suggest the ref of a neighbouring zone. That zone can have

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

It is still possible to tag a highway with 1 single railway track on it highway=* + railway=tram/train. But this proposal is for the case where the highway has 2 railiway tracks which are already mapped separately because the way railways curve is different from how how highways behave at

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

Sergio, This is not an issue, anyway some will argue that the highway is a highway AND a railway too, so they would be happy too. Yves ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

It will not be a trouble. After OSM wiki page about specific value is created it is easy to find (it is true for any documented value and it is not changing whatever given proposalis a good idea or not). 21. Nov 2018 23:11 by yve...@mailbox.org : > I like the railway

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

Hello Yves, maybe you're missing that according to the proposal we will have a first feature tagged as *both */highway=*/ *and */railway=separately_mapped/, *plus *a second overlapping/parallel feature tagged as/railway=*/ Utterly confusing, IMHO: the embedded rail is an attribute of the

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

Here is another example : https://www.openstreetmap.org/#map=18/46.72145/6.53707 I like the railway key: if it's a railway, don't make it an obscure tag that no one can find in the wiki. Yves Le 21 novembre 2018 22:47:34 GMT+01:00, Graeme Fitzpatrick a écrit : >On Wed, 21 Nov 2018 at 19:04,

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

On Wed, 21 Nov 2018 at 19:04, Nikulainen, Jukka K < jukka.nikulai...@helsinki.fi> wrote: > > It is true that that would be more precise, but are there in fact any > examples of this? I mean a railway that runs parallel to _and_ on a road? > Usually highways do cross railways, but this is not a

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

Yes, I agree, railway tracks in a highway is more seldom than tram rails. In former times that existed oftener and I assume that in eastern Europe more of such cases still exist, also in Asia. Some examples that I know: Many streets in Forst (Lausitz) had such railways, some still exist

Re: [Tagging] Physical vs legal access tagging on barriers

that is simple with a reallity ;-) you can have barrier=lift_gate+access=private+foot=no (or foot=use_sidepath) in lot of cases there is an other acces specificelly fo foot (and bicycle) because lift_gate work with weight detection and when the barrier was lowered it can shoot your head!

Re: [Tagging] Physical vs legal access tagging on barriers

The wiki says the access tag represents the *legal* access condition, so not related to the physical aspects of the feature. Reading the wiki a bit, I see the access on gates exists to override the default characteristics inherent to the barrier type: “Each barrier has its own accessibility

Re: [Tagging] Suggestion: ref:mobile_payment for amenity=parking

On Wed, Nov 21, 2018 at 4:04 PM marc marc wrote: I already have trouble imagining that there are mobile apps so badly > made that it asks the user to transcribe the parking ref instead > of finding it by geolocation > Then you have not tried as many badly-designed apps as I have. None of them

Re: [Tagging] Suggestion: ref:mobile_payment for amenity=parking

Le 21. 11. 18 à 16:33, Paul Allen a écrit : > On Wed, Nov 21, 2018 at 3:21 PM marc marc wrote: > > Le 21. 11. 18 à 13:39, Michael Brandtner a écrit : > > it's a ref specific to this parking lot to be entered into an app > or sms. > > payment:sms=yes or payment:sms= >

Re: [Tagging] Suggestion: ref:mobile_payment for amenity=parking

On Wed, Nov 21, 2018 at 3:21 PM marc marc wrote: > Le 21. 11. 18 à 13:39, Michael Brandtner a écrit : > > it's a ref specific to this parking lot to be entered into an app or sms. > > payment:sms=yes or payment:sms= > payment:=yes > > > ref:payment:app=12345 > > ref:payment:sms=12345 > >

Re: [Tagging] Suggestion: ref:mobile_payment for amenity=parking

Le 21. 11. 18 à 13:39, Michael Brandtner a écrit : > it's a ref specific to this parking lot to be entered into an app or sms. payment:sms=yes or payment:sms= payment:=yes > ref:payment:app=12345 > ref:payment:sms=12345 ref=12345 look enough, isn't it ?

[Tagging] Physical vs legal access tagging on barriers

There may be a sitation where 1) there is a barrier (like barrier=lift_gate)2) it is not blocking foot traffic3) but pedestrians are not allowed to pass I think that optimal tagging in this case would be barrier=lift_gate + foot=yes on barrierhighway=* + foot=no on way with barrier node See for

[Tagging] RfC: tagging whatever power line is insulated as an attribute

I created https://wiki.openstreetmap.org/wiki/Proposed_features/insulated to with intention of allowing mappers not interested in the extreme detail of power networks to allow ignoring this detail in case of isolation of power

Re: [Tagging] Suggestion: ref:mobile_payment for amenity=parking

Philip Barnes schrieb am 23:29 Dienstag, 20.November 2018: > I am not 100% sure that mobile payment is the correct term, that to me > implies using your phone for contactless payment. But wouldn't that be payment:contactless?  > The English term used in these cases is Pay by Phone. So your

Re: [Tagging] Suggestion: ref:mobile_payment for amenity=parking

Am Dienstag, 20. November 2018, 23:32:40 MEZ hat marc marc Folgendes geschrieben: > it's a ref specific to this parking to be entered in an app ? > or a > https://wiki.openstreetmap.org/wiki/Key:payment#Payment_via_phone ? Yes, it's a ref specific to this parking lot to be entered into an

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

The whole issue is that due to tram rails bending differently than road ways, the tram rails are mapped on their own OSM ways. This gives a nicely detailed rendering, a better description of reality, but now the information that for the straight parts the rails are embedded into the highway is

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

I think I agree with Rainer: You propose to add a  "railway=" tag to a way that already has a "highway=" tag. So then why not just add "railway=tram" and delete the separate way? If this is not wanted (e.g. for rendering reasons) then I think we should use another tag instead of "railway=".

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

Sorry, I forgot to comment on this earlier >embedded_rails=yes or even more precise >embedded_rails=tram | embedded_rails=railway. >The latter is even worse for bicycles, because the rail grooves are >broader. It is true that that would be more precise, but are there in fact any examples of

Re: [Tagging] Feature Proposal - Voting - (Tramtrack_on_highway)

Hello, and thank you all again for your comments! >>Le 20 novembre 2018 22:02:01 GMT+01:00, Rainer a écrit : >>Sorry that I enter the discussion late. >>First, is my understanding correct that you want to add a tag on a >>highway that has embedded tram rails? So e.g. a bicycle router might