<html><head></head><body>Thanks Simon for bringing this back to best practices.<br><br>Is there a good how to for this alignment of aerial imagery? <br>I always struggled with the JOSM interface. I also thought that this was something stored locally for the JOSM instance only.<br><br><br><div class="gmail_quote">On 16 May 2021 3:56:59 am AEST, Simon Poole <simon@poole.ch> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">IMHO this is not what you should be doing. You should be using the GPS <br>traces and possible other data to adjust the aerial/sat imagery (and <br>then storing the offsets in the imagery offset DB).<br><br>The reason for this is simple, GPS traces are notoriously bad at <br>capturing the actual topology of roads (that is junctions etc) and if <br>they are available you will nearly always (except if they are very out <br>of date, or very hilly/mountainous areas and bad orthorectification) <br>want to derive the geometry from the aerial imagery.<br><br>Simon<br><br>Am 14.05.2021 um 08:23 schrieb Bob Cameron:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Just checking if this is an okay thing to do. ie moving a major road <br> so it is centred on GPS traces - assuming there enough data for <br> accuracy (eg bidirectional, multi trace etc)<br><br> The traces are probably more accurate than overhead imagery.<br><br> Other features placed relative to roads will also need moving?<br><br> Reason I ask is a concern that there may be an automated process that <br> adjusts existing roads.<br><br> Tnx<hr> Talk-au mailing list<br> Talk-au@openstreetmap.org<br> <a href="https://lists.openstreetmap.org/listinfo/talk-au">https://lists.openstreetmap.org/listinfo/talk-au</a><br></blockquote><br></pre></blockquote></div></body></html>