-
Notifications
You must be signed in to change notification settings - Fork 102
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
[WIP] Preliminary styling for protected areas #66
base: gh-pages
Are you sure you want to change the base?
Conversation
Hi @kylebarron thanks a lot for your PRs and comments, I need to take a closer look.
If you export a style from Maputnik, the style is formatted with gl-style-format: From where did you get the style which you modified in Maputnik? Edit: |
@kylebarron I formatted the style you submitted with your PR with Could you please do the same, so it's possible to review the changes. This should also make Travis happy, currently the test is failing. However, we should find out if the Maputnik export is well formatted. It would help if you could describe your workflow creating this PR. |
The workflow is
then make edits through Maputnik in the browser, and commit the generated JSON
I'd already forked maputnik/osm-liberty, so to make these two PRs without irrelevant changes from my fork, I did
I think the two git processes are equivalent? |
Also, regarding the PR's styling changes, I think it's too confusing for a general basemap currently: I'd think that I should take labels off completely or only have them visible at a much higher zoom. Also, I think I should experiment a bit more with opacity, because contrasts look a bit stark. nst-guide/osm-liberty:master is a topo-oriented fork of osm-liberty (you can see it live here, though only generated for the west coast US). I might incorporate protected areas styling there regardless, but I'm interested in hearing your thoughts on what's best for a generalist basemap. |
When I run
I do get a significant diff. It looks like that has more condensed JSON formatting. If you could try running the Maputnik 1.6.1 release, and then if you open the style JSON with
if I do anything, like toggle the visibility of a layer on and off, the JSON is automatically reformatted in the style of this PR |
Ahh, you're using https://github.com/maputnik/desktop. I was refering to the online version: When you export a style with the online version, the style is formatted with Opened an issue regarding the desktop version: |
Yes, I downloaded from maputnik/editor, but there was no install, so it makes sense that it was packaged using that golang repo. maputnik/desktop definitely reformats the JSON in some way, but not with gl-style-format |
Yep. I think so, too.
Yep, worth a try at much higher zoom. Thanks for mentioning the topo fork, looks great!
I think the current situation we are having with protected areas for For me the two main complaints in #4 are the following:
I would try to style only the outline of the protected areas (use a What do you think? |
Preliminary styling for protected areas. Would close #4. Styling is hard, so take this as a discussion point.
Adds labels for named
protected_area
andnational_park
Points.In the current style.json, there's a
park
layer and apark_outline
layer. Are both needed since there can be a specific color for the outline of a fill?It's impossible to create a small diff because maputnik reformats the JSON automatically. In order for this PR's diff to be small, it would be best if a separate PR reformatted style.json.