Trim data feeds to work with *24-hour cache* data.
- Dominant language
- Python
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
the original starting feed is UNIDATA, which is at least one (perhaps more) orders of magnitude data than what is on the GTS. to do a test for performance as a 24 cache, it makes sense to start with the actual data set, and not one far, far bigger. First shot at filtering is to just pick certain GTS type messages from within the WMO_Sketch_2mqtt.conf feed:
```
subtopic *.GTS.*.SA.#
subtopic *.GTS.*.SM.#
subtopic *.GTS.*.IS.#
subtopic *.GTS.*.FT.#
```
It would be great to get a full listing of the TT's needed to get a complete 24 hour cache.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with WMO_Sketch_2mqtt.conf and review the existing GTS subtopic filters for SA, SM, IS, and FT messages. Determine which TT message types are needed for a complete 24-hour cache, then verify that the feed uses the resulting filtered set for performance testing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100