I have a question, is GPS in the scanner the same as the zip code implementation In that it brings in too much even set at 0 miles. Could there be more control over the range when using both zip and GPS?
Whether you use a GPS, or manually enter your location by zip code, or actual latitude & longitude, there is no difference in the range for systems to monitor. Using a zero for range in your scanner, you'll still hear systems & channels that are in the range setting in the database. The range the scanner uses in determining which systems to monitor is the sum of the range you set (in the scanner) and the range of the system or site as listed in the database. Imagine a circle with a radius of, say, ten miles for a system. Now, imagine a circle with a radius of what you set in your scanner. If these two circles intersect, that system would be scanned. Even if you set the range in the scanner to zero, if your location is within the range radius for the system, it would be scanned. See this for a more complete description of how location & range works.I have a question, is GPS in the scanner the same as the zip code implementation In that it brings in too much even set at 0 miles. Could there be more control over the range when using both zip and GPS?
That's especially true for systems in the "nationwide" category.Some stuff in the database has huge ranges set and even thought it’s far away from you, it can overlap your range, even at 0.
I ALWAYS use "zero" I want to hear what's in front of me, not behind me..... I have asked UJE for exactly that, GPS is very precise (within a few meters) at its best. If anyone has an algorithm please shareWhether you use a GPS, or manually enter your location by zip code, or actual latitude & longitude, there is no difference in the range for systems to monitor. Using a zero for range in your scanner, you'll still hear systems & channels that are in the range setting in the database. The range the scanner uses in determining which systems to monitor is the sum of the range you set (in the scanner) and the range of the system or site as listed in the database. Imagine a circle with a radius of, say, ten miles for a system. Now, imagine a circle with a radius of what you set in your scanner. If these two circles intersect, that system would be scanned. Even if you set the range in the scanner to zero, if your location is within the range radius for the system, it would be scanned. See this for a more complete description of how location & range works.
Its easier to comprehend if just saying that a range set in the scanner will be added to a sites range. If a site has a 25 mile range and the scanner are set to 5 miles then that site will have a 30 mile range.Now, imagine a circle with a radius of what you set in your scanner. If these two circles intersect, that system would be scanned.
I've suggested a setting in the scanner for ranges that allows a selection of "Use DB/FL ranges" or "Use own range of XX miles" for sites as well as allowing both negative and positive offset values to its current scanner range setting to be added with a minimum for a site to not be lower than 5 miles or so.I ALWAYS use "zero" I want to hear what's in front of me, not behind me..... I have asked UJE for exactly that, GPS is very precise (within a few meters) at its best. If anyone has an algorithm please share.
GPS sets the location. period,full stop, that is ALL that it does. No difference if you use a zip code, set a lat/lon. etc.I have a question, is GPS in the scanner the same as the zip code implementation In that it brings in too much even set at 0 miles. Could there be more control over the range when using both zip and GPS?
While I agree in principle, this would be quite a clunky approach in terms of relational data. You have one true or false parameter that you are trying to apply to an entry: Encrypted or not encrypted. Rather than creating 25 new tags, this data should be stored in its own field. The Home Patrol Database (HPDB), as we all know, is created from the RR DB. The RR DB sports a column called "Mode" for both conventional and trunked entries. If the value of this field ends in "E", the channel is encrypted. It seems that the HPDB does not implement this field, but that can change. This would require adding a field in Sentinel under both conventional and trunked ("T-Freq" and "C-Freq" in *.HPD terms) channels, updating the sentinel UI to support these new fields, adding a setting along the lines of "ignore encrypted channels" with a scanner menu entry (via a firmware update) and a sentinel UI, and it would also necessitate updating whatever mechanism is used on their end to export the RR data and build the HPDB to look at the value of the mode field and set the encryption flag in the HPDB.If there was only a way to not scan those encrypted talk groups while GPS scanning by adding a few new Service Type categories like...Law Dispatch/Tac/Talk ENCRY....Fire Dispatch/Tac/Talk ENCRY. The database administrators would have to update those talk groups to reflect the new Service Types, and a new Sentinel and Firmware would have to be updated so each user could modify the preferred Service Types they'd like to monitor. Many systems, especially statewide systems have encrypted talk groups that the scanner will "skip" but does a momentary "pause" no matter the range setting and delays scanning and causes users to potentially miss the first part of conversations. Just a future suggestion...
The "Jon" internal GPS works within seconds...the GPS acquired GPS position in about 1-2 minutes....
Good guess, you can enable or disable the GPS through the settings menu.I'm just taking a guess here...
You probably can turn the GPS off in the 150 thru the menu when not using it...
The mod that Jon was doing I believe the GPS board was always powered using it or not... Hence the quick acquisition...