Because I didn't want to leave the comment field empty. And since I didn't use any aerial imagery, I decided to put the only thing I used, aside from just plain logic to look and see that the landuse was cutting through buildings. But actually you can do whatever you feel you have to do with the changeset its fine, I've moved on to other matters. Thanks, best,

Thanks, I understood the restrictions on Google Earth, I was not aware of them, thanks for letting me know. But I disagree with reverting the changeset. I only used Google Earth to find the location of the aquatic settlement. Once found, the changes on OSM were done without any tracing, I only edited the geometry of some landuse polygons, which were not aligned, and were overlapping (which is also a error, regardless of the source, and it was now corrected). This has nothing to do with Google Earth. Could you please reinstate the changeset? Many thanks.

Actually could not find addr:quarter on the wiki (addr=*). And addr:district doesn't work because it is a higher level admin boundary, one that groups several neighbourhoods (that we tag addr:subdistrict). I don't see anything suitable below addr:subdistrict level that would correspond to a block...

Thank you very much. We will correct the toilets as per your suggestion (found this toilets=*). Will also replace quarteirao as you suggested. Will look once again for similar replacements to the other custom tags we created. Will let you know. Many thanks,

Hi @mueschel thank you very much for reaching out. It is inspiring to know the community is being attentive.

Please allow us a couple of days to get back to you with a proper answer to each of the questions you raised. For now let me advance these brief comments:

- we are mostly well-aware of the recommended mapping procedures and ethics. But we also try to push the possibilities that the platform gives us as far as possible. This sometimes includes creating work-arounds when we don't find a conventional way of contributing to the Map, but we know and ensure to always stay within the boundaries of what is right. We would love to discuss the data (for instance number of inhabitants) in more detail, and please know we left out a whole lot of data that we considered private.

- the OSM tagging system has a very strong western-bias, and a lot of features and attributes that are common and important in African informal settlements are not accounted for in the official tagging lists. This is a much broader issue that we would be very happy to discuss more about.

As I said we will provide a more detailed response to the questions raised, and we are open to removing any data that is deemed inadequate after we discuss.
Again many many thanks for your contact, talk soon.

Hi Jan, "route_ref" does not appear to be a predefined tag... Is it used elsewhere in OSM or was your suggestion specific for our case? Or is there something I'm not seeing?
Thanks,

Thanks Jan! Very useful! Wish I had known before, we opted for using a general tag (description) exactly because we thought there was no specific way to indicate which routes pass on a given stop. Your suggestion comes in handy and it will free up the description tag for other uses. Its perfect many thanks. If you bump on anything else we could do better let me know. Thanks