Editorial Policy
By Marko Visic · Updated Nov 21, 2026
SimpleMapLab is run by Marko Visic, an independent operator. No advertiser relationship shapes the content, and there is no “sponsored partner” section. This page describes how content is researched, written, fact-checked and corrected, how AI is used, and how the content stays independent of the display ads that pay for the site.
Editorial mission
SimpleMapLab exists to make open and public geographic data usable by non-specialists, through free tools and sourced studies. Editorial decisions are made against four commitments:
- Specificity over vagueness. Where data exists for a real number, we use it. Where it doesn't, we say so.
- Sourced over asserted. Every factual claim should trace to a dataset, an official document or a published method named on the page. A claim we can't source comes off the page.
- Transparent over polished. Limitations, uncertainty and method choices are stated where the finding is, not in fine print.
- Useful over viral. A page exists because it answers a real question. We won't add a tool, a study or a blog post that is only there for keyword coverage.
Who writes the content
Marko Visic is SimpleMapLab's developer and editor and decides what it publishes. There is no contributor program, no freelance pool and no guest-posted content. Long-form prose (tool descriptions, blog posts, study narratives) is drafted with the help of large language models, as the AI disclosure below explains, and then reviewed, fact-checked and edited before publication.
How we write and verify content
A page goes from research and an outline to a draft, a fact-check against primary sources, an edit and publication. Facts, figures, place names and sources are checked against primary data before a page goes live, and published pages are audited again later. What those checks catch is fixed and listed on the corrections page.
AI assistance disclosure
We use Anthropic's Claude to draft text, write code and check pages against their sources. We disclose this because readers should know how the content is produced, and because Google's guidance on AI-generated content (Google Search Central, February 8, 2023) suggests an AI disclosure wherever readers would reasonably expect one.
What AI is used for on SimpleMapLab:
- Drafting prose from an outline of facts (number, place, source) at a set voice and length.
- Phrasing FAQ answers from a list of common questions.
- Writing captions for maps and charts once they have been computed.
- Writing and reviewing the site's code, including the scripts that compute the study results. The figures come from running that code on the datasets.
- Checking pages against their primary sources and the site's code, and listing what doesn't match.
What AI is not used for:
- Supplying numbers. Figures come from the datasets through the site's code, or from a primary source named on the page, not from a language model's own text. A figure found breaking this rule is fixed and logged on the corrections page.
- Final calls on sources and methods. Which dataset and formula to use (haversine or an ellipsoid formula, straight-line or road distance, a reverse geocoder or a point-in-polygon test) is Marko Visic's decision, recorded on the Methodology page.
Marko Visic decides which studies to publish, how a finding is framed, what the method notes and corrections say, how press questions are answered and what to leave out. He is responsible for every claim on the site, whatever produced the first draft.
Sourcing standards
Every factual claim on the site should trace to one of these source classes:
- Government data: the Census Bureau (population, ZIP Code Tabulation Areas, boundaries), USGS (the elevation models in the terrain tiles), NOAA (ocean depths, coastline lengths) and the National Park Service (national parks).
- Open datasets: OpenStreetMap (roads, addresses, places; ODbL), Natural Earth (world boundaries; public domain), GeoNames (world towns; CC BY 4.0), the AWS Terrain Tiles (elevation), and timezone-boundary-builder with the IANA time zone database (time zones).
- Other official statistics: national statistics offices and international bodies, such as the Bureau of Economic Analysis, the IMF and the CIA World Factbook, named on the pages that use them.
- Licensed data: the SimpleMaps US ZIP Codes Database. Its free file (CC BY 4.0) backs the public ZIP lists and both ZIP-code studies; its paid Comprehensive file backs the ZIP lookups on our server.
- Software documentation: Valhalla (routing), MapLibre (rendering), d3-geo (projections). Where we describe how a calculation works, we cite the project documentation.
We don't source from listicle blogs, Reddit threads, Quora answers, or AI summaries of any of the above. If a fact needs a citation, we cite the primary source directly.
Editorial process per content type
Tool pages (70 currently published)
- Identify the task the tool addresses: what someone is searching for when they need it.
- Build the tool. The calculation is the source of truth, not the prose.
- Write the "How to use this tool" section and 4 to 6 worked examples with named places and specific numbers.
- Write the method notes (the formula, the data source, the accuracy bound), pointing to the Methodology page where relevant.
- Write the FAQ (typically 8 to 12 questions) and the technical reference table.
- Link related tools.
- Test the tool's main paths at phone and desktop widths before publishing.
Open-data studies (3 currently published)
- Identify a real research question that open data can answer.
- Compute the results with a script that turns the input data into a JSON file; the same inputs always give the same output. The coastline study instead tabulates NOAA's published figures.
- Check the top entries against an independent source, such as Census tables or the relevant agency's reports.
- Write the hub page with the headline finding, ranked tables, per-state grid and method.
- For the two ZIP-code studies, write the per-state pages: a few carry written historical context, the rest are built from each state's data.
- Publish the results as JSON and CSV under CC BY 4.0 and link them from the page's Schema.org
Datasetmarkup. - Review the top 20 entries once more to confirm the headline finding holds.
Blog posts (10 long-form posts)
Each blog post answers one question (for example, "how many counties in each US state" or "the largest US counties by area") with sourced data tables and links to the relevant tools. Posts are factual and topical, not listicles. They are revised when a reader reports a possible error or the underlying data changes.
What we don't do
- We don't fabricate data. A number we can't source doesn't go on the page, and one found without a source is sourced or removed.
- Approximations aren't presented as exact. Estimates carry "about" or "~", and rounding is disclosed.
- Nothing is copied from other sites. Prose is original; data comes from primary sources.
- No sponsored content. Display ads run on the site's pages; sponsored articles, guest posts and paid links are declined.
- No scraping of protected sites. Each dataset is used under its own terms: an open license (CC BY 4.0, ODbL, the terrain tiles' credit terms), the public domain, or, for the ZIP lookups on our server, SimpleMaps' paid license.
- Methods aren't behind a paywall. The formulas, sources and known limits of the tools and studies are on the Methodology page, free to read.
- No location names stuffed in for search. A page about state capitals talks about state capitals; we don't add lists of state names to a page for ranking.
Corrections policy
When a reader, a journalist or our own re-check finds a mistake, the workflow is:
- Verify. Confirm the error against the underlying source data. Sometimes a reported error turns out to be a method choice we should explain better; sometimes it's a real bug.
- Fix at the source. Update the data file, the script or the prose, whichever is the root cause, and rerun any dependent pipelines.
- Publish the fix. Rebuild the affected pages and deploy.
- Log the correction. Add an entry to the corrections page with the date, what the page said and what it says now. The page's “Updated” date moves only when its content changes, not for wording or design edits.
- Reply to the reporter. Thank them and explain what was wrong and what we fixed.
To report a possible correction: email hello@simplemaplab.com with "Correction:" in the subject line, the page URL, the value you think is wrong and, ideally, a source. We respond within 1–3 business days; fixes typically publish within 48 hours of confirmation.
Editorial independence and advertising
SimpleMapLab is supported by display advertising. Raptive, the site's ad network, decides where the ads sit on a page and serves them; we don't choose which ads appear. Marko Visic has no editorial relationship with individual advertisers, no advance knowledge of which ads will run on which pages, and no incentive to write content favorable to specific advertiser categories.
Concretely, this means:
- No content on SimpleMapLab is paid for by an advertiser.
- No tool design, study scope, or blog topic is chosen because an advertiser asked for it.
- No factual claim is shaped to favor or disfavor an advertiser category.
- Editorial decisions about what to publish, what to retract, and how to correct are made independent of advertising performance.
Affiliate and partnership disclosure
SimpleMapLab does not currently run affiliate links, sponsored content or paid partnerships. If that changes, for example through an affiliate relationship with a hardware or software company relevant to the site's topic, this section will be updated, affiliate links will carry the rel="sponsored" attribute that Google asks for on paid links, and the page itself will carry an inline disclosure.
Conflict of interest
Marko Visic has no financial stake in any product, service or organization discussed on the site, apart from the site's own income from display ads served by Raptive. SimpleMapLab is not affiliated with the US Census Bureau, the OpenStreetMap Foundation, the National Park Service, USGS, Google, or any other agency or provider whose data we use. The tools and studies use their data but are independent of them and not endorsed by them.
Sources and external links
When we cite an external source (a government agency, an open-source project, an academic paper), we link to the primary source, not to an aggregator or summary. Outbound links are not affiliate or referral links.
Voice and style
Pages are written to be useful, not breathless. Concrete claims with named places and specific numbers outweigh adjectives. We avoid:
- "Discover the amazing fact that…"
- "Did you know that…"
- "In today's digital world…"
- "Whether you're a student, a researcher, or a curious traveler…"
- Listicle filler ("5 amazing reasons to use a radius map").
- Bait-and-switch headlines whose claim isn't supported in the body.
We try to write like a colleague who knows the data well and is helping you find what you need fast.
Update cadence
- Tool functionality: updated continuously.
- ZIP population: from SimpleMaps' ZIP file (American Community Survey 2020–2024 5-year estimates), rebuilt when we adopt a newer SimpleMaps release.
- Map tiles: rebuilt by OpenFreeMap from OpenStreetMap data on its own schedule.
- Blank maps: regenerated when their boundary data or drawing changes. The US maps use the Census Bureau's 2017 boundaries.
- Studies: rerun when the method changes or we adopt a newer data release.
- Blog posts: tables built from the site's data files are rebuilt at each site build; prose is revised when a reader reports an issue or the data changes.
- Footer pages: About, Methodology, Editorial, Contact, Privacy, Terms, Disclaimer. Reviewed on any major site change.
Reader trust signals (how to verify the above)
Ways to check what this page says:
- Every study has a downloadable dataset in JSON and CSV. Run your own analysis; if our numbers don't match yours, tell us, and we'll correct the page or explain the difference.
- The corrections page lists every correction with its date, what the page said and what it says now.
- Tool, study, blog, and reference pages carry a byline with the author and the date of the last content update, from the site's page-dates record.
- Outbound links go to primary sources, not aggregators, so you can check a figure where it comes from.
- The Contact page lists response times by request type.
Questions
Questions about how content is produced, sources we use, or how we'd handle a specific edge case: hello@simplemaplab.com, or the Contact page.