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

Deal with US National Forest, US National Park server side #475

Closed
nvkelso opened this issue Jan 8, 2016 · 6 comments
Closed

Deal with US National Forest, US National Park server side #475

nvkelso opened this issue Jan 8, 2016 · 6 comments
Milestone

Comments

@nvkelso
Copy link
Member

nvkelso commented Jan 8, 2016

This type of filter evaluation (on operator) is too prevalent in the stylesheet:

    landuse:
        data: { source: osm }
        tier1:
            filter: 
                any:
                    # limit show smaller landuse areas to higher zooms
                    - { $zoom: { min: 3 },  area: { min: 300000000 } }
                    - { $zoom: { min: 4 },  area: { min: 300000000 } }
                    - { $zoom: { min: 5 },  area: { min: 150000000 } }
                    - { $zoom: { min: 6 },  area: { min: 150000000 } }
                    - { $zoom: { min: 7 },  area: { min: 100000000 } }
                    - { $zoom: { min: 8 },  area: { min: 10000000 } }
                    - { $zoom: { min: 9 },  area: { min: 5000000 } }
                    - { $zoom: { min: 10 }, area: { min: 1000000 } }
                    - { $zoom: { min: 11 }, area: { min: 500000 } }
                    - { $zoom: { min: 12 }, area: { min: 500000 } }
                    - { $zoom: { min: 13 }, area: { min: 100000 } }
                    - { $zoom: { min: 14 }, area: { min: 50000 } }
                    - { $zoom: { min: 15 }, area: { min: 20000 } }
                    - { $zoom: { min: 15 }, area: { min: 2000 } }
                    - { $zoom: { min: 16 } }
            national_park:
                filter: { kind: [national_park, "park or protected land"], not: { operator: [ "United States Forest Service", "US Forest Service", "U.S. Forest Service", "USDA Forest Service" ] } }
                draw:
                    polygons:
                      color: *green7
                us_national_park:
                    # yosemite national park, death valley national park, grand canyon national park
                    filter: { operator: [ "United States National Park Service", "US National Park Service" ] }
                    draw:
                        polygons:
                            color: *green1
@nvkelso nvkelso added this to the v0.8.0 milestone Jan 8, 2016
@zerebubuth
Copy link
Member

This is kind of a fudge in the style sheet to handle wanting to draw US National Parks differently from other large parks (#227), which is really a cartographic decision. Pushing this into the vector source feels, to me, like specialising the data source and reducing its usefulness; it seems like we're moving beyond "cleaning up" the data and into "opinionating" the data.

@bcamper
Copy link
Collaborator

bcamper commented Jan 8, 2016

While I agree it's opinionated (which I am personally fine with as long as we do it responsibly), I also feel like it represents a kind of data normalization issue that is likely to be useful beyond our specific designs. One way to accomplish this type of thing could be to have an additional or alternate field, in case one wants to access the original data. There's a balance in changing underlying data vs. additively providing an opinion on top of it.

@nvkelso
Copy link
Member Author

nvkelso commented Jan 8, 2016

For operator, we standardize other non-conventional (or misspelled) tags to the conventional value elsewhere in the code, this seems like the same thing?

In terms of National Parks versus National Forests, there's other things we can look at here (like the protected_class stuff), like populating it explicably on National Forests and US National Parks when it's not provided in data.

@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 modified the milestones: v0.10.0, v0.9.0 Mar 14, 2016
@nvkelso nvkelso modified the milestones: v1.0.0, v0.10.0 Apr 4, 2016
@nvkelso
Copy link
Member Author

nvkelso commented Jul 29, 2016

Splitting of the operator part into #927.

@nvkelso nvkelso modified the milestones: v1.1.0, v1.0.0 Aug 24, 2016
@nvkelso
Copy link
Member Author

nvkelso commented Aug 24, 2016

#473 should most address this.

Moving this to v1.1 to track any additional cleanup that might be needed.

@nvkelso nvkelso modified the milestones: v1.2.0, v1.1.0 Oct 5, 2016
@nvkelso nvkelso modified the milestones: v1.6.0, v1.7.0 Sep 25, 2018
@nvkelso nvkelso modified the milestones: v1.8.0, v1.7.0 Dec 29, 2018
@nvkelso
Copy link
Member Author

nvkelso commented Dec 29, 2018

Don't think this is an issue anymore.

@nvkelso nvkelso closed this as completed Dec 29, 2018
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

3 participants