These four Wayspots provide an excellent example of this bug in action. They are (from north to south):
"Sydney Building" (-35.278712,149.130475)
"All Aboard The No.1 And No.2" (-35.278864,149.130476)
"Divergent Church City – The Loft" (-35.278974,149.130429)
"That Game Store Civic" (-35.278974,149.130429)
"Sydney Building" was restored first and went live because it was not within 20 metres of a Wayspot.
"All Aboard The No.1 And No.2" was restored second and was correctly blocked because it was 17 metres from "Sydney Building"
"Divergent Church City – The Loft" was restored third. It should have gone live as it was 30 metres from "Sydney Building", but was blocked by "All Aboard The No.1 And No.2"
"That Game Store Civic" was restored fourth. It should have gone live as it was 42 metres from "Sydney Building", but was blocked by "Divergent Church City – The Loft". Note that "All Aboard The No.1 And No.2" could not have blocked this one as it was 25 metres away.
This sequence of events is supported by metadata for the Wayspot restoration times.
"Sydney Building" was restored by Niantic at Tuesday, 28 November 2023 5:38:37 AM GMT
"All Aboard The No.1 And No.2" was restored by Niantic at Tuesday, 28 November 2023 5:40:11 AM GMT
"Divergent Church City – The Loft" was restored by Niantic at Tuesday, 28 November 2023 5:41:36 AM GMT
"That Game Store Civic" was restored by Niantic at Tuesday, 28 November 2023 5:42:03 AM GMT
There are several possible solutions, but to accommodate both the team and the agent, it would be a good idea to change the target condition of the 20m rule from wayspot to portal.
However, this may not be possible since it would be a difference comparison in different databases.
There are wayspots accepted into lightship where I have added the blue and red crosses. The blue one was accepted first (not mine) and shows in pokemon but not ingress. This is correct as it is within 20m of another but in its own lvl17 cell. I later submitted the red one and it was accepted but never showed in any games. This is not within 20m of any ingress portals so I would expect it to show up in Ingress. It is within 20m of the blue one which appears to be blocking it from appearing although it is not a portal.
This just happened to my approved wayspot Kids District Colorblock Mural (41.758105, -88.212244). It is showing within Wayfarer an approved location outside of any Ingress POI radii, but probably within a Lightship POI. @NianticBrian
I have another example of a POI that is greater than 20m from the nearest Ingress game feature that is excluded from the sync because there is another POI that is LightShip only within 20m
POI Name: Butterfly Mural
Location: 52.201559, 0.125586
Street Address: 35 Regent St, Cambridge CB2 1AB, UK
Wayfarer Image for details:
The below is only an approximation taken from satellite view from the different Niantic tools.
Downing College Gate @ 52.201493, 0.12523199999999998 blocks George V Post Box @ 52.201541, 0.125336 which is fair as it only 9.144m, but because George V Post Box is within 20m of Butterfly Mural @52.201558999999996, 0.125586this is also blocked even though it is over 25m from Downing College Gate which is the only game feature meaning that Ingress misses 2 POIs when the correct mechanic should only exclude 1.
Agreed, that it would need dev work and possible them tracking which POIs they have already synced, but they know which ones have been synced to Ingress so shouldn't be too bad, but you can bet that there would be an issue where 2 new POIs are blocked by a LS only which then both get synced.
Comments
These four Wayspots provide an excellent example of this bug in action. They are (from north to south):
This sequence of events is supported by metadata for the Wayspot restoration times.
What the ****, Niantic.
Get your **** **** together.
This is absolutely **** pathetic, and my standards for you are LOW.
This is not the first time this has happened.
When the Navarro portal could not be restored, I could guess the problem.
So I assumed they restored it elsewhere and that they knew about the problem and did it.
And I have written about this before on this forum.
There are several possible solutions, but to accommodate both the team and the agent, it would be a good idea to change the target condition of the 20m rule from wayspot to portal.
However, this may not be possible since it would be a difference comparison in different databases.
I think I have a portal not showing up because of a hidden wayspot. The screenshot below is from IITC... https://intel.ingress.com/?pll=53.54335,-2.605159&z=20
There are wayspots accepted into lightship where I have added the blue and red crosses. The blue one was accepted first (not mine) and shows in pokemon but not ingress. This is correct as it is within 20m of another but in its own lvl17 cell. I later submitted the red one and it was accepted but never showed in any games. This is not within 20m of any ingress portals so I would expect it to show up in Ingress. It is within 20m of the blue one which appears to be blocking it from appearing although it is not a portal.
Below is screenshot of wayspots from lightship...
This just happened to my approved wayspot Kids District Colorblock Mural (41.758105, -88.212244). It is showing within Wayfarer an approved location outside of any Ingress POI radii, but probably within a Lightship POI. @NianticBrian
I have another example of a POI that is greater than 20m from the nearest Ingress game feature that is excluded from the sync because there is another POI that is LightShip only within 20m
POI Name: Butterfly Mural
Location: 52.201559, 0.125586
Street Address: 35 Regent St, Cambridge CB2 1AB, UK
Wayfarer Image for details:
The below is only an approximation taken from satellite view from the different Niantic tools.
Downing College Gate @ 52.201493, 0.12523199999999998 blocks George V Post Box @ 52.201541, 0.125336 which is fair as it only 9.144m, but because George V Post Box is within 20m of Butterfly Mural @ 52.201558999999996, 0.125586 this is also blocked even though it is over 25m from Downing College Gate which is the only game feature meaning that Ingress misses 2 POIs when the correct mechanic should only exclude 1.
Not just one but two would be stopping it. "Gamers World Fox Valley" and "Fox Valley Mall Kiddie Ride Zone"
Agreed, that it would need dev work and possible them tracking which POIs they have already synced, but they know which ones have been synced to Ingress so shouldn't be too bad, but you can bet that there would be an issue where 2 new POIs are blocked by a LS only which then both get synced.
BTW, if you don't vote for the bug then NIA will def not look into it, loads of comments, but only 9 votes on the bug report.
Both votes and comments will be important.
Wayfarer team say this is now resolved.
@NianticBrian Can you confirm and update?