The Project Template should set up the Project and ideally create a project including the libraries from issue #2.

It should also add Typescript support out of the box.

amCharts has a new major release. The API has changed quite significantly, but it has some major improvements, which are relevant for us:

• New rendering pipeline which promises a significant performance improvement
• Fast data processing
• React support out of the box
• Theming
• Accessibility
• Build with TypeScript

Related Issues

• #93

• Project Overview
• Screenshots
• How to build
• How to contribute
• Code of Conduct

Add a template for PRs that enhances the software quality. It should contain:

• Check Formatting
• Check Best Practices
• Check Tests and Coverage
• Check Documentation

@lucaspataro do you have anything to add?

API-Response times for requests by day can take up to 5 seconds per request.

Enable the frontend to fetch data from the backend.

• add serchbar functionality
• add autocomplete functionality for QoL
• PR #59 to add feature awaiting review

@lucaspataro Jonas told me to notify you for deployment as soon as I merge Eisenach into Wartburgkreis in lk_germany_reduced.geojson

@JonasGilg

• add customizable multi-color gradient for heat Legend
• set heat legend to accept single color gradients as per the design documents
• add editor for custom heat legends
  • Mockup Example:
    

Separate sections to differentiate between information just for users and information relevant for contibuting developers.

Requires #80 to be completed first.

The python package nose-progressive uses use_2to3 during installation to handle python3 codebase.

in setuptools version 58.0.0+, support for use_2to3 has been removed.
setuptools changelog for v58

To install the requirements correctly, setuptools have to be downgraded using
pip install -U setuptools==58, prior to requirements installation.

(similar to this stackoverflow question)

Related Issues:

• #227
• #228
• #229

In the future, with models with many states of "infected" like "infected vaccinated" or "infected unvaccinated", aggregation of compartments should be possible to be visualized.

The idea is to create a visual editor to aggregate different compartments:

One idea is to do it similar to this feature in factorio, where you can chain "and" and "or" queries:

The editor could be opened here:

Select an open source license and add it to the project:

• License selected
• LICENSE.txt added
• Additional steps?

Add I18N support .

• what exactly needs to be shared (selection slice, ... ?)
• create share link
• parse link (where?) (different route /shared....??)

Related Issues

• #166
• #144
• #127
• #290

Tooltip

Improve tooltip with a lens highlighting the selected disctrict and show scenario p25, p50, and p75 of selected scenario (and real value)

• Tooltip Example:
  
  • Lens highlights selected District (might take up too much space)
  • Left gradient shows scenario's p50 (center dot), p25 and p75 (gradient start/end)
  • Right shows tooltip text
  • Border colored depending on selected scenario
  • selected District colored in current real value (?)

Scenario Comparison

Allow scenarios to be compared in the district map

• display heatmap with relative difference between two scenarios or scenario and real value
• reduce districts to a node map with colored nodes
  • colored with a heat legend based on the differece between scenarios
  • colored with both scenarios as gradients from p25 to p75
  • Node with borders colored according to scenario and real value in center:
    
  • Node without borders:
    

The Top Bar does not strech over the whole content/window (horizontally) if the viewport is small enough to cause an overflow (see screenshot).

Create a Hello World App using React Hooks.

[x] using redux-persist to save the state of the store to local storage
[ ] fix/figure out errors related to this (the heatlegend component breaks when loading state from localstorage)
[ ] think about breaking edgecases (backend data changed, or something like that)

• Automatic Tests
• Code Coverage
• Formatting Checker
• Linting Checker

Since we are a public organisation we have to fulfil accessibility requirements. We need to create a strategy to meet the requirements. I would suggest we comply to the WCAG standards.

TODOs:

• choose a standard
• find out how to help developers meet these standards during development
• automatically test for these standards using unit and integration tests
• automatically test for these standards using CI
• write appropriate developer documentation

jest test for the searchbar component is failing in PR #59.

Add the following libraries:

• React
• Redux
• Material UI
• AmCharts
• Jest

• create a responsive layout strategy for narrow viewports
• implement strategy
  • changes do not break existing layout
  • frontend layout for narrow viewports shows no bugs or layout issues

Will probably fix issue #55

• adjusting the box-sizing property to border-box to include borders and padding may alleviate the problems with the scrollbars showing up

The Attributions dialog has problems loading the content with slow laptops. This should be addressed by either:

• Rendering them simpler
• Lazy loading of entries

Enable the frontend to fetch data from the backend.

Add CI checks that verify:

• Correct code formatting
• No linting errors

am4core.useTheme(am4themes_animated) in the simulation chart seems to propagate to the district map in the sidebar leading to lag on the hover effect and tooltip.