<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">25 apr. 2017 kl. 21:52 skrev Martin Koppenhoefer <<a href="mailto:dieterdreist@gmail.com" class="">dieterdreist@gmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class=""><div class=""><br class=""><br class="">sent from a phone</div><div class=""><br class="">On 25. Apr 2017, at 19:07, Tobias Zwick <<a href="mailto:osm@westnordost.de" class="">osm@westnordost.de</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><span class="">I would say so, as long as there are not in reality two cycleways (see</span><br class=""><span class="">above). Wouldn't you?</span></div></blockquote><br class=""><div class=""><br class=""></div><div class="">it depends on the meaning/reading. I believe cycleway=track is bad anyway, it's ok for preliminary mapping but fails when it comes to […]</div></div></div></blockquote><br class=""></div><div><br class=""></div><div>On a side note, around where I live I see quite a few cycleways mapped as their own ways, tagged highway=cycleway,cycleway=track. Does the cycleway=track mean anything in this context (and if so: what?) or is it a mapping error?</div><div><br class=""></div></body></html>