Bitruvius exists because the infrastructure underneath geospatial, imagery, and 3D data has not kept up with the data itself. We spend our days working on that problem at the level of bytes, memory layouts, and modern silicon. This blog is where we step back from all of that and talk about the work like people.
Why a blog
The product pages already explain what each format and codec does, and the specs and documentation live with each product, where they belong. What has been missing is a home for the thinking behind the work: why we made the bets we made, what we are learning as the suite meets real workloads, and where we believe the industry is heading. That is what this blog is for. Ideas, in plain language.
What to expect
Three kinds of writing will show up here, and we will keep all three honest.
Engineering notes. How we think about compression and data infrastructure from first principles, written for a general technical audience. You will not need a background in codecs to follow along. If a post needs a spec to make its point, the point belongs in the documentation instead.
Company updates. Milestones, pilots, partnerships, and the occasional hard lesson. Most companies tell this story after the fact, once the rough edges have been sanded off. We would rather tell it as it unfolds.
Industry perspective. Why foundational data infrastructure matters for geospatial, scientific, and 3D imaging, and what is changing as datasets grow faster than the systems built to serve them. The gap between how much data we capture and how well we move it is the defining constraint of this industry, and it deserves more plain-spoken discussion than it gets.
Who is writing
Posts come from the people doing the work: the founders and the team building, selling, and supporting the Imagery & 3D Suite. Nobody here writes for a living, which we consider a feature. You will get the perspective of practitioners who have spent careers inside geospatial, imagery, and 3D data, not a content calendar.
We will not publish on a fixed schedule. When we have something worth your time, we will write it down. When we do not, we will stay quiet.
Follow along
If any of this sounds useful, we would love to have you along. Subscribe to the newsletter from any page on the site, or add the RSS feed to your reader and let the posts come to you.
And if you read something here that you disagree with, or that you have seen play out differently in your own work, tell us. The best part of writing in public is finding out what we got wrong.
Welcome. We are glad you are here.