How sco1/skyportal works
Main Components
a. Hardware Layer:
• PyPortal Device (Central component)
• /Touchscreen Interface
• WiFi Module
b. Software Components:
• Core Application Modules (skyportal/)
• aircraftlib.py (Aircraft data handling)
• displaylib.py (Display management)
• maplib.py (Map rendering)
• networklib.py (Network communications)
c. External Services:
• Adafruit IO (Time lookup & image hosting)
• Geoapify (Static mapping)
• Aircraft Data Sources:
• OpenSky Network API
• ADSB.lol API
• Custom Proxy API (Optional)
[External Services Layer]
• ↕
[Network Layer]
• ↕
[Application Layer]
• ↕
[Hardware Layer]
Specific Implementation Details
• Rectangles: Core system components
• Clouds: External services
• Hexagons: Hardware components
• Blue: Core application components
• Green: External services
• Orange: Hardware components
• Purple: Network components
Key Relationships to Highlight
a. Data Flow:
• External APIs → Network Layer → Application Processing → Display
• Touch Input → Display Controller → Application Logic → Data Requests
b. Component Interactions:
• Tile generation/caching system
• Aircraft state processing pipeline
• Touch event handling system
Critical Elements
a. Memory Management:
• Filesystem cache for map tiles
• RAM constraints handling
b. Configuration Systems:
• secrets.py integration
• skyportal_config.py settings
c. Library Dependencies:
• CircuitPython core libraries
• Adafruit support libraries
The touch interface interaction flow
• Data flow directions
• Component types
• State indicators
• API endpoints
Keep in mind the project's constraints:
• Memory limitations of PyPortal
• Blocking nature of web requests
• Single-touch event handling
Remember to include error handling paths and the boot process modification for filesystem caching, as these are critical to the system's operation.