(updated 9/19) myLPFM September 2013 release

REC is doing a "rolling" release of myLPFM, which means that we are developing the changes live.  This means that there will be times when you may see some strange results.  If you see anything real strange, please feel free to let us know about it. 

This will likely be the last major release of myLPFM prior to the October 15 filing window that impacts searching (myLPFM Search).   Overall, myLPFM is a complete platform of LPFM support applications that tracks pending applications and provide LPFM licensees with ongoing assistance.  This functionality is already built.  A free myLPFM username and password is required to access these functions.

For myLPFM/Search, here are the release notes for the September rolling release: 

  • Fixed a bug that was placing some translators in the wrong "sub-class'.  This was causing some translators to be overprotected and others to be underprotected. 
  • NAD27 and NAD83 cross compatability.  myLPFM will make a best effort to convert between NAD27 and NAD83 (similar functionality is also on the Broadcast Query).    See disclaimer about NAD conversions on REC tools.
  • Channel searches will be done using NAD27 and rendering of maps and other measurements will be done used NAD83.
  • New Tower -> By Coordiantes: Geographic coordinates can now be added using either as NAD27 or NAD83. 
  • New Tower -> By Coordinates: Now accepts seconds to the hundreths level.
  • New Tower -> By Coordinates: Fixed a bug that did not allow seconds entries above 59.00
  • Existing Tower: In addition to an ASRN, FM callsign or TV callsign, a Facility ID for a TV or FM station can now be entered in the field search by tower.
  • The method of entering tower height has completely changed.  Going forward, click on the [Site Info] button, answer a question about the type of antenna arrangement and then follow the prompts for the tower height and radiation center.  HAAT will be calculated and updated with a screen refresh.  (A future release later this mornth is going to streamline this a little better than it is right now).
  • Other buttons next to Site Info will be enabled as those features are activated in this rolling release.  Those three buttons are dependant on entering the site info.
  • Logged-in users will be able to save the site details when they save the location. 
  • It is strongly advised that logged-in users using a saved location created prior to this change should set their antenna height using the new method (including saving to determine HAAT) and resave the location.
  • Reject Report & Nearby FM Stations:  Clicking on the frequency will bring up a Channel Report for that channel, even if LPFM is not available.
  • Waivers: Now using free-space calculations instead of a table to determine the size of overlap zones.  Service contour measurements are now done in 0.1dBu increments to better represent the estimated overlap zone size.
  • Made several changes to improve the overall channel search speed.
  • Domestic second adjacent channel spacing no longer allows for "rounding".  Normally in distance spacing rules, the FCC allows stations to short space up to 0.5 km as it is rounded to the nearest km.  Since second adjacent channel waivers also involve contour overlap, we need to assure that the interference contour of the LPFM is fully outside the second adjacent's service contour.
  • New nearby AM station functionality designed to be complant with the newly released Part 1  Subpart AA.  Once the Site Details are entered (tower height, etc.) , a new [AM Details] button will show the AM stations within 5km.  The system will measure the distance from the LPFM site to the AM station as well as measure the LPFM tower in electrical degrees in relation to the AM station. 
  • When site information is entered, myLPFM will enable the [Environmental] button that will be able to access a Radio Frequency Interference worksheet which will detail whether an Environmental Assessment will need to be filed.  Most LPFM installations will not need this but it's always good to check.
  • REC TOWAIR has been implemented.  This is the REC version of the FCC's TOWAIR search tool.  TOWAIR is used to determine whether FAA notification and FCC antenna structure registration is required by looking at the height of the antenna and the distance from the nearest runway in respect to a slope.  Results for TOWAIR have not been verified yet (as of 9/19), please use this tool as a reference only but still double check with the FCC's TOWAIR tool.
  • Vendor specific tower data is now supported by myLPFM.  Currently we have added American Tower and SBA Communications tower data to our database.  Because of this change, the tower database now includes information about towers that do not require an FCC antenna structure registration.
  • Wide Area Tower Search map now includes non-ASRN towers from American Tower and SBA.  For most American Tower and SBA assets, additional information is displayed such as the vendor's internal identifier for the tower, the vendor's name for the tower and salesperson information.
  • Search by tower now includes the ability to enter in an American Tower asset ID or a SBA Communications Tower ID code.

Changes still planned:

  • Determination of county and Arbitron metropolitan market where proposed LPFM site is located.
  • Local presence map based on which media market site is located in.
  • Estimated population based on actual service contour instead of just a 5.6 km radius.
  • Simplification of the tower type selection when [Site Details] is clicked (those that have already been saved will be migrated to the new category).

There were also some low level enhancements that did not go into this release,.  These will go into another release, likely before the window.   Please report any bugs.

These changes only went into the desktop version of the myLPFM website.  They will be added to the mobile version at a later date.