Meeting notes
Goal: Participants:
Keep in mind: *
To-Do 1.
Goal: Participants:
Keep in mind: *
To-Do 1.
Goal: Participants:
Keep in mind: *
To-Do 1.
Goal: Participants:
Goal: Discuss FE concepts based on previously created requirements: (https://docs.google.com/document/d/1Y8mXNuit3eA8AI3zsE1gk8xR9Givt_Uvndifn5rclHE/edit#heading=h.nyheprkbuwq0) Participants: Oli, Celine, Lucas, Emil
FE team concept
PO concept
Keep in mind
- Open apis / external apis (for routes, satellite images, etc)
- Accessibility
- 3D view constraints
To-Do
- Clarify scope with IP
- Clarify priority with IP
- Simplify FE concept for presenting, getting started, prioritizing
Simplified version by Oli
This should be the basis of what will be implemented in the upcoming sprint(s), may be refined after meeting with IP
Draft for presenting to IP
Draft for presenting to IP
For beginning of the implementation, Oli split it into 2 different view:
Goal: Participants:
Keep in mind *
To-Do 1.
Goal: Create and assign ticket for Sprint 2 for frontend vertical Participants: Tanja, Emil, Celine and Lucas
What we will need to implement (UI perspective)
- Basic layout a. Header b. Left-side (multimap) c. Right-side (data view)
- Multimap component (keeps track of zoom, location) a. TabController Component b. Map Component c. Pop-up for add. Map Views -> Pop-up Container necessary d. 3D View
- Load data component (=”arrow”) a. After selecting a location on the map user needs to click this button to load the data into the data view component.
- DataView Component a. Favorite Component b. SearchBar Component c. KeyValues Component (x3) i. Hover effect - popup component - question about loading the specific dataset
Keep in mind:
- Check integration for material ui (add as a subtask to multimap)
- The task “Popup Map Selection” P2 2 (Lucas) is going to the future sprint
To-Do
- PO will create tickets on the feature board and assign them to team members
- PO will create tickets for future sprints
Goal: Align with each other updates for current tickets
Participants: Tanja, Leon, Nicolas, Ahsan
Content:
Nicolas: CSV parser is done, but some questions are still open. What does CSV parser need to deliver to the YAML parser (having the data as an argument) and what to send to the database (the resulting String or SQL query). Which columns do we need for the YAML parser? String as a key and Object as a parameter.
Leon: The YAML parser is not yet started, it will be started today in the afternoon. Proposal: function iterator, do it lazily to reduce some storage. For the database, Leon proposed: for the CSV parser to have a function ReadHeader and GetNextLine function (gets a next row) and then this is a dictionary with header names as values.
Ahsan: Ahsan's opinion: better not to consume data as each row, but dump all data at once. For the database, he wants to have a list of objects where each object contains each row (to have a custom class for each CSV).
Keep in mind:
- The Async call for GetData is obsolete, this is an old option from a not simplified version.
- CSV file -> string[] -> dictionary -> SQL query.
- Assumptions: db lost connection is not that common, processing of huge data is preferred over speed of delivering data.
- Pair programming is preferred, let's try to push more pair programming.
- We don't want to have separate db for each CSV file
- Decision to merge all branches in the evening of 13. May
- Update Emil about updating all docker files in the main docker-compose (because Ahsan will create a db docker file presumably in the next Sprint and the database will be accessible after that)
Goal: Participants:
Keep in mind: *