Changelog: November 21
Big and little improvements to how you can make custom maps and edit geospatial data with Placemark
Dependency management in practice
A simpler router progress bar for this Next.js application
How we built a concise implementation of a page loading bar, just using the Placemark application's existing ingredients
Announcing multi-feature selection, SVG export, and lasso selection
A slew of new features that make it easier to style maps and use them everywhere
Polyline: a spruced-up polyline utility
A new encoded polyline converter that works well with TypeScript and modern applications.
Changelog: September 26
Share maps as gists, rotate features, and sign up without needing a credit card!
Betterknown: a new WKT & EWKT parser
Placemark's new open source WKT & EWKT parser, and a review of our existing open source modules.
Changelog: August 16
Better WKT support, hide individual features, import CSV files with GeoJSON columns, and more!
Which of the parts that make up Placemark have changed, what's new, and some ideas about what's next.
Changelog: June 28
OSM XML support, duplication, basic support for iPads, bulk invites, and bug fixes in this week's changelog.
Making maps with addresses
New support for importing CSV and Excel files with address data, plus adding locations to the map after searching.
A big boost for properties
Rich text, images, improved keyboard shortcuts, and a lot of improvements for the data that lives in geospatial files.
Introducing our free map file converter
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.
Placemark & Tom on the MapScaping Podcast
Chatting with the MapScaping podcast about Placemark, its start, future, and the unique approach I've taken so far.
Changelog: May 31
Feature better attribute editing with the table plus labels for features on the map!
Changelog: May 23
Dragging, right-clicking, importing, drawing… it's all better with a big batch of improvements!
Using folders to organize your map data
Nestable, nameable, hidable folders are a great way to organize your maps.
Changelog: May 2
Announcing XYZ layer support, faster collaboration, faster API, edit feature IDs, and better polygon rendering.
The evolution of data-parsing leniency in Placemark
Accepting not-quite-valid data so you can make maps instead of fixing XML.
It's still too hard to make maps
It's too hard to make a map. It's also hard to say what making a map is.
2021 Map technology in review
From image formats to satellites, what seemed inspiring in geospatial technology this year.
Why we switched to Webflow
Why it might be a good idea to build your marketing site with a different technology stack than the one your application uses.
How we implement undo/redo to make maps fearlessly
Inspired by Figma, here's a peek into how we implement mutable, command-oriented, local history.
Keeping the bugs away
How we use error logging, code analytics, uptime monitoring, and continuous deployment to power map editing tools you can rely on.
Escaping engineering FOMO
How to stop worrying about using the fastest web framework and just ship the thing.
Good magic with TypeScript
Some of our favorite open source modules that perfectly work with TypeScript and make our lives happier.
Engineering round up
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.
Thoughts on Collaboration
How we use Replicache to power real-time, multiplayer, collaborative map editing.
Tech brief: JSON Pointer
How JSON pointer lets you target and modify certain parts of JSON objects, and how this can be really useful for GeoJSON.
GitHub issues-only project management
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.
The application stack: Blitz
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.