search

kartoza / sawps

SANBI WPS
https://kartoza.github.io/sawps/
GNU Affero General Public License v3.0
0 stars 6 forks source link

Cartography Expectations #285

Closed Jeremy-Prior closed 10 months ago

Jeremy-Prior commented 1 year ago

  1. ~The architecture should consist of PostGIS + Tegola + Maputnik Editor~ done

  2. At the end the following should be delivered:

    • [x] a pg_dump of the database
    • [x] the tegola config file
    • [x] the maputnik json style file

  3. ~The cartography should be monochrome so that user attention is focused on the visualisations and reports produced~ - done

  4. ~All tables should have spatial indexes~ - done

  5. ~ll columns that are used for filtering should be indexed~ - done

  6. ~Any column not needed for filtering or cartography should be removed from the tables~ done

  7. ~Use views to subset data as first preference~ - done

    • ~Simplify complex geometries~

  8. ~Use materialised views as second preference~ - not needed

  9. ~All parcels should include the DG code or similar identifier that we can use to identify them with, and their parcel type~ done

    • Identifier: id
    • Parcel Type: layer name?
    • Parcel Name: tag_value?

  10. ~Only the NGI Imagery should be accessed as an external resource. All other resources should be 'in-house'~ done

  11. ~NGI Imagery can be off by default, Dimas will make it toggle-able in the product~ - done

  12. Include design document accompanying the cartography:

    • [x] list all the layers used
    • [x] screenshots showing how it looks rendered that Amy can include in the inception report
Jeremy-Prior commented 1 year ago

sanbi_all_layers_dark_style.webm

LunaAsefaw commented 1 year ago

Comment from Matthew: " The ecosystem type, Critical Biodiversity Areas (please change this in the drop down list, at the moment it just says Biodiversity Areas) and the Protected Areas layer are not distinguishable at all. For the Ecosystems and CBAs, we should categorise the colours via the types listed in the attribute data. The PAs should also stand out more clearly. Also, is there not a way to ID what features are on what layer, much like the info arrow does on normal GIS software? We have to be able to see what we're looking and know what ecosystem type of category of CBA or the name of the PA is that we're looking at. " @Jeremy-Prior @timlinux