An easy way to communicate data & analysis with just a link.

Gritty details on how Placemark implements collaboration.

Placemark's new open source WKT & EWKT parser, and a review of our existing open source modules.

Better WKT support, hide individual features, import CSV files with GeoJSON columns, and more!

Geospatial data meets tabular, with the new join feature

Feature in the wrong place? Not anymore.

Great arcs, big tables, better statistics, and more!

Making thematic maps, custom styles, and exporting better than ever.

Which of the parts that make up Placemark have changed, what's new, and some ideas about what's next.

OSM XML support, duplication, basic support for iPads, bulk invites, and bug fixes in this week's changelog.

New support for importing CSV and Excel files with address data, plus adding locations to the map after searching.

Rich text, images, improved keyboard shortcuts, and a lot of improvements for the data that lives in geospatial files.

Announcing Placemark's new free map file converter, which runs in your browser and supports converting lots of file formats to and from each other.

Chatting with the MapScaping podcast about Placemark, its start, future, and the unique approach I've taken so far.

Feature better attribute editing with the table plus labels for features on the map!

Dragging, right-clicking, importing, drawing… it's all better with a big batch of improvements!

Friday update: here's what's new! FlatGeobuf and fixes and features.

Nestable, nameable, hidable folders are a great way to organize your maps.

Announcing XYZ layer support, faster collaboration, faster API, edit feature IDs, and better polygon rendering.

Just another Monday, with some improvements, fixes, and commentary!

Announcing a big new feature: the sign up button.

How we make Placemark faster, so you can make maps faster.

A fun conversation with Ed Freyfogle about geo and business

Accepting not-quite-valid data so you can make maps instead of fixing XML.

It's too hard to make a map. It's also hard to say what making a map is.

From image formats to satellites, what seemed inspiring in geospatial technology this year.

Why it might be a good idea to build your marketing site with a different technology stack than the one your application uses.

Inspired by Figma, here's a peek into how we implement mutable, command-oriented, local history.

Why maps are still interesting in 2021

How we use error logging, code analytics, uptime monitoring, and continuous deployment to power map editing tools you can rely on.

How to stop worrying about using the fastest web framework and just ship the thing.

Some of our favorite open source modules that perfectly work with TypeScript and make our lives happier.

From DNS to SQL to design, here's what's been changing with the Placemark map editor.

This is one of those hard-to-pin-down engineering concepts of how to shape your data, which trickles into the whole system design.

Here are the goals and principles we're keeping in mind, building this geospatial application.

How we use Replicache to power real-time, multiplayer, collaborative map editing.

How JSON pointer lets you target and modify certain parts of JSON objects, and how this can be really useful for GeoJSON.

My thoughts on why project management applications are often overkill, and using simple tools forces you to adopt more efficient practices as a small team.

Here's why we use react-aria, a React component library made by Adobe and focused on control and accessibility.

Here's why we use Render, instead of options like AWS, to host our map editor.

There are lots of different ways to build a web application. It's about choosing the one that fits your problem area - here's why I ended up with Blitz.js, a level on top of Next.js, for Placemark.

Here's my framework for how to think about some fundamental choices I have to make when building a company.