About 5 days ago I had a nomination accepted (see pictures) and it stands alone in an L17 cell. It is adjacent to, but not inside, a cemetary that was disabled for Pokémon Go a long time ago, and I think that is causing the issue.
Is there any recourse for this waypoint to become a Pokestop, or is it doomed to the eternal lightship?
Hmm… that is completely across the street from the cemetery
I think you are going to need Niantic to tell you the issue here.
I haven’t heard about any Pokemon Go sync delays, and the Ingress portal has already synced in.
Thanks for the reply! Though I’ve read about the rules on what becomes a stop and what doesn’t, I’m still relatively new to this.
Any tips on how to go about getting a Niantic look for this?
Niantic staff monitor the whole forum, but especially this category and Wayspot Appeals . If they haven’t replied by Monday, I would bump it then. I don’t tag staff unless I think they might have missed something that needs their attention. I added the screenshot of the portals to confirm it had gone live in that game for them.
There have been a couple of times recently they have had to do something “on the backend” for PoGo, and only they can check if the geo block on the cemetery extends this far.
I wasn’t expecting such a thorough and thoughtful response so quickly! Thank you!
I’ll keep an eye on the post here and take your advice to bump it if necessary.
it’s 100% this, the way they draw the boundaries is never perfect.
have any situations come up where they have been able to make backend adjustments when the boundary is clearly wrong?
there was one posted somewhat recently on this forum that was handled this way but i don’t think i’m allowed to share details.
so not a lost cause - ty
Not an official response just from my recollection:
But i thought that property owners can request removal a certain perimeter around their property, at least i think this was true for SFPRP.
I came here to see if the person who fixed it had posted, but I suppose not. Either way, thank you, stranger! Problem resolved.
