The purpose of the VisualLMR website is to integrate GoogleMaps with basic, well known, tools that have been used to assure compliance with the existing FCC rules that govern the use of Land/Mobile spectrum.

Most of the credit for the visual aspects you see in the VisualLMR tools goes to Google ( GoogleMaps ) – all we do is tell GoogleMaps what to display and it does all the heavy lifting. If you know how to navigate in GoogleMaps, the scrolling, panning, zooming semantics should seem very familiar when using the ViusalLMR tools. If you’re not familiar, take a look at a GoogleMap Tutorial.

For those that are using the VisualCoverage tool, you most certainly want to check out the capabilities of GoogleEarth –- you can fly over a transmitter's coverage area and visualize, in 3D, the relative signal strength performance in the surrounding terrain -- Very Cool. Thanks again to the folks at GoogleMaps. See a video demo of a VisualCoverage 3D GoogleEarth fly-over on: YouTube.

The user interface is predominantly forms based; you fill in the required parameter(s) for a report, submit the form, and the result is returned. If you're new to VisualLMR, you can try some example links have pre-populated parameters required by their respective forms -- after you click on one of the links below, all you need to do is hit the Submit Study button in the form.

  • VisualShortSpacing
  • VisualContour
  • VisualSpectrumFinder
  • VisualCoverage
  • VisualCallSign
  • Many of the VisualTools allow for the specification of latitude and longitude in two basic forms: DegreesDecimal and DMSD. If the field DegreesDecimal is provided, the specification for DMSD, if any, is ignored. If DegreesDecimal is not specified, then DMSD is used. The assumed direction for DMSD is North for latitude and West for longitude. One of the two is required: DegreesDecimal or DMSD.

    There are three types of response diagnostics that are returned in addition to the germane information provided by the reports. They are Advisory ( general information ), Warnings ( some parameters were deduced to be in error or out-of-acceptable tolerance ), and Errors ( the underlying subsystems could not process a report request because of missing parameters, internal error(s), database faults, too many security faults, too much traffic, etc. )

    Browser Issues

  • Not all browsers are configured the same -- some may be configured not to allow downloads, uploads, cookies, javascript, java, etc.
  • Formatting and display layouts vary across browsers.
  • Browsers built on WebKit technology will work fine.
  • Microsoft's IE platform is, at best, problematic; even the most current versions of IE are a mess.
  • Google's Chrome browser works best with this website.

  • Map