<div dir="ltr">Hello Tobias<br><br>I was the developer of the software used for this
import currently ongoing by the Spanish community. Our intention is to
improve the map in the best possible way so I would like to correct the
tagging problem you mention. I will translate this point to the Spanish
community to evaluate it.<br><br>I would like to denote that this is not
an automated import. Since it began many people have devoted and still
makes a big effort to get it done reviewing and improving each bit of
data before uploading it manually. Although there is a considerable
amount of data already imported, there is still a long way to go to
complete the entire amount available.<br><br>I could retake the software
development in order to correct this issue for the non completed part
of the import as soon as possible.<br><br>Regarding the already imported
data, I will take a look on ways to correct it, but take into
consideration that it's not an easy task.<br><br>A significant amount of
the data may have been modified before being imported due to our data
flow that consists of each building being reviewed by a person before
upload. These modifications may include, among others, topology
improvements like deletion of noisy unneeded nodes, checks against high
resolution background aerial imagery that include precision
repositioning or even geometry fixes. So to add the missing building
part it's not only necessary to filter buildings (and its parts) edited
after the import but all those whose geometries differ in the least. <br><br>This
process would have to be automatic because I do not believe that the
participants in the importation can assume the amount of effort
necessary to review 3 years of editions. <br><br><div>I never developed a
project like this correction before, so I would like to hear more
opinions and to see a good consensus about its necessity.</div><div><br></div><div>Best regards,</div><div>Javier Sanchez</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El mar, 2 mar 2021 a las 20:18, Tobias Knerr (<<a href="mailto:osm@tobias-knerr.de">osm@tobias-knerr.de</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi all,<br>
<br>
I stumbled upon an issue with the ongoing Spanish Cadastre buildings <br>
import that was discussed on this list in 2018.[1]<br>
<br>
The imported data does not follow the Simple 3D Building tagging <br>
standard[2]. If a building consists of 2 parts, the import will only <br>
create 1 building:part area, rather than 2 building:part areas, and <br>
assumes that renderers will create a virtual building part for the <br>
remainder of the building.<br>
<br>
One of many examples:<br>
<a href="https://www.openstreetmap.org/way/840244312" rel="noreferrer" target="_blank">https://www.openstreetmap.org/way/840244312</a><br>
<a href="https://www.openstreetmap.org/way/840244317" rel="noreferrer" target="_blank">https://www.openstreetmap.org/way/840244317</a><br>
<br>
It turns out that deleting these building parts before the import is an <br>
intentional attempt to reduce the volume of data in the OSM database, <br>
and is in fact documented on the import's "Data Conversion/Problems" <br>
subpage: <br>
<a href="https://wiki.openstreetmap.org/wiki/Spanish_Cadastre/Buildings_Import/Data_Conversion/Problems#Reduction_of_building_parts" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Spanish_Cadastre/Buildings_Import/Data_Conversion/Problems#Reduction_of_building_parts</a><br>
<br>
This bit of information is very easy to miss. I certainly didn't notice <br>
it when first reviewing the import, and I suspect others didn't either. <br>
If an import intentionally departs from documented tagging practices, I <br>
would expect this to be given far more attention during discussion of <br>
the import.<br>
<br>
In the interest of consistent tagging, I would like to see this <br>
behaviour corrected at least for the part of the import that hasn't been <br>
completed yet, and ideally also for already-imported data that hasn't <br>
seen any major manual editing since.<br>
<br>
Yours,<br>
Tobias<br>
<br>
[1] <br>
<a href="https://lists.openstreetmap.org/pipermail/imports/2018-January/005342.html" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/pipermail/imports/2018-January/005342.html</a><br>
[2] <a href="https://wiki.openstreetmap.org/wiki/Simple_3D_Buildings" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/Simple_3D_Buildings</a><br>
<br>
_______________________________________________<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.org/listinfo/imports</a><br>
</blockquote></div>