It's still nasty as hell. I've been doing searches for locating DMR licenses in BC and Alberta over the weekend and even after the "improvements" that kept it down all Saturday, it's still ugly.
Not only is the search field case-sensitive but it breaks on single quotes ("Vancouver Int'l" fails but "Vancouver Int" will get you the results including "Vancouver Int'l Airport Authority").
Little Bobby Tables, anyone?
I don't know if this is a Chrome thing or if it works differently in IE, but search result pages that have more than one page (10 results) very briefly show the search criteria menu and then blank/hide it, leaving a ton of whitespace below the results instead. I figured out that if you hit Esc to stop loading the page when you see a blue border poking out from under the search results, you can get (some of, depending on how fast you are vs your browser's load time) the criteria to stay on screen. Included on that criteria page is an option to download your results via CSV, which prevents you from having to copy-and-paste 10 results at a time and then hit Next Page and repeat x up to 99 pages.
Frequencies with more than 3 significant digits past the decimal are still rounded up or down in search results, which is annoying as hell. The biggest frustration here is
it isn't consistent. 466.6375 might be rounded up to 466.638, but 451.2375 is rounded to 451.237. And there's a bunch of freqs in BC that go out to 6 decimal places, so 412.884375 for example is returned as 412.884.
Search results are limited to 1000 rows returned, unless you decide to filter out some unwanted returns by asking for "Land Mobile" results only... now you're limited to 500 rows. WTF?
Lat and long are displayed in (d)dd:mm:ss format which is tolerable (except that lat and long are separated in the table that's returned by "Location", since it comes alphabetically before longitude) - unless you paste into an Excel workbook or save to CSV and load into Excel, at which point Excel interprets them as
times ((h)hh:mm:ss)! Okay, I know that one isn't
entirely IC's fault, but still, ugh.
The other gripe I have about search returns is that you get two returns for every frequency you're looking for. The type is designated as "TX_RES : Simplex", "TX_RES : Duplex", or the same two repeated for "RX". So if you're looking for a large amount of search results, you'll essentially get twice as much data as you need (or be limited to returning half as much as you want, since you're limited to 1000 rows). For example for a UHF repeater and the authorization for a mobile (or handheld) to talk to it, you get four rows - "TX_RES : Duplex" with ITU class FX for the repeater site's "output" frequency, "RX_RES : Duplex" for the repeater's "input" freq; and "TX_RES : Duplex" with ITU class ML for the repeater's input freq as permission for a mobile to use it, and "RX_RES : Duplex" for the repeater's output freq as permission for mobile.
Having said all that, the virtual license documents are kind of improved.
Though it's amusing to see DMR and NXDN licenses with restrictions stating "CODED SQUELCH AND/OR PRIVATE-LINE IS MANDATORY ON THIS SHARED FREQUENCY".
:roll:
