TL;DR: NASA's public Planetary Data System is at risk of being shut down. Anyone have any ideas for backing it up?

Hi everyone,

Bit of a long-shot here, but I wanted to try on high-quality tildes before jumping back into the cesspool of reddit. I'm posting it in ~science rather than ~space as I figure interest in backing up public data is broader than just the space community.

I work regularly with NASA's Planetary Data System, or PDS. It's a massive (~3.5petabytes!!) archive of off-world scientific data (largely but not all imaging data). PDS is integral for scientific research - public and private - around the world, and is maintained, for free, by NASA (with support of a number of Academic institutions).

The current state of affairs for NASA is grim:

• NASA Lays Off ISS Workers at Marshall Space Flight Center
• More layoffs at JPL
• NASA is sinking its flagship science center during the government shutdown — and may be breaking the law in the process, critics say

And as a result, I (and many of my industry friends) have become increasingly concerned that PDS will be taken down as NASA is increasingly torn down for spare parts and irreparably damaged. This administration seems bent on destroying all forms of recording-keeping and public science, so who knows how long PDS will be kept up. Once it's down, it'll be a nightmare to try and collect it all again from various sources. I suspect we'll permanently lose decades worth of data - PDS includes information going all the way back to the Apollo missions!

As such, we've been pushing to back-up as much of PDS as we can, but have absolutely no hope of downloading it all within the next year or two, nevermind in a few months if the current cuts impact us soon.

If you or someone you know would be interested in helping figure out how we can back-up PDS before it's too late, please let me know here or in a DM. I've already tried reaching out to the Internet Archive, but did not hear anything back from them.

Edit: to clarify, the larger problem is download speeds - we've topped out at 20mb/s with 8 connections.

For reference, here is the ODbL. There is a nice human readable summary. You can also read more in the Wikipedia entry.

The most famous database available under the ODbL is OpenStreetMaps.

I recently found out about OpenCorporates, which is a global database of companies, published under the ODbL. I thought this was great, so I applied for access to use the database for a project. I was denied because I'm not a journalist or a nonprofit and instead was invited to pay for access instead. And it's not cheap, likely because company databases are often used in the B2B space.

I replied that this seemed to be in conflict with their mission, especially given that my project was focused on using the data to create a benefit to the public, and their response was that they wanted to protect against their database being copied.

From my reading, this seems to be in direct conflict with the ODbL. Egregiously so, which has me thinking I'm missing something.

Does anyone have any insight? It seems to me that the whole point of the ODbL license is to make data freely available. This is backed up by interpretations I came across while searching and by the ethos of other orgs using the license, such as OSM. What am I missing?

Edit: I'm still excited to hear from anyone with knowledge in this area, or just general insights into how I'm misunderstanding the license.

And also, having learned that The Open Data Commons, which publishes and maintains the ODbL, uses this definition of the concept of open... I'm leaning towards the interpretation that OpenCorporates wants the aura of using a reputable license with the word "open" in it, but isn't genuinely interested in the ethos. Which is disappointing but not shocking, they'd be far from the first.

I work for a GIS company and our tools have not grown with our projects and client base. We use ArcPro personal geo databases (GDBs) for ALL data. We recently had a project where shit really hit the fan, one major issue was related to invalid values from poor version control. Everything uses personal GDBs and is just "version controlled" by dating filenames in Explorer. It would have been trivial to fix in a proper database. We also have operational constraints, like we can only have one person doing X job at a time since all the data for X job is in a personal GDB.

But I'm just an analyst. I've garnered some attention for my technical expertise beyond processing the data. PostGIS is a thing so it isn't as though we'd be recreating the wheel. How can I push for that sort of change? I'm thinking I can sell it using how much we lost on this project because of these avoidable failures. I'm also wondering if I can make this an opportunity to create a "database administrator" position for myself

I am planning to use Plaid API and have a spring boot backend but given that I will be storing my financial information (such as whatever the Plaid API needs me to store to use their endpoints as well as just the transactions on my credit and chequing account), the security of the data is obviously crucial. and I think my problem is I don't know what I don't know.

I have a basic idea of what kind of things I need to protect against.

1. WIll have to use Spring security (or whatever is best) for thing like protecting against xss and csrf
2. I need to ensure that the PostgreSQL database is encrypted

but beyond that, I don't know much about the nuances of each type of security and customizations I should be on the look-out for. wonder if there's a trustworthy resource for at least detailing for me the kind of security I need to implement on either the Spring or PostgreSQL side of things?