Skip to content
Snippets Groups Projects
planning.rst 2.90 KiB

Planning, Design, etc

Nominal Use Cases/Requirements

  • replace intermapper/heat map

    • availability
    • capacity
    • utilisation
    • etc.
  • integrate with connectivity map

    • visualize geant-owned data-driven info on the same map with static (manually input/managed) non-geant data
  • monitoring

    • health of nodes/edges
    • alarms/link state edge heat map
  • grid-based for fixed (e.g. our) networks

  • handle overlapping edges

Ideas

  • For the Geant-managed heat maps: maybe nice to agree upon a simple grid-locked geo-node/edge approach

Some R&E Samples

Misc Internal things

NRENS with their network info

FrontEnd Technologies worth exploring

High-Level Architecture

Design/Edit concerns for subway map

  • rendered end-user maps are static (i.e. end-user can't move map elements around)

  • designers need some way of customizing maps

    • draw.io?
    • can we support full design control? i.e. artists drawing shapes/effects
    • some styles are ok with draw.io
  • Designer input

    • how should we handle errors in designer input?

      • should we have a validation step when designers return their modifications?
    • should we keep the design template completely outside of mapping provider? or some metadata (e.g. lists of nodes/edges) in mapping provider?