Pudsey Bear
Full Member
- Posts
- 20,600
- Likes
- 32,703
The biggest problem with Google Map's which in my go to, is if you put a town in, it never takes you to the town centre, just some arbitrary road or street, also when you get to this street, half of the map disappears under a graphic and you are lost, also a MASSIVE problem is despite it having the best data as they physically drive down almost every street & road everywhere, the speed limits are often far from correct, it doesn't know bridge heights or road widths, and there is no way to put vehicle dimensions in, why is this so?
You've raised several valid and common frustrations with
Google Maps, especially useful for users of large vehicles like campervans or motorhomes. Here are the reasons for these limitations:
1. Navigation to "Arbitrary Roads" instead of the Town Centre
When you search for a general location like "Keighley" (rather than a specific address or point of interest like "Keighley Town Hall"), Google's algorithms try to pick a relevant, accessible point within that area, which might be a main road on the edge or a well-known intersection, rather than the exact geographic or commercial centre.
2. Map Disappearing under Graphics at Destination
The graphic overlay at the destination, which shows estimated time of arrival (ETA), distance, and other information, is a common user interface design choice in the Google Maps app.
3. Inaccurate Speed Limits
While Google uses Street View imagery and third-party data to determine speed limits, the data isn't always perfect or up-to-date.
4. No Vehicle Dimensions Input (Bridge Heights, Widths)
This is a fundamental limitation of general consumer navigation apps and is related to liability and data complexity.
You've raised several valid and common frustrations with
Google Maps, especially useful for users of large vehicles like campervans or motorhomes. Here are the reasons for these limitations:
1. Navigation to "Arbitrary Roads" instead of the Town Centre
When you search for a general location like "Keighley" (rather than a specific address or point of interest like "Keighley Town Hall"), Google's algorithms try to pick a relevant, accessible point within that area, which might be a main road on the edge or a well-known intersection, rather than the exact geographic or commercial centre.
- Algorithm Logic: The search algorithm is complex and uses various factors (prominence, accessibility, nearby businesses) to determine the best default pin location.
- Lack of Specificity: Since "town centre" isn't a single universal address point in the map data, the default chosen might seem arbitrary.
- Solution: To get around this, search for a specific landmark, post office, or the actual name of the main street in the town centre.
2. Map Disappearing under Graphics at Destination
The graphic overlay at the destination, which shows estimated time of arrival (ETA), distance, and other information, is a common user interface design choice in the Google Maps app.
- Design Choice: It's intended to present the key "arrival" information clearly.
- User Frustration: As you've noted, this can obscure the final meters of the map, making it difficult to find the exact spot or specific house number on a complicated street.
- Solution: You can usually swipe down on that information bar or tap on the map area to minimise the graphic and reveal more of the map.
3. Inaccurate Speed Limits
While Google uses Street View imagery and third-party data to determine speed limits, the data isn't always perfect or up-to-date.
- Data Collection Methods: Speed limits are primarily sourced by algorithms reading signs in Street View photos or from official government databases.
- Infrequent Updates: Street View cars don't constantly drive every road, so changes in speed limits might not be reflected for a year or more.
- Local Variations: Speed limits can change due to temporary roadworks, local bylaws (e.g., 20mph zones in Wales), or the presence of streetlights, which can be difficult for a static database to track perfectly.
- Disclaimer: Google Maps explicitly states the speed limits shown are for informational purposes only, and drivers must always obey actual road signs.
- Reporting: While you can report general road issues, there isn't a simple, direct way to report an incorrect speed limit through the app, which makes correction a slow process.
4. No Vehicle Dimensions Input (Bridge Heights, Widths)
This is a fundamental limitation of general consumer navigation apps and is related to liability and data complexity.
- Complexity of Data: Truck or large vehicle regulations are incredibly complex, varying by country, state, time of day, cargo type, bridge weight/height limits, road widths, and even tunnel curvature. Google would need an immense, constantly updated database that is far more detailed than what is currently required for standard cars.
- Liability: If Google were to offer HGV or RV routing and a user got stuck under a low bridge, the potential legal liability would be enormous.
- Target Audience: Google Maps is designed for the mass market (cars, walking, public transport), not specialised commercial or large vehicle use.
- Commercial Alternatives: Specialised, often paid, HGV or motorhome sat nav systems (like CoPilot GPS or dedicated Garmin/TomTom units) exist precisely to solve this problem. They allow you to input your vehicle's height, weight, and width, and their maps contain the specific data to route you safely, a feature Google currently chooses not to offer.
