Territorial Disputes & Location Records

1. The Mechanical Problem

Location services on mobile devices occasionally return a detailed local address without specifying a country or region. Ten positions were tested across three hardware devices and three iOS versions, with reported horizontal accuracies from 2.8 to 169 metres. These were not poor positioning fixes.

In eight cases the geocoder returned a locality — a village or city name — and left the country and region fields empty. In two, at the Old City of Jerusalem and at Bir Tawil, no country, region, or locality was returned at all.

We do not know why these fields are empty. The location data was present; the administrative container was omitted.

2. How Domicile365 Resolves Unassigned Coordinates

When an incoming location payload contains precise coordinates but lacks a country or regional designation, Domicile365 does not rely on operating system geocoders to supply the missing label. Instead, the ingestion engine evaluates raw latitude and longitude coordinates directly against spatial boundary datasets to attribute the corresponding jurisdiction.

This spatial resolution mechanism ensures complete record continuity across every logged day. Rather than making assumptions or leaving gaps when an OS geocoder omits a country name, the system records every valid coordinate fix and assigns it to a geographic jurisdiction based on spatial geometry. This design maintains an unbroken audit trail for subscribers while framing the platform's role strictly as an objective recorder of location data rather than an arbiter of geographic or political status.

3. Data Sources & Spatial Resolution

To populate administrative attributes from raw coordinates, Domicile365 evaluates positioning data against public cartographic and statistical spatial datasets:

• ISO 3166-1: Standardized alpha-2 and alpha-3 codes for representation of names of countries and their subdivisions.
• Natural Earth: Public-domain cultural and land boundary polygon datasets at 1:10,000,000 scale.
• Marine Regions: Standardized geographic boundaries for internal waters, archipelagic waters, and territorial seas.
• US Census Bureau TIGER/Line: High-precision boundary files for United States states and territories.
• OpenStreetMap: High-resolution spatial data utilized selectively for microstate land boundaries (such as Monaco) where global cartographic datasets lack sufficient polygon precision.

4. Worked Examples — Spatial Resolution Mechanics

The table below illustrates how specific coordinates are resolved in the system ledger. The attribution reflects the boundary geometry of the spatial dataset, without reference to political claims or legal recognition.

The mechanics behind these determinations demonstrate the purely spatial nature of the ledger:

• Ma'ale Adumim: The ledger attributes coordinates in Ma'ale Adumim to Palestine on Natural Earth's armistice line geometry. Many residents in this area file tax returns with Israeli tax authorities. The attribution is geographic, not legal or tax-determinative.
• North Nicosia: The record shows no jurisdiction because no ISO 3166-1 country code exists for Northern Cyprus in international standard tables, not because of an administrative decision to abstain.
• Bir Tawil: In regions where no state claims sovereignty, the ledger records "no jurisdiction" rather than attempting to infer an administrative entity.
• Laayoune: ISO 3166-1 assigns the code EH to Western Sahara. However, Natural Earth's primary land boundary layer merges the region into Morocco's administrative polygon. The ledger reflects the polygon boundary of the selected spatial dataset.

5. What the Record Asserts — and What It Does Not

The purpose of a Domicile365 location record is to establish a verifiable physical audit trail.

6. Why Coordinates Cannot Answer Legal Questions

Whether a day spent in a disputed or unrecognised territory impacts personal tax liability—and which authority holds taxing jurisdiction—depends on legal factors that no coordinate fix can contain. Tax outcomes turn on personal citizenship, tax residency status, governing administrative bodies, double taxation treaties, and statutory rules. None of these variables is carried by latitude and longitude coordinates.

This approach matches how Domicile365 handles transit days across maritime waters and international airspace. The system records physical location data objectively; determining the legal and tax consequences of that physical presence is a matter of statutory interpretation for professional advisers.

7. Recommended Steps for Subscribers & Advisers

Subscribers with recorded days in disputed or unrecognised territories should provide their advisers with the complete location record while clarifying that jurisdiction labels are assigned mechanically from public spatial datasets.

Standard subscriber CSV exports include local timestamps, assigned jurisdictions, determination methods, positioning accuracy metrics, and (when coordinate tracking is enabled) raw latitude and longitude coordinates. Additional database metrics—such as spatial confidence scores and edge distance measurements—are maintained in the system database and available upon request for formal audit verification. Because the underlying data is fully transparent and auditable, advisers can independently verify every entry against whatever statutory standards or specialized legal frameworks apply to their client's tax position.