Heatmap from Points
Load coordinate rows to visualise clusters and dense areas — a simple density view.
By Aryan Khan, Founder & Editor · Updated October 2026
For example, 5,000 delivery stops plotted as a heatmap reveal the two neighbourhoods that generate half the work — structure invisible in the spreadsheet and obvious in the glow.
How to use Heatmap from Points
A thousand rows of lat/lon hide their story. Heat shows it:
The Heatmap from Points tool loads coordinate rows and visualises where they cluster, as a simple density view in your browser. Paste or drop the points and read the pattern — hot spots, cold gaps and the shape of the data — before any formal statistics begin.
- 1Load CSV points.
- 2Inspect dense regions on the map.
What people use Heatmap from Points for
1. Delivery and service demand
Stops, calls and orders as points glow where the work concentrates — depot and territory decisions start from this picture. Sparse data cleans up first with the CSV Coordinate Deduplicator.
2. Event and incident patterns
Reports, sightings and incidents cluster for reasons — the heatmap is the first look that suggests where to ask why.
3. Ecology and survey points
Sightings density hints at habitat use — a hypothesis generator, honestly labelled as such, before effort-corrected analysis.
4. Data quality checks
A suspicious hot spot at a round coordinate (or at 0,0) is the classic data-entry artefact — heatmaps catch what row counts never will.
Worked examples
A sales dataset glows brightest at head office — because un-geocoded rows defaulted to the HQ address. The heatmap did not show demand; it showed a data pipeline. Both readings are valuable; only one is true.
A small radius draws many tight hot spots (individual venues); a large radius merges them into districts. Neither is 'correct' — the radius is an editorial choice, and the honest analyst reports which one the picture used.
Reading a density view honestly
What the glow means — and what it cannot mean.
| You see | It means | It does not mean |
|---|---|---|
| Bright hot spot | Many points close together | Importance, causation or correctness |
| Smooth gradient | Density thinning with distance | A real-world gradient — may be sampling effort |
| Cold gap | Few or no points | Nothing happens there — maybe nobody recorded there |
| Single bright pixel | A pile of identical coordinates | A phenomenon — check for defaults and duplicates |
This is a density visualisation, not a kernel-density statistical surface with bandwidth inference. It shows where points are; conclusions about why remain yours.
A heatmap reveals concentration, but visual intensity is not automatically statistical density
Heatmaps are useful when hundreds or thousands of points make a pin map unreadable. They highlight areas where observations concentrate and can quickly reveal hotspots, corridors or gaps. The visual result depends on radius, blur, zoom and weighting settings, so two heatmaps of the same points can look different without either being mathematically wrong.
Use the map for exploratory pattern recognition. If a report requires formal density estimates, significance testing or population-normalized rates, move the same dataset into GIS or statistical software and document the chosen method.
How to interpret the result
The most common errors come from using a correct result to answer the wrong geographic question. Keep these points in mind for Heatmap from Points:
- For big CSVs, fix the coordinate columns first and map a sample before mapping everything: auto-detection is good but not magical, and one swapped column renders a beautiful map of the wrong ocean.
- Keep the original file even after converting: GPX→GeoJSON drops timestamps' context, KML→GeoJSON drops styling, and every pipeline has a lossy edge. Originals are cheap; re-acquisition is not.
Limits & appropriate use
File formats support different combinations of geometry, timestamps, properties and styling. Converting between them can lose information, so keep the original and inspect the output before sharing or using it.
Capabilities differ by workspace: check the accepted format and the operations actually offered on this page. Some tools process files locally but may request map tiles or other services over the network; large or specialised datasets may require dedicated GIS software.
- Cadastral/legal formats → jurisdictional land-registry exports.
- Point clouds and rasters → desktop GIS with proper spatial indexes.
- Certified tracks (evidence, insurance) → chain-of-custody originals, untouched.
Data & methodology
The CSV workspace displays points and zoom-dependent clusters; it does not calculate a heatmap or density surface.
For source details, licences and model limitations, see Data Sources and Methodology.
Key terms worth knowing
- GeoJSON
- JSON geographic format; the web-mapping native dialect.
- KML
- XML format from the Google Earth era, with styling and ExtendedData.
Editorial guidance: MapBench explains the method and limitations so the tool can be used as a transparent reference, not as a black-box answer. For legal boundaries, safety-critical routing, surveying, engineering, regulated decisions or official statistics, verify the result with the responsible authority or a qualified professional.
Category: Map Files. Results are intended for everyday analysis and planning unless a page explicitly states otherwise.
Method, assumptions & limits
- This tool’s method
- The CSV workspace displays points and zoom-dependent clusters; it does not calculate a heatmap or density surface.
- Before relying on the answer
- Inspect the accepted file format and the fields reported by this specific tool. Keep a copy of the original file before converting or editing it.
- What the result cannot establish
- File geometry and recorded timestamps can be incomplete. Verify row or point counts and inspect the exported file in your target application.
Coverage: Worldwide. Search, basemap and external data requests may use third-party services; browser-based does not mean every operation is offline. Read the source and licence notes, calculation methodology and privacy policy. If a result looks inconsistent, report a correction with the inputs and mode used.
Frequently asked questions
Clear answers about the calculation, accuracy and appropriate use.
True kernel heatmap?
Point plot density view — for advanced kernels use dedicated GIS.
Is my uploaded map file sent to a server?
Where a page says browser-first or local processing, the file is handled in your browser. Check the individual tool note for any external-service dependency.
What should I do if a file will not load?
Check that the file type is supported, the structure is valid and the file is within the stated size limits. Converting to GeoJSON, GPX, KML or CSV can also help.
Will converting a file preserve every property?
Not always. Geographic formats support different geometry, style and metadata features, so inspect the output before relying on it.
Is this a true kernel density estimate?
It is a simple density view — points contribute glow around themselves and the picture aggregates them. Formal KDE with bandwidth selection and edge correction is GIS-statistics work; this page is the honest first look, labelled as such.
What input formats work?
Coordinate rows — CSV-style lat/lon lists and pasted pairs. Messy files clean up in the CSV coordinate tools first; the heatmap wants two numeric columns it can trust.
Does point order matter?
No — density is order-blind. Duplicates matter: identical rows stack glow, which the deduplicator exists to tame.
Weighted points?
A plain density view counts each point once. Weighted analysis (by sales, severity, population) belongs to fuller GIS tooling.
The map looks different at each zoom.
Density rendering responds to scale — features merge as you zoom out. Fix the zoom when comparing two datasets' pictures, or the comparison is theatre.
Empty areas mean no activity?
They mean no points. Absence of records and absence of activity are different facts — the map shows the first; only you know the second.
Privacy — points are people's locations.
Aggregate glow is actually a privacy-friendlier way to share patterns than pins, but dense rural points can still identify. Round coordinates before sharing if the data is personal.
Related tools and resources
Bubbles instead: the Cluster Map from Points; clean rows: the CSV Coordinate Deduplicator; on a map: the CSV to Map; centre: the CSV Coordinate Centroid Calculator.
More free tools
Sources, methodology & editorial trust
- ✓ Browser-first processing where supported
- ✓ External sources are documented
- ✓ No account required for public tools
- ✓ Review data sources
Calculations are documented with their assumptions, limitations and source context rather than presented as unexplained answers.
Reviewed and maintained by Aryan Khan, Founder & Editor of MapBench.
Part of our map maker hub
Heatmap from Points sits in the map maker cluster, alongside 26 other tools that answer neighbouring questions with different methods or datasets.
You may also need
When this answer is only part of the job, these clusters cover the next step.
Read the guide behind this tool
Free Printable Blank Maps: How to Choose Outline, Labeled, or City Variants — Classroom worksheets, sales territories, and presentation slides need different map styles. How to pick blank vs labeled vs coloured — and SVG vs PNG.