kartoza / geosafe

InaSAFE package for Geonode
GNU General Public License v3.0
7 stars 16 forks source link

modify default layer sort #509

Open gubuntu opened 6 years ago

gubuntu commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

@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 commented 6 years ago

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

lucernae commented 6 years ago

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.