I have a spatial trajectory dataset which basically contains about 10E6 (lat,lon,time)-tuples, grouped together by an identifier so they form trajectories.
Currently, SQLite is used to store the raw data.
Lat/Lon are in WGS84 but span only small areas (i.e. European country size).
I would like to store it in a geodatabase for easy descriptive & exploratory analysis, eg. calculating the overall and average distance for trajectories, and basic data preprocessing, eg. dismissing all tuples that are outside a polygon, for example.
Thus, I thought PostGIS would be optimal since I have worked with it before.
Some questions arise though: Should I just store the tuples as POINTS with GEOMETRY data type, or should I use MULTIPOINTS for whole trajectories?
And what about performance? Performance is not critical since the data is used for a research project and not for a production application, but I don't want to wait 5 hours to calculate distances between a million point-pairs.
What about indexing? What type of indices should I use and on what type of data?
I know this question is kind of general but I would like to see if people have experience with storing trajectory data and maybe they can give me some advice.