Actually, it's a really good idea to at least verify that the location info in the RR database is accurate for the systems you want to monitor while mobile. The RR database is often horribly inaccurate, to the point of being useless in some cases. The RR location data depends on user input, so it all depends on how much effort has been put into defining location data for a given agency. Sometimes it's very good, but you CAN NOT depend on it. It's one reason I'm not a big fan of the Home Patrol style of scanning the full database using a zip code or coordinates. That method is only as accurate as the database. One thing you can do, but it is time consuming, is to use Freescan as a tool to evaluate the location data for the systems you want to monitor while mobile. Freescan has a great mapping tool that shows the location circle defined in the RR database, and updates the circle if you change the center coordinates, or the range. Once you've got it dialed the way you want, you can enter your revised location info in your Favorites List in Sentinel. It sucks that Sentinel does not include a mapping tool like this, but at least it is available in Freescan. See this thread for more info on this topic, including some map images:
http://forums.radioreference.com/uniden-tech-support/325613-sentinel-location-setting.html
.
The Freescan coordinates mapping tool is very good. Using it, I find that the systems in RR are frequently understated in terms of their range, or favor one side of the true range and not the full range.
Some of the statewide ranges in RR are for the whole state, when in reality the usage of the frequency is just in a corner of the state.
These things make scanning the main database with gps inefficient (in some cases its scanning stuff you will never hear based on your location) or less optimal (the coordinates and range in RR won't activate receivable systems because of understated/mis-stated database coordinates or range.
After moving all the stuff I listen to in a 3 state area to several favorites lists, I modified their coordinates and ranges based on known reception ranges, and using Freescan to check and adjust the coordinates. Generally the coordinates are not bad, but I needed to modify ranges to activate in known receivable areas.
If I am mobile outside this 3 state range where I am not familiar with the systems, I go ahead and use the main database, but not where I spend most of my time.
Sent from my LG-V410 using Tapatalk