Home › Microsoft Streets and Trips › Review: Microsoft Streets and Trips
But North York is a part of Toronto, and according to the government of Ontario and the government of Canada and the government of Toronto, North York is at best a postal designation, and all of it is the City of Toronto. That is another problem with the map... I know I live in North York, but it is definitely the City of Toronto that shows up on my property tax bill. They should be able to use BOTH North York and Toronto in a look-up.
4900 Yonge St, Toronto, ON [maps.google.ca]
Is there parking at passport canada, 4900 yonge street, toronto?
So people searching often use Toronto and NOT North York...
4900 Yonge St, Toronto, ON [maps.google.ca]
Is there parking at passport canada, 4900 yonge street, toronto?
So people searching often use Toronto and NOT North York...
And I live across the street from 4900 Yonge and look out my window at that building and its plaza all the time... so I know exactly where it is, and that it has one p in its Shepard, while the street two blocks south has 2 p's...
Navigation programs which search by street name or address first do best if you do not include the name of the city. This is not a shortcoming of S&T but rather the Navteq data. Where they get their city information is not clear but the search is very fast as long as they know which province/ state you are in. Don't fight it, just go with the flow!
Terry
Terry
Further testing shows you can't even add the 'st' without confusing S&T. '4900 yonge' or even '4900 yonge street' is ok as long as it knows you are in Canada!
Terry
Terry
Try that with 15 King Street West in Canada and see how many locations come up. The search tool in Microsoft software calls for address, city, province/state, postal code/zip code and country, so it should be able to accept being specific about the city without difficulty. The problem you speak of is with Navteq and not with Tele Atlas, so why should I have to change my method depending on which map source was used? That simply is not on. Remember, the Customer is always right!
I think TeleAtlas has the same problem but uses some fuzzy logic to guess which city you might really want. I have used programs that search by city first and hate them all, no matter what data they use!
If it is really a concern for you, you might try iGuidance which gives you a choice of city or street first. Or CoPilot Live V8 laptop which is strictly city first.
There is so little advantage in the speed of searches for these programs that I have no idea why they force that approach. Yes, there are some examples which need more information. But unless they are in the majority, so what.
Terry
If it is really a concern for you, you might try iGuidance which gives you a choice of city or street first. Or CoPilot Live V8 laptop which is strictly city first.
There is so little advantage in the speed of searches for these programs that I have no idea why they force that approach. Yes, there are some examples which need more information. But unless they are in the majority, so what.
Terry
We've had this conversation before, many times. It's not the fault of the map or the search engine. The problem is people guessing wrong.
With large metropolitan areas like Toronto you just mess up the search engine by specifying a city name because you are very likely to get it wrong unless you are an expert (literally) on the municipal boundaries. Better to just enter the address info (house number, street name) and accept the fact that you might get a few duplicates. Better to get some duplicates than get nothing if you guess the city name wrong.
...ken...
With large metropolitan areas like Toronto you just mess up the search engine by specifying a city name because you are very likely to get it wrong unless you are an expert (literally) on the municipal boundaries. Better to just enter the address info (house number, street name) and accept the fact that you might get a few duplicates. Better to get some duplicates than get nothing if you guess the city name wrong.
...ken...
For the heck of it, I looked up the 4900 Yonge St, Toronto, ON address in CoPilot 8. It found it perfectly. CoPilot uses NavTeq data.
On the PC I'm at right now, I only have Streets & Trips 2010. It successfully finds the correct location when I enter "4900 yonge, toronto". Later, I'll test it with the new 2011 version. If the 2011 version doesn't find it, and it only finds it when searching for "4900 yonge, north york", than this indeed would be a glitch. Bob, how many years has it been since North York and all the other cities were amalgamated? Has it been a decade yet? This worked in earlier S&T versions, is this really not working in v.2011?
Amalgamation was 1999 if memory serves. And I only know that it did not work in MapPoint 2011. I haven't checked it in Streets & Trips 2011. Don't have the time right now, either. Too busy with other stuff <grin> and as of now with the way they've screwed up the 401 and the 427-QEW connection I'm not sure I really want 2011 :-)
I'll be keeping both, 2010 and 2011, on my laptop. And I'll try to remember to test the adress search in 2011 tonight.
2011 can't find it if you add the Toronto part. 2010 can!!
Terry
Terry
Quote:
Originally Posted by malaki86
For the heck of it, I looked up the 4900 Yonge St, Toronto, ON address in CoPilot 8. It found it perfectly. CoPilot uses NavTeq data.
Sounds like S&T has added an error to their own database.
Terry
Quote:
Sounds like S&T has added an error to their own database.
Marvin, I don't know if it is that serious. If you try the same test with your GMPC, you will find that a search without city will show the address in North York and no Toronto choice. A search using the city will give the same location in Toronto. If one was not aware that North York was part of Toronto, this could certainly be confusing..but not for someone living there.
Terry
Terry
Similar Topics