Start with the decision
A map score is only useful if it answers a concrete question. A retail expansion team may ask where reachable demand is high and direct competition is thin. A healthcare planner may care more about underserved population and travel friction. The same geography can be attractive for one objective and weak for another.
Before comparing colors on a map, write down the decision the score is meant to support. Horizon Mapper works best when the model objective, category filters, travel mode, and time window match that decision.
Read the components, not only the rank
A high-scoring area can happen for several reasons: dense reachable demand, low nearby supply, strong accessibility, or a favorable mix of all three. Those are different stories. One site may be a clean gap; another may be a dense cluster where demand is high but competitive pressure is also high.
The useful question is not simply whether a score is high. It is whether the evidence explains the score in a way that matches the strategy.
- Demand signal: enough reachable population or target audience to matter.
- Competition signal: existing supply is sparse, distant, overloaded, or strategically useful as a cluster.
- Friction signal: travel time and accessibility do not make the area harder to serve than the score implies.
- Confidence signal: the result is not driven by sparse POI coverage, small polygons, or unstable edges.
Check the geography around the winner
The top cell or polygon is rarely the whole answer. H3 grids, isochrones, and administrative boundaries all have edges. A candidate can look strong because a boundary cuts through a dense neighborhood, or weak because the relevant demand sits just outside the chosen catchment.
Use the score as a shortlist, then inspect the surrounding cells and a slightly wider travel-time band. A robust opportunity should remain plausible when you nudge the origin, adjust the travel time, or compare adjacent hexes.
Make uncertainty visible
Open data is powerful, but it is uneven. POI density varies by country and category. Population rasters have native resolution limits. Routing profiles use typical speeds rather than live traffic. Those limits do not make the analysis useless; they tell you where to slow down and ask for corroborating evidence.
Good opportunity mapping keeps caveats close to the recommendation. A medium score with high confidence may be a better planning input than a high score built on thin coverage.
Turn the score into a field question
The final step is practical: convert the map result into a question someone can validate. For example, 'Is this catchment underserved because supply is actually absent, or because the POI data missed local operators?' That question can be checked with field visits, local business registries, customer interviews, or operational data.
The score helps decide where to look first. The decision should still be defended with the evidence behind it.
