Spawn Point migration - Githubissues

matt-yml commented 2 years ago

Along with the OSM update Niantic is updating spawn points. This ticket tracks its impact and efforts to update from the migration.

Discover the new points.
Find the TTH timing of all (new) unknown points.
Remove old spawn points that haven't been updated recently

1- Discovery Round (IV fence only)

[x] Asheville (dev)
[x] Asheboro
[x] Cabarrus
[x] RDU
[x] Charlotte
[x] GSO
[x] Pittsboro

2- Timing each spawn point (TTH)

[x] Asheville (dev)
[x] Asheboro
[x] Cabarrus
[x] RDU
[x] Charlotte
[x] GSO
[x] Pittsboro

3- Remove defunct points

[x] Asheville (dev)
[x] Asheboro
[x] Cabarrus
[x] RDU
[x] Charlotte
[x] GSO
[x] Pittsboro

matt-yml commented 1 year ago

spawn points have significantly changed in Asheville. this was the last area to be scanned before the migration, but hasn't been regularly scanned since.

will need to do blank scanning of all areas, remove spawn points that don't meet 'last seen criteria'.

this matches the announcement. rural areas will get many new spawn points, city not so much.

matt-yml commented 1 year ago

Found new non-event spawn points in Asheboro for the entire thing, not just monster areas. Now added to auto TTH time finding route, which is fence based. New spawn points: 12967 Unknown TTH(Red): 8668 Known TTH(Blue)

matt-yml commented 1 year ago

Extensive database rework done for migration. Includes SQL commands to modify.

Adding new first_seen column to spawn points.

ALTER TABLE spawnpoint
ADD COLUMN first_seen TIMESTAMP DEFAULT CURRENT_TIMESTAMP;

Added green regular indices for despawn_sec and first_seen as well. This may slow insertion times into the db, but is necessary now while developing a plan. May remove later, or it may not be an issue as new points aren't being added constantly.

Rough SQL scratch for Asheboro coord tracking

-- Asheboro new spawn points tracking
SELECT * FROM spawnpoint
WHERE lat BETWEEN 35.606356 AND 35.764605
-- seen since monday midnight
-- AND last_seen >= 1671426000
-- unknown spawn point
AND despawn_sec IS NULL
-- first seen epoch 2022-12-21 03:11:14
AND first_seen > '2022-12-21 03:11:14'
-- AND first_seen >= '2022-12-21 19:07:00'
AND lon BETWEEN -79.892942 AND -79.715541;

Rough SQL scratch for CAM coord tracking

-- CAM spawn point tracking
SELECT * FROM spawnpoint
WHERE lat BETWEEN 35.721821 AND 35.814978
-- seen since monday midnight
-- AND last_seen >= 1671426000
-- unknown spawn point
-- accountAND despawn_sec IS NULL
-- first seen epoch 2022-12-21 03:11:14
AND first_seen > '2022-12-21 03:11:14'
-- AND first_seen >= '2022-12-21 19:07:00'
AND lon BETWEEN -78.918606 AND -78.773371;

matt-yml commented 1 year ago

Will likely need to add new bots to scan all the new areas within a reasonable amount of time. Let's add 10 because we're also adding Charlotte and Pittsboro.

matt-yml commented 1 year ago

RDU has added a LOT of new points. ~233k so far

matt-yml commented 1 year ago

11 more bots added to system bringing us to 101 total. In theory that's 660 more phones. Noice

Seem to be leveling off at 21000 tcp connections.

matt-yml commented 1 year ago

Let's start measuring the spawn points and unknowns for the overall map. Yellow=Unknown - need to scan Green=Total new points found That means the timing has been found for 239,301 new points. 👀