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

modify default layer sort #509

Open
gubuntu opened this issue Nov 21, 2018 · 4 comments
Open

modify default layer sort #509

gubuntu opened this issue Nov 21, 2018 · 4 comments

Comments

@gubuntu
Copy link
Contributor

gubuntu commented Nov 21, 2018

problem

in the layer view, the default ordering mixes up layers randomly (that's how it appears to the casual user)

solution

change the default order to sort on keywords, specifically

  1. GeoSAFE exposure
  2. GeoSAFE hazard
  3. GeoSAFE aggregation
  4. Other curated layers (like drought, landslides, powerlines etc) that are useful but not available in in GeoSAFE
  5. GeoSAFE impact layers generated by analysis

As a quick fix, change the default sort to 'less recent first' so that most the impact layers go to the end of the list

@myarjunar
Copy link
Collaborator

change the default order to sort on keywords, specifically

GeoSAFE exposure
GeoSAFE hazard
GeoSAFE aggregation
Other curated layers (like drought, landslides, powerlines etc) that are useful but not available in in GeoSAFE
GeoSAFE impact layers generated by analysis

@gavin we already use this order in the map view except layers other than inasafe layer, because we cannot show them on the map CMIIW @boney-bun

@NyakudyaA
Copy link
Collaborator

@myarjunar I think what Gavin is trying to say is that when a user goes to our geonode the layer list is alphabetical I think. So instead of having this default list rather sort the layers based on the keywords allocated as described above.

@gubuntu
Copy link
Contributor Author

gubuntu commented Nov 22, 2018

yes we're talking GeoNode layer view here, not GeoSAFE

@lucernae
Copy link
Collaborator

This the default behaviour in GeoNode. I assume it is more make sense to override this behaviour in GeoSAFE instead and not change this default GeoNode behaviour. For GeoNode, I think the correct approach would be to play with the sort filter they provided.

I suggest we move it to GeoSAFE and solve it there because in GeoSAFE we can easily check if the layer is InaSAFE layer or not (in addition of taking the Keywords into consideration).

There's a transfer issue button in Github now, so if we agree, we can move it over to GeoSAFE.

@gubuntu gubuntu transferred this issue from kartoza/geonode Nov 25, 2018
@gubuntu gubuntu added the ready label Nov 26, 2018
@gubuntu gubuntu added backlog and removed ready labels Mar 18, 2019
@gubuntu gubuntu removed the backlog label Jul 9, 2019
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

No branches or pull requests

4 participants