Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mark spawn points as regular or event/bonus on map #1085

Open
zakius opened this issue Jan 25, 2025 · 1 comment
Open

Mark spawn points as regular or event/bonus on map #1085

zakius opened this issue Jan 25, 2025 · 1 comment

Comments

@zakius
Copy link

zakius commented Jan 25, 2025

It would probably require using additional 2 colors to easily distinguish 4 types of spawns

verified regular, unverified regular, verified event, unverified event

as a naive implementation marking spawns that had no pokemon spawned on during last few hours would suffice, perfectly we'd need to track behavior between known extra-spawns events and regular times to permanently mark spawn points as event ones

@lenisko
Copy link
Contributor

lenisko commented Jan 25, 2025

It's not fully doable the way you want it, since the game is not providing us details related to type of spawn (normal, event).

As I see it, it could be split using last seen field as:

  • Known spawn : Last Seen under X hours
  • Known spawn : Last Seen more than X hours
  • Unknown spawn

Where X could be set between 1, 168 (1 hour - 1 week) which would be enough to filter out SH and show CD only. Maybe as a list? eg: 2 hours, 1 day, 3 days, week.

So the query would have to distinguish active and inactive spawnpoints in addition to known, unknown.

In addition, here's example data we have saved in parser:

id | lat | lon | updated | last_seen | despawn_sec | first_seen
911118302985 | 40.47816609080911 | -3.58194151462559 | 1736714194 | 1736722125 | NULL | 1736714194

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants