POI Scanner Version 1.8.0
for MS S&T 2006 to 2009 with Vista and XP. Plus Autoroute 2007.
Other versions of Windows are untested.
Adds compatibility with
Street & Trips 2006-2009 on Vista.
Fixes bug with year 2008 of beta001
Download zip file below
http://www.laptopgpsworld.com/attachments/435d1223788817-toyfountain_poi_scanner_1_8_00_2006-2009.zip
The POI Scanner acts as a warner when approaching points of interest and plays a different alert (mp3 or wave) for each of four types of POIs when detected in the preset range around the GPS icon. The POIScanner searches the map for four specially colored push pin symbols. The defaults are blue, purple, yellow and orange large circles. Personalized push pins can be used as long as colored pixels from the default push pins are incorporated in them. Just copy and paste the colored pixels into your preferred symbols. The POI Scanner is compatible with Microsoft Streets & Trips 2006 to 2008, AutoRoute 2006 and 2007 and MapPoint 2006.
What's new:
1) Select the individual wave volume at which the sound alerts will be played.
2) The scan area has been resized to reduce the bottom scan area (rearward to the GPS icon) to ten percent of the top scan area (forward of the GPS icon). This should reduce the alert warnings set off once it is passed.
Once a POI is detected, the scanner warns by playing the default sound files, included in the download zip file. Just unzip them in the same directory as the POI Scanner. You can also select any other sound file that you would like instead of the default sound files (in MP3 or wave format) by selecting the Sound Alerts tab of the POI Settings.
How does the POI Scanner work? It first determines the GPS position on the map by finding the position of the first dark burgundy pixel of the GPS icon. Then it establishes a search area around itself, defined in pixels on the map image. The size of this area varies depending of the preferred range set in the POI Settings and the zoom level of the map. When a POI is found to enter this area, it plays the sound alert. The first alert will also indicate the approximate distance setting. A few seconds later, the second reminder alert will not indicate the approximate range since it is assumed the vehicle is moving and the distance has reduced. The rearward scan distance is set to 10% of the forward and sides distance. There is no need to know of a POI once it is passed and behind.
The POI Scanner is configured to work with a zoom level of the map above 50%. Below this the scan range is set to 1 pixel of the map image only. At this zoom level even one pixel is more than 2 km. In short, it needs to be almost touching the dark burgundy section of the GPS icon to sound an alert. The later versions detects the zoom level even when the tool bar is hidden. There's no need to keep it visible. (thanks Marvin)
I made a short video clip of the POI Scanner in action to help in visualizing how it operates. It's uploaded it on Youtube. Be sure to raise the volume on your system and disable mute if there is no sound. I created a GPS icon to emulate the moving GPS icon, it's made with the same dark burgundy pixels found in the GPS icon. This way it allows me to test in different areas I could never access. It does the job for testing and saves on gas money. The first alert should be heard after about 20 seconds into the video clip.
YouTube - POI Scanner 1.7 Microsoft Streets & Trips,AutoRoute MapPoint
http://www.laptopgpsworld.com/attachments/435d1223788817-toyfountain_poi_scanner_1_8_00_2006-2009.zip
Pushpins surrounded in red with a red slash across them should not be used because they will interfere with the detection of the GPS icon. To scan for POI's the four custom coloured flags must be used. Anyone can make his own icon as long as they copy and paste pixels of the active colors of each flags to their icons.
This is a screenshot of the POI Scanner in Toronto (well not really, I emulated the GPS icon with the maroon pushpin).
This is the POI Scanner settings general pane. It gives a quick description.
Different scan distances can be selected for each pushpins.
(Approximation only)
OFF-10 meters/yards
250 meters/yards
500 meters/yards
1000 meters/yards
1500 meters/yards
2000 meters/yards
Here you can adjust the number of pixels the scanner skips while searching to accelerate the search. A value of 1 is the slowest, but most reliable. You can play by increasing the value in steps to find you comfortable point. Personally I use one. Todays laptop are more than capable of maintaining the pixel search.
I've programed default sounds which you can modify by browsing to your sound files on your computer. A newly selected file will be written in the white box after the settings tab is closed and reopened. You can test the sound file chosen to be sure this is the message you need by clicking on the test button.
When browse is clicked it will open in the same directory where you have the POI Scanner unzipped.
If you have not selected a file, this window will open to indicate it. It closes itself after seven seconds.
This will show the sound file you have selected for confirmation. It will be written in the white box after the settings tab is closed and reopened. You can test the sound file chosen to be sure this is the message you need.
This is a sample of the main directory. I keep the POI Scanner and Keys together. I've modified my version of Keys to start the POI Scanner as it starts if they are located together.
3) The same version is used for Streets & Trips 2006 to 2008. It may work with previous versions of S&T if the id control for the map control pane is identical to year 2006. If it doesn't and you are prepared to send me the needed data, I can attempt to modify the scanner to add compatibility for previous years.
4) It detects the zoom level even when the toolbar is hidden. No need to keep it visible and it works with Win98, XP and Vista the same way. (thanks Marvin)
NEW POI Scanner Version 1.8.0
Now with voice prompts and volume control.
Download by clicking the zip file below
http://www.laptopgpsworld.com/attachments/435d1223788817-toyfountain_poi_scanner_1_8_00_2006-2009.zip
Select custom sound prompts from over 500 mp3 files at this thread
Custom MP3 files for GPS POIs
for MS S&T 2006 to 2009 with Vista and XP. Plus Autoroute 2007.
Other versions of Windows are untested.
Adds compatibility with
Street & Trips 2006-2009 on Vista.
Fixes bug with year 2008 of beta001
Download zip file below
http://www.laptopgpsworld.com/attachments/435d1223788817-toyfountain_poi_scanner_1_8_00_2006-2009.zip
The POI Scanner acts as a warner when approaching points of interest and plays a different alert (mp3 or wave) for each of four types of POIs when detected in the preset range around the GPS icon. The POIScanner searches the map for four specially colored push pin symbols. The defaults are blue, purple, yellow and orange large circles. Personalized push pins can be used as long as colored pixels from the default push pins are incorporated in them. Just copy and paste the colored pixels into your preferred symbols. The POI Scanner is compatible with Microsoft Streets & Trips 2006 to 2008, AutoRoute 2006 and 2007 and MapPoint 2006.
What's new:
1) Select the individual wave volume at which the sound alerts will be played.
2) The scan area has been resized to reduce the bottom scan area (rearward to the GPS icon) to ten percent of the top scan area (forward of the GPS icon). This should reduce the alert warnings set off once it is passed.
Once a POI is detected, the scanner warns by playing the default sound files, included in the download zip file. Just unzip them in the same directory as the POI Scanner. You can also select any other sound file that you would like instead of the default sound files (in MP3 or wave format) by selecting the Sound Alerts tab of the POI Settings.
How does the POI Scanner work? It first determines the GPS position on the map by finding the position of the first dark burgundy pixel of the GPS icon. Then it establishes a search area around itself, defined in pixels on the map image. The size of this area varies depending of the preferred range set in the POI Settings and the zoom level of the map. When a POI is found to enter this area, it plays the sound alert. The first alert will also indicate the approximate distance setting. A few seconds later, the second reminder alert will not indicate the approximate range since it is assumed the vehicle is moving and the distance has reduced. The rearward scan distance is set to 10% of the forward and sides distance. There is no need to know of a POI once it is passed and behind.
The POI Scanner is configured to work with a zoom level of the map above 50%. Below this the scan range is set to 1 pixel of the map image only. At this zoom level even one pixel is more than 2 km. In short, it needs to be almost touching the dark burgundy section of the GPS icon to sound an alert. The later versions detects the zoom level even when the tool bar is hidden. There's no need to keep it visible. (thanks Marvin)
I made a short video clip of the POI Scanner in action to help in visualizing how it operates. It's uploaded it on Youtube. Be sure to raise the volume on your system and disable mute if there is no sound. I created a GPS icon to emulate the moving GPS icon, it's made with the same dark burgundy pixels found in the GPS icon. This way it allows me to test in different areas I could never access. It does the job for testing and saves on gas money. The first alert should be heard after about 20 seconds into the video clip.
YouTube - POI Scanner 1.7 Microsoft Streets & Trips,AutoRoute MapPoint
http://www.laptopgpsworld.com/attachments/435d1223788817-toyfountain_poi_scanner_1_8_00_2006-2009.zip
Pushpins surrounded in red with a red slash across them should not be used because they will interfere with the detection of the GPS icon. To scan for POI's the four custom coloured flags must be used. Anyone can make his own icon as long as they copy and paste pixels of the active colors of each flags to their icons.
This is a screenshot of the POI Scanner in Toronto (well not really, I emulated the GPS icon with the maroon pushpin).
This is the POI Scanner settings general pane. It gives a quick description.
Different scan distances can be selected for each pushpins.
(Approximation only)
OFF-10 meters/yards
250 meters/yards
500 meters/yards
1000 meters/yards
1500 meters/yards
2000 meters/yards
Here you can adjust the number of pixels the scanner skips while searching to accelerate the search. A value of 1 is the slowest, but most reliable. You can play by increasing the value in steps to find you comfortable point. Personally I use one. Todays laptop are more than capable of maintaining the pixel search.
I've programed default sounds which you can modify by browsing to your sound files on your computer. A newly selected file will be written in the white box after the settings tab is closed and reopened. You can test the sound file chosen to be sure this is the message you need by clicking on the test button.
When browse is clicked it will open in the same directory where you have the POI Scanner unzipped.
If you have not selected a file, this window will open to indicate it. It closes itself after seven seconds.
This will show the sound file you have selected for confirmation. It will be written in the white box after the settings tab is closed and reopened. You can test the sound file chosen to be sure this is the message you need.
This is a sample of the main directory. I keep the POI Scanner and Keys together. I've modified my version of Keys to start the POI Scanner as it starts if they are located together.
3) The same version is used for Streets & Trips 2006 to 2008. It may work with previous versions of S&T if the id control for the map control pane is identical to year 2006. If it doesn't and you are prepared to send me the needed data, I can attempt to modify the scanner to add compatibility for previous years.
4) It detects the zoom level even when the toolbar is hidden. No need to keep it visible and it works with Win98, XP and Vista the same way. (thanks Marvin)
NEW POI Scanner Version 1.8.0
Now with voice prompts and volume control.
Download by clicking the zip file below
http://www.laptopgpsworld.com/attachments/435d1223788817-toyfountain_poi_scanner_1_8_00_2006-2009.zip
Select custom sound prompts from over 500 mp3 files at this thread
Custom MP3 files for GPS POIs
For those who would like to see how it works, you can now use the maroon pushpin instead of the maroon tack to emulate the GPS icon position. The maroon pushpin is made with the same dark burgundy pixels in the GPS icon. Just set the zoom level to 200 km or less, place the maroon tack in the map. Then place the indicated coloured tacks near the maroon pushpin and if within the set distance, it should play the wave files.
toyfountain, congratulations on the release of this new version! Here are a couple of screenshots:
To access the above menu, click the system tray icon, as illustrated bellow:
To access the above menu, click the system tray icon, as illustrated bellow:
New version of POI Scanner 1.3.1 is available for download
1) This version now offers extended scanner range distances.
Added to the existing four are:
10 meters/yards
250 meters/yards
500 meters/yards
1000 meters/yards
1500 meters/yards
2000 meters/yards
2) POI Scanner version 1.3.1 now uses a detailed scan area for each unit of the zoom level from 50 % to 100 % zoom (200km to 1 km). There are 50 different defined scan areas. Compared to the previous version which used only five defined scan areas from 50% to 100% zoom.
3) The sound notification is modified to reduce the amount of sleep time between repeat alerts if two or three are functioning simultaneously.
Download below
1) This version now offers extended scanner range distances.
Added to the existing four are:
10 meters/yards
250 meters/yards
500 meters/yards
1000 meters/yards
1500 meters/yards
2000 meters/yards
2) POI Scanner version 1.3.1 now uses a detailed scan area for each unit of the zoom level from 50 % to 100 % zoom (200km to 1 km). There are 50 different defined scan areas. Compared to the previous version which used only five defined scan areas from 50% to 100% zoom.
3) The sound notification is modified to reduce the amount of sleep time between repeat alerts if two or three are functioning simultaneously.
Download below
Wow, more options and a nice icon, too . But for some reason I'm getting false warnings. Occasionally I hear various types of sound for no apparent reason even when I'm using a clean, brand new map, with no pushpins, (and even all POIs turned off). Try to drive around with POI Scanner, but without any pushpins, to see what I mean.
I'll have to attempt the welding on my motherboard before I can take the laptop on the road again. I might have time next week to attempt it.
I did notice that when right clicking in the map control pane the window that opens will set off the alarm because it contains icons with the scanned colours.
Can you identify which of the sounds it makes?
pink pixel is the ding.wav
light grey is the chimes.wav ( same colour as the GPS icon when it losses the sat signal)
Dark yellow is the notify.wav
If you can PM the location where it happens and the approx zoom level, maybe I can attempt to duplicate it using the maroon pushpin as the gps icon. As much information as possible can help in detecting why it happens. I imagine this was with Vista, 1400 X ??? resolution, S&T 2008.
Does this happen with both version 1.3.0 and 1.3.1 ? I did modify the code to sound off to some degree. If version 1.3.0 is exempted from this, I'll have a good indication that the new code might be the problem.
Also, in previous versions, it would detect the icons in the toolbar if the GPS icon came too close to them. I set up a limitation in the scanned area. It's not supposed to scan outside the map control pane. Where you in the true full screen mode with the driving guidance pane?
I did notice that when right clicking in the map control pane the window that opens will set off the alarm because it contains icons with the scanned colours.
Can you identify which of the sounds it makes?
pink pixel is the ding.wav
light grey is the chimes.wav ( same colour as the GPS icon when it losses the sat signal)
Dark yellow is the notify.wav
If you can PM the location where it happens and the approx zoom level, maybe I can attempt to duplicate it using the maroon pushpin as the gps icon. As much information as possible can help in detecting why it happens. I imagine this was with Vista, 1400 X ??? resolution, S&T 2008.
Does this happen with both version 1.3.0 and 1.3.1 ? I did modify the code to sound off to some degree. If version 1.3.0 is exempted from this, I'll have a good indication that the new code might be the problem.
Also, in previous versions, it would detect the icons in the toolbar if the GPS icon came too close to them. I set up a limitation in the scanned area. It's not supposed to scan outside the map control pane. Where you in the true full screen mode with the driving guidance pane?
toyfountain/marvin- i keep getting the following error using poi locator 1.3.1 autoit error
X line 1:
error: variable used without being declared
this occurs when i do the following:
start poi scanner 1.3.1
start s&t 2007
zoom in on map(to 14 mi.)
create purple flag p/pin and place on map
create maroon p/pin and place within scan range of purple flag p/pin
whenever i place the maroon p/pin the above error box pops up
i'm running s&t 2007 and windows xp(sp2)
i've also gotten this error message a couple of other times when initially starting s&t with poi scanner already running- i'll keep playing with it to see if i can get better info for you- otherwise it seems to work ok(at my desk)
X line 1:
error: variable used without being declared
this occurs when i do the following:
start poi scanner 1.3.1
start s&t 2007
zoom in on map(to 14 mi.)
create purple flag p/pin and place on map
create maroon p/pin and place within scan range of purple flag p/pin
whenever i place the maroon p/pin the above error box pops up
i'm running s&t 2007 and windows xp(sp2)
i've also gotten this error message a couple of other times when initially starting s&t with poi scanner already running- i'll keep playing with it to see if i can get better info for you- otherwise it seems to work ok(at my desk)
hrp41, that will be very useful to toyfountain, thanks for the feedback. I haven't had the time today to do any testing myself, but from what I can recall from a few days ago:
* Version 1.3.0 would play a sound while in full-screen mode when the black auto-hiding tool bar on top appeared. This problem has been corrected in the new 1.3.1 version. I'm not sure if there were other issues with 1.3.0.
* Version 1.3.1 plays all three different sounds at various times even with no pushpins. I will try to give more useful feedback on this next time I test it.
I'm sure when these issues are corrected, POI Scanner will be a very useful tool for very many Streets & Trips users! Keep up the great work, toyfountain! And take the time to fix the laptop, too !
* Version 1.3.0 would play a sound while in full-screen mode when the black auto-hiding tool bar on top appeared. This problem has been corrected in the new 1.3.1 version. I'm not sure if there were other issues with 1.3.0.
* Version 1.3.1 plays all three different sounds at various times even with no pushpins. I will try to give more useful feedback on this next time I test it.
I'm sure when these issues are corrected, POI Scanner will be a very useful tool for very many Streets & Trips users! Keep up the great work, toyfountain! And take the time to fix the laptop, too !
For the error: variable used without being declared
I was able to reproduce this.
I think this is caused when the zoom level is under 50. I introduced new variables in version 1.3.1 and didn't define them for the zoom under 50
In the source code, in all instances, instead of
case $x_coord_zoom = 50
$Zoom_pixel_1 = 1
I modified these two lines to this:
case $x_coord_zoom = 50
$Zoom_pixel_1 = 1
case $x_coord_zoom < 50
$Zoom_pixel_1 = 1
It adds a definition for Zoom_pixel_1 when under 50. The same needs to be done for Zoom_pixel_2 and Zoom_pixel_3.
I've downloaded a modified version 1.3.12 below
Please tell me if you still get the error.
For the others, I'll keep trying to figure it out.
I was able to reproduce this.
I think this is caused when the zoom level is under 50. I introduced new variables in version 1.3.1 and didn't define them for the zoom under 50
In the source code, in all instances, instead of
case $x_coord_zoom = 50
$Zoom_pixel_1 = 1
I modified these two lines to this:
case $x_coord_zoom = 50
$Zoom_pixel_1 = 1
case $x_coord_zoom < 50
$Zoom_pixel_1 = 1
It adds a definition for Zoom_pixel_1 when under 50. The same needs to be done for Zoom_pixel_2 and Zoom_pixel_3.
I've downloaded a modified version 1.3.12 below
Please tell me if you still get the error.
For the others, I'll keep trying to figure it out.
Quote:
Originally Posted by Marvin Hlavac
hrp41, that will be very useful to toyfountain, thanks for the feedback. I haven't had the time today to do any testing myself, but from what I can recall from a few days ago:
Quote:
Originally Posted by Marvin Hlavac
* Version 1.3.0 would play a sound while in full-screen mode when the black auto-hiding tool bar on top appeared. This problem has been corrected in the new 1.3.1 version. I'm not sure if there were other issues with 1.3.0.
edit : Try version 1.3.12 below
You might/will get the occasional warning when going from TFS to normal screen until the program can redefine the coordinates of the newly resized map control pane. It should fix the detection of the grey moon pixels. It establishes a minimum top coordinate of 50 pixels. I imagine it should be pretty rare that the GPS icon travels that high before centering on the map.
Quote:
Originally Posted by Marvin Hlavac
* Version 1.3.1 plays all three different sounds at various times even with no pushpins. I will try to give more useful feedback on this next time I test it.
I noticed when coming back from TFS it detected an icon in the standard toolbar. See reason above for a possible explanation. Try hiding all toolbars. If this is it, it should eliminate the yellow and pink detection. Keep the gps icon in the upper left corner and set the range of the scanner to 2000 meters.
Quote:
Originally Posted by Marvin Hlavac
I'm sure when these issues are corrected, POI Scanner will be a very useful tool for very many Streets & Trips users! Keep up the great work, toyfountain! And take the time to fix the laptop, too !
Download here, just below
toyfountain - thanks for your reply and program change - i think this will be a great enhancement to s&t - thanks again for all the effort you have put into this - hrp
I'm going to give a go again with custom pushpins to avoid false warnings. Below is version 1.3.13 with the three necessary custom p/pins that are needed.
I noticed custom p/pins change colours if it is clicked on and selected. They get lighter in colour when not selected. This is why I kept getting different colour codes for the same p/pins before. In reality, there's only two codes. I found that the light yellow pushpin does not change colour. For now try it with these three. You will find that when the red and purple p/pins are clicked on, they will react as a new colour and sound off five times again. That is normal for now. The yellow is unique and will not do this.
I noticed custom p/pins change colours if it is clicked on and selected. They get lighter in colour when not selected. This is why I kept getting different colour codes for the same p/pins before. In reality, there's only two codes. I found that the light yellow pushpin does not change colour. For now try it with these three. You will find that when the red and purple p/pins are clicked on, they will react as a new colour and sound off five times again. That is normal for now. The yellow is unique and will not do this.
POI Scanner Version 1.4.0
What's new
1) Made four custom coloured flags included in the zip file instead of using the standard ones. It should provide less interference from other colours.
(added the chord.wav sound for the new orange colour).
2) Restored the complete search to the true full screen mode. The top bar should not be detected using these new flags.
3) When going from TFS to standard screen, there should be no false detections with the new flags.
edit: changed the file for better cpu usage.
What's new
1) Made four custom coloured flags included in the zip file instead of using the standard ones. It should provide less interference from other colours.
(added the chord.wav sound for the new orange colour).
2) Restored the complete search to the true full screen mode. The top bar should not be detected using these new flags.
3) When going from TFS to standard screen, there should be no false detections with the new flags.
edit: changed the file for better cpu usage.
I bet you were resisting for the longest time the temptation to implement custom pushpins to make POI Scanner work. I bet this will tremendously simplify things for you. And the added benefit is that you can now create really cool pushpins that look like a red-light camera, or anything else .
I'll test it tomorrow for false warnings. And, by the way, I actually haven't used the 'true' full-screen in many months. I only use the 'regular' full-screen. But that will likely make no difference .
I'll test it tomorrow for false warnings. And, by the way, I actually haven't used the 'true' full-screen in many months. I only use the 'regular' full-screen. But that will likely make no difference .
toyfountain - being a total "idiot" concerning this software, i have downloaded version 1.4.0 and have a question about using it - should i import the new .bmp files into s&t as "custom pushpins" and then use them instead of the "standard pushpins" supplied with s&t ? - also can i import them directly from the folder they are in after being extracted from the downloaded 1.4.0 zip file or do i need to create a new folder to hold the .bmp files before importing them to s&t ? - thats probably enough dumb questions for awhile -
thanks - ray
thanks - ray
Customs colours actually makes it more difficult because S&T assigns the colours it wants while importing. For the red and purple it assigns two colours depending if it is clicked on or not. I had to do a double scan for the two reds and two purples. To lessen the load on the CPU I assigned the POI Scanner to scan every seventh pixel. I made sure each flag has two seven pixels strings in them to be sure it isn't missed on the first try. When changing to night mode, again S&T sometimes modifies the custom colours. I was able to find two super colours that aren't modified ( the light yellow and orange). I had much trouble with aqua and green. The aqua was even assigned different colours between 2006 and 2008 in night mode.
I'll post a revised version tonight with an increased Sleep time and I'll assign the default distance to 250 meters instead of 500 meters. When a flag isn't used, setting it to 10 meters helps the CPU even more.
I'll post a revised version tonight with an increased Sleep time and I'll assign the default distance to 250 meters instead of 500 meters. When a flag isn't used, setting it to 10 meters helps the CPU even more.
Quote:
Originally Posted by hrp41
toyfountain - being a total "idiot" concerning this software, i have downloaded version 1.4.0 and have a question about using it - should i import the new .bmp files into s&t as "custom pushpins" and then use them instead of the "standard pushpins" supplied with s&t ? - also can i import them directly from the folder they are in after being extracted from the downloaded 1.4.0 zip file or do i need to create a new folder to hold the .bmp files before importing them to s&t ? - thats probably enough dumb questions for awhile -
thanks - ray
thanks - ray
Be sure to come back and get the next one I'll post tonight. It will be easier on the cpu usage.
edit: Below is the new one. I didn't change the number since only two persons downloaded the previous one.
toyfountain - downloaded latest version, imported custom symbols, tested(at desk) - everyhing works fine - i'll be taking it on the road in the next few days - i'll give it a good "real world" test and let you know how your "baby" works - thanks again for all your & marvins efforts - ray
I have a few custom push pins. Marvin made me think about this possibility.
With all of these you'll need the revised version 1.4.1 because I had to reduce the number of skipped pixels from 7 to 3 with these. 7 pixels with the flags is fine, but not with these. Sometimes it missed the push pins, so I reduced it. It should make the scanning of a large area a little slower, but not by very much.
Version 1.4.1 is needed with these custom pushpins.
They will not work with version 1.4.0
With all of these you'll need the revised version 1.4.1 because I had to reduce the number of skipped pixels from 7 to 3 with these. 7 pixels with the flags is fine, but not with these. Sometimes it missed the push pins, so I reduced it. It should make the scanning of a large area a little slower, but not by very much.
Version 1.4.1 is needed with these custom pushpins.
They will not work with version 1.4.0
a few more
Version 1.4.1 is needed with these custom pushpins.
They will not work with version 1.4.0
Version 1.4.1 is needed with these custom pushpins.
They will not work with version 1.4.0
Last for now
Different coloured frames around the police car sound off differently, same for the lights.
Version 1.4.1 is needed with these custom pushpins.
They will not work with version 1.4.0
Different coloured frames around the police car sound off differently, same for the lights.
Version 1.4.1 is needed with these custom pushpins.
They will not work with version 1.4.0
POI Scanner 1.4.1 + all the custom pushpins
The revised version with a setting of 3 skipped pixels at a time for the scan.
I've included all the custom pushpins with the zip file.
When there are four of the same, choosing the name of the color will sound off differently.
For example
police car_red.bmp will play the ding.wav
police car_purple.bmp will play the chimes.wav
police car_yellow.bmp will play the notify.wav
police car_orange.bmp will play the chord.wav
The revised version with a setting of 3 skipped pixels at a time for the scan.
I've included all the custom pushpins with the zip file.
When there are four of the same, choosing the name of the color will sound off differently.
For example
police car_red.bmp will play the ding.wav
police car_purple.bmp will play the chimes.wav
police car_yellow.bmp will play the notify.wav
police car_orange.bmp will play the chord.wav
POI Scanner 1.4.11 + all the custom pushpins
New settings are available in the version to accelerate the pixels scans.
A setting of 1 is the most reliable, but the slowest and the most CPU intensive. Some of the custom push pins I have created are reliable with a setting of up to 10 skipped pixels. The small red lights are up to 3 only. The colored pixel strings are only 4 pixels in length. If you wish to virtually turn off a color, you can set the skipped pixels to 20 with a scan area of 10 meters. This should reduce the chance of a warning sounding off to almost nothing since sometimes the area is smaller than 20 pixels in low zoom levels.
I've included all the custom push pins with the zip file. Added four new police cars. I've also tweaked them to be used with the new pixel search settings.
When there are four of the same, choosing the name of the color will sound off differently.
For example:
police car_red.bmp will play the ding.wav
police car_purple.bmp will play the chimes.wav
police car_yellow.bmp will play the notify.wav
police car_orange.bmp will play the chord.wav
New settings are available in the version to accelerate the pixels scans.
A setting of 1 is the most reliable, but the slowest and the most CPU intensive. Some of the custom push pins I have created are reliable with a setting of up to 10 skipped pixels. The small red lights are up to 3 only. The colored pixel strings are only 4 pixels in length. If you wish to virtually turn off a color, you can set the skipped pixels to 20 with a scan area of 10 meters. This should reduce the chance of a warning sounding off to almost nothing since sometimes the area is smaller than 20 pixels in low zoom levels.
I've included all the custom push pins with the zip file. Added four new police cars. I've also tweaked them to be used with the new pixel search settings.
When there are four of the same, choosing the name of the color will sound off differently.
For example:
police car_red.bmp will play the ding.wav
police car_purple.bmp will play the chimes.wav
police car_yellow.bmp will play the notify.wav
police car_orange.bmp will play the chord.wav
POI Scanner 1.4.12 + even more custom pushpins
This version should fix a small bug that happenned when inserting a maroon tack (in effect the GPS icon) in the map with the zoom level below 50. At least that's the hope.
This version should fix a small bug that happenned when inserting a maroon tack (in effect the GPS icon) in the map with the zoom level below 50. At least that's the hope.
I'd like to know if anyone would like to be able to select their own wave file or MP3 files for the POI Scanner? To have speech files played instead of a beep, tada or chimes wave file. It is possible to make it, but if everyone is OK with the way it is, I might leave it like it is for a while.
toyfounatin - thanks for the reply - i now have a much better understanding of how the process works - as to adding the ability to play audio files related to custom symbols, i don't know about other users but i would probably never have enough symbols active at one time to cause me any confusion - however i have noticed that some user's like having things "verbalized" by the system - thanks again - hrp41
I've finally isolated my laptop problem and should become mobile again soon once I receive the part I need. I'll be able to try and replicate the problems on the road and see what tweaking the program needs.
I've tested the POI Scanner on the road for the first time today. I used the four flags for the pushpins and a skippixels setting of 1. They worked well, as expected. The only surprise was at 10 meters. It really is a virtual off switch. Just driving in by it didn't detect. From 250 meters to 2000 meters it worked well.
toyfountain, would you please test the following:
* Open new map (w/out any pushpins)
* Don't add any pushpins
* In Streets & Trips, go to Find Nearby Places => Add/Remove Places, and then select all possible POIs
* Set POI Scanner to its default settings
* Set your destination, and drive with your usual settings
* Observe for any false warnings (I get them in both full-screen mode, and windowed mode)
* Open new map (w/out any pushpins)
* Don't add any pushpins
* In Streets & Trips, go to Find Nearby Places => Add/Remove Places, and then select all possible POIs
* Set POI Scanner to its default settings
* Set your destination, and drive with your usual settings
* Observe for any false warnings (I get them in both full-screen mode, and windowed mode)
Marvin, are you getting more than one kind of alert or just the ding,ding,ding alert (for red)?
I just noticed the map's red POI changed color depending on the zoom level.
When they are little squares the code is FF0000, they change to FF0033 when they are full size on the map. FF0033 is one of the colors that is scanned. In the legends and overview menu, they remain FF0000 even at full size. It looks like I'll have to find another red or different color altogheter.
Disable the red scan by setting it at 10 meters or better yet, remove all the red POIs and see if it still declares false warnings.
I just noticed the map's red POI changed color depending on the zoom level.
When they are little squares the code is FF0000, they change to FF0033 when they are full size on the map. FF0033 is one of the colors that is scanned. In the legends and overview menu, they remain FF0000 even at full size. It looks like I'll have to find another red or different color altogheter.
Disable the red scan by setting it at 10 meters or better yet, remove all the red POIs and see if it still declares false warnings.
Quote:
Originally Posted by Marvin Hlavac
toyfountain, would you please test the following:
* Open new map (w/out any pushpins)
* Don't add any pushpins
* In Streets & Trips, go to Find Nearby Places => Add/Remove Places, and then select all possible POIs
* Set POI Scanner to its default settings
* Set your destination, and drive with your usual settings
* Observe for any false warnings (I get them in both full-screen mode, and windowed mode)
* Open new map (w/out any pushpins)
* Don't add any pushpins
* In Streets & Trips, go to Find Nearby Places => Add/Remove Places, and then select all possible POIs
* Set POI Scanner to its default settings
* Set your destination, and drive with your usual settings
* Observe for any false warnings (I get them in both full-screen mode, and windowed mode)
This new 1.4.13 has the red removed and replaced by a new purple. I renamed the old purple to blue. Disregard the new Sound Play tab in the settings. It's not functional yet. I only included the flags in this version for now since all the red bmp files will have to be modified.
Cool, I'll test it on Monday.
I drove with POI Scanner for a few hours today. I didn't set any pushpins, because I was only interested in testing for false warnings. Today was the very first time I received not a single false warning. It may still not be perfect, and I will still keep on testing this. But so far so good. I'm impressed. Good job, toyfountain! I'll let you know the minute I get a single false warning .
I did notice that as the S&T window is minimized , I sometimes get a warning for two colors. I'm guessing it's still searching until it detects the window is not active anymore. I have a pic on my destop and it must contain two of these colors.
Have you noticed this on your set up Marvin?
Have you noticed this on your set up Marvin?
I noticed this a few times, but not today with the newest version. However, this may still be present, and there may likely be nothing that can be done about it. And I wouldn't worry too much about it either.
I can confirm it still happens with this version too. I just made it happen. It also keeps on going. Since it is only when the program closes it won't be the highest priority. I figure adding a line to bypass the scan when S&T is minimized will do it.
Ok, I taught about it and decided to fix that alert when S&T gets minimized. I have a fix for it with this new version 1.4.14
The new version with voice messages instead of dings and chimes sounds is done. Please see the read me first text message in the file first.
POI Scanner Version 1.5.00 now with voice prompts.
Download zip file below
Select custom sound prompts from over 500 mp3 files at this thread http://www.laptopgpsworld.com/290-custom-mp3-files-gps-pois
You can download the english_francais_mp3.zip file if you wish to switch the default voice prompts from english to french.
POI Scanner Version 1.5.00 now with voice prompts.
Download zip file below
Select custom sound prompts from over 500 mp3 files at this thread http://www.laptopgpsworld.com/290-custom-mp3-files-gps-pois
You can download the english_francais_mp3.zip file if you wish to switch the default voice prompts from english to french.
POI Scanner Version 1.6.0 now with volume control.
Download zip file below
Download zip file below
POI Scanner Version 1.7.0
Works with Windows XP only, For Windows Vista please use version 1.8.0
Fixes bug with volume control on english versions of Windows.
Fixes recognition bug with AutoRoute.
Adds compatibility with MapPoint 2006.
Download zip file below
Works with Windows XP only, For Windows Vista please use version 1.8.0
Fixes bug with volume control on english versions of Windows.
Fixes recognition bug with AutoRoute.
Adds compatibility with MapPoint 2006.
Download zip file below
Nice! I will download it tomorrow on my mobile pc. I no longer have MS MapPoint installed, but I will test the new version of your POI Scanner at least on MS Streets & Trips 2008.
From a post from jol on gpspassion I found two important bugs. I had written AutoRoute without the capital R in the code. It is case sensitive. This completely prevented it from working in AutoRoute. In a few weeks I'll be able to test it myself once I get my copy of the french AUtoRoute.
There's also a difference with the french windows and the english windows volume control window. In english it is written with a capital V, not so in french, small v. I replaced Volume and volume with "olume" instead. It should work the same way in both french and english. I can confirm it works in french, but I can't test it on an english windows. I expect it will work the same as in the french version.
Thanks again, Marvin. I asked on MapForums and Eric Frost offered to test it on MapPoint. I could only test it on the trial version myself.
There's also a difference with the french windows and the english windows volume control window. In english it is written with a capital V, not so in french, small v. I replaced Volume and volume with "olume" instead. It should work the same way in both french and english. I can confirm it works in french, but I can't test it on an english windows. I expect it will work the same as in the french version.
Thanks again, Marvin. I asked on MapForums and Eric Frost offered to test it on MapPoint. I could only test it on the trial version myself.
Sounds good. Your MS AutoRoute should come with an airline ticket to Europe, so you can test it better ! By the way, I'm not sure how you control the sound volume, but AutoIt has SoundSetWaveVolume() and I think there may be another function for Windows master volume.
I use SoundSetWaveVolume() to raise before the alert and then lower the wave volume after the alert is played, but haven't found a control for the master volume. If you see it, please post it. I'd like to add it to the scanner. So far, I usually leave my master volume at maximum. I play the alerts at the maximum wave volume too. I find anything lower is too low to hear over the engine noise. Next car radio, I'll have an aux input. This will take care of this low volume problem.
Here's the code part for the volume
Opt("WinTitleMatchMode", 2)
ShellExecute("C:\Windows\system32\sndvol32.exe","","","", @SW_MINIMIZE )
sleep(300)
$sound_slider = ControlGetHandle("olume", "", "msctls_trackbar324")
sleep(100)
$volume = (_GUICtrlSliderGetPos($sound_slider)/5)
;MsgBox(4096,"1365", _GUICtrlSliderGetPos($sound_slider))
if $volume = -1 Then
ShellExecute("C:\Windows\system32\sndvol32.exe","","","", @SW_MINIMIZE )
sleep(300)
$sound_slider = ControlGetHandle("olume", "", "msctls_trackbar324")
sleep(100)
$volume = (_GUICtrlSliderGetPos($sound_slider)/5)
;MsgBox(4096,"1370", _GUICtrlSliderGetPos($sound_slider))
endif
$volume_int = Int($volume)
$volume_prior = 100 - $volume_int
sleep(100)
;MsgBox(4096,"", $volume_prior)
SoundSetWaveVolume($input_5)
Sleep(100)
$file_sound = IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "sound_file", "")
SoundPlay($file_sound, 1)
Select
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 1
SoundPlay(@ScriptDir & "\distance_250.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 2
SoundPlay(@ScriptDir & "\distance_500.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 3
SoundPlay(@ScriptDir & "\distance_1000.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 4
SoundPlay(@ScriptDir & "\distance_1500.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 5
SoundPlay(@ScriptDir & "\distance_2000.mp3", 1)
EndSelect
SoundSetWaveVolume($volume_prior)
sleep(100)
WinClose("olume")
BTW: Some day you'll have to tell me how you post code and maintain the original colors of the script editor.
Here's the code part for the volume
Opt("WinTitleMatchMode", 2)
ShellExecute("C:\Windows\system32\sndvol32.exe","","","", @SW_MINIMIZE )
sleep(300)
$sound_slider = ControlGetHandle("olume", "", "msctls_trackbar324")
sleep(100)
$volume = (_GUICtrlSliderGetPos($sound_slider)/5)
;MsgBox(4096,"1365", _GUICtrlSliderGetPos($sound_slider))
if $volume = -1 Then
ShellExecute("C:\Windows\system32\sndvol32.exe","","","", @SW_MINIMIZE )
sleep(300)
$sound_slider = ControlGetHandle("olume", "", "msctls_trackbar324")
sleep(100)
$volume = (_GUICtrlSliderGetPos($sound_slider)/5)
;MsgBox(4096,"1370", _GUICtrlSliderGetPos($sound_slider))
endif
$volume_int = Int($volume)
$volume_prior = 100 - $volume_int
sleep(100)
;MsgBox(4096,"", $volume_prior)
SoundSetWaveVolume($input_5)
Sleep(100)
$file_sound = IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "sound_file", "")
SoundPlay($file_sound, 1)
Select
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 1
SoundPlay(@ScriptDir & "\distance_250.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 2
SoundPlay(@ScriptDir & "\distance_500.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 3
SoundPlay(@ScriptDir & "\distance_1000.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 4
SoundPlay(@ScriptDir & "\distance_1500.mp3", 1)
case IniRead(@UserProfileDir & "\POI_Scanner.ini", "Section1", "Scanner_1", 0) = 5
SoundPlay(@ScriptDir & "\distance_2000.mp3", 1)
EndSelect
SoundSetWaveVolume($volume_prior)
sleep(100)
WinClose("olume")
BTW: Some day you'll have to tell me how you post code and maintain the original colors of the script editor.
Working on version 1.8 to add support for S&T 2009 and correct the sound volume set for Vista (different than with WinXP, presently results in an error with Vista).
Quote:
Originally Posted by toyfountain
Working on version 1.8 to add support for S&T 2009 and correct the sound volume set for Vista (different than with WinXP, presently results in an error with Vista).
is tht why I got problem with version : POI Scanner V. 1,7.
Get two error windows when I drive to a alert point and it dosent work
the first on are:
C:\Windows\system32\sndvol32.exe
Coulden`t find C:\Windows\system32\sndvol32.exe. control the
name and try agin
the second one are:
AutoIt error:
Line-1:
Error: Unable to execute the external program.
Coulden`t find the file.
do anybody have some solution on this problem for me????
POI Scanner Version 1.8.0
for MS S&T 2006 to 2009 with Vista and XP. Plus Autoroute 2007.
Other versions of Windows are untested.
Adds compatibility with
Street & Trips 2006-2009 on Vista.
Fixes bug with year 2008 of beta001
Download zip file below
Source code included
for MS S&T 2006 to 2009 with Vista and XP. Plus Autoroute 2007.
Other versions of Windows are untested.
Adds compatibility with
Street & Trips 2006-2009 on Vista.
Fixes bug with year 2008 of beta001
Download zip file below
Source code included
Quote:
Originally Posted by Tjabbe
is tht why I got problem with version : POI Scanner V. 1,7.
Get two error windows when I drive to a alert point and it dosent work
the first on are:
C:Windowssystem32sndvol32.exe
Coulden`t find C:Windowssystem32sndvol32.exe. control the
name and try agin
the second one are:
AutoIt error:
Line-1:
Error: Unable to execute the external program.
Coulden`t find the file.
do anybody have some solution on this problem for me????
Get two error windows when I drive to a alert point and it dosent work
the first on are:
C:Windowssystem32sndvol32.exe
Coulden`t find C:Windowssystem32sndvol32.exe. control the
name and try agin
the second one are:
AutoIt error:
Line-1:
Error: Unable to execute the external program.
Coulden`t find the file.
do anybody have some solution on this problem for me????
I had the same error when using v1.7 with Vista. 1.7 was written on an XP machine and MS modified the name of the volume player for Vista.
from C:\Windows\system32\sndvol32.exe
to C:\Windows\system32\sndvol.exe
The beta 1.8 should work on Vista with 2009 and 2006. I haven't had time to test for 2008 yet, nor do extensive tests yet. Give it a try and please tell me if you still get bugs.
I've replaced the beta file above with version 1.8.
The POI Scanner version 1.8 should work now with years 2006 to 2009 on both Vista and XP. I also programmed it for other OS versions (98, 2000 and ME), but can't test it since I don't have these versions of Windows.
The POI Scanner version 1.8 should work now with years 2006 to 2009 on both Vista and XP. I also programmed it for other OS versions (98, 2000 and ME), but can't test it since I don't have these versions of Windows.
Nice! A question: Does your new version of POI Scanner work with the new 2009-style pushpins, or users need to import the old-style pushpins to their Streets & Trips for POI Scanner to work?
The POI Scanner works with the four included circular push pins that are in the zip file. It recognizes the color pixels of these push pins.
If you're comfortable creating bmp images, custom push pins can be created by using pixels of the included push pins. I steered away for using the S&T push pins because I didn't want to have copyrights issues with anyone. This is the reason for using a plain circular push pin instead of the nice S&T push pins.
If you're comfortable creating bmp images, custom push pins can be created by using pixels of the included push pins. I steered away for using the S&T push pins because I didn't want to have copyrights issues with anyone. This is the reason for using a plain circular push pin instead of the nice S&T push pins.
toyfountain - with this latest release(v 1.8), is there a specific icon(pushpin) that can be used to simulate the gps "car symbol" or is the only way to test the program to activate the gps function and take it on the road ? thanks - hrp
For the easiest of use, you need to use one of the four circular images included in the download and import them as pushpins. The POI Scanner detects these four colors in the map.
You could customize your preferred car symbol. Just copy and paste a section of the color you want in your preferred car symbol from of the included images. I've done it for myself with a few of the old S&T pushpins, but I can't make them available for public download since they are copyrighted material. I would need permission from Microsoft to do this.
You could customize your preferred car symbol. Just copy and paste a section of the color you want in your preferred car symbol from of the included images. I've done it for myself with a few of the old S&T pushpins, but I can't make them available for public download since they are copyrighted material. I would need permission from Microsoft to do this.
For what i have seen so far version 1.8.0 of POIScanner is not compatible with S&T 2009 running XP operating system. On my system, it refuses to run correctly and is crashing at startup. I need more time to investigate this problem once i have some free spare time after releasing S&T Keys 2009 which is my top priority now...
Any other help is welcome
Any other help is welcome
Hi,
I posted this on the S&T keys thread:
Currently (for Europe) I'm running MapPoint 2009. I'm about to create an add-on similar to S&T/AR Keys. However it should be of specific help in case one doesn't have a keyboard (like I do when using the Asus R2H in the car.)
One of the harder parts will be a POI notification that I would like to write. At run time I want to download new POI coordinates for speed cams and put them as POI's in MapPoint. Then I want to have the programm check if a POI of that type is nearby. If so a sound should be played.
Have you got any idea on how to arrange something like this?
I'm using the MapPoint 2009 object model with Visual Basic .Net.
Thanks!
I'm really looking for ways to get this to work! As another part of the notification tool I would like to enable the user to click a button and send a speedcam notification to a website.
I posted this on the S&T keys thread:
Currently (for Europe) I'm running MapPoint 2009. I'm about to create an add-on similar to S&T/AR Keys. However it should be of specific help in case one doesn't have a keyboard (like I do when using the Asus R2H in the car.)
One of the harder parts will be a POI notification that I would like to write. At run time I want to download new POI coordinates for speed cams and put them as POI's in MapPoint. Then I want to have the programm check if a POI of that type is nearby. If so a sound should be played.
Have you got any idea on how to arrange something like this?
I'm using the MapPoint 2009 object model with Visual Basic .Net.
Thanks!
I'm really looking for ways to get this to work! As another part of the notification tool I would like to enable the user to click a button and send a speedcam notification to a website.
There is a good cleaning job to do with POI scanner and using it under S&T 2009.
I think this could be a 2009 project
I think this could be a 2009 project
Any chance of increasing the maximum 2Km range to say 10Km?
Has anyone tried POI Scanner with Streets & Trips 2010? If so, does it work? I'm too chicken to try it without someone telling me it isn't going to break everything.
Thanks!
Regards, Chris
Thanks!
Regards, Chris
Crazy Chris said:
You can give it a try. There is nothing it could break on your system and it installs nothing at all.
But i guess you would get some problems because i got some with S&T 2007 version. On my system, it sometime confused between map elements colors and special POI colors that it used, so this results in false alert some times. Also it refused to start correctly with S&T Keys for S&T 2009. I don't know if Toyfountain had a chance to work on it last year, but i didn't have time myself...
Quote:
Has anyone tried POI Scanner with Streets & Trips 2010? If so, does it work? I'm too chicken to try it without someone telling me it isn't going to break everything.
But i guess you would get some problems because i got some with S&T 2007 version. On my system, it sometime confused between map elements colors and special POI colors that it used, so this results in false alert some times. Also it refused to start correctly with S&T Keys for S&T 2009. I don't know if Toyfountain had a chance to work on it last year, but i didn't have time myself...
Downloaded POI Scanner MSST for my 2007 version of Microsoft Streets and Trips (V. 1.8.0.002)
Everything unzipped, was able to test the sounds, imported the 4 colored circles onto my map, but my gps icon does not even pick up any one of them. I tried different distances also. I took it for a ride and it just passed each color without detection.
What am I doing wrong?
Windows XP
Microsoft Streets and Trips 2007
Everything unzipped, was able to test the sounds, imported the 4 colored circles onto my map, but my gps icon does not even pick up any one of them. I tried different distances also. I took it for a ride and it just passed each color without detection.
What am I doing wrong?
Windows XP
Microsoft Streets and Trips 2007
Yes I tried on the trial version of Microsoft Streets and Trips 2010 running Windows 7. Doesn't work. Forgot what the error said, but it was some type of error.
Yep,
I think the app need a cleanup to make it usable again. I thought i can do it last year, but unfortunatly i underestimate the effot i had to put for S&T Keys (that need a major refresh every year). So i don't think i will do it in the near future. If Toyfountain (the original creator) want to do it, it is probably the best chance to make it work again in the near future...
I think the app need a cleanup to make it usable again. I thought i can do it last year, but unfortunatly i underestimate the effot i had to put for S&T Keys (that need a major refresh every year). So i don't think i will do it in the near future. If Toyfountain (the original creator) want to do it, it is probably the best chance to make it work again in the near future...
I'd hold out for Streets & Trips 2011, Mister Moonlight. Maybe Larry can get you an advance copy!
Terry
Terry
tcassidy said:
Yep good idea . It would help for S&T Keys also to prepare a version and make it available earlier than waiting for the final product release! A kind of Street and Trips pre-release could help on the timing schedule
Quote:
I'd hold out for Streets & Trips 2011, Mister Moonlight. Maybe Larry can get you an advance copy!