KNOWN_ISSUES.txt

Known issues:
1. API crashes with multiple simultaneaous requests to access the DB.
2. API does not proof for every expected argument to be valid.
3. The Web-GUI's map viewers don't update poses of open segments during a live experiment, they get removed and re-drawn.
4. The Web-GUI's map viewers don't update poses of closed segments during a live experiment. Therefore, the last point might not be added to the map due to posting and getting timing.
5. If the first segment on a live experiment doesn't have position data, the leaflet map will not show map tiles until an ITO segment with start position data is selected from the table.
6. If a mandatory select field is empty (e.g. the vehicle field in the shift edit window) the script will fail to update any changes. This can happen if the database entry was not inserted by the web script.
7. If a segment is created, but no position data references it, the report generator will fail to produce a well-scaled timeline (the longer the segment duration, the worse the scaling of the timeline).