Locating sites

To pin a site on the map, Client Mapper looks its address up with Microsoft Azure Maps and keeps the location it finds.

Only when a map needs it

A site is located the first time a map that shows it, or measures a distance to it, is opened, and again only if its address changes. Indexing, counting in the editor and refining never locate a site. So the first time a map is opened, the summary may show “0 of 143 located”, and pins appear as sites are located; the next time, they are all shown at once.

The on-site layers locate the sites of their tickets and visits the same way, when the layer first needs them.

Sites that cannot be located

Reason	What happens
The address cannot be found, or has nothing to look up	Listed under sites could not be located with its company and reason. Not tried again until the address changes in ConnectWise.
The look-up failed for a temporary reason	Tried again the next time the map is opened.

A daily allowance

Each company can have up to 10,000 sites located a day by Client Mapper. Beyond that, sites are counted as not yet located and are located on a later open. Sites already located cost nothing to show again.

Distances

A distance is measured in a straight line, from the centre of a postal code, or from the stored location of a client’s site, to each site’s stored location. A postal code is looked up once for your company and kept. A site placed only approximately is measured from where it was placed. A site not yet located is counted as not yet measured, never as inside or outside the distance.

Limits

Limit
Sites on one map	5,000. More, and the map shows its counts and asks you to narrow it.
Candidate sites for a distance	5,000 matching the other conditions.
A distance	1 to 250 whole miles.
Items in an on-site layer	1,000; scheduled visits the earliest first.