About

22:36 Adrian 0 Comments

Summary: The purpose of this blog and the related YouTube channel, RideWithGPS activities, Custom IBHWGM Google Map and Twitter account is to improve Google Maps Cycling layer in a systematic, scalable way by providing a comprehensive rationale, exemplary evidence and a process reusable in other locations.

The author (Adrian Lobo) lives in Melbourne and so this site's content relates to Melbourne and Australia. If interested in working on a similar site in another city or country, feel free to contact me at loboadrian AT gmail.com

2017 Project Status: On Hold. Google killed off Map Maker - the imperfect but capable crowd-sourced mechanism for making map edits more efficient, accurate and useful. Now it only provides a nominal "Send Feedback" method where the types of issues I report (e.g. inaccurate or misleading cycling infrastructure) appear to get piped straight to the Do Not Action or Respond bin.

When the fantasies about a future of self-driving, electric cars finally evaporate whichever firm wants to have useful transport maps may rediscover Google's prior mission "to organize the world's information and make it universally accessible and useful."
See: > Transport tech fantasies vs existing cycling solutions

The Problem:

1. The purpose of Google Maps Cycling layer is help cyclists find the best route from A to B. This primarily involves safety, convenience, feasibility and comfort.

2. The purpose is NOT to simplistically display superficial cycling "infrastructure" data government agencies and map contributors wish to add regardless of accuracy, quality and usefulness. And outdated info (e.g. StreetView images) shouldn't be the last word on validating map edits or vetting submitted corrections, especially when those providing corrections are submitting verifiable, current images or videos. Unfortunately, this is the present situation in many cities (e.g. Melbourne).

Also, Google's Cycling Directions should aim to show the routes most local cyclists, familiar with the options, actually take, not just show any route. Yet, most regular cyclists will tell you that the Cycling Directions almost never show the best route, are often wildly off, and exclude most of the highest value route tips like off-road sections and the safer ways to cross intersections or change between route sections.

3. Consequently, there is plenty of potential to improve the Google Maps Cycling layer and directions in two ways:

(a) The general functionality, interface, classifications, terminology and utility.
(b) The accuracy and usefulness of the data, particularly regarding on-road cycling infrastructure.

The Solution:

1. Create an indisputable, easy-to-check evidence base of the current facts on the ground which anyone can access and utilise

- I use a Garmin Virb Elite video camera with GPS logging and automated overlays (Date/Time, Latitude/Longitude) to record all the routes.

2. Create a way of readily cross-checking the facts on the ground against Google Maps Cycling layer

- I export the GPS .gpx file to RideWithGPS and create a playable Google Maps route with the Cycling layer enabled.

3. Create a way of combining the video with the live map position inclusive of the Google Maps Cycling layer

- I screen record the RideWithGPS route using Camtasia Studio's recorder and then use its Picture-in-Picture to overlay the live map in the top right of the video. The sycing of the video position with the RideWithGPS position requires slowing down the RideWithGPS recording to around 86% as it runs faster than 1speed.

4. Enable anyone to use the videos and screenshots in checking, reporting and trying to improve cycling infrastructure or its representation in Google Maps

- I created a YouTube channel to store the raw videos of Melbourne routes. These are kept free of annotations or additional audio in order to make them readily available for use by others.

- The easiest way to reference the videos is to take screenshots which include the Google Maps Cycling layer and the Latitude and Longitude. I use the FastStone screen capture program to do this.

5. Flesh out and document the details of the main types of issues or improvements needed to Google Maps Cycling layer

- I use this blog to develop the rationale for desired improvements and systematic fixes to the way cycling route information is displayed and used in Google Maps. These universal issues can be referenced by those in other locations and linked to their own local video and photo examples.

Issue List:

> Issue 1: Useless Door Zone Bike Lanes need to be removed from Google Maps

> Issue 2: Bike lanes that don't exist need to be removed from Google Maps

> Issue 3: A new cycling layer classification for Part-time Dedicated lanes should be added to Google Maps

> Issue 4: Off-road bike paths should be marked as trails not displayed as on-road routes

> Issue 5: Safer intersection and connecting links should be prioritised in Google Maps Cycling layer

> Issue 6: Off-road paths that fill gaps in on-road bike lanes need to be added effectively to Google Maps

> Issue 7: Gaps in bike lanes should be displayed not concealed on Google Maps

> Issue 8: Direction of travel differences in bike lanes and bike-friendliness need to be indicated on Google Maps

> Issue 10: Google Maps need to add bikeable links so that Cycling Directions follow recommended routes

> Issue 11: Google Maps Cycling Directions should enable avoiding high speed roads

> Issue 13: Google Maps Cycling Directions should allow cyclists to avoid Stairs, Unpaved Trails and Highways

> Issue 14: Inaccurate and inconsistent changes to the Google Maps Cycling layer should be minimised

> Issue 15: Google Maps needs a comprehensive, timely process for updating its Cycling layer

> Issue 16: The Bicycle-friendly roads classification should be used selectively for genuinely useful routes

> Issue 18: Bike routes marked as Avoid should be visible in Google Maps Cycling layer

> Issue 19: Google Maps Cycling Directions should show accurate and practical routes through intersections

> Issue 20: Dirt/unpaved trails should be accurate, unsuited for most wheeled transport and avoidable

6. When available again and efficient, use Google Map Maker to directly fix the specific instances

- Google Map Maker is currently closed for editing in most countries and is gradually reopening with, hopefully, a more effective editing and QA process.

- I have applied to be a Regional Lead and will commence submitting edits as soon as it is open. I will be referencing blog posts with GPS-stamped images and the YouTube videos in making my submissions.

2017 Update: Google killed off Map Maker and corrections can now only be requested via the Send Feedback function within Google Maps. Based on my experience sending feedback, Google refuses to correct most of the issues I've listed here as it seems to consider accurate and useful cycling information to be a low priority.

7. Current Status of submitted corrections and improvements to Google Maps Cycling layer

- Corrections I submitted via the Google Maps > Send Feedback were not been implemented or responded to.

- As of July 2018 Google still sends auto-responder confirmations of your reports promising to review them. But there is no sign of Google actually trying to make its Cycling Layer a more useful tool for cyclists to find the best route from A to B.

8. Full details on the steps and tools involved in creating the videos, maps and data

For more details on the steps, software and tips see: > How to make cycling videos with Google Maps GPS Track overlays