myLPFM v. 3.1 release (RadioDNS & other features)

Due to the delays getting FEMA approval for production access to IPAWS-OPEN, we have moved our EAS/alerting functionality originally scheduled for v3.1 to v3.2 and we have moved up the flagship v3.2 project (RadioDNS) to v3.1.

RadioDNS Support

RadioDNS allows compatible receivers to be able to tune in to a broadcast station's live stream once they leave the listening area.  RadioDNS also permits stations to have logos and basic station metadata such as station name, description and website links display on compatible consumer receivers. 

In order for a station to use RadioDNS, they must have RDS.  Stations with HD Radio can also take advantage of RadioDNS.  Several car brands are starting to implement RadioDNS.  The role myLPFM can play is a place where station logos can be uploaded and served as well as the serving the XML files and appropriate DNS entries necessary to activate the service.  For all myLPFM users, stations may set their basic metadata, upload logos and register with RadioDNS.  Client users with a historic minimum spend of $350 will also be able to specify their station's internet stream to support Service Following functions. 

Any LPFM station, regardless of past spend with REC can use this functionality to get their station name and logo on RadioDNS compatible connected car and other consumer devices.

A new magnifing glass icon has been added to the left menu as well as the main menu in order to access RadioDNS services on myLPFM. 

Some of the metadata will already be pre-filled based on their directory listing at  

Stations will need to prepare, outside of myLPFM, 5 image files of their station logo at specific dimensions.  Software such as Adobe Photoshop or other image making software will work to produce these JPEG or PNG files.

Once RadioDNS is set, the station does not have to maintain it unless they change their name, stream (clients), logos, call sign or FM frequency.

Channel Report

On channel searches, at the channel level, provide a link to a channel report which shows all co-channel, first-adjacent, second-adjacent and third-adjacent as well as intermediate frequency and Channel 6 TV facilities within specific distances along with the distance and bearing to the other facility, the §73.807 recommended distance for non-interference, the §73.807 or §73.825 required distances and the amount of clearance.  Availability: REC clients with a historical minimum spend of $350.

Advanced geometry functions

Functions to better handle geometry within myLPFM and the rest of the REC Universe.  For myLPFM, this will allow us to better determine contour overlap by taking the entire contour into consideration instead of just point to point as the current system works.  This will allow for some improvements in the Encroachment Report as well as allow us to better implement some of the planned features on our development roadmap.

HD Radio evaluation

Checks an LPFM site to determine which level of HD Radio the station can have and what the digital ERP will be.  Availability:REC clients with a historical minimum spend of $350.

Long move availability.

For proposed moves of over 11.2 km, indication of whether a move would have contour overlap pursuant to §73.870(a).  This would not include a map.  Availability: all LPFM stations.

RDS PI Code ifnormation

On the Station Information screen, myLPFM will show the station's Program Identification (PI) code that is to be used with a Radio Data Service (RDS) encoder.  Availability: all LPFM stations.

Sunday, November 6, 2022
Systems affected: 
myLPFM v3
RadioDNS Server
Issue type: