Landscape format.
I love SVGs. Vector images are interesting and seeing an image stored in readable text and still being so small is really cool to me. It’s also fun to play around with since you can plug html into it and vice versa.
TIFF 6 and MKV/FFV1v3. Both great for digital preservation.
M4V for the win.
Is .png no good?
PNG is fine. The industry likes to reinvent the wheel every few years so that you have to upgrade everything. It’s ridiculous nonsense.
I like svg, as it is basically an ASCII file. And i can manipulate them with sed/grep etc for bulk changes.
mkv is king.
Video, audio, subtitles, chapters - all in one file.
.bmp just for the anarchy in me
Highest quality format there is and ever will be.
.mp4 - Only flaw? No subtitles .png - Good compatibility and it scales well
I still have a fondness for TARGA (.TGA) from back in the day…
AVIF. It’s a video format but it works great for photos too and offers much better compression than jepg or even webp without much noticeable loss. I use it on my blog to make the few images I use as light as possible.
What’s the compatibility like? If someone visits your site using IE 11 does it work? How about Firefox 4.0, or Safari 6.1?
The place I used to work had those compatibility requirements. But they were also still mandating the use of IE 11 for all their corporate software. If you’re designing and developing for IE 11, you often get Firefox 4.0 and Safari 6.1 compatibility for free.
Still, it’s nothing like when I was in uni we needed to design websites with IE 6 compatibility, that will make you question your career choice.
GIF and GIF
I created several of them back when I had a BBS.
geotiff
fucking fight me.
and if any one posts h5 as their favorite I’ll rip your fingernails off with a pliers.
Do you mean hdf5? I extensively used COGs (cloud optimised geotiffs) and NetCDF4 (based on hdf5) at work over the last 10 years. Both have their pros and cons.
The main limitation with geotiff is its pretty much only usable for layered 2D raster data.
NetCDF4 (hdf5) can set up frames of any dimensionality, you can have datetime axes, time series data, 100d ensemble data, etc.
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.
HDF5 was designed for multidimensional numeric arrays, which are particularly ill-suited to putting in a classic relational DB.
It’s a scientific data format, not an image format and it sounds like you’re not the intended audience.
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.
I’m familiar with gif in this thread but other than that I have no idea what people are talking about lol. I use pngs for static images and gifs for moving ones because I know they’ll probably work anywhere