<div dir="ltr"><div dir="ltr">On Sat, 24 Oct 2020 at 12:42, Supaplex <<a href="mailto:supaplex@riseup.net">supaplex@riseup.net</a>> wrote:</div><div dir="ltr"><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>I would like to invite you to discuss a proposal for "parking =
street_side" for areas suitable or designated for parking, which
are directly adjacent to the carriageway of a road and can be
reached directly from the roadway without having to use an access
way:
<a href="https://wiki.openstreetmap.org/wiki/Proposed_features/parking%3Dstreet_side" target="_blank">https://wiki.openstreetmap.org/wiki/Proposed_features/parking%3Dstreet_side</a><br></div></blockquote><div><br></div><div>I don't think a new parking=street_side is necessary for off-carriageway</div><div>street-side parking.</div><div><br></div><div>The example image you give in the sub-section "Tagging" <br></div><div><a href="https://wiki.openstreetmap.org/w/images/thumb/b/b8/Parking-render-carto.png/500px-Parking-render-carto.png">https://wiki.openstreetmap.org/w/images/thumb/b/b8/Parking-render-carto.png/500px-Parking-render-carto.png</a><br></div><div>is (in my opinion) not a good way to use existing tagging. The parking areas</div><div>are not routeable (not a big problem unless somebody wants to route</div><div>to a named parking area). As rendered it appears you need a skyhook or</div><div>a cargo helicopter to park. Not good. You're probably as unhappy with that</div><div>method of tagging as I am.</div><div><br></div><div>Connecting it with an invented service road also misrepresents the true</div><div>situation.</div><div><br></div><div>But there is another way of doing it. A way which comes in two variants,</div><div>either quick-and-dirty or purist.</div><div><br></div><div>Variant 1. Extend the parking area out to the roat it is on. Pretty much as</div><div> you handled the lay-by example. As far as rendering goes, where most</div><div>carto renders the road on top of the parking area, it represents things</div><div>as a way that matches reality. Here's one I did years ago.</div><div><br></div><div><a href="https://www.openstreetmap.org/?mlat=52.08560&mlon=-4.65830#map=19/52.08560/-4.65830">https://www.openstreetmap.org/?mlat=52.08560&mlon=-4.65830#map=19/52.08560/-4.65830</a></div><div>Streetview for comparison: <a href="https://goo.gl/maps/R7Q1RUWGziLaMemW8"> https://goo.gl/maps/R7Q1RUWGziLaMemW8</a></div><div><br></div><div>A data purist on the list objected to that. The rendering is a good</div><div> representation of reality but if a data consumer were to look at the</div><div>data rather than the rendering then he or she would assume the</div><div>car could be parked perpendicular to the carriageway with half<br></div><div>the car blocking traffic. So for purists...</div><div><br></div><div>Variant 2. Map the precise boundary of the parking area. Connect it</div><div>to the carriageway with highway=service + area=yes. This results</div><div>in rendering that is an even better (if slightly uglier) representation of</div><div> reality at the expense of extra effort. Here's one I did a few weeks</div><div>ago to test the idea.</div><div><br></div><div><a href="https://www.openstreetmap.org/?mlat=52.08268&mlon=-4.66461#map=19/52.08268/-4.66461">https://www.openstreetmap.org/?mlat=52.08268&mlon=-4.66461#map=19/52.08268/-4.66461</a><br></div><div>Streetview for comparison: <a href="https://goo.gl/maps/YHTv9dDvSbm6DL1A8">https://goo.gl/maps/YHTv9dDvSbm6DL1A8</a> The</div><div>streetview is somewhat misleading as recent aerial imagery shows clear</div><div>surface marking delineating the boundaries. That's also a weird example</div><div>because some of it is off-carriageway and some on-carriageway (turn 180</div><div>degrees in streetview and move forward to see), a situation your proposal</div><div> doesn't cater to.</div><div><br></div><div>I don't see your proposal achieving anything we can't already do and</div><div>doesn't keep the data purists happy, either.<br></div><div><br></div><div>-- <br></div><div>Paul</div><div><br></div></div></div>