I have done some nominations at a train station for some murals of my towns history and present. There is 12 murals but some are getting marked as duplicate but definetly dont exist on the wayfarer map. Is there any advice i dont believe appealing is any use always get rejected.
Sometimes, multiple separate objects are seen as a combined entity, meaning that one will represent the entire group. When this happens, additional objects will be marked as duplicate.
An easy example is a playground, which can only have one wayspot legitimately. One piece of equipment might be submitted, then another, but should get marked as a duplicate of the first one even though it is a separate object.
For your murals, it depends a lot on how similar they are and how close together they are.
If you want more specific advice, please post more details ![]()
The murals are really close together but they are all very different all have name plates next to them too they look different
They are too close together to be treated as separate items. Having separate name plates doesn’t change this.
(Had they been identical murals further distance apart, being identical would have been an issue.)
That’s not correct.
If they are distinct artworks, the location being close together does not matter. Having name plates for each one supports these being individual artwork and separately eligible.
@Pokemangame do you want to share examples? I think appeals are likely to be useful here if you provide evidence of these having their own name plates, different subjects and artists etc.
If an external wall contains multiple artworks in a grid, for example, 4 x 4, is that 16 separate wayspots or one wayspot for the wall of art?
That would depend on the presentation. If its 16 different artists with individual commisions, maybe its 16 different PoI? If its a commissioned piece of artwork then maybe its 1. Can’t really say. The submitter would know best there
My point is proximity actually has nothing to do with what is considered a duplicate or what’s considered eligible. There are no proximity rules in wayfarer with regards to what’s acceptable, and a duplicate simply means “its the same exact item”
Each wayspot is evaluated without regard to what is nearby, except when it is considered a duplicate.
Duplicate does NOT mean “the same exact item” in wayfarer. See the clarification about playgrounds for example.
A local example of murals on seating.
The seating at the back (light green), the planters in the middle (orange) and the seating at the front (dark green) are all separate distinct items.
Anyone attempting to submit each of these as separate wayspots would be taking a liberty. Spread them out so they are (say) 100m apart, and they would be seen as eligible separately.
Ok sure thing
The murals arent paintings on a wall they are these banner things attached to the fence outside the train station all about 2m apart from eachover. 2 of them have been accepted but some have been marked as duplicate and others have been refused for “not being perminant” which makes no sense
It isn’t possible to provide specific advice about these artworks without more details. The location would help if they are visible on streetview.
“Not being permanent” means it failed for “permanent and distinct”. Which basically means reviewers thought they were not distinct enough from existing wayspots, but chose to reject this way instead of rejecting for duplicate.
That makes no sense its honestly strange how wayfarer works. If i cant get some of them in i dont mind anyways other players will end up doing them either way.
Reviewing, except when pulled by Niantic, is done by players of the game just like you and me. When something is rejected it is always worth trying to think like someone who didn’t submit the wayspot and only knows what is on the submission.
Most of the time, it becomes possible to understand the rejection (even if you don’t agree with it) as long as you are willing to understand (sometimes people aren’t).
Other people are likely to get the same result as you did. I’m still curious to see these by the way ![]()
