[Tagging] Dispute of surface-values
Hello Are there any rules for disputes / edit wars in Wiki? http://wiki.openstreetmap.org/wiki/Disputes seems to be for disputes inside map, not wiki? And only 3 persons are on the list, and no one seems to be german. But german language might be an adavantage, because dispute starts in the german forum http://forum.openstreetmap.org/viewtopic.php?id=14098 and includes some german wiki pages There Taunide prefers an interpretation of fine_gravel that doesn't match the original english surface wiki page, where his definition is already nearly used for compacted since some years ... Wiki pafes affected: http://wiki.openstreetmap.org/w/index.php?title=DE:Reitenaction=history http://wiki.openstreetmap.org/w/index.php?title=Template:De:Map_Features:surfaceaction=history http://wiki.openstreetmap.org/w/index.php?title=Template:Map_Features:surfaceaction=history http://wiki.openstreetmap.org/wiki/Talk:Key:surface#gravel_.2F_water-bound_.2F_macadam http://wiki.openstreetmap.org/wiki/Talk:Key:surface#fine_gravel I also don't found a Template at http://wiki.openstreetmap.org/wiki/Category:Wiki_templates to mark the wiki page as in dispute Heiko / Mueck ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
[Tagging] different access restrictions for different entrances to an area
http://mapper.acme.com/?ll=28.42073,-81.58224z=15t=Kmarker0=28.41788%2C-81.57674marker1=28.41250%2C-81.59031marker2=28.42977%2C-81.57694 This is the area behind the Magic Kingdom in Walt Disney World. Signs going northbound at A and B say Service Authorized Vehicles Only. Southbound at C, a sign says Private Property / Walt Disney World Resort Guest, Cast, and Business Invitees Only. (I verified A and C a few days ago; it's possible that B has changed recently.) The exact tags to use for these are a matter of recent debate, and it's not worth rehashing that. But it's clear that they are different (a guest can enter Disney from Reams but can't exit that way), so for the sake of argument let's call the former access=private and the latter access=destination. Note that the area from A and B south to the beginning of the motorway is also access=destination due to the presence of the main entrance gate (and a sign identical to that at C on Vista west of Golden Oak). The question is how the segments of road between these points should be tagged. Should the ability to U-turn be taken into account (thus everything but the close vicinity of A and B is destination in both directions)? Or should it be assumed that one won't U-turn for the hell of it (thus all three roads are private northbound and destination southbound)? Or should no_straight_on restrictions be used at the signs, with no access tags on the ways? ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature Proposal - RFC - Relations/Proposed/Level Map
Hi Marl, I also am working for some time with indoor mapping, but till now in never really came to document my schema properly. I just published some text in images on http://wiki.openstreetmap.org/wiki/Proposed_features/indoor The text is currently only german, this should be changed some time. I have also added likes to example data, my main play field is http://www.openstreetmap.org/?lat=48.262437lon=11.667689zoom=18 Difference to your proposal, I found so far: In my schema elevators are really a way, not only nodes with a vway tag. I think your solution get's some problems in routing, mine has the problem that with current editors it's not so really easy to use. For floors, I only use numbers. So i always know which floor is above or below of another. For outdoor ways i use an additional outdoor tag, see picture on the proposal page. Greets, Andi PS: is there a way to contact per private message? Sending mails to osm-marl at gmx.de failed twice. ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] different access restrictions for different entrances to an area
On 10/25/2011 6:03 PM, Anthony wrote: What are we pretending, for the sake of argument, that As I say below: access=destination Private Property / Walt Disney World Resort Guest, Cast, and Business Invitees Only and access=private mean? Service Authorized Vehicles Only On Tue, Oct 25, 2011 at 2:43 PM, Nathan Edgars IInerou...@gmail.com wrote: http://mapper.acme.com/?ll=28.42073,-81.58224z=15t=Kmarker0=28.41788%2C-81.57674marker1=28.41250%2C-81.59031marker2=28.42977%2C-81.57694 This is the area behind the Magic Kingdom in Walt Disney World. Signs going northbound at A and B say Service Authorized Vehicles Only. Southbound at C, a sign says Private Property / Walt Disney World Resort Guest, Cast, and Business Invitees Only. (I verified A and C a few days ago; it's possible that B has changed recently.) The exact tags to use for these are a matter of recent debate, and it's not worth rehashing that. But it's clear that they are different (a guest can enter Disney from Reams but can't exit that way), so for the sake of argument let's call the former access=private and the latter access=destination. Note that the area from A and B south to the beginning of the motorway is also access=destination due to the presence of the main entrance gate (and a sign identical to that at C on Vista west of Golden Oak). The question is how the segments of road between these points should be tagged. Should the ability to U-turn be taken into account (thus everything but the close vicinity of A and B is destination in both directions)? Or should it be assumed that one won't U-turn for the hell of it (thus all three roads are private northbound and destination southbound)? Or should no_straight_on restrictions be used at the signs, with no access tags on the ways? ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] different access restrictions for different entrances to an area
Have you actually driven through the roads, or just verified signs at the entrances? From only looking at the map, I would expect that cast, resort guests, business invitees etc can enter at C, but only to go to the car parks right by the entrance, and further down that road the restrictions would change to the same ones as for A B. They would be expected to exit by the same gate they came in. I could be wrong, of course, but I've seen that setup used elsewhere. I've seen a similar case to the problem you described elsewhere, though. There's a complex I've been to where only vehicles with a key/transponder of some sort can use most of the entrances. All other vehicles have to go through the main entrance, which (usually) has security personnel. Once you're inside, though, you can drive around and exit anywhere. So most of the entrances are restricted one way, but not the other. I'm not sure how you'd tag that, either. Stephen On 26 October 2011 04:43, Nathan Edgars II nerou...@gmail.com wrote: http://mapper.acme.com/?ll=28.42073,-81.58224z=15t=Kmarker0=28.41788%2C-81.57674marker1=28.41250%2C-81.59031marker2=28.42977%2C-81.57694 This is the area behind the Magic Kingdom in Walt Disney World. Signs going northbound at A and B say Service Authorized Vehicles Only. Southbound at C, a sign says Private Property / Walt Disney World Resort Guest, Cast, and Business Invitees Only. (I verified A and C a few days ago; it's possible that B has changed recently.) ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
[Tagging] Announcing: website key integrity checking
KeepRight, at http://keepright.ipax.at/ now validates website tags on ways and nodes. The script loads each page and performs a fuzzy match... a restaurant for example needs to match on name, phone number or address (any one will do). The script also checks for hijacked domains, though this detection could use additional match strings. The http error check could use some help also: many http errors are transient, which leads to unfortunate flagging of non-problems. ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
