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 new kinds for full OSM.org / iD icon library support #1425

Closed
46 of 64 tasks
nvkelso opened this issue Nov 3, 2017 · 12 comments
Closed
46 of 64 tasks

Add new kinds for full OSM.org / iD icon library support #1425

nvkelso opened this issue Nov 3, 2017 · 12 comments
Assignees
Labels
Milestone

Comments

@nvkelso
Copy link
Member

nvkelso commented Nov 3, 2017

Around 39:

Dec. 12th: Looking at https://github.com/gravitystorm/openstreetmap-carto/blob/master/amenity-points.mss, propose also:

  • shop=cosmetics
  • shop=fishmonger
  • military=bunker
  • historic=wayside_cross
  • barrier=swing_gate
  • historic=memorial_plaque
  • man_made=obelisk
  • military=danger_area
@nvkelso nvkelso added this to the v1.6.0 milestone Nov 3, 2017
@nvkelso nvkelso modified the milestones: v1.6.0, v1.5.0 Nov 13, 2017
@pnorman pnorman self-assigned this Nov 21, 2017
@pnorman
Copy link
Collaborator

pnorman commented Nov 24, 2017

What should we do with objects which are shop=chemist amenity=pharmacy? amenity=pharmacy is already handled, this would add shop=chemist.

@nvkelso
Copy link
Member Author

nvkelso commented Nov 25, 2017 via email

@pnorman
Copy link
Collaborator

pnorman commented Dec 9, 2017

beach kind_detail
beach_coarse from http://wiki.openstreetmap.org/wiki/Key:surface???

I'm looking at this and am not sure about it.

The osm.org reference to beach is https://github.com/openstreetmap/openstreetmap-website/blob/e3357b27e61c3ee4f4cf51c87fdc94deeaaa7c6f/config/locales/en.yml#L666 and iD has nothing about beach surfaces that I see.

Taginfo shows 19% of beach have surface, and 15% of beach have surface=sand. 1% have surface=pebblestone, and of the remaining 3%, they don't have a common enough tag to make taginfo.

@nvkelso
Copy link
Member Author

nvkelso commented Dec 9, 2017 via email

@nvkelso
Copy link
Member Author

nvkelso commented Dec 9, 2017

Looks like only OSM Carto beach_coarse is a symbolizer for the following surface values src:

 [natural = 'beach'],
    [natural = 'shoal'] {
      [surface = 'sand'] {
        polygon-pattern-file: url('symbols/beach.png');
        polygon-pattern-alignment: global;
      }
      [surface = 'gravel'],
      [surface = 'fine_gravel'],
      [surface = 'pebbles'],
      [surface = 'pebblestone'],
      [surface = 'shingle'],
      [surface = 'stones'],
      [surface = 'shells'] {
        polygon-pattern-file: url('symbols/beach_coarse.png');
        polygon-pattern-alignment: global;
      }
    }

@pnorman
Copy link
Collaborator

pnorman commented Dec 12, 2017

Looks like only OSM Carto beach_coarse is a symbolizer for the following surface values src:

SVG files have no direct relationship to OSM tags, e.g. square.svg is just a 1px square used multiple places where we wanted a square for a symbol. The tags go through osm2pgsql to turn into columns (generally a trivial transformation) then the SQL to MSS. In most cases it's easy to read off what the original tag is from the MSS selectors fairly easy, 95% are either [key = 'value'] or using a feature column and have [feature = 'key_value']. There are exceptions like like the [railway = 'runway'] which used to be used to select objects with aeroway=runway.

I'll go through and strike out the ones that are only file names, not related to OSM tags.

@pnorman
Copy link
Collaborator

pnorman commented Dec 12, 2017

For grave_yard_christian, grave_yard_generic, grave_yard_jewish, grave_yard_muslim kind_detail, I have a PR doing that right now, but I'm wondering if those are the best values for kind_detail. I think it would make more sense to have kind_detail of christian, jewish, or muslim, and no kind_detail for where it's not tagged.

This would also apply to kind_detail of forests with leaf_type and the wetland values.

@nvkelso
Copy link
Member Author

nvkelso commented Dec 12, 2017 via email

pnorman added a commit to pnorman/vector-datasource that referenced this issue Dec 14, 2017
@pnorman
Copy link
Collaborator

pnorman commented Dec 14, 2017

Do we really want to duplicate the religion between religion and kind_detail fields?

@nvkelso
Copy link
Member Author

nvkelso commented Dec 14, 2017 via email

pnorman added a commit to pnorman/vector-datasource that referenced this issue Dec 16, 2017
This is part of tilezen#1425 and sets up the parts of code to place the
other amenities in.
pnorman added a commit to pnorman/vector-datasource that referenced this issue Dec 16, 2017
This is part of tilezen#1425 and sets up the parts of code to place the
other amenities in.
pnorman added a commit to pnorman/vector-datasource that referenced this issue Dec 16, 2017
This is part of tilezen#1425 and sets up the parts of code to place the
other amenities in.
@ghost ghost added the in review label Jun 27, 2018
@nvkelso
Copy link
Member Author

nvkelso commented Aug 24, 2018

barrier=lift_gate is going into kind_detail (which is fine), but we'll need to add client logic for that. Same for barrier=swing_gate.

@nvkelso
Copy link
Member Author

nvkelso commented Aug 24, 2018

Filed some followup issues for the next milestone but generally everything here is verified (or has an issue). Closing :)

@nvkelso nvkelso closed this as completed Aug 24, 2018
@ghost ghost removed the in review label Aug 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants