Jochen Stier

> Looks good. Thanks for the tedious effort. A couple of things I would like to tackle before merging: > > * [x] Why does the area calculation differ? >...

-> this might be done, lets double check if the current aggregation is the one we want for geometries

- [x] move development to the first section - [ ] add json object from firebase for each project type - [ ] project_type -> update (images, descriptions) delete or...

Last Section Indices and Tables seems to be useless - [x] removed? - [x] Add logo with sphinx html_logo? - [x] Whats up with completness project type (4)? - ->...

## After update check if: ### Data - [ ] last table is formatted properly - [ ] HOT Tasking Manager Geometries heading is now a proper heading

Proposed steps to address this issues: - [x] 0. Build test dataset -> dev database is test dataset - [x] 1. adjust init_db: all tables get new integer "postgres"id, the...

maby test if indices on multiple columns improve performance, e.g.: ```sql CREATE INDEX tasks_idx ON tasks using btree (project_id, group_id, ?task_id?); ``` -> queries should mostly involve all the id...

2end meeting notes: - [x] leave taskid as varchar, no seperate firebase from postgres id in this case - [x] -> this means we dont need to join on task...

Tests: Setup new schemas and fill with dev data: - [ ] dont replace ids with ints, but split results into group_results and results - [ ] switch project and...