<html xmlns:v="urn:schemas-microsoft-com:vml" 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 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:1476142261;
mso-list-type:hybrid;
mso-list-template-ids:-1572321054 67698705 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This is a great thread and I wanted to provide some additional information on behalf of DigitalGlobe:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">1)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Our goal in collecting imagery and making it available via open license is to provide as much data as possible given the humanitarian nature of this
event. This means we use our satellites in a manner not typically seen. Charlie did a great job summarizing this in his recent blog
<sup>[1]</sup><o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">2)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Given this, we are actually swiveling our satellites to “point” at Nepal even when our orbits are not directly over Nepal. As an example, a satellite
may be vertically overhead Bangladesh, yet, the satellite is looking back at Nepal. This is actually quantified and measured in the image metadata by referencing the Off Nadir Angle<sup>[2]</sup> and Target Azimuth. In typical circumstances, best accuracy
is achieved when Off Nadir angle is less than 20 degrees. In these cases, the ground RMSE is within a few meters
<sup>[3]</sup> . However, the events in Nepal are not considered to by typical circumstances, and in some cases, we are pushing Off Nadir Angles above 40 degrees.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">3)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I wanted to confirm that all imagery is indeed ortho-rectified and geo-corrected to the best of our ability considering timeliness and the fact many
many people and organizations are waiting for imagery and heavily dependent on its availability. In our orthorectification process, we are leveraging a variety of elevation models. Important to note that most elevation models have linear error that can range
from 5-15m. <sup>[4]</sup> As the off nadir angle increases, these inaccuracies in the elevation model propagate into horizontal displacements in the imagery. This is why we are seeing large offsets.
<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo1"><![if !supportLists]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><span style="mso-list:Ignore">4)<span style="font:7.0pt "Times New Roman"">
</span></span></span><![endif]><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">The tradeoff here is timely, massive amounts of post event imagery acquired under less than ideal circumstances containing horizontal error, or, very
limited imagery only collected under ideal circumstances with minimal horizontal error. As noted below, typically, the former is preferred.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hope this helps, Kevin<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[1] -
<a href="https://www.mapbox.com/blog/nepal-imagery-collection/">https://www.mapbox.com/blog/nepal-imagery-collection/</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[2] -
<a href="http://www.landinfo.com/buying-optical-satellite-imagery-2.html">http://www.landinfo.com/buying-optical-satellite-imagery-2.html</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[3] -
<a href="https://www.digitalglobe.com/sites/default/files/WorldView_Geolocation_Accuracy.pdf">
https://www.digitalglobe.com/sites/default/files/WorldView_Geolocation_Accuracy.pdf</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[4] -
<a href="http://www.satimagingcorp.com/services/orthorectification/">http://www.satimagingcorp.com/services/orthorectification/</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Steve Bower [mailto:sbower@gmavt.net]
<br>
<b>Sent:</b> Thursday, May 07, 2015 10:49 AM<br>
<b>To:</b> Milo van der Linden<br>
<b>Cc:</b> Heather Leson; info@hotosm.org; Ross Taylor; HOT@OSM (Humanitarian OpenStreetMap Team)<br>
<b>Subject:</b> Re: [HOT] [info-hotosm] Reference Project #1030 Nepal Earthquake<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Springfield,<o:p></o:p></p>
<div>
<p class="MsoNormal">You raise important points, and are not "raining on a parade". The resulting data will not be suitable for all purposes, but it can be very useful for this crisis response.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I do think there is significant risk that some mappers will map directly from un-rectified imagery, and introduce problematic location errors. That needs to be minimized, e.g., through clear instructions and good validation. I think there's
room for improvement on the instructions, e.g., it would be good to have a wiki page on mapping from un-rectified imagery in combination with rectified imagery, for crisis response.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Thu, May 7, 2015 at 5:14 AM, Milo van der Linden <<a href="mailto:milo@dogodigi.net" target="_blank">milo@dogodigi.net</a>> wrote:<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Hello Springfield Harrison,<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">As a 20 year GIS veteran I understand what you say. I do agree that in communication with first responders it is important to have them clearly understand that the accuracy of features can be off ~100m. But
for them having maps that give a good indication is way better then having no maps at all. In the end, and that is what I hope for, it can save lives.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I have a long running discussion with y'olde GIS community on "how can a map created by amateurs be better then what we professionals do?". It is my opinion that it can be. I believe that "the many are smarter
than the few" (quote by James Surowiecki). And the HOT tasks have all the ingredients to succeed:<o:p></o:p></p>
</div>
<p class="MsoNormal">1. There is diversity of opinion<o:p></o:p></p>
</div>
<p class="MsoNormal">2. People involved in the mapping process have opinions not influenced by those around them<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">3. People operate decentralized<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">The only thing that might need more attention (and this is where geospatial experts can take their role) is that HOT and openstreetmap as a whole could use more mechanisms to turn all these little "private judgements"
into collective quality. This process could involve analysing quantity and different representations of the same feature through time. In that way, you could see the mapping activity (in dense area's) as GPS. There are faults, influenced by methodology, opinion
and conditions. And as a GPS professional, you know that it is _knowing the error_ that automagically creates accuracy. I would love the GIS/GPS community to think about how to know the error in community mapping.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I love this new way of mapping. It creates new opportunities. It involves new ways of thinking. It is not influenced by what GIS people say GIS should be like.<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">Kind regards, with respect,<o:p></o:p></p>
</div>
<p class="MsoNormal">Milo<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><br>
<br>
<a href="https://en.wikipedia.org/wiki/The_Wisdom_of_Crowds" target="_blank">https://en.wikipedia.org/wiki/The_Wisdom_of_Crowds</a><o:p></o:p></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">2015-05-07 10:21 GMT+02:00 Springfield Harrison <<a href="mailto:stellargps@gmail.com" target="_blank">stellargps@gmail.com</a>>:<o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Hello Steve,<br>
<br>
Sorry to rain on the parade yet again but I find this matter of image alignment to be puzzling and concerning.<br>
<br>
One of the first things I learned when embarking upon GIS/GPS mapping was that accurate georeferencing of all layers, but especially the base layers (imagery in this case) was sacrosanct. If things are not in their correct point in space, what use
is that to the end user? Especially in rugged terrain, with difficult access and rapidly changing stream flows, it is important to know where a trail or road really is. Why try to cross a raging torrent when you don't need to?<br>
<br>
Having untrained users realign the imagery willy-nilly is amazing to me. What faith can anyone have in the new tracings if the earth is literally moving every time a new user opens up the file? Accurate map datums and projections were created for
a reason.<br>
<br>
How is it that, "</span>...the DigitalGlobe 2015-05-03 (DG) images have had minimal georectification.." This is bizarre, this is not GIS, this is merely sketching. Why is such imagery being offered and accepted? I know that this is a major emergency
but then all the more need for quality data.<br>
<br>
However, I am newly arrived, and it seems that most people are content with a world that can be up to 200 m out of whack. I'm not sure if I can contribute much under the circumstances other than this gloomy criticism. Sorry, will try not to dampen
the enthusiasm further.<br>
<br>
Thanks for your patience, Cheers . . . . . . . . Spring<br>
<br>
<br>
<br>
At 06-05-2015 11:59 Wednesday, Steve Bower wrote:<br>
<br>
<o:p></o:p></p>
<p class="MsoNormal">Ross - If you haven't already, see the recent threads on "data alignment to satellite imagery" and "imagery alignment", in the archives for May:<br>
https://lists.openstreetmap.org/pipermail/hot/2015-May/thread.html <br>
<br>
Note some links pointed out there by althio:<br>
 http://wiki.openstreetmap.org/wiki/Using_Imagery <br>
 http://learnosm.org/en/editing/correcting-imagery-offset/ <br>
<br>
Because the DigitalGlobe 2015-05-03 (DG) images have had minimal georectification (needed mainly for elevation distortion), they may be offset by 100m or more. On one tile (5.5km wide) I saw offsets relative to Bing of 125m to the west and, elsewhere, 85m to
the east. The offsets may vary considerable even in nearby areas, especially in steep terrain.Â
<br>
<br>
You should align your work with Bing imagery. Thus to digitize from the DG imagery you should first adjust the DG imagery to the Bing imagery, and re-adjust it as you move from place to place. As you noted, adjusting in one area makes it worse in others, so
you have to keep re-adjusting as you go. You should be able to compare the Bing and DG imagery to confirm where a feature visible on DG is located on the Bing imagery (if Bing is clear enough). I try to adjust based on buildings, or road intersections/curves
(keeping in mind that roads are sometimes relocated), or even less permanent features (rivers generally are not good, they move around to much). It's a time-consuming process, but needed to correctly locate features.<br>
<br>
It's not essential that everything be within a few meters of its true location, but features should be mapped correctly relative to one-another.<br>
<br>
The links above provide guidance on how to align imagery to correct locations. It's easy in JOSM with the Imagery Offset tool (on the toolbar).<br>
<br>
Steve<br>
<br>
On Wed, May 6, 2015 at 1:53 PM, Steve Bower <sbower@gmavt.net> wrote:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
I don't think Chad's IDP guidance document (though very helpful) addresses the issue of spatial accuracy of the DG imagery, raised by Ross. I'm going to post that as a separate issue with more detail.<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">On Wed, May 6, 2015 at 4:35 AM, Heather Leson <heather.leson@hotosm.org > wrote:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
HI Ross, sorry for my delayed response. It is best if you ask your questions on the main Hot@openstreetmap.org mailing list.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Chad provided this guidance document on IDPs http://hotosm.github.io/tracing-guides/guide/Nepal.html#IDP%20Collection%20Guidance
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Hope this helps<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Heather <o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">On Tue, May 5, 2015 at 12:40 AM, Ross Taylor <ross@byrdtechnology.com > wrote:<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Hi, I am seeing many more IDP sites using DigitlaGlobe imagery vs Bing. I can toggle between the two image sets, but they are significantly nonaligned. I created a landuse=brownfield tagged area which aligns with Bing, but if I mark and tag the individual IDP
sites showing up in DigitalGlobe imagery, the brownfield and idp are not going to be aligned. I want to help out as much as possible and would like the data to be correct. Please advise, thanks!<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Note: I tried to adjust alignment but it fixes one area and creates more offset in other areas.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
-Ross<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
Sent from mobile<o:p></o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-left:.5in">_______________________________________________<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">HOT mailing list<o:p></o:p></p>
<p class="MsoNormal" style="margin-left:.5in">HOT@openstreetmap.org<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
https://lists.openstreetmap.org/listinfo/hot<o:p></o:p></p>
<p class="MsoNormal"><br>
<br>
_______________________________________________ HOT mailing list <a href="mailto:HOT@openstreetmap.org" target="_blank">
HOT@openstreetmap.org</a> https://lists.openstreetmap.org/listinfo/hot <o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
HOT mailing list<br>
<a href="mailto:HOT@openstreetmap.org" target="_blank">HOT@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/hot" target="_blank">https://lists.openstreetmap.org/listinfo/hot</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><span class="hoenzb"><span style="color:#888888">-- <o:p></o:p></span></span></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<table class="MsoNormalTable" border="1" cellspacing="0" cellpadding="0" width="353" style="width:264.75pt;border:solid white 1.0pt;border-radius:5px">
<tbody>
<tr style="height:70.5pt">
<td width="88" style="width:66.0pt;border:none;padding:.1in .1in .1in .1in;height:70.5pt">
<p class="MsoNormal"><a href="http://www.dogodigi.net" target="_blank"><span style="border:solid windowtext 1.0pt;padding:0in;text-decoration:none"><img border="0" width="66" height="96" id="_x0000_i1025" src="cid:image001.jpg@01D088D0.999AF9B0" alt="Image removed by sender. http://www.dogodigi.net"></span></a><o:p></o:p></p>
</td>
<td width="230" style="width:172.5pt;border:none;padding:.1in .1in .1in .1in;height:70.5pt;vertical-align:inherit">
<p class="MsoNormal"><b><span style="font-size:17.0pt;font-family:"Arial","sans-serif";color:#888888">Milo van der Linden</span></b><o:p></o:p></p>
<p class="MsoNormal"><span style="color:#666666">web: <a href="http://www.dogodigi.net" target="_blank">
dogodigi</a><br>
</span><span style="font-family:"Arial","sans-serif";color:#666666">tel: <a href="tel:%2B31-6-16598808" target="_blank">
+31-6-16598808</a></span><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
<br>
This electronic communication and any attachments may contain confidential and proprietary information of DigitalGlobe, Inc. If you are not the intended recipient, or an agent or employee responsible for delivering this communication to the intended recipient,
or if you have received this communication in error, please do not print, copy, retransmit, disseminate or otherwise use the information. Please indicate to the sender that you have received this communication in error, and delete the copy you received.
<br>
<br>
DigitalGlobe reserves the right to monitor any electronic communication sent or received by its employees, agents or representatives.
</body>
</html>