Methodology

How we calibrate budgets + stats

Every daily-budget number and FIFA-style stat card on MapSorted is derived from a small set of documented rules. This page explains those rules so you can decide how much to trust any given number — and where to push back if something looks off for a city you know well.

Who writes this & how

MapSorted is written and maintained by Anthony, its founder — one person, not a content farm. The work splits into three layers, and they don't carry the same weight of first-hand experience, so it's worth being clear about which is which:

Update cadence:guides carry a visible "Updated" date sourced from the same field that drives the sitemap, so it only moves when the content actually changed. A standing freshness review runs twice a month to keep budgets, prices, and that date honest.

Corrections:if a number or a claim looks wrong for a place you know well, that's genuinely useful — flag it and it gets looked at in the next pass. The whole point of documenting the rules below is so you can push back on any specific figure.

The three tiers

Every guide shows three daily totals: Backpacker (🎒), Mid-range (🧳), and Luxury (💎). The same labels cover four per-day categories in the cost calculator (stay, food, transit, activities), so you can mix and match — e.g. pay for a nicer room but eat where locals eat.

🎒 Backpacker — what it buys you

🧳 Mid-range — what it buys you

💎 Luxury — what it buys you

Daily-budget $/day numbers

Each destination has a hand-calibrated triple — e.g. Bangkok is { budget: 25, mid_range: 60, luxury: 180 }. These aren't pulled from a single API; they're editorial judgements cross-checked against:

The cost_index(a 1–100 number you'll see in some charts) is a separate abstract measure of overall cost of living. It usually tracks mid_range $/day closely, but diverges when a destination has unusual structure — e.g. Botswana's Okavango Delta sits at cost_index 90 but real mid-range $/day is $800 because of all-inclusive safari lodge pricing. In that case, trust the dollar number.

How the split is allocated

Inside each tier's daily total, we split spending across four buckets: stay / food / transit / activities. The base split is roughly 42 / 25 / 15 / 18, then shifts per destination:

That gives each destination a distinctive stack — a Paris day tilts toward stay, a Bangkok day toward food, a Banff day toward activities — rather than every city showing the same pie chart.

FIFA-style stat cards

Each destination page shows a stat card with up to 9 attributes on a 30–99 scale: safety, affordability, food, culture, nightlife, walkability, nature, connectivity, transit. These are not votes or survey scores — they're derived from the same underlying data that drives comparisons and badges.

Seasonal modifiers

Stat cards shift with the calendar. Each month, attributes like walkability, nature, culture, and affordability receive small modifiers (roughly ±3 to ±10 points) based on the destination's best months, estimated temperature, and seasonal patterns. During peak season, culture and food scores nudge upward (festivals, full restaurant scenes); in extreme heat or cold, walkability drops; off-season months get a small affordability bump.

The stat card shows these shifts with small up/down arrows next to each score, plus a season pill (Peak, Shoulder, or Off-Season) in the header. The Overall score always uses base values — seasonal arrows are informational context, not baked into the composite.

Type-aware stat cards

Not every destination is a city. For national parks, fjords, and wilderness regions (typed as "natural" or "region"), the stat card drops three attributes that don't apply — nightlife, walkability, and transit — showing 6 stats instead of 9. The subtitle changes from "9-stat city rating" to "6-stat nature rating" or "6-stat region rating." Islands show all 9 stats with an "island rating" label.

This means destinations like the Norwegian Fjords, Swiss Alps, Banff, or Patagonia show a cleaner card focused on what actually matters there: safety, affordability, food, culture, nature, and connectivity.

Affordability score

Affordability is derived from the destination's cost_index — an abstract 1–100 measure of overall cost of living, where 1 is cheapest and 100 is most expensive. The formula inverts the index: affordability = 115 − cost_index, clamped to the 30–99 range. So a cost_index of 20 (very cheap — Hanoi, Yogyakarta) yields an affordability score of 95, while a cost_index of 85 (very expensive — Maldives, Bora Bora) yields 30.

The cost_index usually tracks mid-range $/day closely, but they can diverge for destinations with unusual pricing structures — e.g. all-inclusive safari lodges where the daily rate is very high but the cost_index reflects the regional economy more broadly.

What these numbers aren't

Found a number that looks off?

Guide content, budget tiers, and stat scales get edited all the time. If a city you know well has a score that doesn't match reality, flag it and we'll recalibrate in the next pass.