PlaygroundDocsBook a review
MapScale for branch and store networks

“Your nearest branch” is usually the wrong branch.

Straight-line distance picks the branch across the river. Meanwhile the address a customer typed at onboarding will not verify, and the same branch appears three times in the estate report.

What breaks

Networks have two location problems that are usually owned by different teams: customers cannot find the right site, and the business cannot agree on where its own sites are. Both come back to whether an address is a canonical record or a text field.

Nearest by distance is not nearest by road

A branch 900 m away across a canal, an expressway or a rail line can be twenty minutes further than one 3 km away with a direct road.

Free-text addresses cannot be verified

Onboarding and KYC need an address that resolves to one checkable place. Text that a human can read is not the same as a record a system can confirm.

One site, written three ways, is three sites

The same branch address entered differently in the CRM, the ledger and the facilities system reconciles as three locations — and every count built on top of them is wrong.

What it costs

Operations knows the volume and the review cost. The rejection rate is usually visible once someone looks for it.

applications or registrations per month × address rejection rate × cost of manual review or re-contact

Put your own numbers in the calculator

The endpoints you would use

GET/v1/geocode

Resolve a typed address to one canonical, storable record instead of keeping the free text.

GET/v1/reverse

Turn a captured coordinate back into a structured Thai address for the file.

POST/v1/matrix

Rank every branch by drive time from the customer, in one call.

GET/v1/static/{lonLatZoom}/{sizeFile}

A map image for the branch page, the appointment confirmation and the printed letter.

A request you can run

Canonicalise an address, then rank candidate branches by drive time rather than distance.

# Turn the applicant's typed address into one canonical, checkable record —
# the same address written three ways is three customers in your reporting.
curl -H "X-MapScale-Key: $MAPSCALE_API_KEY" \
  "https://api.mapscale.io/v1/geocode?q=อาคารสาทรสแควร์%20สาทร%20กรุงเทพ&lang=th&limit=1"

# Rank branches by drive time, not by straight-line distance. The nearest
# branch across a river or a motorway is not the nearest branch.
curl -X POST -H "X-MapScale-Key: $MAPSCALE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"sources":[[100.5290,13.7220]],"targets":[[100.5348,13.7466],[100.5601,13.7279],[100.4920,13.7180]],"profile":"driving"}' \
  "https://api.mapscale.io/v1/matrix"

What we can actually claim

Reverse geocoding returns the full administrative chain plus the attribution for each dataset that produced it, so a compliance file can record where the answer came from.

Bring us your data.

A 30-minute review against your own addresses — not a demo dataset. You will see the failure rate before you see a price.

Book a 30-min reviewRead the docs