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

-Yogi Berra

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

help-circle

  • TropicalDingdong@lemmy.worldtomemes@lemmy.worldAccepting Donations
    link
    fedilink
    arrow-up
    43
    arrow-down
    2
    ·
    11 hours ago

    why we aren’t more open to separating the work from the artist

    Because we shouldn’t?

    We shouldn’t support pieces of shit. Not with our eyes. Not with our ears. Not with our dollars or our attention. Its not like there aren’t hundreds of thousands of other hilarious people who aren’t pieces of shit. Its not like we don’t have literally PLENTY of other options.









  • 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.