<div dir="ltr">Hi Majd,<div><br></div><div>I can show you how to draw more complex buildings using JOSM. L-shaped, C-shaped, using "extrusion". All still very quick. Buildings with rounded corners, all you like. That doesn't solve the low resolution imagery, I realise that.</div><div><br></div><div>The data you want to import, does it include number of floors//height? They seem to be mostly high rise buildings.</div><div><br></div><div><br></div><div>Jo</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-05-02 11:47 GMT+02:00 Majd Al-shihabi <span dir="ltr"><<a href="mailto:majd.al@gmail.com" target="_blank">majd.al@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi folks - thanks for all of the replies. <div><br></div><div>I have a meeting with the AUB-NI folks to see what we can do about licensing. From the sound of it, I don't think that they're strictly against it. </div><div><br></div><div>Tracing over the entire city from aerial imagery is doable, but I'm afraid about a few things:</div><div>1. The aerial imagery from Bing is mostly unusable, partly because it's cloudy. Mapbox imagery is better, but not of a very high resolution. </div><div>2. The architecture in most of Beirut is not as clean and well-defined as most European/North American cities. Buildings are separate but are *very* tightly packed. The low resolution of the aerial images does not help with this. </div><div>3. The building tools plugin for JOSM only draws rectangular buildings, which is not the shape of most buildings in Beirut. Drawing the irregular shapes of the buildings is very important, especially because there is no commonly used address system here, so buildings (and their irregular shapes) become used as landmarks for people to find places. </div><div><br></div><div>I'll let you know what is the result of my meeting with AUB-NI is. </div><div><br></div><div>Cheers,</div><div><br></div><div>/majd</div><div><br></div><div><br></div><div><br></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 2 May 2017 at 11:51, Rory McCann <span dir="ltr"><<a href="mailto:rory@technomancy.org" target="_blank">rory@technomancy.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
So here's a suggestion, rather than doing a semi-manual "import" of this<br>
data, why not just trace the buildings manually from aerial imagery?<br>
You're suggesting a very manual "import" process anyway, so I don't<br>
think a proper tracing mapping party would take much longer? You can use<br>
something like the Tasking Manager, or MapCraft to split the city up<br>
into "cake slices" and just go through them one by one, mapping buildings.<br>
<br>
The JOSM Building Tools plugin is fantastic and can allow you to map<br>
buildings very quickly.<br>
<br>
This has the advantage of not being an import, and you don't need to<br>
think about licencing, you don't need to write software to "show a<br>
random building". You'd be surprised at how fast some people can map<br>
once they get the hang of it.<br>
<br>
Rory<span><br>
<br>
On 28/04/17 15:35, Majd Al-shihabi wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
Hi folks,<br>
<br>
I have been working with an organisation called Public Works Studio to<br>
create a map of housing evictions in Beirut over the past couple of<br>
years. As a part of it, we need a good base map containing buildings in<br>
the city, but unfortunately, OSM doesn't have that yet.<br>
<br>
Through our network, we found out that a group at the American<br>
University of Beirut called The Neighbourhood Initiative (AUB-NI) has<br>
done a survey of all of the buildings in the city. The data can be<br>
viewed here<br></span>
<<a href="https://scholarworks.aub.edu.lb/handle/10938/10283?show=full" rel="noreferrer" target="_blank">https://scholarworks.aub.edu.<wbr>lb/handle/10938/10283?show=ful<wbr>l</a>>. As far<span><br>
as I understand (and of course i'm not a legal expert), the license on<br>
the data from the AUB-NI is not incompatible with the Open Database<br>
License. In any case, my understanding is that they got the data freely<br>
from the municipality.<br>
<br>
Unfortunately, the Lebanon OSM mailing list has been inactive since<br>
2012, but at a recent HOT training, and through my work, I have met a<br>
few people who are interested in activating the community again.<br>
<br>
What we would like to do is to start importing all 20k+ building<br>
polygons into OSM, but do that in a special way. We would like to run a<br>
series of mapathons where people enter the buildings one by one. We<br>
would create a simple tool with the following workflow:<br>
<br></span>
1. Display to the mapper a random building from the available 20k+<br>
buildings<br>
2. Overlay the building on the mapbox satellite images (Mapbox is<br>
clearer than Bing)<br>
3. If<br>
* the building already exists in OSM, discard the new polygon<span><br>
(maybe we can avoid this option by doing some cleaning of the<br>
data using QGIS)<br></span>
* the building does not exist on OSM, and the polygon matches the<span><br>
satellite image, then add as many tags as we know, and upload it<br>
to OSM<br></span>
* the building does not exist on OSM, and the polygon does NOT<span><br>
match the satellite image, then modify the polygon so it<br>
matches, add as many tags as possible, then upload to OSM<br>
<br>
This process serves an important function: to verify the accuracy of the<br>
data from the AUB-NI, especially since the dataset is from 2004, and the<br>
city has changed A LOT since that date.<br>
<br>
>From a technical point of view, I can see three options to do this:<br>
1. The simplest way is to find a way to pass the polygons to the iD<br>
editor (through GET or POST parameters) and have it preselected for the<br>
user to make any modifications to it.<br>
2. Alternatively, we could build an interface that would save the<br>
polygon to OSM *and then* ask the user to verify it.<br>
3. Otherwise (and least desirable option) is to build an entire<br>
javascript app that would implement the workflow.<br>
<br>
I've done a bit of research and option 2 seems like it's the most<br>
feasible one, but I'd like to hear some more thoughts from the community<br>
about this.<br>
<br>
Many thanks for your advice, in advance :)<br>
<br>
/majd<br>
<br>
<br></span><span>
______________________________<wbr>_________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/imports</a><br>
<br>
</span></blockquote><div class="m_-2054456159439519982HOEnZb"><div class="m_-2054456159439519982h5">
<br>
<br>
<br>
______________________________<wbr>_________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org" target="_blank">Imports@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.or<wbr>g/listinfo/imports</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>_________________<br>
Imports mailing list<br>
<a href="mailto:Imports@openstreetmap.org">Imports@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/imports" rel="noreferrer" target="_blank">https://lists.openstreetmap.<wbr>org/listinfo/imports</a><br>
<br></blockquote></div><br></div>