<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div>Fellow mappers,</div><div><br></div><div>So what's up with the recent changes in our aerial photo imagery?</div><div><br></div><div>It used to be so simple and I followed the rule(?) of making sure features</div><div>line up with Bing imagery. I'm wondering about that now - big time.</div><div>I have been mapping in a variety of locations lately and the situation is</div><div>different in each location. In Minnesota, for instance, I really don't want</div><div>to use Bing imagery unless at some zoom level it shows me the most</div><div>current images (especially in high growth areas like northwest Rochester).</div><div>And when recently updating an intersection in southwest Minnesota to a</div><div>new roundabout, I was aghast at what Bing was giving me and so only used</div><div>it where the quality/resolution "wasn't TOO bad". Sad. Mapbox, ESRI and</div><div>other imagery were all much better choices, especially between Blomkest</div><div>and Hutchinson, MN. </div><div><br></div><div>So the main question now is: Does the "line up with Bing" rule still stand?</div><div>In recent work around the city of Virginia, Minnesota (re-routing of US 53)</div><div>I felt I had to use Mapbox imagery and so lined up what I could with it rather</div><div>than Bing. In most cases, they matched or were off by only 2 meters or so.</div><div><br></div><div>I would provide a link to show you the worst area I found (along MN 7 several</div><div>miles east of Blomkest) but Openstreetmap.org seems to be down right now.</div><div><br></div><div>David</div><div>Your Village Maps</div><div><br></div></div></body></html>