the return of nests

[matt-yml]

issue

nest computation is not finished code or even implemented in the "new stack" there's currently discussion about what project it should be in (or its own), and who should write it

as a temporary solution we'll run the old nest routes so people and see what's on the ground live, and decide if it's a nest or not.

unfortunately this only works in areas we had nest scans established:

• charlotte
• cabarrus co
• wsm
• greensboro
• asheboro
• rdu

the nest feature is the culmination of data from multiple services, requires planning far in advance, consistent & clean data, and is very compute intensive.

work around

we'll have to stick with the live-scan approach until a stable beta is made. in the meantime we'll work on nest fence discovery for new areas that aren't mentioned above.

spawn times will be shorter for these areas, as we're reporting mon frequency, and aren't primarily meant for alerts

[matt-yml]

Something's working...

[matt-yml]

[matt-yml]

initially reopened to advanced access tiers, will open to premium tiers this afternoon.