-
Notifications
You must be signed in to change notification settings - Fork 819
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
Order landcover by osm_id #3224
Conversation
This resolves #2782
Do you thing it would be possible to sort by feature instead. I understand sorting by osm_id would produce different rendering when someone deletes/recreates an object, which seems like a hack to me. |
Hmm, good point. I've been thinking about it, but I think it would add quite a lot of code for a relatively small gain. So I think I'd prefer to leave it as it. |
Wouldn’t it be enough to leave the inner query as it is currently (without this PR), and add to the outer query |
My bad, this would work of course. Will fix it. |
Hm, my bad, should be |
I don't see that we need |
Good point. |
imho - the original varied color problem is solved, but it can be a similar problem in the varied landcover labels. ( in rare cases ) |
The landcover layer is used for fills, not labels. |
What is current state of this code and what are the plans to do with it? |
It needs changes to stop ordering after |
It resolves #1291 also. |
@matthijsmelissen What would you like to do with code? Do you have any plans? |
Updated. |
I'm not sure if you've seen this, but there's 1 conflict left (related to #2874). |
Superseded by #3441. The current PR is a PR from a branch on gravitystorm directly, it should of course come from matthijsmelissen:landcover, which is fixed in the new PR. |
This resolves #2782