Placemark
HomeBlogDocumentationPricingSign inSign up

Changelog: May 13

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

👆 Fresh content!

Using folders to organize your map data

Using folders to organize your map data

Nestable, nameable, hidable folders are a great way to organize your maps.
Changelog: May 2

Changelog: May 2

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

Changelog: April 25

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

Announcing Placemark

Announcing a big new feature: the sign up button.
Engineering round up: Optimization

Engineering round up: Optimization

How we make Placemark faster, so you can make maps faster.
Placemark on the Geomob Podcast

Placemark on the Geomob Podcast

A fun conversation with Ed Freyfogle about geo and business
The evolution of data-parsing leniency in Placemark

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

2021 Map technology in review

From image formats to satellites, what seemed inspiring in geospatial technology this year.
Why we switched to Webflow

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.
Maps, a decade later

Maps, a decade later

Why maps are still interesting in 2021
Keeping the bugs away

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

Escaping engineering FOMO

How to stop worrying about using the fastest web framework and just ship the thing.
Good magic with TypeScript

Good magic with TypeScript

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

Engineering round up

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

Choosing atoms

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

Values

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

Thoughts on Collaboration

How we use Replicache to power real-time, multiplayer, collaborative map editing.
Tech brief: JSON Pointer

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

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.
Components: react-aria

Components: react-aria

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

Hosting: Render

Here's why we use Render, instead of options like AWS, to host our map editor.
The application stack: Blitz

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.
Stack thinking

Stack thinking

Here's my framework for how to think about some fundamental choices I have to make when building a company.
Screenshot of the Placemark user interface

The modern way to collaborate on, manage, and edit maps and geospatial data.

ProductPricingDocumentationBlogRoadmap & limitsGive us feedback!
CompanyTerms of ServicePrivacyContactOpen Source
@2022 Working IdeaTwitterGitHubLinkedInDiscord