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

Suppress "historical" feature label_position until zoom 17+ #291

Closed
nvkelso opened this issue Oct 3, 2015 · 6 comments
Closed

Suppress "historical" feature label_position until zoom 17+ #291

nvkelso opened this issue Oct 3, 2015 · 6 comments
Assignees
Milestone

Comments

@nvkelso
Copy link
Member

nvkelso commented Oct 3, 2015

#15/37.7697/-122.1435

https://www.openstreetmap.org/edit?#map=16/37.7693/-122.1452
https://www.openstreetmap.org/relation/317369

Sometimes these are points, sometimes they're landuse AOIs. We should still show the AOI, but the label shouldn't show until zoom 17+ (was z15+, revised recommendation 13 Jan 2016).

screen shot 2015-10-03 at 15 21 06

screen shot 2015-10-03 at 15 20 56

@nvkelso nvkelso added this to the Compilation 2.1 milestone Oct 3, 2015
@nvkelso
Copy link
Member Author

nvkelso commented Oct 3, 2015

Related: #267.

@nvkelso nvkelso removed this from the Compilation 2.1 milestone Oct 18, 2015
@nvkelso nvkelso added the ready label Dec 18, 2015
@nvkelso nvkelso added this to the v0.7.0 milestone Dec 18, 2015
@nvkelso nvkelso removed the ready label Jan 8, 2016
@nvkelso nvkelso modified the milestones: v0.8.0, v0.7.0 Jan 8, 2016
@nvkelso nvkelso changed the title Suppress "historical" feature label_position until zoom 15+ Suppress "historical" feature label_position until zoom 17+ Jan 13, 2016
@nvkelso nvkelso added the ready label Jan 22, 2016
@nvkelso nvkelso removed the ready label Feb 4, 2016
@nvkelso nvkelso modified the milestones: v0.9.0, v0.8.0 Feb 12, 2016
@nvkelso nvkelso added the ready label Mar 7, 2016
@zerebubuth zerebubuth added in review and removed ready labels Mar 7, 2016
@zerebubuth zerebubuth self-assigned this Mar 7, 2016
@zerebubuth
Copy link
Member

A couple of questions:

  1. How do we want to identify these? Looking in the North America extract, there are 49,437 points and 146 polygons with name ILIKE '% (historical)'. Do we want to suppress all of those, or only some of them? See below for more detail.
  2. The example given, "Naval Hospital Oakland" seems like it's not just historical, but in fact no longer a hospital at all. Would this instance perhaps be better dealt with by removing amenity=hospital from the source data? If so, is that something we could or should apply more generally?

Historical stuff

For the polygons, the top counts of kind (plus "building" when it's a building but no matching kind - usually means it has a disused:amenity tag or similar - e.g):

        kind         | num 
---------------------+-----
 building            |  49
 school              |  41
 place_of_worship    |  14
 water               |  13

And the top values for points:

          kind           |  num  
-------------------------+-------
 school                  | 35068
 post_office             |  6262
 place_of_worship        |  6186
 hospital                |   371
 grave_yard              |   191
 park                    |   178

The reason there are so many more points than polygons is that many of these features came from the GNIS import and have never been touched or verified.

@nvkelso
Copy link
Member Author

nvkelso commented Mar 7, 2016

Your frequency list match what I've seen on the map.

  1. How do we want to identify these? Looking in the North America extract, there are 49,437 points and 146 polygons with name ILIKE '% (historical)'. Do we want to suppress all of those, or only some of them? See below for more detail.

Using the basic ILIKE '% (historical)' filter sounds good. Like you said, these are mostly GNIS points so keeping it simple like this is fine. Updating for the v0.8 meta tiling change – Include them at z16 but mark them min_zoom:17. I think we can use the same approach for points and polygons (there are so few of them).

  1. The example given, "Naval Hospital Oakland" seems like it's not just historical, but in fact no longer a hospital at all. Would this instance perhaps be better dealt with by removing amenity=hospital from the source data? If so, is that something we could or should apply more generally?

Good suggestion. What would the kind end up being in this case and in general (especially if there were no other tags to fall back to)?

@zerebubuth
Copy link
Member

What would the kind end up being in this case and in general (especially if there were no other tags to fall back to)?

We could rewrite the kind to be historical and remove the (historical) from the name? We already keep a few disambiguation tags around, so the type of whatever it was that it used to be can probably still be inferred... If not, we could always add historical: <old value of kind>?

From a cartographic point of view, is the "historical" name a bit like a building name - it's kinda useful, but you wouldn't want it to look like a current POI? Would it be useful to, for example, display a greyed out or crossed-through hospital symbol for the old naval hospital? Or better just to display a text label only?

@nvkelso
Copy link
Member Author

nvkelso commented Mar 7, 2016

We'd display these with a generic dot icon only. I'm fine with kind:historical alone.

Let's pass on removing the (historical) part from the name, and from adding historical: <old value of kind> for now. Both seem potentially useful, but could be argued either way.

@nvkelso
Copy link
Member Author

nvkelso commented Mar 18, 2016

Verified the POI layer fix.

screen shot 2016-03-17 at 16 59 22

Looks like the hospital AOI still comes thru the landuse layer (the light red background color in the image above). Filed #617. Recapping Matt's findings above:

Looking in the North America extract, there are 
49,437 points and 
146 polygons 
with name ILIKE '% (historical)'.

The remaining polygons are a 1% problem, and it's probably better to fix their data tags upstream in OSM than write more code here.

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

2 participants