Skip to content
master
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
css
 
 
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

MapSwitcher

Chrome extension to switch from one online map provider to another, maintaining (as far as possible) the map centre, zoom level, and directions of the source map.

Installation

Most users will want to use the released version, available on the Chrome Store.

To install the development version

If you're interested in contributing to its development, modifying the extension for your own use, or simply using the most recent code, you should follow these steps:

  • Clone this repository
  • Open chrome://extensions/ in your browser
  • Check the 'Developer Mode' checkbox
  • Choose 'Load unpacked extension...' and select the root directory (which contains manifest.json)

Building the release version

You can build the release version using npm:

nvm use
npm install
npm run build

This will clean and build into ./release, generating or copying all necessary files. It can be tested using the chrome://extensions 'Load unpacked extension...' option (see above), and also packed through the same page.

Mapping services supported

Input mapping services

With directions
  • Google
  • Bing
  • OpenStreetMap
  • Waze
  • Here
  • Yandex
Without directions
  • Wikimapia
  • Wikimedia Labs
    • Geohack info page
  • Geocaching
  • OpenSeaMap
  • Stamen
  • Streetmap.co.uk
  • GPX Editor
  • TopoZone
  • SunCalc
  • SysMaps
  • OpenCycleMap
  • Facebook (pages and events)
  • CalTopo
  • Strava
    • Rides
    • Routes
    • Global Heatmap
  • F4map
  • OpenTopoMap
  • Qwant
  • Mapillary
  • Komoot
  • Waymarked Trails
  • Rightmove
  • OnTheMarket
  • Zoopla
  • PrimeLocation
  • Peakbagger
  • NGI / IGN (Belgium)
  • OSMaps
  • Windy
  • Flightradar24

Output mapping services

With directions
  • Google
  • Bing
  • Here
With limited directions

(These services only support single segment directions, no 'via' points.)

  • OpenStreetMap (only for routes with coordinate-specified waypoints)
  • Waze (only for routes with coordinate-specified waypoints)
  • Yandex
Without directions
  • Wikimapia
  • Wikimedia Labs
    • Geohack info page
    • WikiMiniAtlas
  • Geocaching
  • what3words
  • OpenSeaMap
  • Stamen
  • GPX Editor
  • Streetmap.co.uk (UK)
  • NGI / IGN (Belgium)
  • OpenCycleMap
  • TopoZone (US)
  • SysMaps (UK)
  • Strava
    • Global Heatmap
  • F4map
  • OpenTopoMap
  • CalTopo (US + CA)
  • Qwant
  • Mapillary
  • Komoot
  • Waymarked Trails
  • OSMaps
  • Windy
  • OpenWeatherMap
  • Flightradar24

Utilities

  • GPX download
  • Copy to clipboard
  • SunCalc
  • Boulter (coordinate conversion)
  • Flickr (map of nearby photos)

Known issues

  • Where directions are specified by address (not coordinates), different services can geocode these in radically different ways. So the routes may not start or finish where they did on the input mapping service. Where available, coordinates are used instead, but not all services make the coordinates of each waypoint on the route available.
  • Zoom / scale may not always be exact, depending on the limitations of the input & output map services
  • Directions handle multi-segment routes (with intermediate specified locations) where possible. Only some services (google, microsoft) support this. In these cases, output services which only support single segments will show maps from the first location to the last location.
  • Waze currently fails to handle zoom. The parameters do not work as its own documentation suggests they should.
You can’t perform that action at this time.