Map Rendering Tiles — eeuz.mp0, .mg1–.mg4

Status: ✅ Mostly cracked · MAP_COMPRESSED

The actual map-rendering tile layers. mp0 = most detailed/primary, mg1→mg4 = progressively generalized for lower zoom levels. CONFIRMED, a later session, directly from the real RNS510 unit's own on-screen behavior (the user has the actual hardware running this exact disc): each layer is a real ROAD-CLASS tier, not just a generic "less detail" simplification — mg4=highways, mg3=main roads, mg2=boulevards, mg1=main streets, mp0=everything else (local/residential streets and smaller roads). Directly validated: a real A1/Trakia motorway segment near Sofia is present in mg4, but a real local one-way street (Vladimir Bashev, Sofia) is NOT present anywhere near its own real coordinates in mg4 (nearest-anchor match landed ~6-7km away) — only found in mp0, exactly matching this hierarchy. Sizes on the reference disc:

File	Size	Tiles (geo-indexed)
eeuz.mp0	2.14 GB	194,650 / 194,705 (99.97%)
eeuz.mg1	240 MB	63,970 / 63,996 (99.96%)
eeuz.mg2	113 MB	34,200 / 34,209 (99.97%)
eeuz.mg3	46 MB	16,495 / 16,503 (99.95%)
eeuz.mg4	16.5 MB	6,106 / 6,110 (99.93%)

For the shared container/directory format (how to find and decompress a tile), see MAP_COMPRESSED Container Format. For what's inside a decompressed tile — the coordinate geometry and the point-connectivity topology table — see Tile Geometry and Topology, which applies identically across mp0/mg1–mg4.

The map viewer

rns510_map_viewer.py pools these 5 layers together for live rendering, with per-layer visibility checkboxes and a "Draw connected roads" mode built on the topology resolver — see Map Viewer Tool and the README's §10 changelog for the full feature history.