Preset for a way designated for both cyclists and pedestrians, without separate spaces (segregated=no) #317
Comments
|
This tagging is also included in https://wiki.openstreetmap.org/wiki/DE:Tag:traffic_sign%3DDE:240 (which adds the traffic_sign) which I created an issue for in #267 I think it would be ideal, if this preset would have a field (for countries where it applies) that say "This access rights are also signed with a traffic sign", which then would add the traffic_sign-tag and transform this preset to the one with traffic sign from #267. This extra field would nudge mappers to also check for traffic signs to formally confirm the given access-tagging. |
|
One more think: AFAIK there is an issue with using In any case, we should have a crossing preset as well as a regular preset. |
Not sure if I understand. Is this a blocker from let's call it a technical standpoint as in when iD automatically creates a crossing when two ways cross and there needs to be a matching crossing type? Or is that more of a concept like there should be matching crossing preset for every highway preset? |
|
No, it's nothing technical. It's just very confusing. – How would you tag a way that is tagged like in your proposal as a crossing? |
|
On the wiki path=crossing is documented. https://wiki.openstreetmap.org/wiki/Tag:footway%3Dcrossing |
|
Is there any existing presets matching on multiple tags and having priority over another preset ( highway=path + bicycle=designated + foot=designated + segregated=no over bare highway=path) ? |
|
@matkoniecz I believe there are such presets. For example the existing "Cycle & Foot Path" preset ( (The "Cycle & Foot Path" preset doesn't show in some countries: France, Lithuania, Poland, and Germany) |
…g `segregated` The fields `oneway` and `access` are important for `highway=cycleway|path` crossings but not essential. They are more of a advanced user setup which should be visible when prev filled in but only added by users that read more about it before. They are moved to the `moreFields` for that reason. The `segregated` is added here for the same reasons and because of it's importance for highway types that likely have bike traffic. Ping openstreetmap#317 The `surface` and `smoothness` is extracted from the `@template` because it makes more sense to split them up in `fields` and `moreFields`. A templates adds too much abstraction in this case.
…g `segregated` The fields `oneway` and `access` are important for `highway=cycleway|path` crossings but not essential. They are more of a advanced user setup which should be visible when prev filled in but only added by users that read more about it before. They are moved to the `moreFields` for that reason. The `segregated` is added here for the same reasons and because of it's importance for highway types that likely have bike traffic. Ping openstreetmap#317 The `surface` and `smoothness` is extracted from the `@template` because it makes more sense to split them up in `fields` and `moreFields`. A templates adds too much abstraction in this case.
…g `segregated` The fields `oneway` and `access` are important for `highway=cycleway|path` crossings but not essential. They are more of a advanced user setup which should be visible when prev filled in but only added by users that read more about it before. They are moved to the `moreFields` for that reason. The `segregated` is added here for the same reasons and because of it's importance for highway types that likely have bike traffic. Ping openstreetmap#317 The `surface` and `smoothness` is extracted from the `@template` because it makes more sense to split them up in `fields` and `moreFields`. A templates adds too much abstraction in this case.
…g `segregated` The fields `oneway` and `access` are important for `highway=cycleway|path` crossings but not essential. They are more of a advanced user setup which should be visible when prev filled in but only added by users that read more about it before. They are moved to the `moreFields` for that reason. The `segregated` is added here for the same reasons and because of it's importance for highway types that likely have bike traffic. Ping openstreetmap#317 The `surface` and `smoothness` is extracted from the `@template` because it makes more sense to split them up in `fields` and `moreFields`. A templates adds too much abstraction in this case.
…g `segregated` The fields `oneway` and `access` are important for `highway=cycleway|path` crossings but not essential. They are more of a advanced user setup which should be visible when prev filled in but only added by users that read more about it before. They are moved to the `moreFields` for that reason. The `segregated` is added here for the same reasons and because of it's importance for highway types that likely have bike traffic. Ping openstreetmap#317 The `surface` and `smoothness` is extracted from the `@template` because it makes more sense to split them up in `fields` and `moreFields`. A templates adds too much abstraction in this case.
…g `segregated` The fields `oneway` and `access` are important for `highway=cycleway|path` crossings but not essential. They are more of a advanced user setup which should be visible when prev filled in but only added by users that read more about it before. They are moved to the `moreFields` for that reason. The `segregated` is added here for the same reasons and because of it's importance for highway types that likely have bike traffic. Ping openstreetmap#317 The `surface` and `smoothness` is extracted from the `@template` because it makes more sense to split them up in `fields` and `moreFields`. A templates adds too much abstraction in this case.
There seems to be missing a preset for case S7 in https://wiki.openstreetmap.org/wiki/Bicycle#Miscellaneous
so a combination of tags:
I think main tag: highway=path would be the most universal for a preset.
Fields can be the same as for cycleway or footway.
This type of footway shared with bicycles is (unfortunately) very popular in Poland and it would be good to have a preset corresponding to that so new mappers aren't confused about mapping those.
The text was updated successfully, but these errors were encountered: