Replace Nepal example trajectory with something that makes more sense (and can be analyzed)

[zven]

At the moment, we have a rather large Nepal trajectory that can not be analyzed for inferences. Although the analysis is not important for the study, something that makes a bit more sense and is smaller might be beneficial (e.g. for explaining the basic functionality). Maybe we can re-use one the artificial test datasets that are used for the automated tests?

Mentioned here: #156

[zven]

@JuanFFranco the script dev\generate_test_trajectory.ts creates a set of test trajectories based on the content of the test-data-gpx folder and stores them in a format that is then used in the automatic test execution (see package.json) and could be used to replace the nepal trajectory. If you are struggling with executing the script, please ping me. :-)

[JuanFFranco]

When executing the script, and try all trajectories generated, is not possible to generate inferences.

[JuanFFranco]

I created a new Trajectory, that when I import it, creates inferences with no problem, but when I replace the Nepal trajectory to this one, the app won't create inferences from it. I'm not sure if there's an extra step when importing the json file that does not occur when reading the example json file.

• When replacing example trajectory:

• When importing trajectory:

[zven]

Idea for fix:

• try to import example trajectory on app start into database
• check on every start if it is already there

[JuanFFranco]

Only missing fixing the sorting of the trajectories in the Select Trajectory Page

[JuanFFranco]

Just realized a small flaw, if the trajectory is threated as a TrajectoryType.EXAMPLE is not possible to delete the trajectory, but as this new trajectory is still TrajectoryType.IMPORT, only with a badge that says example, it will be possible to delete it, but if the user does it, won't be possible to get it back.