1.3.1

Performance release. demand_data.json drops from 74 MB to 11 MB.

depot embeds the full polyline of every commute in the demand file when it routes. At 43 vertices per pop that came to 2.85 million vertices — 74 MB, of which 85% was path geometry. That is 1.1 KB per pop against a median of 0.18 KB across the 274 registry maps that ship an uncompressed demand file, a 6× outlier. Tokyo fits 314k pops in 50 MB; at Charleston's density it would need 340 MB.

Nothing reads them from there. The game requests a path one pop at a time over map://paths/{cityCode}/{popId}, which Railyard's map loader intercepts and serves — which is why essentially no other map embeds them.

drivingSeconds and drivingDistance, which the simulation does need, are unchanged.

This was not the bounding box. Measured against the registry, every area-driven file is unremarkable for a map this size:

file	Charleston	peers
PMTiles	66 MB	Baltimore-DC 143 MB, Portland 132 MB
buildings index	54 MB	Tampa 155 MB
ocean depth	1.3 KB/km²	Warsaw 2.9, Tokyo 9.9

Archive drops from 160.8 MB to 151.1 MB. Demand unchanged at 582,306 people across 2,359 points and 66,179 pops. Map files unchanged from 1.2.0.