I need to store aircraft data such as latitude, longitude, altitude, flight-level, speed, etc.
I will have another database (Postgres), which will contain geo-spacial data that I will need to cross-reference with my aircraft data.
In other words, I will need to pull out of the aircraft database an aircraft and all of its lat, long, altitude & flight-levels over a certain duration. I will then need to use that data retrieved (essentially, a flight path) to query the geo-spacial DB and see if, for example, the aircraft went through clouds...
I will need to extract the whole cloud (and there may be many clouds that the aircraft encounters) from the geo-spacial database, not just a boolean value.
My questions are:
- Is postgres suited to storing such aircraft data?
- If not, which database is?
- If I use MS SQLServer to store my aircraft data and postgres to store the geo-spacial data, will I have trouble... like long query times due to mixing databases? Or, is it absolutely fine?
The geo-spacial data will be massive... 7TB for a year. The aircraft data will be less, but I cannot put a figure on it.
The results from the cross-referencing will be likely be stored in another database.