Process and evaluation criteria for new environmental layers - AtlasOfLivingAustralia/layers-service GitHub Wiki

Context

We get requests from inside and outside the ALA to load 'environmental' (and 'contextual') layers into the system. Lee Belbin, as the architect of the use of environmental layers had originally produced most of the requests and evaluated most requests. Recently, requests have not contained sufficient context to enable a fair evaluation and there is no process for formal evaluation. This Wiki is a draft of a light process for structuring requests and establishing criteria for evaluation of current and future requests.

Content of Issue

  • Name of requester
  • Organization of requester
  • Email of requester
  • Priority and any date requirements
  • Case for new layer against Evaluation Criteria

Evaluation Criteria

  • The information doesn’t already exist (e.g., IPAs are in CAPAD)
  • Is it an AREA (single or multi-polygon that could be imported/saved) rather than a layer?
  • National coverage, or international coverage where data helps place the Australian region in context
  • Presents information that suggests spatial control of species distributions or would be useful in the interpretation or management of species and areas
  • Data is from an authoritative source
  • Spatial resolution of 1km or better preferred
  • Fills a gap in or complements our layer collection (name, space, time, environmental factor)
  • Anticipated broad usage by one or more of the following communities (research, area managers, environmental consultants, citizen scientists, education, public)
  • Has quality metadata
  • Data is in a form that is readily ingested into our systems
  • Is up to date
  • Supersedes an existing layer (deprecation or deletion)
  • Anticipates future requirements
  • Supports nationally significant projects (which themselves would need some evaluation, but GBR management given World Heritage status and threats would pass)
  • Openly available (free and open source data). Licences that require the supplied layer data not to be passed on are currently acceptable.
  • Externally funded?

Links to documentation and code