<h3><strong> FlightTracer v0.1.3 - Enhancements & Fixes</strong></h3><h4><strong>Improvements</strong></h4><ul><li><p><strong>More accurate flight leg detection</strong></p><ul><li>Refined logic to prevent splitting continuous flights due to Zulu day transitions.</li><li>Better handling of <code>call_sign</code> to maintain flight continuity.</li><li>Customizable time gap threshold for detecting legs.</li></ul></li><li><p><strong>Expanded customization options</strong></p><ul><li>Users can now choose file output formats: CSV, GeoJSON, or Shapefile.</li><li><code>filter_ground</code> option allows retaining or filtering ground-level data.</li></ul></li><li><p><strong>More robust data processing</strong></p><ul><li>Improved handling of missing or inconsistent <code>details</code> data in ADS-B traces.</li><li>Normalized <code>call_sign</code> extraction for better consistency.</li></ul></li></ul><h4><strong>Bug Fixes</strong></h4><ul><li>Fixed an issue where missing <code>details</code> entries led to <code>UNKNOWN</code> flight leg names.</li><li>Addressed incorrect leg numbering that appeared in continuous flights.</li></ul><h4><strong>Other Updates</strong></h4><ul><li>Improved documentation with clearer examples and customization options.</li><li>Better structured README with new usage scenarios.</li></ul><hr><h3><strong>Next Steps</strong></h3><ul><li>Enhance metadata enrichment (e.g., airline lookups).</li><li>Improve performance for larger datasets.</li><li>Add CLI support for easier command-line execution.</li></ul><hr><p>Does this summary look good to you? Let me know if you want to tweak anything! </p>