LPFM Channel Search Tool - Release Notes for FCC 03/2012 Changes

2012.08.15 (Still on build 2012.06.03)
DEPRECIATION NOTICE: REC Networks has announced today that the LPFM Channel Search Tool will be depreciated and will be replaced by REC's new product suite, myLPFM (myLPFM Search, myLPFM Sites, myLPFM Status, myLPFM Station and myLPFM Application).  myLPFM will include many features in the current LPFM Channel Search Tool and will introduce other additional features.  Only bug fixes and minor enhancements will be supported in the LPFM Channel Search Tool.  All major functionality including anything that is changed as a result of the next FCC Report and Order on LPFM will be placed into myLPFM Search.  The current tool will be discontinued at a time after the Report and Order is released and when myLPFM Search. 
2012.06.03
Bug fix: Translators on STAs in the database without a service class were being substanually overprotected resulting in false blocked channels.  Translators without a service class are now ignored similar to the functionality in web Channel Report and RECPRO.
2012.05.30
Fixed a bug where some types of Channel 6 TV stations were not being properly excluded in in Channel Search and not appearing in Channel Report. Also fixed a bug that impacted the available to navigate to other screens for proposed sites in Puerto Rico.
2012.05.29 (Still on build 2012.05.08)
Updated the Google Maps tool that generates the service contour/coverage maps for proposed LPFM facilities to show 9.5km for the Brown LP250 proposal. Other functionality such as ERP and second adjacent channel overlaps are not supported by the Tool for the Brown LP250 class.
2012.05.08
Added the Brown Broadcasting LP250 proposal into the tool. They are proposing LP250 at 52m HAAT with a service contour of 9.470 km. Most functionality is supported. Some functionality that requires major code changes such as maps and HAAT are not supported on the Brown 250 service. Our adding of this class is strictly for the purpose of evaluation by the public and REC and does not constitute an REC endorsement of this proposal.
2012.05.02
If any portion of the 60dBu contour of the proposed site is on tribal land, the LPFM Tool will now display the population within the tribal land in addition to the overall population as well as the percentage of the overall population that is in tribal census blocks. This functionality is to support REC comments regarding cross-ownership and multiple ownership of LPFM stations by Native Nations. (Currently in the PC version, Mobile will be added later.)
2012.05.01
Backend census block data has been updated for 2010 Census data. Census blocks are the most precise measurement of population within an area that the US Census Bureau can provide.
The LPFM Tool will now include an estimate of population within the service contour of the proposed LPFM station. For second-adjacent waiver channels, the tool will now give the estimated population within the overlap zone.
DISCLAIMER: Just because the Tool returns a result of zero does not automatically entitle this location to a second adjacent waiver. It just states that there are no centroids for any census blocks within the overlap zone. Based on the outcome of the proposed rulemaking, the FCC may also look at commercial locations and nearby roads in order to determine population for interference. As always, if you are in a potential second adjacent waiver situation, please retain the services of a qualified consulting engineer.
2012.04.17
Added a short URL system. When a search is done in the PC Tool, it will display a short URL on our lpfm.ws domain. This URL can be copied and pasted to bring up the LPFM search at that location with the parameters that you used (station class, No IFs, notch, etc.). Keep in mind, it remembers the location and parameters, not the results. REC databases update over the weekend and if there is any other facility activity that may cause the channel availability to change, you will see it. You can use these short URLs to copy and paste into e-mails instead of using the very long URL in the index bar.
Also, if you need to communicate with REC regarding an issue with the Tool or questions about your search results, please copy and paste the short URL into your e-mail.
2012.04.12
Added link on PC version that will provide a link to the FCC LPFM Search Tool at the same location. This will allow users to compare results. REC is written an explanation of why results may be different in the FCC Tool than in the REC Tool.
2012.04.11
Fixed two bugs relating to second adjacent waiver. (1) Tool was including foreign stations at center search and expanded search locations as eligible for waivers. (2) Tool was not properly removing third adjacent channel short spacing from the second adjacent available channel list (this will happen mainly when the third adjacent station is foreign).
We also fixed a tables issue regarding stations located in the British Virgin Islands. For Virgin Islands and Puerto Rico stations, there is no codified protection parameters between US and BVI stations however the FCC expects applicants to protect BVI stations and will report allotments to the ITU to assure proper spacing. The FCC database does contain many of the BVI stations. As a courtesy only, REC Tools are designed to apply the Puerto Rico/Virgin Islands spacing towards BVI stations even though they are not codified in the rules.
2012.04.04
Background changes to the LPFM Tool source code by making different functions of the code into modules. This allows us to use much of the same code across different platforms (PC, mobile, etc.) This update had no changes to the user experience.
2012.04.03
Replaced LP-FLEX support for a concept LP-50 (50 watts @ 30m HAAT).
2012.04.01
Entry screen now has a new optional entry for tower height. If you know what your tower height (above ground) is, enter the height here in meters (I am interested in feedback if we should change this to feet and then do a metric conversion in the program). Based on that entry and the elevation data installed in 2012.03.31b, we will be able to estimate a station's radiation center above mean sea level (RCAMSL). Tool now determines Height Above Average Terrain (HAAT). Using the RCAMSL information, the tool will display a proposed station's HAAT. It will also show based on the HAAT, what the maximum effective radiated power (ERP) is for an LPFM at that station class. If you do not enter a tower height, this section will not display. This function will manually adjust locations within 125km of Mexico that have an ERP over 50 watts to the 50 watt level and display a message indicating the adjustment. This function will also advise that LPFM is not available if HAAT is over 450m for LP-100 or 100m for LP-10.
2012.03.31b
Added new Google Elevation capability. Will be used for future HAAT support. For now, it will give you the elevation of your site in meters.
2012.03.31a
Changed the resolution in the Expanded Search from 30 seconds to one minute by one minute. This now gives you a high level view of 120 other areas up to about 12 km away from the original search location. Now with LP-250 on the horizon, we need a wider search area. This change has also resolved a long running (but not known until now) issue with the tool. We have discovered that the the location that was actually being searched and was up to 1 minute to 1 minute offset from the area input and shown on the maps. This bug may have been in there since LPFM Search has been doing the expanded search function. This has been fixed and tested. The geographic location of the center location now matches that entered into the tool. This change/fix has been put into the PC tool and will eventually go into the Mobile tool.
We have also resolved another bug from the release of 2012.03.28a where channel reports were not showing all off the channels. This has been fixed in both the PC and Mobile versions.
2012.03.28a
We have decided to take a different approach on the translator interference zone. The Channel Search results will now show these channels with a warning message in red to advise that if you use this channel, you will have to make a showing that interference to the translator's input will not take place. Clicking on the Channel Report will show the impacted facility (with a yellow indicator instead of the traditional red or green).
2012.03.26
The FCC's proposed translator input protection rule has been implemented. A newer CDBS table has some really good information on satellite/microwave fed translators vs. those fed directly. We are using that table and if the information is not there, we will assume the translator is getting their feed directly if the translator is located within the 40 dBu (50, 10) interference contour of the primary station. If the translator receives it's input signal directly, the proposed location is within 2km of a translator, the Channel Search will block the channels that are third adjacent to the input channel of the translator. Between 2 & 10km, the channel will only be blocked if your location is bearing -30 degrees to +30 degrees azimuth of the bearing between the translator and the primary station. In other words, the translator has a directional antenna to receive the signal of the primary station, this 30/30 rule assures that an LPFM transmitter is not in the path between the primary station and the translator. So let's say a translator is receiving a signal from 98.5 and the proposed LPFM is in the interference zone, the LPFM tool will exclude 97.9 and 99.1 as available channels. The Channel Report will display these excluded channels, but only if your target channel is third adjacent to the input channel. The Reject Report will also show when a channel has been excluded due to being in a Translator Interference Zone.
Currently, we have a checkbox on the entry screen that allows you to toggle IF protection. This has been a long time REC action item and now the FCC is considering it for stations under 100 watts. When the entry screen comes up, the tool defaults to LP-100 with IF disabled. If you change the power on the menu page to 250 watts, it will automatically uncheck that box. This is only a temporary measure and if the FCC approves the elimination of IF on LP-100, that box will go away and the tables will be updated to reflect the codified rules.
Reject Report will now show channels that are potential second adjacent channel waiver with a yellow background.
There have been some changes in the UI to streamline items and even out both sides of a result screen. The QR code has been moved to the top of the page (please note, the mobile LPFM tool does not have any of these changes yet). The population count box has been removed at this time due to slow system response.
FMQ Broadcast Query has a new release that came out today. There have been some minor changes. Translator primary stations are now shown in the application detail section and also include information on the type of delivery of the primary station and if the translator is daisy chained, which translator it is feeding off of.
This release finishes the mandatory updates we had scheduled to prepare the LPFM Tool for the next rulemaking and eventually for the next LPFM filing window. We may go in and clean up the code and if we think of anything that can go in or get changed, we will do it at that time.
Your comments and suggestions are always welcome.
2012.03.24b
Radio Reading Service support has been added. Under the LCRA, the FCC is proposing that stations that have radio reading services for the blind are still entitled to third-adjacent channel protections. The REC LPFM Channel Search Tool will place a second adjacent channel distance on a third adjacent channel if it is one of the 200 identified facilities with these services. A message in the Channel Report comments will acknowledge the facility having a radio reading service.
We have started the translator input by designing a backend process that runs in the weekly update that identifies the primary station for each translator and then calculates the bearing from the translator to the primary station. Under the FCC's proposed rule, LPFM applications within 2 km of a translator who receives a primary station on the LPFM's third adjacent channel protection will be dismissed unless a showing is made that no interference to the translator being able to receive the primary station will take place. Not every translator is fed over the air, we are proposing that only translators who's primary station's 40dBu (50,10) contour covers the translator be considered as a translator subject to concern. The FCC also wants to extend the interference zone to 10km if the LPFM station is located bearing +/- 30 degrees from the bearing from the translator to primary station. We will get into this more later.
Development will resume next Tuesday.

2012.03.24a
Expanded the grids functionality to include protected channel/points within the "spectrum available" markets. The CHANPOINTS tool has also been updated to support the FCC decision on how translators protect LPFM channel/points within the SA markets.
Implemented the FCC's "Top-50 market preclusion" guidelines. If a translator located outside the 31x31 grid is blocking the only potential LPFM channel at a particular site, the translator is presumed dismissed. Top-50 precluded channels will appear in the Channel Search and Channel Results with messages similar to grid channels but with preclusion specific messaging. NOTE: There are only 8 translators in the entire nation that fall under this guideline. To see one, try running a search here.
The "Old Rules" LPFM Channel Search Tool has been decommissioned. This tool has not been supported since January, 2011.
Tables for third adjacent channels have been updated and now searches in the tools now use the traditional L1 for LP-100 and L2 for LP-10. We are assuming that the FCC will use L3 for LP-250.
LP-250 distance separations have been adjsted to match those proposed by the FCC in the NPRM (including a couple of transposed numbers in the FCC's document). TV, LPTV and REC's proposed LPTV spacing now supports LP-250. Mexico border zone message has been reworded to advise that LP-250 stations will likely not be available within the Mexican strip area (125km to the border). Based on the FCC's proposal for placement of LP-250 stations, a message will now trigger that indicates that a location for a LP-250 station is too close to the center city point of a Top-100 market. NOTE: IF YOU USE LP-250 SEARCHING, YOU *MUST* UNCHECK THE I.F. BOX ON THE ENTRY SCREEN. LP-250 would not be exempt from IF protections. We will be putting in something to automatically switch that when we work on IF later in development.
Header of results pages now offers the ability to toggle between LP-10, LP-FLEX, LP-100 and LP-250.
Other minor adjustments to try to speed up searches.
2012.03.23a
Full implementation of grid support. All market data has been loaded. Minor editorial corrections to address entry page and grid area result messages. Arbitron Metro Rankings have been updated to reflect the recent FCC Report and Order.
2012.03.22a
Completion of grid support. A backend process will run with the weekly update and will flag each translator located in a Spectrum Limited market that is short spaced to the channel/points inside the grid. In the Channel Search, channels that are made available due to these translators will result in a message in blue: "Grid translators presumed dismissed." Clicking on the channel report for that channel will show the translators that are impacted with a similar message in blue. Please note, that these translators are "presumed" dismissed and there is a process where the applicant can make certain showings to save their translators. They can also file amendments to move them away from channels and locations that prevent LPFM opportunities. Also keep in mind, the LPFM Tool does not take into consideration the nationwide and per-market application caps as these methods will dismiss more translators and make more potential LPFM opportunities.
Currently, the Top 50 markets have been loaded and we are definitely seeing some new channels open up. The remaining markets will be loaded on Friday 3/23.
New separate web app that displays our prediction of what locations and channels the FCC will be declaring as LPFM channel/points. Check out http://cdbs.recnet.net:8080/chanpoints.php (As of 1:50AM EDT 3/23/12, the data is still loading up.. most markets are already available. It should finish loading by sunrise.)
The Google map that appears on the Channel Search result now shows a placemark at the proposed LPFM site.
2012.03.21c
If the location falls under more than one grid area, a Census Block search will be performed to determine the county and then which Arbitron Metro market the location is located.
2012.03.21b
Major clean-up removing obsolete projects from the tool including: RM-11099 (New Jersey Broadcasters Assoc. proposed LPFM separations), Distant Translator, "2x70" translator handling, All-translator exclusion, GTI translator exclusion, Ungranted translator exclusion and 10-cap.
Minor update to UI language related to second adjacent channel waivers.
Corrected Mexican restricted zone notification to trigger at 125km instead of 150km.
Updated city search functionality to look at both the Gazetteer (existing functionality) and the ZIP Code file. This is similar to the functionality in the city search in Broadcast Query (FMQ).
2012.03.21a
First phase of grids installed ~ When page is loading, the tool will determine if the location is in one of the FCC's designated Metro grids and if only within one grid, will display the market name, rank and availability. This will display on the search result above the map. If the location falls under multiple grids, it will display a multiple grid message and suggest manual determination of market grid location. We will address this issue in a future release. This functionality is going to be the springboard for future search capability to exclude market in-grid translators.
Clean-up on main menu. Removed the GTI metro market drop down as this will be replaced by grid driven functionality mentioned above. IF exclusion is (for now) turned on. We have an issue that 100 watt LP-100 stations (not 99 watt) will still be required to protect IF, this is an issue that we will be bringing up in comments. We will eventually move IF protections to the tables that hold the minimum distances for each station class. Also removed was the "2x70" switch as the FCC has made their determination of translator processing and "2x70" is now off the table at REC.