Papers › UrbanDiT: A Foundation Model for Open-World Urban Spatio-Temporal Learning
UrbanDiT: A Foundation Model for Open-World Urban Spatio-Temporal Learning
Yuan Yuan, Chonghua Han, Jingtao Ding, Depeng Jin, Yong Li
The urban environment is characterized by complex spatio-temporal dynamics arising from diverse human activities and interactions. Effectively modeling these dynamics is essential for understanding and optimizing urban systems In this work, we introduce UrbanDiT, a foundation model for open-world urban spatio-temporal learning that successfully scale up diffusion transformers in this field. UrbanDiT pioneers a unified model that integrates diverse spatio-temporal data sources and types while learning universal spatio-temporal patterns across different cities and scenarios. This allows the model to unify both multi-data and multi-task learning, and effectively support a wide range of spatio-temporal applications. Its key innovation lies in the elaborated prompt learning framework, which adaptively generates both data-driven and task-specific prompts, guiding the model to deliver superior performance across various urban applications. UrbanDiT offers three primary advantages: 1) It unifies diverse data types, such as grid-based and graph-based data, into a sequential format, allowing to capture spatio-temporal dynamics across diverse scenarios of different cities; 2) With masking strategies and task-specific prompts, it supports a wide range of tasks, including bi-directional spatio-temporal prediction, temporal interpolation, spatial extrapolation, and spatio-temporal imputation; and 3) It generalizes effectively to open-world scenarios, with its powerful zero-shot capabilities outperforming nearly all baselines with training data. These features allow UrbanDiT to achieves state-of-the-art performance in different domains such as transportation traffic, crowd flows, taxi demand, bike usage, and cellular traffic, across multiple cities and tasks. UrbanDiT sets up a new benchmark for foundation models in the urban spatio-temporal domain.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="2411.12164")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2411.12164", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2411.12164")
Code
Syntology 22 code samples harvested from 2 repositories linked to this paper: 20 ran (of which 2 constructed an object rather than computing a result; 11 with no instrument failure: 5 honoured, 0 violated, 6 with no contract checked; 9 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 7 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.
By repository: official repository: 2 samples from 1 repository, 2 ran (2 with no instrument failure; 0 where Syntology's instrument failed); found in paper text by Syntology: 20 samples from 1 repository, 18 ran (9 with no instrument failure; 9 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 5 of the 20 samples that ran have no recorded date.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
Code Syntology ran Syntology
22 samples harvested: 20 ran (of which 2 constructed an object rather than computing a result; 11 with no instrument failure: 5 honoured, 0 violated, 6 with no contract checked; 9 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 8 of the 22 samples are pointer only, meaning Syntology does not serve that copy's text. For 8 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
85748648fb97ed30 · report
fixture: returned GCN · level recorded 2026-09-22 4af35c2b62c7fb82 · report
fixture: returned GraphEmbedding2 · level recorded 2026-09-22 census: 4 implementations from 14 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 src/diffusion/diffusion_utils.py ran · our draft was wrong fingerprinted MIT (permissive) ·
d6a68e210556f857 · report
fixture: signature x:Tensor/2/float · returned Tensor · level recorded, date not recorded 1712a07966b542ee · report
fixture: signature pil_image:Image/0/?, image_size:int/0/int · returned Image · level recorded, date not recorded census: 2 implementations from 5 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 src/diffusion/diffusion_utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only ·
ab1c9568b4e13899 · report
fixture: signature x:Tensor/2/float, means:Tensor/2/float, log_scales:Tensor/2/float · returned Tensor · level recorded 2026-09-22 b2cc78f4103df806 · report
fixture: signature logging_dir:str/0/str · returned Logger · level recorded, date not recorded e48218d7d73db0b3 · report
fixture: signature name:str/0/str, diffusion:MockDiffusion/0/? · returned UniformSampler · level recorded 2026-09-25 61bae757140432aa · report
fixture: signature H:int/0/int, W:int/0/int · returned list · level recorded 2026-09-25 census: 8 implementations from 17 papers, 2 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 2 of 2, arg 1: rank 1, kind float, dtype float32 src/Embed.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant MIT (permissive) here; the stored copy is pointer only ·
5c8ea92d43ead77d · report
fixture: signature embed_dim:int/0/int, pos:ndarray/1/float · returned ndarray · level recorded 2026-09-22 3739773ec6873943 · report
fixture: signature embed_dim:int/0/int, grid_size1:int/0/int, grid_size2:int/0/int · returned ndarray · level recorded 2026-09-25 3e0fa4efc22272d4 · report
fixture: signature beta_schedule:str/0/str, beta_start:float/0/float, beta_end:float/0/float, num_diffusion_timesteps:int/0/int · returned ndarray · level recorded 2026-09-22 36e30c7fb679ec78 · report
fixture: signature schedule_name:str/0/str, num_diffusion_timesteps:int/0/int · returned ndarray · level recorded 2026-09-22 0897f66c098e3d8d · report
fixture: signature noise_scheduler_copy:NoiseScheduler/0/?, timesteps:Tensor/1/int, n_dim:int/0/int, dtype:dtype/0/? · returned Tensor · level recorded, date not recorded census: 9 implementations from 18 papers, 4 distinct outputs across 3 buckets, one shared input per bucket this sample: bucket 1 of 3, arg 1: rank 3, kind float, dtype float32 src/diffusion/gaussian_diffusion.py ran · our draft was wrong fingerprinted MIT (permissive) ·
f6d7c009a8efb8b7 · report
fixture: signature tensor:Tensor/3/float · returned Tensor · level recorded, date not recorded census: 14 implementations from 24 papers, 2 distinct outputs on one shared input this sample: bucket 1 of 1, arg 1: rank 2, kind float, dtype float32 · arg 2: rank 2, kind float, dtype float32 · arg 3: rank 2, kind float, dtype float32 · arg 4: rank 2, kind float, dtype float32 src/diffusion/diffusion_utils.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only ·
8afbfc42c6ea0448 · report
fixture: signature mean1:Tensor/2/float, logvar1:Tensor/2/float, mean2:Tensor/2/float, logvar2:Tensor/2/float · returned Tensor · level recorded 2026-09-22 572665172cac0917 · report
fixture: returned tuple · level recorded 2026-09-25 cb94ddc96b9220cc · report
fixture: signature args:Args/0/?, dataset:str/0/str · returned int · level recorded 2026-09-25 847b1b87d9c07bf8 · report
fixture: signature args:ArgsStandIn/0/?, data:str/0/str · returned int · level recorded 2026-09-25 ea9dbc131adf582e · report
fixture: signature num_timesteps:int/0/int, section_counts:list/1/int · returned set · level recorded 2026-09-22 b97edc3163f3ded8 · report
fixture: signature tensor:Tensor/2/float · returned Tensor · level recorded 2026-09-25 2884deadbb637c3e · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.
1 assembly on this paper: 1 harvested, 0 generated.
harvested Assembly for UrbanDiT (graph method: UrbanDiT). 2 bricks; individually on a fixture: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.
- GraphEmbedding2 entry · level 1 · ran ·
4af35c2b62c7fb82 - GCN model · level 1 · ran ·
85748648fb97ed30
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2411.12164") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections