Roadmap

MyAtlas began with a straightforward goal: create an independent path for the weather data produced by an AcuRite Atlas.

That goal has been achieved. Atlas weather observations are being received locally, processed through the MyAtlas system, collected by WeeWX, and shared with supported weather services.

But accomplishing the original mission doesn't mean development is finished. There is still work to do before MyAtlas is ready for a broader public release, along with additional capabilities that can be explored as the project continues.

The foundation is working. The next step is making it easier for others to use.

What We've Accomplished

The original MyAtlas goal is now working as intended. The project has progressed from receiving the Atlas's local 433 MHz transmissions to a complete weather-data path built around WeeWX.

MyAtlas has already demonstrated:

• Local reception of AcuRite Atlas weather observations

• Integration with WeeWX through the custom AtlasMQTT driver

• Support for rain, lightning, and pressure data

• Configuration through weewx.conf

• Compatibility with WeeWX 5.4 and current Raspberry Pi hardware

• Weather-data sharing with Weather Underground, CWOP, PWSWeather, AWEKAS, and WeatherCloud

• APRS.fi visibility through CWOP

• Synchronized weather-service uploads

• Git-based source and development history

The core MyAtlas data path is working.

What's Next

With the core MyAtlas system working, the next phase is focused less on proving that it can be done and more on preparing the project for others to use.

The remaining work toward a public release includes:

• Complete installation and configuration documentation

• Add clear startup and version information

• Finish the remaining configuration options

• Complete pressure-source selection

• Package the AtlasMQTT driver for easier installation

• Prepare the project for a public GitHub release

• Complete and release MyAtlas Version 2

The goal is to turn a working project into something another Atlas owner can install, understand, and use.

Looking Ahead

Beyond the work needed for a public release, MyAtlas leaves room for additional capabilities as the project continues to evolve.

Future possibilities include:

• Support for multiple pressure sources

• Atlas health monitoring

• Additional sensor diagnostics

• Improved lightning statistics

• Support for additional Atlas observations

• Support for multiple Atlas weather stations

• Additional weather networks

• An optional plugin architecture for future expansion

These aren't requirements for MyAtlas to fulfill its original mission. They're possibilities for where the project can go next.

Development Priorities

As MyAtlas development continues, new features aren't automatically the highest priority. The project follows a simple order when deciding what comes first:

1. Reliability
The system should work consistently and dependably.

2. Data Accuracy
Weather observations need to be received, processed, and reported correctly.

3. Ease of Installation
MyAtlas should become easier for other Atlas owners to install and configure.

4. Documentation
Clear instructions should make the project understandable without requiring knowledge of how it was originally developed.

5. New Features
Additional capabilities come after the fundamentals are solid.

Make it reliable. Make it accurate. Make it usable. Then make it do more.

MyAtlas started with a simple idea: the weather data produced by your own station should remain yours to use.

The original mission has been accomplished. The Atlas data can be received locally, processed independently, and used or shared without depending on a single cloud path.

There is still work ahead before MyAtlas is ready for a broader public release, and there are plenty of possibilities for where the project can go from there.

The mission is accomplished. The journey continues.

Your Weather. Your Data. Take It Back!