the in-game map was recently updated with a fresh OSM data set, roughly dated mid December. We are still investigating the exact date, but it seems that changes made before December 15 are now reflected in the game (at least according to this reddit thread).
The change took place likely last night at around 02:00 UTC, as indicated by ReaperVE, a GO Hub Discord member from Vellmar, Germany:
If you’re wondering why this is a big deal and why there is a post about it on the Hub, let us remind you about the influence of OpenStreetMap data on the in-game behaviour.
Everything from Pokémon spawns, nests, EX raids and even potentially in-game biomes is influenced by the data set that OSM provides. Most notably, areas marked as parks and similar OSM tags are used in several different scenarios.
Alongside S2 cells, OSM data is the second pillar of Pokémon GO’s “spawn and map” system, enabling Niantic to tap into rich geo-contextual data and create meaningful encounters. Ever wondered how the game knows that there’s a river / lake / ocean there? OSM data. Ever wondered why parks often have nests, while your residential block doesn’t? OSM data.
What does this mean for the EX Raid system and our triggering guide?
We don’t know, yet. OSM data can be imported by selecting a data set up to a certain date and it was discovered that not all in-game systems use data with the same date:
- The EX Raid system uses OSM data from July/August 2016 to determine eligible gyms (areas marked as parks after this date can’t produce an EX Raid)
- The in-game overworld map (that renders Pokémon, Stops, Gyms, etc..) uses OSM data from December 2017
Unfortunately, at this moment we don’t know if Niantic changed the date used for EX-raid eligibility. Therefor, we will not be updating our Overpass Turbo query with a new date until we are completely certain that the EX data set date has changed.
The post In-game map updated with new OpenStreetMap data from December 2017 appeared first on Pokemon GO Hub.