mirror of
https://github.com/tiennm99/vngeoguessr.git
synced 2026-10-11 03:13:56 +00:00
tiennm99
b7f8879fe0
Every panorama now carries the district it falls in, so a guess can be attributed to a leaf rather than only to a province. The assignment runs against the indexes already on disk: districts are a property of a panorama, not a separate dataset, and re-fetching per district would multiply a ~2,800-tile build against Mapillary's 50,000/day cap for bytes we already hold. The district is stored as an integer offset into a per-province districts array rather than as a code string, which costs about five bytes an entry instead of twelve. Across 424,617 entries that is the difference between the 2.85 MB the data actually grew and something closer to five. Coverage is judged on distinct places, not on raw counts. The index is thinned at 33m, so a count overstates how many different places a district offers by roughly thirty times -- a district can hold hundreds of panoramas and still be one street seen from many angles. Playability therefore needs both a panorama floor, which exists because the Mapillary lookup retries three times with a different candidate, and a floor on distinct ~1.1km cells. Sixty-four of the sixty-seven regions clear it. The three that do not are one of each kind the coverage note describes: Cu Chi has no boundary, while Cam Le and Hoa Vang have no street imagery at all. A point that falls in a sliver between two simplified outlines is placed in the nearest district by distance to the outline itself. Ranking by bounding-box centre instead was measured putting points up to six kilometres inside the wrong district, because a compact district's centre can beat a sprawling neighbour whose edge is metres away. The stranded tally is recorded per province and the build refuses to write above two percent, since that is the signal that the leaf simplification tolerance has opened gaps along shared borders. It currently sits at 0.05 percent, worst case forty-six metres. fetchCityPanorama now reports the district of the attempt that succeeded. Each retry draws a fresh candidate, potentially from a different district, so carrying the first one forward would credit the wrong place. An exhausted pool returns a failure rather than escaping as a 500. Panorama arrays handed out at runtime are frozen. They are process-global and cached for the life of the server, and an in-place sort on the shared district array had already once repointed every panorama at the wrong district. Nothing is wired to scoring yet: the resolved district is computed and returned but not stored on the session. That lands with the leaderboard fan-out.