Licenses missing from License Search

[Searay]

When running frequencies searches by state the database seems to be missing some when compared to the same frequency search done via FCC Gen menu. Example below shows searching FCC database for 456.8375 in South Carolina. The first image show the result from RR search, and the second shows the results from the FCC Gen Menu search. As you can see, the RR database shows 6 but the FCC shows 14. As an example, the license WQSV827 shows in the FCC search but not the RR search.

 

[GTR8000]

Searching 451.8375 (the repeater output) in SC returns WQSV827, so perhaps it has something to do with mobiles (MO8 in this case) being excluded from the search results. The question is whether that behavior is intended or inadvertent. Keep in mind that mobiles are not tied to a fixed location, which might explain the omission. Only Lindsay can provide some insight.

 

[ecps92]

Even the FCC actual inquiry does not have a location for the input (other than Radius around 1)

ULS License - Industrial/Business Pool, Trunked License - WQSV827 - Tropic Air Inc - Frequencies Summary

Nor does the RR FCC Copy

FCC Callsign WQSV827 (Tropic Air Inc)

FCC Callsign WQSV827 (Tropic Air Inc)

www.radioreference.com

Searching 451.8375 (the repeater output) in SC returns WQSV827, so perhaps it has something to do with mobiles (MO8 in this case) being excluded from the search results. The question is whether that behavior is intended or inadvertent. Keep in mind that mobiles are not tied to a fixed location, which might explain the omission. Only Lindsay can provide some insight.

 

[Searay]

Most of the time that is the way mobiles are listed: "2 - Mobile 32.0 km radius around a fixed location 1"

Is it possible to pick up those when doing a search? There are time when they might have more frequencies than just the input to a repeater pair that are tagged with that location. I am pretty sure the old database picked them up, I used the search on RR since it was so much easier to navigate then Gen Menu. If the search here wont pick up on those I will have to go back to FCC database, and I hope I don't have to . I will do some additional testing to verify that is the case here and I will post any additional findings. Hope there is a fix

Thanks,

Matt

 

[GTR8000]

Even the FCC actual inquiry does not have a location for the input (other than Radius around 1)

Nor does the RR FCC Copy

Which is typical...mobiles and control stations often do not have any location information except for "radius around" or "countywide" area of operation.

 

[ecps92]

Exactly

Which is typical...mobiles and control stations often do not have any location information except for "radius around" or "countywide" area of operation.

 

[Searay]

Which is typical...mobiles and control stations often do not have any location information except for "radius around" or "countywide" area of operation.

That is correct, but in the communications field quite often I find my self needing information on the simplex /input (MO-MO6 etc) frequencies more than the output pairs. (FB2/FB6) Unfortunately if the search does not pick up on those, that is a lot of licenses that will be skipped when doing a search.

 

[blantonl]

I can confirm that our queries are including location data in the query. I'm currently doing full joins on the location data vs optional left joins (meaning location data must exist). I'll look to see how we can possibly resolve this issue with . Stay tuned.

 

[Searay]

Can’t ask for anything more than that! Thanks Lindsay!

 

[blantonl]

I've rolled a proposed fix for this, this morning. Let me know how it is looking and working out.

 

[OpSec]

Keep in mind that mobiles are not tied to a fixed location, which might explain the omission.

Mobiles are usually licensed to a radius around a fixed location. Each FCC call sign can have up to 6 fixed locations, then associated FX1s and MO's. To me, the MO would be considered to be tied to a fixed location.

If an MO is not licensed around a fixed point, it can be licensed within a county or statewide...which makes geolocation more difficult, if not irrelevant.

When searching for inputs, start looking at the fixed locations on the license and look at the FX1s and MOs. If you find an FX1 and an MO that are the same, it's almost always the mobile input to a repeater - trunked or conventional. There are a lot of places that don't license control stations tho, so then it's an MO search only.

 

[GTR8000]

Mobiles are usually licensed to a radius around a fixed location. Each FCC call sign can have up to 6 fixed locations, then associated FX1s and MO's. To me, the MO would be considered to be tied to a fixed location.

If an MO is not licensed around a fixed point, it can be licensed within a county or statewide...which makes geolocation more difficult, if not irrelevant.

When searching for inputs, start looking at the fixed locations on the license and look at the FX1s and MOs. If you find an FX1 and an MO that are the same, it's almost always the mobile input to a repeater - trunked or conventional. There are a lot of places that don't license control stations tho, so then it's an MO search only.

Radius around a fixed location ≠ fixed location. At the end of the day, even if a mobile/input frequency is "tied to" one of those fixed locations, it still is not a fixed location in and of itself, which means database queries can return unexpected results. Countywide/statewide/nationwide are also not considered fixed locations for the purposes of the discussion in this thread. I'm painfully aware of how the ULS is structured and works, having personally maintained numerous public safety licenses over the years.

 

[Searay]

I've rolled a proposed fix for this, this morning. Let me know how it is looking and working out.

Just did a quick search and looks good so far. Will do more throughout the day and advise. Thank you Sir!