<div dir="ltr">Hi Steve,<div><br></div><div>I left those "track" sections where the old off ramps were as they still existed although they have been blocked off at both ends. I think I marked those with bollards. The only current access between Diggers Way and the old Calder is a T junction on the East side. I'd be surprised if I left routing issues there though its possible I guess. All the rest of the tracks / road segments should have been in accessible.</div>
<div><br></div><div>I just made the change and removed completely all of those old road fragments as you suggested. This weekend I will go past with a GPS and get the correct position of the T junction.</div><div><br></div>
<div>regards</div><div><br></div><div>Neil</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 22, 2013 at 2:22 PM, <span dir="ltr"><<a href="mailto:stev391@email.com" target="_blank">stev391@email.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span style="font-family:Verdana"><span style="font-size:12px">G'day Neil,<br><br>Steve, aka Steve91 here, if I have been one of the mappers that have caused issues with this intersection I apologies.<br>
<br>As for the source of nearmap, it must have been a copy and past error, from the adjacent section of the road. I use AGRI, Bing sat images and survey for areas already mapped. The history of the some sections of the offramp show the nearmap as a source tag going back to 10/05/10.<br>
<br>The intersection in question I do remember having a look at, but only for routing issues due to: disconnected ways, incorrect one-way road leading to islands, duplicate ways etc. (i.e. trying to improve the quality of the map, as per the comment on the changeset). I identify items for attention via OSM Inspector or the validator in JOSM. I don't believe I added the ways. It appears that I changed the 2 ways in question from 'track' to tertiary and may have reconnected one end of them. <br>
<br>If the intersection has been remodelled, as per the google earth imagery, then the sections of roads should not exist as 'track' and the ways should be removed. Also the onramp that is one way should be one way through the entire section, not have one way followed by bi-directional followed by one way.<br>
<br>I have no issues with you reverting the changes I made to the intersection, as long as the traffic routing is consistent along the ways.<br><br>Regards<br>Steve.<br><br> <p style="margin:0px;padding:0px"> </p><blockquote style="border-left:1px solid #ccc;padding-left:5px;margin-left:5px;margin-bottom:0px;margin-top:0px;margin-right:0px" type="cite">
<p style="margin:0px;padding:0px"><span style="font-family:Verdana"><span style="font-size:12px">----- Original Message -----</span></span></p><p style="margin:0px;padding:0px"><span style="font-family:Verdana"><span style="font-size:12px">From: Neil Penman</span></span></p>
<p style="margin:0px;padding:0px"><span style="font-family:Verdana"><span style="font-size:12px">Sent: 10/22/13 12:10 PM</span></span></p><p style="margin:0px;padding:0px"><span style="font-family:Verdana"><span style="font-size:12px">To: Nick Hocking</span></span></p>
<p style="margin:0px;padding:0px"><span style="font-family:Verdana"><span style="font-size:12px">Subject: Re: [talk-au] Openstreetmap Quality Issues</span></span></p> <div><div><div><div><div>Hi Nick,<br> </div>Yep thats a good idea to add the survey tag. Interestingly the ways did not not have a source tag up until jan 2013 however Steve91 added the source of Nearmap then. Which I wasn't aware we still had access to.<br>
</div>I'll be heading past the intersection later this week and will check it out.<br><br>regards<br> </div>Neil</div><div class="gmail_extra"> <div class="gmail_quote">On Tue, Oct 22, 2013 at 11:30 AM, Nick Hocking <span><<a href="mailto:nick.hocking@gmail.com" target="_blank">nick.hocking@gmail.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p style="margin:0px;padding:0px">Hi Neil,</p><div>I think the way to get this fixed permanently could be...</div><div><br>Fix it one more time, re-add the note saying that the imagery is out of date and that this intersection has been surveyed.<br>
Change the source tag from nearmap to survey.</div><p style="margin:0px;padding:0px">Now even though one of the mnappers has a fairly colourful history of edit wars and non response to polite messages, it may be useful to send both of them a message pointing out that you have actually surveyed the area and that the Bing imagery is out of date. You could send links to the Google map sattelite view that shows the new layout and also the Google street view that shows the old layout.</p>
<p style="margin:0px;padding:0px">I guess that it's possible (but not likely) that the local council have decided that what they originally had was better and have resealed the parts that were removed. You could check whether the latest mapper actually surveyed it or just traced it from imagery.</p>
<div>I also think it would be nice if all edit software flashed up a warning (once per session) if you change an object that has a "survey" tag. This warning would disappear on the next click but may serve to give the mapper second thoughts as to whether his changes are for the better or not.</div>
<div><span><font color="#888888"> </font></span></div><div><span><font color="#888888">Nick</font></span></div><br>_______________________________________________<br>Talk-au mailing list<br><a href="mailto:Talk-au@openstreetmap.org" target="_blank">Talk-au@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk-au" target="_blank">https://lists.openstreetmap.org/listinfo/talk-au</a><br> </blockquote></div><br><br clear="all"><span class="HOEnZb"><font color="#888888"><br>--<div>
<div><br><a style="color:rgb(17,85,204)" href="http://smap.com.au/" target="_blank">Smap Consulting </a>| Mobile Data Collection Solutions</div><div>Application Developer - <span style="color:rgb(34,34,34);background-color:rgb(255,255,204)"><a style="color:rgb(17,85,204)" href="mailto:minqiang.huang@gmail.com" target="_blank">neilpenman@gmail.com</a></span></div>
<div>Twitter: @dgmsot</div><div>Skype: ianaf4you</div><div>Phone: <a href="tel:%2B61%20402%20975%20959" value="+61402975959" target="_blank">+61 402 975 959</a></div><div>Blog: <a href="http://smap.com.au/blog" target="_blank">http://blog.smap.com.au</a></div>
</div></font></span></div></div></blockquote><p style="margin:0px;padding:0px"> </p><p style="margin:0px;padding:0px"> </p><br><span><span style="font-family:Verdana;font-size:12px"> </span></span></span></span>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><a href="http://smap.com.au/" style="color:rgb(17,85,204)" target="_blank"><br>Smap Consulting </a>| Mobile Data Collection Solutions</div>
<div>Application Developer - <span style="color:rgb(34,34,34);background-color:rgb(255,255,204)"><a href="mailto:minqiang.huang@gmail.com" style="color:rgb(17,85,204)" target="_blank">neilpenman@gmail.com</a></span></div>
<div>Twitter: @dgmsot</div><div>Skype: ianaf4you</div><div>Phone: +61 402 975 959</div><div>Blog: <a href="http://smap.com.au/blog" target="_blank">http://blog.smap.com.au</a></div></div>
</div>