Geospatial
Connection Map
Lines connecting locations, showing routes, flights, or relationships between places.
Major Airline Routes
Daily passenger volume
View data (7 rows)
| Passengers | From | To |
|---|---|---|
| 8500 | New York | London |
| 12000 | New York | Los Angeles |
| 6200 | London | Dubai |
| 4800 | Los Angeles | Tokyo |
| 7100 | Dubai | Mumbai |
| 9200 | London | New York |
| 3800 | Tokyo | Singapore |
Use a connection map when…
- Flight routes, trade flows, migration
- Showing connections between cities
Avoid when…
- Non-geographic relationships (use chord/network)
- Too many connections
Data it needs
| Property | Value |
|---|---|
| Min Rows | 3 |
| Min Columns | 4 |
| Column Types | stringstringnumbernumber |
| Notes | Origin and destination as place-name strings or explicit lat/lon pairs, plus a value column. The renderer geocodes named places automatically. |
Visual anatomy
Marks
arc/linecircle
Channels
position (lat/lon)line-width
Axes
geographic coordinates
Guiding principles
Consider instead
Common mistakes
Too many overlapping lines
No width/color encoding for flow volume
History
Common in airline route maps since commercial aviation began in the 1930s.
Accessibility notes
List connections as origin-destination pairs with values.
Related reading
Got data? Let's see what works.
Drop your CSV. You'll get a Connection Map plus four alternatives - ranked by which one actually fits your data best.