<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1324701482;
mso-list-type:hybrid;
mso-list-template-ids:1166058494 -1 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l0:level1
{mso-level-start-at:0;
mso-level-number-format:bullet;
mso-level-text:\F0D8;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;
mso-fareast-font-family:"Times New Roman";
mso-bidi-font-family:"Times New Roman";}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style></head><body lang=EN-GB link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>“I would like it if the iD 'adjust imagery tool' button were more visible.”</p><p class=MsoNormal>I agree on this, it needs to be more prominent and ideally iD would make it’s users align the imagery before letting them edit.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Dose iD’s tutorial/guide teach about offsets?</p><p class=MsoNormal>If not I think it should as they are very important when editing from imagery and I imagine most iD mappers do this.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>(Sorry if I mess this email up I’m new to how mailing list emails work.)</p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal style='border:none;padding:0cm'><b>From: </b><a href="mailto:aamackie@gmail.com">Alan Mackie</a><br><b>Sent: </b>19 August 2020 10:53<br><b>To: </b><a href="mailto:scolebourne@joda.org">Stephen Colebourne</a><br><b>Cc: </b><a href="mailto:talk-gb@openstreetmap.org">Talk-GB</a><br><b>Subject: </b>Re: [Talk-GB] New Bing Imagery</p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><div><p class=MsoNormal>On Wed, 19 Aug 2020, 10:13 Stephen Colebourne, <<a href="mailto:scolebourne@joda.org">scolebourne@joda.org</a>> wrote:</p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal>So, I followed the links below and added an offset. But this simply<br>isn't a viable solution to the problem because it only works for JOSM<br>and not iD.<br><br>I managed to convince one mapper to type in the offset manually in iD<br>every time, but that is a horrible thing to ask new mappers to do,<br>very offputting. And now I can see Amazon mappers using an iD variant<br>that doesn't have the offset and moving all the roads as a result:<br> <a href="https://osmcha.org/changesets/89549551?aoi=758c7f2b-faca-44e5-acd2-0cb8c33034bd" target="_blank">https://osmcha.org/changesets/89549551?aoi=758c7f2b-faca-44e5-acd2-0cb8c33034bd</a><br> <a href="https://www.openstreetmap.org/changeset/89549551" target="_blank">https://www.openstreetmap.org/changeset/89549551</a><br>This is going to keep happening so long as OSM has multiple image<br>sources and multiple editors. Frankly I'm amazed that this isn't a<br>solved problem.</p></blockquote></div></div><div><p class=MsoNormal>Imagery isn't one image. There are carefully blended seams that often include jumps if you look closely. There is also no guarantee that distortion to "flatten" hills etc. We also tend to receive no metadata about where the seams are, or how they were distorted. It is not an easy problem to solve.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal><br>Having done some mapping across the country recently, it seems like<br>Bing is offset to the previous best imagery across the country, but by<br>varying amounts. Is there really no solution that can be applied to<br>the source Bing layer? Or should we all just accept Bing as golden?</p></blockquote></div></div><div><p class=MsoNormal>I think we tend to accept OS's StreetView as the best source for position. </p></div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal><br>Having added thousands of buildings and fixed roads to align to the<br>previous best imagery, I don't have a good solution to the problem,<br>and it is demotivating to think that others are going to come along<br>and move individual roads/buildings to align without considering the<br>bigger picture.</p></blockquote></div></div><div><p class=MsoNormal>Poorly considered hit and run mapping will happen regardless of the imagery. </p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>At least talk-gb doesn't have to deal with those with "humanitarian" inspiration. These can be prolific and sometime give the impression they are too busy "helping people" to read even basic instructions. (Especially the ones who go off piste)</p></div><div><div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm'><p class=MsoNormal><br>The only solution I can think of is to move all nodes in the area I've<br>worked on to match the new Bing (ie a mass edit). Any other<br>suggestions?</p></blockquote></div></div><div><p class=MsoNormal>Readjusting every time a source updates is not a good solution. It assumes there is one "authoritative" source and would become and endless task.</p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I would like it if the iD 'adjust imagery tool' button were more visible.</p></div></div><p class=MsoNormal style='margin-left:4.8pt'><br>Stephen<br><br><br><br><br><br><br><br><br><br><br>On Sun, 12 Jul 2020 at 23:36, Mateusz Konieczny via Talk-GB<br><<a href="mailto:talk-gb@openstreetmap.org" target="_blank">talk-gb@openstreetmap.org</a>> wrote:<br>><br>> <a href="https://wiki.openstreetmap.org/wiki/JOSM/Plugins/Imagery_Offset_Database/Quick_Start" target="_blank">https://wiki.openstreetmap.org/wiki/JOSM/Plugins/Imagery_Offset_Database/Quick_Start</a><br>> <a href="https://wiki.openstreetmap.org/wiki/Imagery_Offset_Database" target="_blank">https://wiki.openstreetmap.org/wiki/Imagery_Offset_Database</a><br>> (I think that nowadays it is built in - is plugin installation still necessary?)<br>><br>><br>> No idea about iD support - <a href="https://github.com/openstreetmap/iD/search?q=imagery+offset" target="_blank">https://github.com/openstreetmap/iD/search?q=imagery+offset</a><br>><br>> Jul 13, 2020, 00:21 by <a href="mailto:scolebourne@joda.org" target="_blank">scolebourne@joda.org</a>:<br>><br>> Wow, the imagery is really good. But in my area the imagery is about<br>> 3-4m east west and 3-4m north south out of alignment with Esri World<br>> Imagery (Clarity) Beta, which is what I've been using up until now<br>> (for thousands of buildings).<br>> <a href="https://www.openstreetmap.org/#map=18/51.39886/-0.24940" target="_blank">https://www.openstreetmap.org/#map=18/51.39886/-0.24940</a><br>><br>> Is there any way to unify the alignments?<br>><br>> Stephen<br>><br>><br>> On Thu, 9 Jul 2020 at 06:41, Gareth L <<a href="mailto:o.i@live.co.uk" target="_blank">o.i@live.co.uk</a>> wrote:<br>><br>><br>> I’ve noticed patches of vastly improved bing imagery since December, but it is really patchy.<br>> Gareth<br>><br>> > On 6 Jul 2020, at 23:21, Cj Malone <<a href="mailto:me-osm-talk-gb@keepawayfromfire.co.uk" target="_blank">me-osm-talk-gb@keepawayfromfire.co.uk</a>> wrote:<br>> ><br>> > I was splitting houses in Portsmouth/Southsea this morning. The imagery<br>> > is great, I don't know if it was part of this update, or if it's been<br>> > like this for a while.<br>> ><br>> ><br>> > _______________________________________________<br>> > Talk-GB mailing list<br>> > <a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>> > <a href="https://lists.openstreetmap.org/listinfo/talk-gb" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>> _______________________________________________<br>> Talk-GB mailing list<br>> <a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>> <a href="https://lists.openstreetmap.org/listinfo/talk-gb" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>><br>><br>> _______________________________________________<br>> Talk-GB mailing list<br>> <a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>> <a href="https://lists.openstreetmap.org/listinfo/talk-gb" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><br>><br>><br>> _______________________________________________<br>> Talk-GB mailing list<br>> <a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br>> <a href="https://lists.openstreetmap.org/listinfo/talk-gb" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a><br><br>_______________________________________________<br>Talk-GB mailing list<br><a href="mailto:Talk-GB@openstreetmap.org" target="_blank">Talk-GB@openstreetmap.org</a><br><a href="https://lists.openstreetmap.org/listinfo/talk-gb" target="_blank">https://lists.openstreetmap.org/listinfo/talk-gb</a></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>