“The future ain’t what it used to be.”

-Yogi Berra

  • 16 Posts
  • 1.26K Comments
Joined 2 years ago
cake
Cake day: July 29th, 2023

help-circle








  • Yeah but we didn’t necessarily have that book. And also, you had to know which book. So first you had to find a book that could tell you what kind of book to look in. And if you just didn’t know how or where to ask the question, well. That was that.

    And actually a lot of the books were just wrong but because those were the only books we had, welp. You just learned it wrong.










  • Litterally a scientist working with NASA data and it’s scientists and I’m not the intended audience?

    I’ve been in the remote sensing game almost 25 years. And a good amount of that at the federal government. I’ve sat at the table and shared beers and dinner with the chief scientists behind the modis and gedi mission. There isn’t a geospatial data type or format I haven’t encountered, and half of them I’ve buried.

    So please, spare this old hand any lectures.

    The fact is geospatial has been able to explode because we finally got away from these kinds of anachronistic approaches to data. It’s litterally never been a better time to be a geospatial data scientist. Praise be that the age of h5s and local processing is over.


  • Yeah. h5 is the typical industry shorthand and file extension.

    The h5 saga was NASA saying “we’re going to create a file format that does EVERTHING”, and well… it does… poorly.

    Everything that h5 is allegedly better for is better solved by just moving to either sql or postgres. And if the data aren’t that complex, then just send me a geotiff.

    If you send me an h5 the first thing I’m doing is moving it over to sqlite or postgres.