Coverage Map: configuration and operations

What Coverage Map solves

Coverage Map combines the ISP’s own network, national datasets, and configured third-party providers in one address check. Operators can compare available technologies and use the evidence during sales, activation, and service management.

A positive result supports qualification but does not replace the provider’s final technical and provisioning checks.

Recommended configuration order

1. Set the public name, logo, and access rules.
2. Load the private wired Netmap.
3. Register wireless base stations.
4. Configure only third-party APIs backed by a valid account.
5. Run a known internal address check.
6. Style and authorize the public widget.
7. Review the automatic customer-address report.

General settings and public visibility

General settings control the public name and logo, whether the private Netmap can be shared, and which ISP codes are allowed to use it. These controls are separate from module activation.

Use radio bridges for FWA allows saved base stations to contribute wireless availability when the line-of-sight calculation succeeds. Enable it only after coordinates and site heights have been checked.

Private Netmap: the wired network

The private Netmap describes coverage built or directly managed by the ISP. A record can identify one street number, a whole street, or an entire postal code. Its fields include town, street prefix, address, street number, postal code, technology, POP or cabinet, and advertised download/upload capacity.

The * wildcard broadens matching: in the street-number field it can cover the full street, while in the address field it can cover the postal code. Use it only when the infrastructure genuinely serves the entire declared area. An overly broad rule can show coverage for addresses that still require a different cabinet, route, or feasibility check.

Available labels include FTTH, FTTC VDSL2/EVDSL, FTTO, point-to-point fiber, wireless/FWA, HiperLAN, LTE, 4G/5G, and business GPON. Select the service that can actually be sold and provisioned, not the most attractive commercial label.

Importing the Netmap from CSV

For a large footprint, download the supplied template, prepare the CSV, upload it, and map each file column to the corresponding Netmap field. Check encoding, delimiter, headers, leading zeroes in postal codes, and the exact technology vocabulary before confirming.

Update keeps the existing inventory and adds or updates matching records. Replace removes the current Netmap and retains only the uploaded file. Use Replace only with a complete, backed-up, sample-verified export: a partial file would make every omitted area disappear from searches.

After either operation, test several precise addresses, wildcard matches, and addresses expected to return no private coverage. Do not publish the widget until those samples reproduce the real network plan.

Third-party coverage providers

The Third-party Netmap APIs tab can configure Pianeta Fibra with an enabled flag, provider token, and Base URL. Save the configuration and repeat a known-address search.

Keep tokens in protected fields and never expose them in public screenshots, tickets, or widget code.

Search and interpret results

Select the town and address from suggestions and enter the street number. Guided selection prevents incomplete or inconsistent place data from reaching providers.

Results are grouped by technology and may include several pieces of evidence. A real Rome test returned FTTH, VDSL2 and EVDSL FTTC, FTTO, point-to-point fiber, wireless, and LTE. Multiple cards do not mean that every option can be ordered from the same supplier; continue with the correct commercial and provisioning chain.

Automatic scan report

The automatic report lists customer addresses, technology availability, last check, new coverage, and linked services. Filters isolate locations, providers, dates, and invalid addresses. Recalculate refreshes one address.

An address flagged as unverifiable is excluded from scheduled refreshes until it is corrected. Normalize street, number, postal code, and town instead of repeatedly recalculating invalid text. The scheduled process refreshes the cache and can postpone checks when FTTH is not found.

Statistics and upgrade opportunities

The graphical summary covers analyzed addresses, addresses requiring correction, recent recalculations, FTTH/FTTC totals, and newly available FTTH. Clickable cards open the matching filtered list.

City rankings and provider distribution reflect the ISP’s own customer-address dataset, not the national market. Correct invalid addresses and review the last scan date before using the figures for a commercial campaign.

Saved radio points

Saved points represent base stations. Store a clear name, latitude, longitude, pole height, GHz frequency, and MHz channel width. Use for check transfers the site and its radio parameters into the feasibility page.

Points can be searched, edited, deleted, exported, and imported through CSV. Verify coordinate order and units before a bulk import.

Radio Feasibility

Point A normally represents the customer CPE and point B the tower. Coordinates use lat,lng and can be entered, selected on the map, or loaded from saved points.

The calculation evaluates terrain profile, line of sight, and Fresnel clearance. Green is favourable, orange indicates reduced margin or instability, and red indicates an infeasible path. Poor Fresnel clearance should be addressed through antenna height or a better site, not merely additional power. This preliminary calculation does not replace a survey, interference analysis, equipment limits, or regulatory checks.

Public widget: styling and installation

The Script to publish tab generates the code used to embed the checker in HTML or a CMS such as WordPress, Joomla, or Wix. Configure the button and text colors, input borders, labels, corner radius, and border style before copying the final code.

Use the preview to check legibility, spacing, labels, and the no-result state. Paste the code into a block that permits both HTML and scripts; a visual editor may strip it. After publishing, try a covered address, an uncovered address, and incomplete input on desktop and a narrow mobile viewport.

Authorized domains and widget security

The authorized-domain list prevents the script from being reused on unrelated sites. Enter the exact HTTPS origin, including the intended subdomain. Staging, local testing, a new domain, or a change between www and the bare domain may require a separate entry.

Protection does not depend on hiding browser code, which visitors can inspect. It depends on server-side origin validation and application controls. Never place Pianeta Fibra or other provider tokens in the published script.

Public messages for each technology

Each technology can have its own HTML message, allowing the result to explain availability, benefits, and the next commercial step. A separate message handles addresses where no coverage is found. Leaving a technology message empty hides that technology from public results.

Write specific, verifiable copy. State that availability remains subject to final technical checks, link to the appropriate contact or quotation path, and avoid promising speeds, installation dates, or provider acceptance that the result does not prove. Italian and English pages should communicate the same conditions.

Common problems

• No result: confirm guided town and address selection, then check enabled sources, tokens, and endpoints.
• Address cannot be verified: correct street prefix, name, number, postal code, and town before recalculating.
• Private network missing: inspect records, wildcard scope, postal code, technology, and the last CSV import mode.
• Unexpected FWA result: verify base-station coordinates, mast heights, channel parameters, and the radio-bridge option.
• Widget does not load: check the exact authorized origin and whether the CMS permits the generated script.
• Old statistics: inspect the last scan date, scheduled refresh, invalid-address exclusions, and provider availability.

Operational checklist

• Define public identity and visibility rules
• Load the private Netmap and verify samples
• Review every wildcard for excessive scope
• Register base stations with correct coordinates and units
• Enable only providers backed by valid credentials
• Keep provider tokens out of public code
• Test known positive and negative addresses
• Correct invalid customer addresses before rescanning
• Review scan freshness and newly available coverage
• Treat radio feasibility as a preliminary assessment
• Authorize only required web origins
• Test the checker on desktop and mobile
• Use results as qualification evidence, never as an activation guarantee