feat(vessels): AISStream (US) + VesselAPI (Hormuz) as two active providers #19
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "feat/vesselapi-ais-poller"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Two independent vessel providers, both first-class. Not a fallback pair.
AISSTREAM_API_KEYVESSELAPI_API_KEYBoth upsert into the same
vessel_last_knownstore (GET /api/vessels). Missing one key never disables the other. Paste both on the dashboard Keys page.What changed
app/vesselapi.py: Hormuz bbox25.5,55.4,27.3,57.2(span 3.6 ≤ 4°). 5 successful 2xx/UTC day, no pagination, no satellite, no map-pan fetches.keystoreregistry copy splits the two keys so the Keys UI cannot be read as one AIS backup.AISSTREAM_IN_APP/VESSELAPI_IN_APP).extra.srcisaisstreamvsvesselapi.Quota
VesselAPI stays at 5 calls/day (150/mo). AISStream is unchanged.
Tests
tests/test_vesselapi.py— idle/poll independent of the AISStream key; span validator; daily cap; markers withextra.src=vesselapi.feat(vessels): VesselAPI quota-capped AIS poller (Strait of Hormuz)to feat(vessels): AISStream (US) + VesselAPI (Hormuz) as two active providers