This FAQ addresses the most common questions from LuData users.
It is intentionally concise and will evolve over time based on user feedback.
If your question is not covered here, please contact us at
support@lucisun.be
LuData is a unified data platform developed by Lucisun that provides access to:
LuData is accessible via:
Both access modes rely on the same data sources, processing logic, and usage rules.
LuData is designed for:
In addition to traditional engineering workflows, LuData is well suited for:
LuData provides:
This makes LuData a reliable data layer for LLM-augmented analytics, where models must rely on verifiable inputs rather than inferred or synthetic information.
LuData integrates multiple data sources, including:
Data source selection is handled automatically by the platform.
There is no single satellite that provides optimal coverage and resolution worldwide.
LuData uses a multi-satellite strategy to:
Users do not need to select satellites manually.
LuData currently operates on a monthly update cycle.
At the end of each month:
As a result, the most recent available data typically corresponds to the end of the previous month.
Roadmap note
Lucisun is actively working toward providing near real-time data access, with a target latency of up to a few days for selected variables and regions.
This capability will be introduced progressively as part of future platform updates.
Updates on data freshness improvements will be communicated through the documentation and release notes.
Depending on the service and data availability, LuData supports:
TMY outputs can be also provided on those same resolutions.
Usage is measured using requests (also called credits).
For most data services:
This model reflects the actual data volume processed and delivered.
No.
LuData pricing is based on annual capacity, not per-click billing.
Requests consume capacity progressively as data is accessed.
This approach ensures:
A Site Unit is an internal reference used by LuData to normalize usage across services and use cases.
It corresponds conceptually to:
In practice, a fully exploited site typically represents several hundred requests.
This reference value:
The exact number of requests associated with a Site Unit:
Users only interact with:
The Site Unit is a normalization concept used to ensure fair, predictable, and scalable pricing.
No.
The Web UI and API:
The choice between UI and API depends only on your workflow.
Yes.
You may:
All usage is tracked centrally.
Each user account has:
If you regenerate your token:
This policy ensures security and traceability.
Results are delivered as compressed archives (.zip or .gzip) containing:
Some standard formats are available by default.
If you require:
please contact Lucisun to discuss feasibility.
If you approach or reach your usage limit:
Depending on your plan, options may include:
Usage limits ensure:
They also allow Lucisun to maintain consistent service quality.
Documentation is continuously improved.
If:
please contact support@lucisun.be.
Frequently asked questions are progressively added to this FAQ.
Yes.
Lucisun actively collects feedback from users to:
Feature requests can be sent to support@lucisun.be or via https://wiki.lucisun.com/en/support.
This FAQ is intentionally concise and will grow over time.