Skip to main content

Release Licence Python Django pre-commit.ci statusCode style: black Checks codecov Translation status

ko-fi

AA Belt Radar module for AllianceAuth.

A Belt Survey Analyser to track how fast you mine your belt.


Features

  • Interactive Live Sessions & Mining Analytics
    • Dynamic live session updates: new survey scans and mining data are automatically loaded and immediately visible
    • Real-time mining speed tracking in m³/s
    • Estimated completion time (ETA) for belt mining
    • Remaining volume and belt size calculation
    • Compressed ore price estimation
  • Visual Analytics & Diagrams
    • Ore Progression: Visual chart tracking the progress and composition of mined ore
    • Mining Speed & Volume Chart: XY line & column diagram displaying remaining volume (m³) alongside mining speed (m³/s) over time
  • Belt Automation & Timers
    • Automatic belt type and size detection
    • Automatic respawn timer creation when only 10% of the belt volume is left
    • Public and private belt respawn timers
  • Collaboration & Notifications
    • Optional session sharing with fleet members or corporation
    • Configurable Discord webhook notifications for belt respawn timers

Highlights

Image: Belt Radar Dashboard Image: Belt Radar My Sessions Image: Belt Radar View Session

Installation

Step 1 - Install the Package

Make sure you're in your virtual environment (venv) of your Alliance Auth then install the pakage.

pip install aa-beltradar

Step 2 - Configure Alliance Auth

Configure your Alliance Auth settings (local.py) as follows:

INSTALLED_APPS = [
    # other apps
    "eve_sde",  # only if it not already existing
    "beltradar",
    # other apps?
]

# This line is right below the `INSTALLED_APPS` list, if not already exist!
INSTALLED_APPS = ["modeltranslation"] + INSTALLED_APPS

Step 3 - Add the Scheduled Tasks

To set up the Scheduled Tasks add following code to your local.py

CELERYBEAT_SCHEDULE["AA Belt Radar :: Update Belt Radar"] = {
    "task": "beltradar.tasks.update_all_belt_radar",
    "schedule": 600,
}
CELERYBEAT_SCHEDULE["AA Belt Radar :: Update Market Price"] = {
    "task": "beltradar.tasks.update_market_prices",
    "schedule": 86400,
}

Step 3.1 - (Optional) Add own Logger File

To set up the Logger add following code to your local.py Ensure that you have writing permission in logs folder.

LOGGING["handlers"]["beltradar_file"] = {
    "level": "INFO",
    "class": "logging.handlers.RotatingFileHandler",
    "filename": os.path.join(BASE_DIR, "log/beltradar.log"),
    "formatter": "verbose",
    "maxBytes": 1024 * 1024 * 5,
    "backupCount": 5,
}
LOGGING["loggers"]["extensions.beltradar"] = {
    "handlers": ["beltradar_file"],
    "level": "DEBUG",
}

Step 4 - Migrate & Preload EVE SDE Data

AA Skillfarm uses EVE SDE data to map IDs to names for EveTypes. You will need to preload some data from SDE once.

python manage.py migrate eve_sde
python manage.py esde_load_sde

Step 4.1 - Migrate App and collect static

Migrate the app and collect static.

python manage.py migrate beltradar
python manage.py aabeltradar_migrate_market_data
python manage.py collectstatic --noinput

Step 5 - Setting up Permissions

With the Following IDs you can set up the permissions for the Belt Radar

ID Description
basic_access Can access the Belt Radar module All Members with the Permission can access the Belt Radar.
manage_access Can Manage Belt Radar module Can manage Application
admin_access Has access to all Survey Sessions Can see all Survey Sessions

Step 6 - (Optional) Setting up Compatibilies

The Following Settings can be setting up in the local.py

Setting Name Descriptioon Default
BELT_RADAR_APP_NAME Set the name of the APP "Belt Radar"
BELT_RADAR_TASK_TIME_LIMIT Defines the time (in seconds) a task will timeout 1200
BELT_RADAR_WEBHOOK_URL Defines URL for Webhook notification None

Translations

Translations

Help us translate this app into your language or improve existing translations. Join our team!"

Contributing

You want to improve the project? Please ensure you read the Contribution Guidelines

Metadata

Release files for aa-beltradar 2.0.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aa-beltradar 2.0.1
File Size Uploaded Provenance
aa_beltradar-2.0.1.tar.gz 1.9 MB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for aa-beltradar 2.0.1
File Interpreter ABI Platform
aa_beltradar-2.0.1-py3-none-any.whl Python 3 none any Details

Total release size: 3.8 MB

Release files / aa_beltradar-2.0.1.tar.gz

Download URL aa_beltradar-2.0.1.tar.gz
Size 1.9 MB
Tags Source
SHA-256 checksum
How to use checksums
d0d08cdd0a2c7948fc68ca6f4af20324846a7d77b6e8ee2149c944044d5dbc5d
BLAKE2b-256 checksum
How to use checksums
f9a4efd41707c20564ae7df9872dc1bb9d410c2279c4cf30b93b546223df0d02
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

Release files / aa_beltradar-2.0.1-py3-none-any.whl

Download URL aa_beltradar-2.0.1-py3-none-any.whl
Size 2.0 MB
Tags Python 3
SHA-256 checksum
How to use checksums
d907e79493381e8604d7e2a963eeddd82c39589bff3fe6044c357e31da95defc
BLAKE2b-256 checksum
How to use checksums
15eb4d0264853e4ae1a91c92f9778d71d3dc9c1278c4fdf4c20e02bb49237cfc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

Security for aa-beltradar 2.0.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for aa_beltradar-2.0.1.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 18, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page