Skip to main content
Language
Methodology

How postcode pages are produced

Every PLZHub page is built from named data sources, explicit transforms, and a review layer. The methodology matters because postcode pages can look simple while the geography and municipality relationships underneath them are not.

Named sources

Core page data comes from Swiss public sources including swisstopo, ESTV, BFS, geo.admin.ch, and opendata.swiss.

Refresh cadence

The build pipeline checks freshness metadata before build and syncs when a data year or upstream source date changes.

Verification rule

PLZHub is for orientation. Official provider tools remain the authoritative place for tax, statistical, and legal confirmation.

Primary data sources

swisstopo provides the postcode and locality base, ESTV provides tax inputs and calculator references, and BFS provides population and demographic statistics. Additional map, warning, transit, and open-data context is requested from public services at runtime where useful.

Street names are utility context only. They are not treated as an authoritative address register, and they are not the main indexable content surface of the site.

How tax data is interpreted

PLZHub compares effective tax outcomes by household scenario, not just raw municipal multipliers. Where a precise municipality-level result is unavailable for a postcode split, the page may rely on a canton-level median estimate and marks that clearly.

Once the comparison turns into a financial decision, users should switch to the official ESTV calculator, especially when the postcode spans multiple municipalities or deductions materially change the outcome.

How demographic and locality splits are derived

Postcodes and municipalities do not line up perfectly. When one postcode covers more than one municipality, PLZHub uses the address-share information available in the source data to estimate the split and make the weighting visible.

That estimate is useful for orientation, but it should not be treated as a population register. Municipal or cantonal statistical publications remain authoritative.

Known limitations

Public datasets update on different schedules, so a page may combine source years that are close but not identical. Runtime sections such as weather or warning data can also change after the static page was generated.

  • A postcode is not the same thing as a municipality boundary
  • Some metrics are weighted estimates, not direct postcode counts
  • Live API sections can be temporarily unavailable or delayed
  • Official providers remain the source of record for binding decisions