Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add rendering for historic=ruins #331

Open
EdLoach opened this issue Feb 7, 2014 · 100 comments
Open

Add rendering for historic=ruins #331

EdLoach opened this issue Feb 7, 2014 · 100 comments
Assignees
Milestone

Comments

@EdLoach
Copy link

EdLoach commented Feb 7, 2014

Neither POI or area/multipolygon ruins are currently rendered. http://www.openstreetmap.org/note/114642 brought this to my attention, as the castle named in the note is already mapped as both POI and multipolygon.

For POI, perhaps just the name rendered, and for areas - well I'll let you pick a suitable colour. The wiki also suggests a lot of ways are also tagged as ruins - perhaps for these render a bit like generic barriers?

@thecrazychemist
Copy link

Yes, there is a need for this. historic=ruins should render on the map.

@matthijsmelissen matthijsmelissen added this to the New features milestone Aug 18, 2014
@matthijsmelissen matthijsmelissen changed the title historic=ruins (request to render them) Add rendering for historic=ruins Sep 24, 2014
@kocio-pl
Copy link
Collaborator

I guess dashed outline (as mentioned here, citing OsmAnd) could work as a visual hint.

@nebulon42
Copy link
Contributor

I don't think that works for historic=ruins. AFAIK OsmAnd uses an icon (shown in the screen) for historic=ruins. A dashed outline makes only sense for building=ruins (see #1898).

@dieterdreist
Copy link

sent from a phone

Il giorno 24 set 2016, alle ore 21:07, Michael Glanznig [email protected] ha scritto:

I don't think that works for historic=ruins.

what s the difference to archaeological site? Maybe we can use the same rendering?

@kocio-pl
Copy link
Collaborator

@kocio-pl kocio-pl self-assigned this Sep 23, 2017
@kocio-pl
Copy link
Collaborator

Example rendering on z17:
yfahggcc

@polarbearing
Copy link
Contributor

The separate shape above is implausible, what is it supposed to be?

@kocio-pl
Copy link
Collaborator

I agree that ruined castle icon is not working in practice. I guess we can use the idea of decomposed shape for something simpler, like house.

@ghost
Copy link

ghost commented Sep 25, 2017

It is directly derived from the castle icon. I could change it to a version where the parts are joined.

@kocio-pl
Copy link
Collaborator

Please try, we're still looking for something good enough.

@SomeoneElseOSM
Copy link
Contributor

FWIW (different map) for nodes I went for the name and a dot, in a "historical" colour https://map.atownsend.org.uk/maps/map/map.html#zoom=17&lat=53.429972&lon=-1.26303 and for ways the name if present and a "not quite a building" colour https://map.atownsend.org.uk/maps/map/map.html#zoom=19&lat=53.122449&lon=-1.853998 and https://map.atownsend.org.uk/maps/map/map.html#zoom=20&lat=53.2699203&lon=-1.989286 .

The actual colours won't transfer to OSM Carto, but I'm not convinced you need a "characteristic" icon - the name normally describes the thing well enough.

@ghost
Copy link

ghost commented Sep 28, 2017

@kocio-pl
Copy link
Collaborator

Still not recognizable for me at 14 px.

@ghost
Copy link

ghost commented Oct 2, 2017

I prefer version 3 the most.

Btw. are there any icons, which should be created?

@kocio-pl
Copy link
Collaborator

kocio-pl commented Oct 2, 2017

Nice try, but none of them work for me at 14px (32 px would be OK). I was thinking about solid, easy to recognize shape like a simple house as a base.

@PontiacCZ
Copy link

PontiacCZ commented Oct 2, 2017

I like Building_ruins_generic6.svg... and Building_ruins_generic4.svg as well.

@kocio-pl
Copy link
Collaborator

kocio-pl commented Oct 2, 2017

Btw. are there any icons, which should be created?

Sure, you may for example look at #131, #152, #2518, #1870, #958, #2856...

@kocio-pl
Copy link
Collaborator

kocio-pl commented Oct 2, 2017

@PontiacCZ Try to look at 14 px version only, because that's the only thing the user will see.

@PontiacCZ
Copy link

Yep, that's what I actually did, I compared icons in the "Icon original size" row on the summary page and my Firefox tells me they're 14 px wide.

Well, the more I look at the variants the more I like Building_ruins_generic6.svg (Building_ruins_generic6.svg) - the concept of one fallen tower and the other one still standing is pretty clear for me to understand it as ruins.

I am not sure, MastroGlanz, what you mean by version 3 - is it Building_ruins_generic4.svg (Building_ruins_generic4.svg)? Pretty nice as well, for me on the 2nd place.

But any of those would be better than none.

BTW kocio-pl, you have mentioned that "one of them work for me at 14px". Which one is it?

@kocio-pl
Copy link
Collaborator

kocio-pl commented Oct 2, 2017

I meant "none" - sorry for the typo.

6 is a nice concept, but the details are too small for me, so it looks just like 2 rectangles, with no connection to buildings.

@dieterdreist
Copy link

dieterdreist commented Nov 12, 2020 via email

@DujaOSM
Copy link

DujaOSM commented Nov 12, 2020

historically significant ruins are always archaeological sites, and this style tries to avoid rendering several tags with the same meaning. For other ruins we would want a different rendering anyway.

I disagree. I've always interpreted a historic=archaeological_site as something known to have undergone a documented archaeological research, and possibly still marked as such in situ, with a information board or a fence.

Historic=ruins is used for ruins of lesser, former or unknown archaeological interest, but which are nonetheless important local landmarks. I cannot think of a better tag for several objects I mapped recently, e.g:

https://www.wikiloc.com/hiking-trails/fruska-gora-popovica-okretiste-raskrsnica-borove-sume-vaga-raskrsnica-borove-sume-jezero-popovica-o-29555178/photo-18887728
Remnants of quarry cable car station, abandoned since 1920s. Important landmark for hikers. Worked around using man_made=tower.

https://www.wikiloc.com/hiking-trails/ps-fruska-gora-170205-crveni-cot-sajlovac-gradac-potoranj-stranputica-tancos-krug-16339306/photo-10245666
Mapped today. Late Roman-period military outpost hidden in a remote forest. Could perhaps apply archaeological_site, but I do not know about any excavations.

https://fruskac.net/en/locations/misc/old-church-saint-george
Walls of a late medieval church.

Historic=ruins is documented in OSM wiki, supported as an iD preset, and, with near 150,000 objects, it is one of most popular tags not rendered on Carto. And I don't think those are going away anytime soon.

@ghost
Copy link

ghost commented Nov 12, 2020

I made 13 suggestions here. I think, there should be a one fitting:
https://wiki.openstreetmap.org/wiki/User:MeastroGlanz

If you want another one, another style, let me know.

@jeisenbe
Copy link
Collaborator

These three objects are quite different: 1) "Remnants of quarry cable car station”, 2) "Late Roman-period military outpost hidden in a remote forest”, 3) "ruined late medieval stone church”. Consider that the last could also be tagged abandoned:building or abandoned:amenity. I’d suggest discussing how to tag these on a more appropriate forum, such as help.openstreetmap.org or the Tagging mailing list.

@DujaOSM
Copy link

DujaOSM commented Nov 13, 2020

A 40-story skyscraper, a 10,000 m2 shopping mall and a backyard shed are also quite different objects, yet we permit tagging them all with building=yes. Conceptually, historic=ruins are not much different, "here are the ruins of a rather old object", and one can apply other tags to describe them closer.

I do read (but do not participate in) tagging and talk mailing lists, and, with respect, I don't remember anything ever solved there. I think that moving discussion to another forum would be a good way to not solve it for another 6 years. With over 100,000 uses, documentation in wiki and support in iD, I believe mappers have already "voted with their feet" about the issue.

Consider that the last could also be tagged abandoned:building or abandoned:amenity.

It certainly could, but that would not render in Carto either.

@dieterdreist
Copy link

dieterdreist commented Nov 13, 2020 via email

@DujaOSM
Copy link

DujaOSM commented Nov 13, 2020

we do not advocate or encourage tagging them the same

Certainly. But we render them nonetheless.

@imagico
Copy link
Collaborator

imagico commented Nov 13, 2020

@DujaOSM - the meaning of building=yes is pretty well defined and it is used with high consistency according to this meaning (crappy AI based imports aside). Yes, it is a broad tag, but that is not a problem and that is neither the problem why historic=ruins is currently not rendered.

If you think historic=ruins is a well defined tag consistently used according to this definition we invite you to present this view here. Above in #331 (comment) you indicated that in your view the difference between historic=ruins and historic=archaeological_site is one of significance, notability and on-site documentation. Verifiability issues with that aside - if this is the consensus delineation between the two tags that should be (a) documented on the wiki and (b) confirmed to be actually reflected in use of the tags in the database.

@DujaOSM
Copy link

DujaOSM commented Nov 13, 2020

@imagico I'm afraid you're asking for shrubbery. How can I prove or disprove that historic=ruins is "consistently used according to this definition" except by data mining thousands of objects and comparing them with real-world objects that I'm not familiar with? All I can do is to quote the wiki and hope that the text has been forged by consensus and reasonably followed by mappers:

The tag historic=ruins is used with ruins that are of historic importance, where it is not possible, or not appropriate, to be more specific about the type of structure that is now in ruins.
historic=ruins is a generic description, that records only a limited amount of information. More specific approaches are preferred whenever it is possible to describe the original type of structure that is now in ruins. To some extent, contributors can use alternative forms to suggest the degree to which a structure is ruined. Although they both provide similar information, a form such as historic=ruins,ruins=castle suggests a structure that is mainly in ruins, while a form such as historic=castle,ruins=yes suggests a structure that still appears much like a castle.
Generally, most older ruins can also be described with historic=archaeological_site and its subtags.

Besides, what this has to do with rendering or not rendering in Carto? I really did not come here for that discussion, but to report an issue that irked me for a while (and I found this one by searching). In my opinion, the default and flagship map style of the project ought to render all reasonably common and on-wiki documented map features, regardless of any ongoing disagreement about the exact scope. I don't really care which visual style is applied as long as the object is somehow rendered on the map.

@imagico
Copy link
Collaborator

imagico commented Nov 13, 2020

In my opinion, the default and flagship map style of the project ought to render all reasonably common and on-wiki documented map features, regardless of any ongoing disagreement about the exact scope.

Well - that is not going to happen as @jeisenbe explained. Again - we invite you to argue for feature addition under the premises and goals of this style but if you don't want to do that it will have to wait until someone else does.

Yesterday i presented some numbers from taginfo (supplemented by @dieterdreist) that could be used (in combination with the discussion in #4238) as a starting point for sorting out how different tags in the historic/abandoned/ruined structures field are practically used. This is all no rocket science, taginfo and overpass turbo are your friends here (also geofabrik's regional taginfo instances can help you with analyzing regional differences). Sometimes you might need to run a planet file through osmium for some more detailed stats. And yes, geographic knowledge is useful here as well as the ability and willingness to discuss tagging with other mappers on the usual channels.

You write:

I don't really care which visual style is applied as long as the object is somehow rendered on the map.

Well - we do and we take our responsibility to produce a style of decent cartographic quality and pursuit of our documented goals seriously. So our perspectives here differ. If that causes incomprehension and annoyance on your side i can relate but this does not change the situation in substance.

@DujaOSM
Copy link

DujaOSM commented Nov 13, 2020

"An engineer is a person that makes something work. An expert is a person that can thoroughly explain why something cannot work."

Going back to my engineering business, then. Sorry for wasting your time.

@dieterdreist
Copy link

dieterdreist commented Nov 13, 2020 via email

@DujaOSM
Copy link

DujaOSM commented Nov 13, 2020

We can argue all day about differences between historic=archaeological_site, historic=ruins, building=ruins and abandoned:building. The fact of the day is, there are some 200,000+ verifiable ruins on the ground, and thousands good-faith mappers of who know or do not know about their importance and other details have entered those in our database, but we do not find those worth rendering because shrubbery.

Accidentally, I've just stumbled upon this:

Anders Torger wrote Sat Nov 7 11:21:26 UTC 2020
And now to the most important point, whether one likes it or not,
OSM-Carto as being the face of OSM and the most commonly used style, is
the de-facto reference and driver of features and tagging. If OSM-Carto
doesn't support basic cartography features many mappers won't be
motivated to tag for that, and then the cartographic styles will have
less information than they need to make good maps. OSM-Carto due to its
limited rendering capabilities also make casual mappers tempted to "tag
for the renderer" just to get results, which for example can mean that
villages are upped, and thus the cartographic style will get fed with
incorrect information.

This morning I found out the location of those Roman-era ruins so I wanted it to map them and show to my friends, so that's what brought me here. I'm now going off to tag those for the renderer. Building=whatever will do, I suppose.

@dieterdreist
Copy link

dieterdreist commented Nov 13, 2020 via email

@ferdi2005
Copy link

I gather that historic=ruins is not rendered because there's already historic=archeological_site. So, in your views, should the ruins of a church destroyed by Second World War bombings tagged with historic=archeological_site?

@Adamant36
Copy link
Contributor

I don't know how things work in Germany, but there'a a couple of places from the early 1900s that are archeology sites near where I live in California. I'm pretty sure there's a submerged town from the late 40s a few miles away that's also an archeology site. It doesn't really have anything to do with age of the site, more if it can be excavated for artifacts or other physical objects for the purpose of analyzing them. So I'd assume a building bombed out in WW2 would count. At the end of the day it's probably still archeologists doing the excavation and analysis if someone wants to study the area.

@imagico
Copy link
Collaborator

imagico commented Aug 30, 2022

I gather that historic=ruins is not rendered because there's already historic=archeological_site.

No, historic=archeological_site is rendered here because it has been rendered in this style predecessor already.

No tags indicating ruined/historic structures are specifically rendered so far because the tagging used for those is complicated and not very well defined and no one so far has invested the time to look at this in more depth and analyze how the various tags in that context (see #331 (comment), #331 (comment)) are used and come up with a rendering concept that reflects that.

This issue is open, work on solving it is welcome. What is needed here is:

  1. Someone with the skills to analyze tag use in OSM to look over how the various tags in this context are practically used. Some experience with ruined/historic structures in different parts of the world would be beneficial for that.
  2. Based on that someone with design skills to develop a rendering concept for those tags that are widely used with a consistent meaning that supports mappers in this use of the tag and does not mislead them to using the tags for different purposes.

Neither of these tasks is rocket science. But it requires some ambition beyond the level of i want this tag rendered, i don't care how.

@dieterdreist
Copy link

dieterdreist commented Aug 30, 2022

Yes, historic=ruins is a tag that is used for all kind of things, from the insignificant abandoned and collapsed shed on a field to historic ruins of bigger buildings and likely of more general interest. My advice is to avoid the tag where alternatives are available and prefer historic=archaeological_site over historic=ruins whereever possible. It also has more subtags for additional description and classification. There are also other (more specific feature-) tags under the historic key that sometimes may fit well.

@imagico
Copy link
Collaborator

imagico commented Aug 30, 2022

@dieterdreist - please don't turn this into a tagging discussion. Use number for historic=ruins and historic=archaeological_site are fairly similar - see #331 (comment). And i would not say from my superficial impression that one of them is necessarily used more consistently than the other. We do not tell people here to use one tag over the other, just because it would be convenient for us because we happen to render one of them for historic reasons and not the other.

If there are reasons to definitely avoid rendering historic=ruins based on practical use of the tags please present them. Otherwise my suggestion to analyze the tagging practice in this context and to develop a rendering scheme based on that stands.

@ghost
Copy link

ghost commented Sep 13, 2022

@imagico Propose a rendering rule, I would say, then we can discuss it. I suggest like this:

  • tag_1=x, tag_2=y: reason
  • tag_3......

The goal must be to render ruins, that

  • can be visited
  • have historical value

Historical value defined as

  • listed as historical landmark or building by public authorities
  • would be listed as such in a first world country

The second one is not razor sharp, but we can not get this information from the tagging directly anyway. The question is, where is such a meaning implied by the tags and how.

This would be also a topic for @westnordost and streetcomplete: Is this ruin really a historical landmark? With result as last_checked-tag. Or is_landmark=%date by %user. There is certainly a better solution.

@Adamant36
Copy link
Contributor

Historical value defined as

listed as historical landmark or building by public authorities

would be listed as such in a first world country

Neither of those things are implicit in how the tag is currently being used. All the Wiki article for the tag says is "The tag historic=ruins is used with ruins that are of historic importance." There's nothing about the ruins having to be designated as such by a public authority or that they have to be on some listing somewhere (I don't know how anyone could confirm either thing in most cases anyway).

@Janjko
Copy link

Janjko commented May 30, 2023

Why don't we redirect this issue towards rendering combinations like historic=ruins + ruins=castle;fort;church. That way we at least have historically significant poi's covered.

@BertMule
Copy link

Ran into this problem.
No rendering, nothing to be seen.
Not as a line, not as an area.
Why map at all?

Gave up and searched for an issue.
Which exists since 2014. That's 10 years,
Nothing changed.

Why? How does this work? Does anything change?
This is not the first time.

@imagico
Copy link
Collaborator

imagico commented Mar 29, 2024

Current state of this issue and what needs to be done to solve it is clearly documented in #331 (comment).

@SomeoneElseOSM
Copy link
Contributor

@BertMule With regard to the first part of #331 (comment) :

Someone with the skills to analyze tag use in OSM to look over how the various tags in this context are practically used. Some experience with ruined/historic structures in different parts of the world would be beneficial for that.

I've done that for usage in UK/IE, and the resulting processing can be seen at https://github.com/SomeoneElseOSM/SomeoneElse-style/blob/master/style.lua (search for "ruins"). To summarise, it really doesn't make sense to render historic=ruins as a separate thing; you need to figure out what sort of thing it is a ruined version of.

My implementation is mostly in lua (which this style uses for some processing, but not much). I suspect you would be able to do at least some of that in select statements in the .mml / .mss files that this style uses, but I certainly won't be volunteering to do that. However, you (or anyone else) wants to take this work on I'd be happy to explain how to do the "analyze tag use in OSM" part (and to share what I did myself previously).

To see what this looks like try an overpass query like this one and, click through to OSM, and move the map slightly to get the "map=" layer and co-ordinate details. Then use that same value at map.atownsend.org.uk to see the results.

@imagico
Copy link
Collaborator

imagico commented Mar 30, 2024

I've done that for usage in UK/IE, and the resulting processing can be seen at [...]

Although we of course need to look at global use and not just at a small region it would be helpful - not only for OSM-Carto but also for data users in general - if you'd publish the results of your analysis so people would not need to try to infer that from the tag interpretation logic you use after reconstructing that from some lengthy spaghetti lua 😉.

Learning (and teaching) how to determine quantitative data on use of tags is valuable. But at least as important is learning how to analyze this data to determine established mapping practice and de facto meaning of tags. The latter in my experience is mostly learned by example - having people experienced in the field demonstrate how they look at the data, analyze it and come to their conclusions. I try to do that here as much as possible, but it would definitely be of high value if others with a different perspective and different communication style would demonstrate their approach more often as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests