And here's a shot of the address approaching from the west. Notice the house number on the bottom. The announcement matched the house number indicating destination on the right.

 

 

And here's a shot of the address approaching from the west. Notice the house number on the bottom. The announcement matched the house number indicating destination on the right.

 

How about making the flag wave on the side of the destination. I think my old D3 had that feature.

 

Remove the bmp from the zip and drop it in your common folder and your flags will wave.

My flags already wave. I was just saying to make it wave on the side of the destination. Wave on right for riight and left for left.

How about making the flag wave on the side of the destination. I think my old D3 had that feature.

Remove the bmp from the zip and drop it in your common folder and your flags will wave.

My flags already wave. I was just saying to make it wave on the side of the destination. Wave on right for riight and left for left.

I wish I was that talented to figure that out. Maybe in my next life.

It was just a thought. No big deal. I do know that my D3 had it that way. So maybe it is in there but its hidden like they hid the left/right BS.

It was just a thought. No big deal. I do know that my D3 had it that way. So maybe it is in there but its hidden like they hid the left/right BS.

This thing is like atari from the late 70's where they had everyone trying to uncover easter eggs. I just can't believe one year later and I'm still messing with this trying to make it better than they sold it to us. Why, oh why, oh why?

F.Y.I All

I tried the left right destination announce using Samantha and found it too unreliable. About half the time it announced the destination on the wrong side of the street. In one case I know the nav knows the destination is on the right but the announce says it is on the left.

 

Example of wrong announce:

I went to Fry's Electronics in Anaheim, CA. It is at 3370 E La Palma Ave, Anaheim, CA 92806. When I approach Fry's is on the right but the destination announce says I reached my destination on the left. If I approach from the west the nav tells me to go past Fry's and make a u-turn (it must think there is a divider) then again it tells me I reached my destination on the left. Obviously it knew it was on the right or it would not have told me to make a u-turn.

 

No matter if you approached from the east or west samantha said it was on the left each time? So far I haven't experienced anything like that. The only place it's been wrong is when my home address was entered, the map data had my house on the north side of the street so it said I reached my destination on the left. I then programmed my house with an even number and it's been right since. I'll have to try it coming from the other direction some time and see if there's a difference. Every where I've routed to it's been correct. Has any one else experienced something link vansmack2? BTW - There have been 150 downloads so far and one issue reported. Let's hear the good and the bad.

 

I entered the address and from the east it said you have arrived at your via point on the right. When I approached it from the west it had me make a u-turn and still said arrive on the right. The street numbers on the screen matched the destination address showing it would be on the right.

 

Check the street numbers as opposed to the announcement, the destination must announce the same side as the street numbers show. If the map data is wrong, the destination announcement will also be wrong.

 

FWIW- My maps are from the update cards. Tele Atlas, California 2008.10 [090508] running with the original hacked ezrider for 3.0.

I am running the stock maps from the Pioneer 3.02 update, which I believe are the same as what you listed above. I am running the stock ezrider, not the hacked one, so there is a difference.

I will try it with the hacked ezrider and see if that makes any difference.

I am using hacked ezrider with 2009.6 maps and it still happens to me. I look for mailboxes along side of the road, so no big deal for me.

More leg work on that Fry's location. It appears that when selecting the Fry's location through the POI's that it puts the destination in the middle of the east and west bound lanes. Yesterday I directly inputted the address and it announced the destination on the right. Today I selected Fry's through the POI's and it announced the location on the left. I then put Fry's as a via point and the inputted address as the destination. The via point wound up being about 180 feet ahead, but in the center of the east/west lanes. Below is a picture showing the via point flag in the center or median if there is one, and the destination flag in the center of the east bound lane. The bowling alley at 3364 E La Palma shows the flag well off the road on the right side. I haven't tried any other POI's, but it appears that direct address inputs will announce as correctly as the map data allows and the POI selections I would classify as hit or miss. I believe POI's are created by latitude/longitude entries.

More leg work on that Fry's location. It appears that when selecting the Fry's location through the POI's that it puts the destination in the middle of the east and west bound lanes. Yesterday I directly inputted the address and it announced the destination on the right. Today I selected Fry's through the POI's and it announced the location on the left. I then put Fry's as a via point and the inputted address as the destination. The via point wound up being about 180 feet ahead, but in the center of the east/west lanes. Below is a picture showing the via point flag in the center or median if there is one, and the destination flag in the center of the east bound lane. The bowling alley at 3364 E La Palma shows the flag well off the road on the right side. I haven't tried any other POI's, but it appears that direct address inputs will announce as correctly as the map data allows and the POI selections I would classify as hit or miss. I believe POI's are created by latitude/longitude entries.

I did more testing today with both locations I tested saying they were on the left instead of right but both were POI searches.

Here is exactly what I did today.

1. I deleted my flaskdisk and restored from backup so that I knew it was factory again.

2. I verified my maps are the same version as yours.

3. I put the hacked ezrider on my AVIC.

4. I modified my a copy of my original sys.txt fle to add the announce info then put it on the AVIC (F7010BT).

5. I did a POI search for Pep Boys 11980 Central Ave Chino, CA 91710 and added it as my destination since I previously tested that location with a wrong side announce.

6. I added, via POI search, Carl's Jr. 5295 Holt Blvd., Montclair, CA, 91763 as a via point.

Both locations announced as on the left instead of the right.

If they are using the latitude/longitude as you suggest and sounds plausible then that is just ridiculous.

Unless someone can figure out how to change that it looks like we are screwed.

vansmack2 - I checked both of the other POI's you listed and on mine they announced destination on the right. I'm posting a link to the ca poi file of my unit. Different issues of POi files give differing results. I have read that Navteq's POI's give better accuracy than TeleAtlas. I believe mine are NavTeq issued. You can also have more than one POI file but it would in most cases list the same POI twice. I'm sticking with one.

Before you change the POI file, do a direct address input on both and see if it changes to destination on the right.

As an FYI - One of the things that prompted me to search out how to add this to our units is the announce left/right was a standard turned on feature on many GPS units with IGO. Please stop bashing this based on your results, the pluses outweigh the negative on many fronts. Pioneer short changed us on many fronts with these units. If they were not so messed up to begin with we wouldn't be here trying to improve what they deemed satisfactory for the price point. While you explore other zip's you'll find many not perfect things about them. The people here who provide their discoveries and zip's put a lot of time to share with the community. There's over 32,000 registered users on this forum as a whole, granted at least half don't visit any longer. On the F series hacks forum there are about a dozen of so people who mainly contribute, most others are seeking help to a user created problem or just want to be spoon fed all the answers. I hope that one day you'd be able to provide the community a feature that we currently don't have enabled. I'm just about done. One whole year of trying to improve this is about enough for me.

Since this thread was started, you posted your results in a few other threads as a "ToAll" denouncing that this feature is pretty much useless and flawed. Instead of bashing, how about finding a solution or help us in figuring out the limitations? You will come across a few things in every data.zip that will not be accurate 100 % of the time, for instance do not in any way use the speed camera mod. You will find alerts for camera's in your area that do not exist, and maybe the speed limit post on the alert may be wrong. Also, do not pay attention to the road speed limit. Many places it will be non-existant, others it may be off 5 or 10 mph. Turn restrictions, forget them. They worked pre 3.0 now they don't work as well. If something does not work to your expectations, remove it and move on to something else.

Here's the POI link for California. Good Luck.

http://www.mediafire.com/?sharekey=5b41 ... d2eb488dac

Sorry to have upset you.

I am working with you right now to try and see if we can figure out anything to make this announce better. I understand what you are saying but am giving my opinion (and it is just that, my opinion not "denouncing") as to whether I think this is any good. If doing a POI search gives me incorrect announces at least half the time then in my opinion it is useless, but it may be valuable to others. That is something they have to decide.

I would work on this more if I had the time to dig into the coding but I don't have the time for that at present. I have even waited months to see how others progressed. I do give thanks and much appreciation to all for their great efforts. I would even give some a paypal donation if I could presently afford it.

I agreed that in many ways Pioneer screwed us my not implementing many features that they should have. You have done a lot of great work and I appreciate it so please don't take my comments the wrong way.

I know many cameras are incorrect, etc. but that is not a reason to tell me not to use them just because I find this not to my liking in its current state. In fact I had two red light cameras in my area say they were speed cameras with a 70 mph speed limit. I know they need to be changed and will have to do that if I want to continue to use it.

You are right that there is no perfect data.zip for my taste. If I want one that is exactly what I want then I will have to dig into the code and mod as I like, which I presently don't have time for.

Have a great Thanksgiving weekend and again thanks for all your help to me personally and all of us.

I changed my California POI to the Navteq one you posted.

I did a new POI search for the Pep Boys with the Carl's Jr. via point and they both announced on the right as they are supposed to. I also tried direct address input and that worked correctly too.

I tried several other POI points in the area and they all worked correctly also so apparently the Navteq POIs are much better.

THANKS SO MUCH for working in this with me.

Now more questions:

1. Do you think the Navteq POIs have as many POIs in them because the TeleAtlas has two California files for a total size of 44.5 MB whereas the Navteq single file is only 7.6 MB?

2. Where can I download all of the Navteq US POIs that are hopefully up to date.

I found this link http://www.gpsunderground.com/forums/sh ... php?t=7202 to download the Navteq

POIs after I originally posted this. Do you think this is the best source as far as you know?

I changed my California POI to the Navteq one you posted.

 

I did a new POI search for the Pep Boys with the Carl's Jr. via point and they both announced on the right as they are supposed to. I also tried direct address input and that worked correctly too.

 

I tried several other POI points in the area and they all worked correctly also so apparently the Navteq POIs are much better.

 

THANKS SO MUCH for working in this with me.

 

Now more questions:

1. Do you think the Navteq POIs have as many POIs in them because the TeleAtlas has two California files for a total size of 44.5 MB whereas the Navteq single file is only 7.6 MB?

2. Where can I download all of the Navteq US POIs that are hopefully up to date.

I found this link http://www.gpsunderground.com/forums/sh ... php?t=7202 to download the Navteq

POIs after I originally posted this. Do you think this is the best source as far as you know?

That may be where I got mine. I don't remember for sure, though. I have read that Navteq using a different compression level or something like that, so the files are smaller. That's a huge difference between the two. It's possible there's less content.

Hope you have better results going forward. Sorry I was a little harsh in my response yesterday morning> I need to step back a little and not let this thing get to me like that.

Going downtown tomorrow. Figure I would simulate the route. When I got downtown the beauty of the night sky in the backdrop of the buildings was fabulous.

I have concluded that for me the Navteq POI file for California seems to be missing too much and is probably why the files are so much smaller. BorisM recommended running both Navteq and TeleAtlas POIs for your main state but that would not fix the destination announce problem. More of my comments regarding my testing can be found here viewtopic.php?f=34&t=26446&p=200048#p200048

Unless someone figures out a better way to fix this or comes up with better POI files etc. I will just forgo using the left/right destination announce at this time. I am happy to have been able to help figure out why some were getting incorrect destination announce. Good luck to those of you that want to continue using this feature.

It was just a thought. No big deal. I do know that my D3 had it that way. So maybe it is in there but its hidden like they hid the left/right BS.

 

This thing is like atari from the late 70's where they had everyone trying to uncover easter eggs. I just can't believe one year later and I'm still messing with this trying to make it better than they sold it to us. Why, oh why, oh why?

LOL, Hey N-S-E-W,have there been any advances with the tts voices since your last post here, Samantha announces correctly for me but gosh she sounds terrible, is there a Jason tts or a new Samantha?

After I added the announce left/right command (and this is just my experience) Navteq announces on the wrong side TA announces correctly. I have read others have had the exact opposite effect whereas TeleAtlas would announce on the wrong side.

Just another comparison, for my time TeleAtlas is still winning but I have only been testing this for 30 minutes by simulating routes.