It may or may not be the case here but generally companies will move their architecture away from existing "workarounds" if you want to call it that. It's just business... I can also imagine many reason OSM is more focused on the older devices. It just makes sense to support what will go out of support sooner.
You make good points. Interestingly, the latest MKGMAP utility www.mkgmap.org.uk/ for creating Garmin-compatible maps _does_ have address search working better now for newer Garmin Drive series models, but resulted in address search breaking on older ones. The map still works on older models but address search does not. If the developer of MKGMAP were able to put in some sort of code that could differentiate between "legacy Garmin" and "newer Garmin", that would fix the problem, assuming it's even fixable.
Hello I actually did the same test and the results showed up in 1 second. You have to type in Austin Texas not just Austin otherwise it’s too vague. I wish they would let you set the speed indicator to anything you want like distance or eta. My car already tells me the speed.
I'll try that. On nuvis that support custom dashboards, I believe it is possible to create a custom dashboard with the speedometer removed entirely and replaced with a configurable field, but it takes a lot of coding and experimentation to make it work. www.gpsreview.net/creating-custom-dashboards-for-your-nuvi/
@@sat103 I don't have time for that. Seems like an oversight on Garmin. I used to have a Magellan and loved it. But Garmin is not to bad. Just simple update would be nice to fix this issue.
I bought the Garmin DriveSmart 65 yesterday and brought everything current. After reviewing your experiment, it is clear that the delay is due to searching within 'United States'. Since we know that the address is within Austin, TX choosing to 'Search Near A Place' and specifying Austin, TX will narrow the geographic area massively. Repeating your experiment produced a minimal delay since the search was confined to a single city.
Yeah, strange it does it not ask for either the state or zipcode? They have always been a bit odd that you cannot put in a complete address. The big question is WHY???
Do you have a video on how osm maps and garmin maps differ? Planning to buy a garmin but i couldn’t find maps of my country in garmin website. So i might end up taking OSM maps in the end. But i want to see first how osm looks on a garmin device before buying.
The real problem is not with OSM itself, but with the provider you chose the OSM-based map from. The data itself is fine, it's just that the way someone decided to package it is at fault. Also, the tools that create these Garmin maps from OSM are still receiving updates, so it's possible it is or will be fixed.
I made this video in '20 and my opinion of OSM has changed since then. OpenMapChest with their Garmin-compatible map releases also uses the US Census TIGER database which has improved address search for the USA significantly, and I have experimented with creating my own maps using mkgmap. While the address/POI data still isn't as good as that created by HERE, the road data itself allows a Garmin device to calculate routes significantly faster as I show here ruclips.net/video/FlkrIjHK7qE/видео.html As long as one knows how to get GPS coordinates for locations, the map data is genuinely good for daily use.
They currently do not. Any model made now or previously that has lifetime maps support still gets free map updates. I still have a nuvi 50LM model made back in 2011 and just updated it with a Garmin-issued map literally a few days ago with the free Garmin Express software.
If the problem is with the compatibility between the deice and the map database I would think that should be an easy fix as soon as they work out who is responsible for it. Since Open Streetmap works on other devices I would think it's a Garmin issue. I care what maps I use with my Android phone apps but I dont care about that for my garmin nuvi or drivesmart. I just want to get there. Garmin has a lot of navigation problem that never seem to get fixed as well and no easy way to report them any more. Too many times it shows that you should be in the wrong lane for an upcoming freeway split, at least in Los Angeles & Orange Counties of California. And I wish they would quit telling us what interchanges NOT to take and just tell us how far to the one we need to take. At times, it's just too much trivial information coming too fast to process and should be adjustable. Instruction should be based on actual signs on the freeway and not what lain I need to be in. I have to keep the it muted all the time and just look at the pink line to see where it's trying to take me. I could use the text but I dont what to have to look at the screen that long in high speed Los Angeles traffic.
When using a Garmin issued map, search and navigation is fast. With the OSM map, search is slow but navigation is still fast. The fastest way for both types of maps is to input GPS coordinates directly from "Coordinates" because that skips the search completely.
Наука
Like this video? Subscribe here ruclips.net/user/sat103
It may or may not be the case here but generally companies will move their architecture away from existing "workarounds" if you want to call it that. It's just business... I can also imagine many reason OSM is more focused on the older devices. It just makes sense to support what will go out of support sooner.
You make good points. Interestingly, the latest MKGMAP utility www.mkgmap.org.uk/ for creating Garmin-compatible maps _does_ have address search working better now for newer Garmin Drive series models, but resulted in address search breaking on older ones. The map still works on older models but address search does not. If the developer of MKGMAP were able to put in some sort of code that could differentiate between "legacy Garmin" and "newer Garmin", that would fix the problem, assuming it's even fixable.
Hello I actually did the same test and the results showed up in 1 second. You have to type in Austin Texas not just Austin otherwise it’s too vague. I wish they would let you set the speed indicator to anything you want like distance or eta. My car already tells me the speed.
I'll try that. On nuvis that support custom dashboards, I believe it is possible to create a custom dashboard with the speedometer removed entirely and replaced with a configurable field, but it takes a lot of coding and experimentation to make it work. www.gpsreview.net/creating-custom-dashboards-for-your-nuvi/
@@sat103 I don't have time for that. Seems like an oversight on Garmin. I used to have a Magellan and loved it. But Garmin is not to bad. Just simple update would be nice to fix this issue.
I bought the Garmin DriveSmart 65 yesterday and brought everything current. After reviewing your experiment, it is clear that the delay is due to searching within 'United States'. Since we know that the address is within Austin, TX choosing to 'Search Near A Place' and specifying Austin, TX will narrow the geographic area massively. Repeating your experiment produced a minimal delay since the search was confined to a single city.
Yeah, strange it does it not ask for either the state or zipcode? They have always been a bit odd that you cannot put in a complete address. The big question is WHY???
Do you have a video on how osm maps and garmin maps differ? Planning to buy a garmin but i couldn’t find maps of my country in garmin website. So i might end up taking OSM maps in the end. But i want to see first how osm looks on a garmin device before buying.
The real problem is not with OSM itself, but with the provider you chose the OSM-based map from. The data itself is fine, it's just that the way someone decided to package it is at fault. Also, the tools that create these Garmin maps from OSM are still receiving updates, so it's possible it is or will be fixed.
I made this video in '20 and my opinion of OSM has changed since then. OpenMapChest with their Garmin-compatible map releases also uses the US Census TIGER database which has improved address search for the USA significantly, and I have experimented with creating my own maps using mkgmap. While the address/POI data still isn't as good as that created by HERE, the road data itself allows a Garmin device to calculate routes significantly faster as I show here ruclips.net/video/FlkrIjHK7qE/видео.html As long as one knows how to get GPS coordinates for locations, the map data is genuinely good for daily use.
So Garmin is going to probably going to charge for All Map updates?
They currently do not. Any model made now or previously that has lifetime maps support still gets free map updates. I still have a nuvi 50LM model made back in 2011 and just updated it with a Garmin-issued map literally a few days ago with the free Garmin Express software.
@@sat103 I actually had a Garmin nuvifone G60 I loved that phone ! I wish I still had it!
I just got the Drivesmart 55 + Traffic based on your videos!
@Joe Shabidu That is correct
If the problem is with the compatibility between the deice and the map database I would think that should be an easy fix as soon as they work out who is responsible for it. Since Open Streetmap works on other devices I would think it's a Garmin issue. I care what maps I use with my Android phone apps but I dont care about that for my garmin nuvi or drivesmart. I just want to get there. Garmin has a lot of navigation problem that never seem to get fixed as well and no easy way to report them any more. Too many times it shows that you should be in the wrong lane for an upcoming freeway split, at least in Los Angeles & Orange Counties of California. And I wish they would quit telling us what interchanges NOT to take and just tell us how far to the one we need to take. At times, it's just too much trivial information coming too fast to process and should be adjustable. Instruction should be based on actual signs on the freeway and not what lain I need to be in. I have to keep the it muted all the time and just look at the pink line to see where it's trying to take me. I could use the text but I dont what to have to look at the screen that long in high speed Los Angeles traffic.
OMG !!! This GPS the one at right is very slow
When using a Garmin issued map, search and navigation is fast. With the OSM map, search is slow but navigation is still fast. The fastest way for both types of maps is to input GPS coordinates directly from "Coordinates" because that skips the search completely.
If you had the address in the address storage you should have been able to go right to it. Shouldn't you?