<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt">Martin,<br><br>For HOT Activations in Mali and Congo, I had this experience of detecting where Bing High Res Imagery is available. This is like a gruyere cheese. To detect areas, you have to zoom in and cover large areas. This is a tedious work and I have not find other ways then tracing polygons. The tools you list are not precise enough to do that very precisely. Some areas are colored red, and when you zoom in, this becomes green.<br><br>If you want to help us and test a better way, I would be pleased. Otherwise, please do not remove these polygons.<br><br><div> <br><br></div><div><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;">Pierre <br></span><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-family: arial, helvetica,
sans-serif; font-size: 10pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">De :</span></b> Martin Koppenhoefer <dieterdreist@gmail.com><br> <b><span style="font-weight: bold;">À :</span></b> Stephan Knauss <osm@stephans-server.de> <br><b><span style="font-weight: bold;">Cc :</span></b> osm <talk@openstreetmap.org> <br> <b><span style="font-weight: bold;">Envoyé le :</span></b> Lundi 1 avril 2013 6h20<br> <b><span style="font-weight: bold;">Objet :</span></b> Re: [OSM-talk] Imagery Boundary?<br> </font> </div> <br><meta http-equiv="x-dns-prefetch-control" content="off"><div id="yiv2003687189"><div dir="ltr"><div class="yiv2003687189gmail_extra"><br><div class="yiv2003687189gmail_quote">2013/4/1 Stephan Knauss <span dir="ltr"><<a rel="nofollow"
ymailto="mailto:osm@stephans-server.de" target="_blank" href="mailto:osm@stephans-server.de">osm@stephans-server.de</a>></span><br><blockquote class="yiv2003687189gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
<div class="yiv2003687189im">Florian Lohoff writes: <br>
<blockquote class="yiv2003687189gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
As they were wrong and nobody cared i deleted them.<br>
</blockquote></div>
A better way of dealing with updated data in OSM is usually to fix and not to delete data. Had you considered mailing the users who created the original data before removing their work? <br></blockquote><div><br></div><div>
<br></div><div><br></div><div style="">please take a step back: imagery coverage of external providers is not geographic "data". I am not saying it is completely useless in cases it actually describes the boundaries of imagery coverage in areas with few local mappers (because local mappers usually know the boundaries and don't need coverage polygons), but when the coverage changes (e.g. gaps get filled, coverage gets completed) these polygons really become useless.</div>
<div style=""><br></div><div> </div><blockquote class="yiv2003687189gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
In contrast to eg. underground power lines (seen them mapped in Munich) or TMC data or obscure boundaries, this is data which is easy to verify and used in the more remote areas of the world.<br></blockquote><div><br></div>
<div><br></div><div><br></div><div style="">used for what? The only purpose I can imagine is find areas in the editor with few data where good imagery enables you to trace more stuff out of this imagery. A scope that can be achieved also with external tools like <a rel="nofollow" target="_blank" href="http://ant.dev.openstreetmap.org/bingimageanalyzer/">http://ant.dev.openstreetmap.org/bingimageanalyzer/</a> and <a rel="nofollow" target="_blank" href="http://mvexel.dev.openstreetmap.org/bing/">http://mvexel.dev.openstreetmap.org/bing/</a></div>
<div style=""><br></div><div> </div><blockquote class="yiv2003687189gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
You might not believe it, but there are areas which still have only the low-resolution landsat images. Quite often it's the same areas that lack mapping of major highways.</blockquote><div><br></div><div><br></div><div style="">
sure, but how do coverage boundaries that show that there is no good imagery to refine the data help in these cases?</div><div style=""><br></div><div> </div><blockquote class="yiv2003687189gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex;">
The imagery boundaries are used to give oversea mappers a hint where areas are that can benefit from remote mapping, to complete at least major highways and water features.<br></blockquote></div><br><br>+1, and that's all these boundaries can achieve, and to achieve this it is essential that the coverage is reflecting the actual state. </div>
<div class="yiv2003687189gmail_extra"><br></div><div class="yiv2003687189gmail_extra" style="">Btw.: how many boundaries shall we tolerate? For every imagery provider and every zoom level? I often encountered boundaries that were more or less detailed in lower zoom levels but didn't perfectly reflect the situation for high zoom levels. When tracing in a remote country it is usually "automatic" that you discover the bounds of the good imagery, personally I never needed a meta data polygon for this ;-)</div>
<div class="yiv2003687189gmail_extra" style=""><br></div><div class="yiv2003687189gmail_extra" style="">cheers,</div><div class="yiv2003687189gmail_extra" style="">Martin</div></div>
</div><meta http-equiv="x-dns-prefetch-control" content="on"><br>_______________________________________________<br>talk mailing list<br><a ymailto="mailto:talk@openstreetmap.org" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br><a href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br><br><br> </div> </div> </blockquote></div> </div></body></html>