Taking some time off to choose your next adventure
does give you time to think about things. Some people might take this time to catch up on reading or pick that hobby you dropped back up, but I cannot. I just need to work with geospatial data and the project I’m working on right now is cleaning up my GIS data repository. As I said in a blog post Monday
I am moving a lot of spatial data off of Dropbox and into a better solution. I’ve simplified by dropping Dropbox (unintentional joke) and using iCloud for my cloud data store. There isn’t much to that of course, cloud storage is really a commodity at this point. I’m also migrating older data to Amazon S3 Glacier
which seems like a great choice for long term storage.
The one thing that really worries me is cartography. I think we can probably agree on spatial data formats for archival, there are multiple choices for different data types. But cartography is one that baffles me. I have data in MXDs, QGIS projects and even Adobe Illustrator. I have always been good at using PDF as a storage medium because I think it does a great job of snapshotting the visualization as it was released. But the raw cartography is in some files that could be bad choices for long term archival.
There are tons of ways to store spatial data, but sharing cartography is much harder.
The whole blog post is very much a period piece with references to SLD, CSS and uDig, but maybe there is something to this. I liked the idea of WKT/WKB as a good archival format so in concert with this, maybe SLD
is a great choice. Of course, if I lamented that SLD was not well supported in 2009, you can pretty much be assured that it is even worse in 2020 not to mention that SLD is as ugly as it gets. I felt like OGC would be a great place to get a standard for cartography, but I don’t think there is much there because OGC is more focused on data sharing rather than data visualization