You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a pokemon name or number is entered, all currently known nests for that pokemon should be emphasize in an obvious way (opacity adjustments, marker size changes, whatever works).
When a location name is entered, a geocoding or location search API (ie, OpenStreetMaps' Nominatim) should be used to center on and emphasize the location requested.
I leave as-you-type search suggestions, multiple search results handling, and queries that are neither location names nor pokemon to the developers.
What is the motivation / use case for changing the behavior?
As a user looking for a particular pokemon, I want to search for nests of that pokemon so that I can quickly identify if there's any nests relevant to that pokemon near me.
As a user who frequently visits a handful of locations, I want to search for nests at that location so that I can plan what locations need reports or contain pokemon I need.
Other information
The overall idea here is to not force people to browse around a map, but rather enable them to quickly find the two things (I believe) they're most likely to care about; "Where can I find a ____?", and "What's at ____?"
Environment not specified because this is not a bug.
The text was updated successfully, but these errors were encountered:
I'm submitting a ...
What is the expected behavior or new feature?
There should be a search box in the nest atlas.
When a pokemon name or number is entered, all currently known nests for that pokemon should be emphasize in an obvious way (opacity adjustments, marker size changes, whatever works).
When a location name is entered, a geocoding or location search API (ie, OpenStreetMaps' Nominatim) should be used to center on and emphasize the location requested.
I leave as-you-type search suggestions, multiple search results handling, and queries that are neither location names nor pokemon to the developers.
What is the motivation / use case for changing the behavior?
As a user looking for a particular pokemon, I want to search for nests of that pokemon so that I can quickly identify if there's any nests relevant to that pokemon near me.
As a user who frequently visits a handful of locations, I want to search for nests at that location so that I can plan what locations need reports or contain pokemon I need.
Other information
The overall idea here is to not force people to browse around a map, but rather enable them to quickly find the two things (I believe) they're most likely to care about; "Where can I find a ____?", and "What's at ____?"
Environment not specified because this is not a bug.
The text was updated successfully, but these errors were encountered: