Projects are cross-referencing each other to access the same piece of data to walkaround the first point.

Version control in the dataset is lacking which leads to all sort of inconsistency and mismatching.

Additional space is taken up by duplicated data.

While that is easier to start, it has quickly grown out of control which has led to three major problems: With both GIS and time-series covered, this NAS should satisfy most of our daily requirements when it comes to a centralized database.īut why do we need a NAS? Personal Motivationįor the longest time, I have been saving data as pickle, flat files and occasionally in local databases.

PostGIS would enable us to process and store geospatial data efficiently while TimescaleDB can be treated as the time-series expertise on Postgres. We are also going to extend Postgres with PostGIS and TimescaleDB. Our database server will be a Postgres database in a Docker Container to ensure portability and robustness. In this blog, we will be going through how to assemble and set up your own NAS on a Raspberry Pi. Because of its accessibility, NAS is one of the best solutions for sharing data across devices in the form of a database, be it relational or no-SQL.

For those who are not familiar with it, think of it as Google Drive or dropbox, where data is accessible via the network. Network-Attached Storage (NAS) is a centralized well of data repository which is accessible by other devices in the same computer network. Containerized Postgres Server with PostGIS and TimescaleDB

Install dropbox amazon ec2 ext4