Do Location Encoders Capture Spatial Effects? A GeoShapley Benchmark Across Scales

Daniel Kiv, Shaowen Wang
6/22/2026
cs.LG

No confident code implementation found for this paper.

Abstract

Location encoders transform geographic coordinates into high dimensional embeddings for downstream machine learning, but it is unclear how well these representations capture interpretable spatial effects. We benchmark whether GeoShapley, a game-theoretic explainer that treats all location features as a single joint player, can recover spatially varying coefficients from models built on location-encoder embeddings. Eleven encoders from the TorchSpatial framework are evaluated against a synthetic process with known coefficients, across three scales (grid, county, global), with and without raw coordinates alongside the embedding, and under untrained and contrastively trained conditions. Measuring recovery as the correlation between estimated and true coefficients, we report how it varies with scale and encoder architecture and compare the embeddings against a raw-coordinate baseline. Recovery of the primary coefficient is consistently high across encoders, whereas recovery of a secondary coefficient is more scale-dependent, differing most at the global scale; the raw-coordinate baseline remains competitive throughout.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. Any repos shown below are weak matches — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{kiv2026location,
  title  = {Do Location Encoders Capture Spatial Effects? A GeoShapley Benchmark Across Scales},
  author = {Daniel Kiv and Shaowen Wang},
  year   = {2026},
  eprint = {2606.23453},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2606.23453v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2606.23453.svg)](https://codeofpaper.com/paper/2606.23453)

Discussion