https://github.com/sethoscope/heatmap

Python script for generating high quality heatmaps based on any coordinate data (GPS tracks, eye tracking, etc).
https://github.com/sethoscope/heatmap

geo heatmap latlon map openstreetmap

Last synced: 27 days ago
JSON representation

Python script for generating high quality heatmaps based on any coordinate data (GPS tracks, eye tracking, etc).

• Host: GitHub
• URL: https://github.com/sethoscope/heatmap
• Owner: sethoscope
• License: agpl-3.0
• Created: 2011-05-10T23:23:36.000Z (over 13 years ago)
• Default Branch: master
• Last Pushed: 2024-07-05T01:15:09.000Z (4 months ago)
• Last Synced: 2024-09-30T05:01:52.905Z (about 1 month ago)
• Topics: geo, heatmap, latlon, map, openstreetmap
• Language: Python
• Homepage: http://www.sethoscope.net/heatmap/
• Size: 455 KB
• Stars: 484
• Watchers: 31
• Forks: 103
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-starred - sethoscope/heatmap - Python script for generating high quality heatmaps based on any coordinate data (GPS tracks, eye tracking, etc). (others)

README

        
# heatmap

## why?

There are a few kinds of heat maps. This program is for when you have

data points, each with a pair of orthogonal coordinates (X/Y, lat-lon)

and you want to plot them on a map such that they blob together a bit

to indicate density.

So, it's good for things like:

 - eye tracking data

 - lat/lon geocoded data points

 - GPS tracks

## why not?

It's not good for:

 - showing results in realtime (because it's too slow)

 - running in a browser (because it's in Python)

 - automatically layering on proprietary map systems

So... why use a slow data visualizer that doesn't run in a browser?

Because the output looks better.

There's another kind of heatmap, also called a choropleth map, in

which you divide your map into regions and color each region to

indicate something.  This tool is not for that.

A more thorough description and examples are posted at

 

## change to command line

As of version 1.13 (April 2017), the method of specifying input files

has changed. The old way will continue to be supported for at least

one year, but the new way is nicer.

Read [this tutorial](CMDLINE_UPDATING.md) for examples and help on

switching to the new way.

## Tests

[![Build Status](https://travis-ci.org/sethoscope/heatmap.svg?branch=master)](https://travis-ci.org/sethoscope/heatmap)

[![Coverage Status](https://coveralls.io/repos/github/sethoscope/heatmap/badge.svg?branch=master)](https://coveralls.io/github/sethoscope/heatmap?branch=master)