Appearance
UCalgary Space Remote Sensing
Open Science Platform
Facilitating collaborative research, data sharing, and knowledge dissemination by making scientific resources freely accessible to the public.
118
Operational Sensors
Canada, US, Greenland, Antarctica
23
Instrument Array Datasets
1.2 PB+
Data Archive Volume
50K+
Real-Time Data Streams
2K+
Scientific Users
Last 12 months
122K+
Public Users
Last 12 months
Real-Time Data Streams
Watch data flow in from instruments across the globe, live. Learn more
Live Data Streams
Connecting...
Platform at a Glance
Latest Bulletins
September 24, 2026Sep 24SMILE spacecraft added to AuroraX and Swarm-Aurora
With the recently-launched SMILE (Solar wind Magnetosphere Ionosphere Link Explorer) spacecraft now out of commissioning, we have added it to AuroraX and Swarm-Aurora. Users can now search for conjunctions between SMILE and ground-based instruments and other spacecraft.
September 23, 2026Sep 23Software releases: PyAuroraX v1.26.0, IDL-AuroraX v1.11.0
PyAuroraX v1.26.0 ​
- ATM changes
- forward:
maxwellian_energy_fluxnow defaults to 0; at least one energy flux or acustom_spectrumis required - forward: added
maxwellian_mean_energyas an alternative tomaxwellian_characteristic_energy(at most one may be given) - inverse:
precipitation_flux_spectral_typeis now required (previously defaulted togaussian) - client-side PyUCalgarySRS errors are now raised as
AuroraXError - updated the ATM crib sheets, including the inverse-to-forward example, which previously passed the mean energy as the characteristic energy
- removed the outdated ATM model version 1.0 note from the forward crib sheet
- forward:
- bump PyUCalgarySRS dependency to latest
IDL-AuroraX v1.11.0 ​
- ATM changes
- forward: added the
maxwellian_mean_energykeyword as an alternative tomaxwellian_characteristic_energy(at most one may be given) - forward: removed the default Maxwellian spectrum; at least one energy flux or a
custom_spectrummust be given - inverse:
precipitation_flux_spectral_typeis now required (previously defaulted togaussian) - inverse:
characteristic_energyis no longer returned by the API - fixed the inverse-to-forward example, which passed the mean energy as the characteristic energy
- docstring fixes: inverse location limits, the custom neutral profile description, and the custom spectrum flux units
- forward: added the
September 22, 2026Sep 22AuroraX API improvements
We have deployed another round of improvements to the AuroraX API, this time focused on the underlying database management. As with the previous update, there is no impact to users and no changes are required for existing code.
September 22, 2026Sep 22AuroraX automated data loading
AuroraX has been upgraded with automated data loading. Ephemeris and summary data now flow into the platform every few hours, so you can search for conjunctions and browse last night's data in Keogramist and AuroraDome without waiting for a manual update. PyAuroraX and IDL-AuroraX searches benefit automatically. See the full news post here.
September 22, 2026Sep 22AuroraX documentation moved to aurorax.space/docs
The AuroraX documentation has moved. The standalone docs.aurorax.space site has been retired and replaced with aurorax.space/docs, integrated directly into the AuroraX website. The content has been updated and improved in various places, and the API references for PyAuroraX and IDL-AuroraX are now part of the new docs pages as well. Existing docs.aurorax.space links redirect to the new location.
Latest News
0:00 / 0:00
Our Data
Browse our open data archive. The archive is accessible using a variety of methods, including HTTP, FTP, Rsync, Python libraries, IDL library, and direct API-based access.
- HTTP:by project, by instrument type
- Rsync:
rsync rsync://data.phys.ucalgary.ca - FTP:
ftp://data.phys.ucalgary.ca - API:api.phys.ucalgary.ca
- View thestatus of the platform
- Explore thearchive data volume
- Explore thedataset documentation
0:00 / 0:00
Working with our Data
We provide several libraries for working with our data, along with a vast example gallery. Tools are for Python and IDL, along with a RESTful API available for direct interaction.
- Explore oursoftware packages
- Learn how todownload data
- Explore the crib sheets:Python, IDL
- New to our data? Follow ourlearning pathsto get started
- Writing a paper? Learnhow to citeuse of our datasets and tools
- Learn about theAPI
Data Discovery & Visualizations
Explore our data through a variety of websites and visualizations developed to support exploration and discovery of our data.
Learn MoreFrequently Asked Questions
How do I properly acknowledge and cite the data I'm using?
Each dataset contains an acknowledgements file housed in the appropriate data tree. The file contains required data acknowledgements and/or the DOI for the dataset (e.g., REGO). You can also consult the list of datasets to find links to appropriate acknowledgements file. If you cannot find what you are looking for, please reach out.
I think something is wrong, who do I contact about the data I'm using?
If you encounter issues or have questions about the data please reach out to the instrument contact listed on the Dataset Documentation page.
Can you change the operating mode of the sensors to support my science?
Some UCalgary instrumentation has capacity for different operating modes. If you are interested in discussing operational modes, please reach out to the contact for the appropriate instrument type/network.
Are there any new sensors planned for the near future?
We are always looking for ways to improve the quality and information content of our data. This can be modifications to operational modes, calibration procedures, or designing next generation instrumentation. Currently, SMILE-ASI is in active development, with GDC-G following closely behind. If you are interested in learning more, please reach out the UCalgary team.
How do I get last night's full resolution data?
Depending on the instrument type, full resolution data may not be available in real-time. Higher data rate systems (e.g., ASIs) often rely on physical recovery of hard drives with a 3-6 month lag for data to be available. Our data archive is built on a philosophy of 'if we have it, you have it', so for our fully operational systems if you do not see full resolution data, it is very likely still in the field. For high-value data, and on request, we can sometimes retrieve portions of large datasets (e.g., an hour of data). If you have a specific data request please reach out to the instrument contact.
Have Questions?
If you have any questions, please don't hesitate to contact us.


