Build a story map of incident locations without a data desk

You've got the story. What you don't have is a map person.

Maybe it's a string of break-ins across three neighborhoods. Maybe it's every crash on a dangerous stretch of highway over the last two years, pulled from a records request. Maybe it's every building permit filed downtown this quarter, or every restaurant health inspection, or every polling place closure. Whatever the beat, the pattern is the same: you've got a spreadsheet full of addresses, and a strong hunch that if you could just *see* them on a map, the story would jump out at readers in a way that a paragraph of text never will.

At a bigger outlet, this is a data desk's job. Someone with GIS training takes the list, runs it through mapping software, and hands back a clean, interactive map that goes straight into the story. At a small local newsroom — two reporters, an editor who also does layout, maybe a part-time web person — that person doesn't exist. So the map either doesn't happen, or someone spends an entire afternoon manually looking up each address and dropping pins by hand, one at a time, hoping they don't make a typo on address number 47.

Neither of those outcomes is good for the story. A story without a map loses readers who would have engaged with it visually. A map built by hand, address by address, is slow enough that it often gets cut when deadline pressure hits — and it's exactly the kind of tedious, repetitive task where mistakes creep in unnoticed.

What this actually costs a small newsroom

Think about the last time your outlet ran a data-driven story with a map — a "where crashes cluster" piece, a "here's every location on this list" explainer, a crime-pattern story. If someone built that map by hand, add up the real cost:

• The hours. Manually finding coordinates for 100 addresses, even at a brisk pace, eats up the better part of a workday. For 500 or 1,000 addresses — the kind of list you get from a real public-records request — it's simply not something one person can do between other duties.
• The errors. Manual lookups are exhausting and repetitive, and repetitive tasks are where humans slip. A pin dropped one block off doesn't just look sloppy — it can misrepresent which side of a boundary an incident falls on, which matters when the story is about a specific district, precinct, or school zone.
• The missed story. Sometimes the map doesn't get built at all, and the story runs as text only. Readers scroll past. The story that could have been shared as an image, screenshotted, and passed around social media instead sits quietly on the site getting normal traffic.
• The correction. If a location does end up wrong in print or online, that's a correction — a small credibility hit that's entirely avoidable.

None of this is a criticism of small newsroom staff. It's a mismatch between the tool available (a spreadsheet and a map website meant for one address at a time) and the job at hand (turning hundreds of addresses into map points, fast, on a deadline).

The fix: treat it like a subscription, not a one-off project

The tool that closes this gap isn't mapping software or a GIS course. It's a simple service that takes a spreadsheet of addresses and hands back the same spreadsheet with map coordinates added to it — latitude and longitude for every row. Once you have those coordinates, any basic mapping tool your outlet already uses (or a simple embed on your site) can turn that into a map of pins in minutes.

The reason a subscription makes more sense than a single one-time job is that this isn't a once-a-year need for a newsroom that covers a beat seriously. Crash data, incident logs, permit filings, and public-records lists show up on a recurring basis — monthly crime blotter roundups, a running series on infrastructure, an ongoing investigation that gets updated as new records come in. A subscription means the tool is just there, ready, every time a new list lands in your inbox — instead of scrambling to find (and pay for) a solution each time.

For a small outlet, the Lite plan at $19 a month covers this well: 21,000 US addresses a month. That's enough for a running series with multiple map stories a month, or one very large public-records dump, with plenty of room to spare. You can cancel anytime, so if a story wraps and you don't need it next month, you're not locked in.

How it works

There's no software to install and nothing to learn beyond opening a spreadsheet.

Step 1: Get your address list into a spreadsheet

Whatever the source — a public-records request, a scraped table from a government site, a list your reporter typed up by hand — get the addresses into a simple spreadsheet, one address per row. Street, city, state, and zip in separate columns works best, but a single combined address column works too.

Step 2: Upload the file

Log in, choose your file, and upload it. That's the entire technical step. There's no code, no settings to configure, nothing that requires IT support.

Step 3: Let it run

The service processes every row in the file, looking up the map coordinates for each address. For a list in the hundreds, this takes minutes, not hours.

Step 4: Download your finished spreadsheet

You get back the exact same spreadsheet you uploaded, with two new columns added: latitude and longitude for every address. Nothing else changes — your original columns, your story notes, your case numbers, all stay exactly where they were.

Step 5: Drop it into your mapping tool

From here, the coordinates plug straight into whatever your outlet uses to build maps — a simple embeddable map tool, a spreadsheet-to-map service, or your CMS's built-in map feature. The hard part — matching addresses to coordinates — is already done.

What this looks like in practice

Picture a two-reporter local outlet covering a string of car break-ins across a mid-sized city. A records request comes back with 340 incident addresses over six months. Instead of one reporter spending a day squinting at a map website and typing addresses in one at a time, the whole list gets uploaded as a spreadsheet on a Tuesday afternoon. Twenty minutes later, the same spreadsheet comes back with coordinates for every incident. By Wednesday morning, there's a finished map ready to go with the story — showing readers exactly where the pattern is concentrated, block by block, in a way no paragraph of description could match.

Or picture a newsroom running a monthly feature on new business permits downtown. Same list format every month, same workflow every month: export, upload, download, map. It stops being a special project and becomes routine — the kind of recurring visual element that makes a beat feel consistently well-covered rather than occasionally illustrated.

Handling messy public records

Public-records addresses are rarely clean. Police logs sometimes list a cross-street instead of a street number. Permit filings sometimes have a typo in the zip code. A subscription service built for this kind of work is designed to handle that — matching what it reasonably can, and flagging the handful of addresses it can't confidently place so a reporter can eyeball just those, rather than the whole list. That's a five-minute check instead of a five-hour one. If your outlet regularly deals with rough incoming data, it's worth reading through handling addresses that won't geocode for a plain-English look at what to do with the stragglers.

Frequently asked questions

Is this hard to set up if I'm not techy at all? No. If you can attach a file to an email, you can use this. There's no software to install and no code involved anywhere in the process.

What happens if an address in our public-records list is incomplete or oddly formatted? The service does its best to match it and will flag anything it genuinely can't place with confidence, so you can check just those few rows by hand instead of the whole list.

Do we need a developer or IT person to set this up? No. The entire workflow is upload a spreadsheet, wait a few minutes, download a spreadsheet. Anyone on staff who can use a spreadsheet can run it.

What if we only need this occasionally, not every month? You can cancel anytime. Many newsrooms only keep an active month running when there's a story in progress, and pause otherwise — there's no long-term contract.

Is our data safe? These are sometimes sensitive incident locations. Your file is used to process your request and isn't shared or sold. If your outlet handles particularly sensitive location data — say, addresses tied to an ongoing investigation — treat it the same way you would any records handling: strip anything you don't need to submit, and only include what's necessary to get coordinates back.

How much can the Lite plan actually handle? 21,000 US addresses a month for $19. That covers a large public-records dump or several smaller story maps in the same month, with room to spare for a typical local beat.

What if our list is international, or we need more volume some months? Higher-volume plans exist for bigger jobs, and pay-as-you-go pricing is available too if a single month is unusually large. The pricing page lays out every option side by side.

Can we reuse this for other data-heavy stories, not just incidents? Yes — the same process works for permits, inspections, polling places, business openings and closings, or any other address-based public list your beat touches.

Related articles

• Checking service area coverage for warranty claims
• Mapping where your audience actually is
• Location-tagging a season of content in one batch
• The real cost of running your own geocoder
• Startup guide: from free tier to first paid plan

--- *I.A. / CSV2GEO Creator*