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

Order landcover by osm_id #3224

Closed
wants to merge 1 commit into from
Closed

Order landcover by osm_id #3224

wants to merge 1 commit into from

Conversation

matthijsmelissen
Copy link
Collaborator

This resolves #2782

@andrzej-r
Copy link
Contributor

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.

@matthijsmelissen
Copy link
Collaborator Author

Do you thing it would be possible to sort by feature instead.

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.

@sommerluk
Copy link
Collaborator

it would add quite a lot of code

Wouldn’t it be enough to leave the inner query as it is currently (without this PR), and add to the outer query ORDER BY feature, osm_id? This should order by feature alphabetically (which is just as arbitrary as osm_id, but independent from deleting/re-creating objects in the OSM database) before ordering by osm_id…

@matthijsmelissen
Copy link
Collaborator Author

My bad, this would work of course. Will fix it.

@sommerluk
Copy link
Collaborator

Hm, my bad, should be ORDER BY way_area DESC, feature, osm_id on the outer query (and no order in the inner query), otherwise way_area wouldn’t be the primary order criterium any more.

@pnorman
Copy link
Collaborator

pnorman commented May 28, 2018

I don't see that we need osm_id ordering if we've got feature in the ordering

@sommerluk
Copy link
Collaborator

I don't see that we need osm_id ordering if we've got feature in the ordering

Good point.

@ImreSamu
Copy link

I don't see that we need osm_id ordering if we've got feature in the ordering

imho - the original varied color problem is solved, but it can be a similar problem in the varied landcover labels. ( in rare cases )

@pnorman
Copy link
Collaborator

pnorman commented May 28, 2018

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.

@kocio-pl
Copy link
Collaborator

What is current state of this code and what are the plans to do with it?

@pnorman
Copy link
Collaborator

pnorman commented Jul 12, 2018

It needs changes to stop ordering after feature.

@Tomasz-W
Copy link

It resolves #1291 also.

@kocio-pl
Copy link
Collaborator

kocio-pl commented Oct 7, 2018

@matthijsmelissen What would you like to do with code? Do you have any plans?

@matthijsmelissen
Copy link
Collaborator Author

Updated.

@kocio-pl
Copy link
Collaborator

kocio-pl commented Oct 7, 2018

I'm not sure if you've seen this, but there's 1 conflict left (related to #2874).

@matthijsmelissen
Copy link
Collaborator Author

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.

@matthijsmelissen matthijsmelissen deleted the landcover-order branch October 7, 2018 22:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should landcover be ordered by osm_id in addition to way_area?
7 participants