<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">What surprises is that such colossal
structures as Eiffel Tower [1], Emley Moor Mast [2], Ostankino
Tower [3], etc. do not even have an icon on the OSM map. They look
as an usual building at best. Just for comparison, - on Google map
it is immediately visible that it is a tall structure [1][2][3],
and it's right. These are really tall, hundreds of meters, towers
made of steel and concrete, which are and will be standing for
centuries. <br>
<br>
Verticalization is an inevitable complex process in urban
development, so 3D is necessary. The good place to start would be
these "elephants in the room". However, drawing turrets of normal
buildings in 3D in my opinion is still an experiment, a "future
music".<br>
<br>
[1]<br>
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Eiffel_Tower">https://en.wikipedia.org/wiki/Eiffel_Tower</a><br>
<a class="moz-txt-link-freetext" href="http://osm.org/go/0BOdUuUUg">http://osm.org/go/0BOdUuUUg</a><br>
<a class="moz-txt-link-freetext" href="https://www.google.com/maps/@48.8581675,2.2947875,18.31z">https://www.google.com/maps/@48.8581675,2.2947875,18.31z</a><br>
<br>
[2]<br>
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Emley_Moor_transmitting_station">https://en.wikipedia.org/wiki/Emley_Moor_transmitting_station</a><br>
<a class="moz-txt-link-freetext" href="http://osm.org/go/evinV00xh">http://osm.org/go/evinV00xh</a>-<br>
<a class="moz-txt-link-freetext" href="https://www.google.com/maps/@53.6121585,-1.6630658,17.75z">https://www.google.com/maps/@53.6121585,-1.6630658,17.75z</a><br>
<br>
[3]<br>
<a class="moz-txt-link-freetext" href="https://en.wikipedia.org/wiki/Ostankino_Tower">https://en.wikipedia.org/wiki/Ostankino_Tower</a><br>
<a class="moz-txt-link-freetext" href="https://www.openstreetmap.org/#map=18/55.81972/37.61209">https://www.openstreetmap.org/#map=18/55.81972/37.61209</a><br>
<a class="moz-txt-link-freetext" href="https://www.google.com/maps/@55.819668,37.6118877,18.31z">https://www.google.com/maps/@55.819668,37.6118877,18.31z</a><br>
<br>
Best regards,<br>
Oleksiy<br>
<br>
On 17/06/16 18:50, Martin Koppenhoefer wrote:<br>
</div>
<blockquote
cite="mid:CABPTjTCptKSRCAAU9wxdgHLhDZVYttOHOb5njw1Uw652_Ttugw@mail.gmail.com"
type="cite">
<div dir="ltr">With this mail I would like to open a general
discussion, whether it makes sense to add detailed 3D data into
the current OSM db. <br>
<div><br>
Living in a historic city with lots of tourists (many of them
mappers apparently), and lots of famous monuments, I am
observing for years now, that more and more detailed 3D
objects get mapped.<br>
<br>
</div>
<div>While at first this seemed to be an interesting (and maybe
logical) development of some advanced mappers, to further push
the limits of mapping, more and more doubts have grown in the
meantime whether this kind of data is sustainable.
Particularly because the raised complexity leads to many
errors, where people recreate already existing objects or add
localized name tags (or other tags) to (building:)parts that
are mainly there for geometric representation in 3d, but are
not the objects that actually represent the feature (i.e.
those that have most of the tags). Subsequently other mappers
find these objects (with some tags) and add more, and after a
while it can become plain chaos, until someone with a lot of
time dedicates herself to clean the mess up.<br>
<br>
</div>
<div>And honestly, I can understand this happening, these
objects are really complex and after something has been
"3D-fied" it becomes at least time consuming, if not
completely confusing to make any simple edit (like adding a
new tag), because you have to search the "main object" and
understand where to put the tag.<br>
<br>
</div>
<div>I believe there is something conceptually wrong with adding
those 3D-monsters into the common db and require from
everybody to understand them, without proper support or
hierarchy on an API- or editor-level.<br>
<br>
</div>
<div>(a side-issue is that many monuments like columns, obelisks
and similar are modelled as "building:parts", where there
clearly is nothing that is a building, but rather a massive
stone)<br>
</div>
<div><br>
</div>
<div>Some examples (load them in your editor to understand what
I am talking about):<br>
<br>
<a moz-do-not-send="true"
href="https://www.openstreetmap.org/#map=19/41.90224/12.45784">https://www.openstreetmap.org/#map=19/41.90224/12.45784</a><br>
<a moz-do-not-send="true"
href="https://www.openstreetmap.org/#map=19/41.90297/12.46658">https://www.openstreetmap.org/#map=19/41.90297/12.46658</a><br>
<a moz-do-not-send="true"
href="https://www.openstreetmap.org/#map=19/41.89591/12.48466">https://www.openstreetmap.org/#map=19/41.89591/12.48466</a>
(the Trajan's column, a simple column consisting in osm of 9
concentric objects! Find the right one, if all of them get
their name rendered at the same spot in the editor)<br>
<a moz-do-not-send="true"
href="https://www.openstreetmap.org/#map=19/41.89854/12.47695">https://www.openstreetmap.org/#map=19/41.89854/12.47695</a>
(the Pantheon, countless times there pop up duplicates as
nodes)<br>
<br>
</div>
<div>What are your experiences? <br>
<br>
<br>
</div>
<div>Cheers,<br>
</div>
<div>Martin<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
talk mailing list
<a class="moz-txt-link-abbreviated" href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk">https://lists.openstreetmap.org/listinfo/talk</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>