Skip manual provider hunting
Search availability from one workflow instead of opening separate catalogues, comparing dates, and copying product metadata by hand.
Opening Lucida
Preparing your satellite workspace
Loading workspace
Preparing account data...
Lucida centralizes satellite acquisition for teams that need consistent, same-footprint subsets without manually searching every provider, downloading scattered products, and rebuilding project history by hand.
Lucida turns map interaction into persistent project memory. Operators can define a point, bbox or shared hex grid tile, then recover the same markers, tile names and products later from their account.
Search availability from one workflow instead of opening separate catalogues, comparing dates, and copying product metadata by hand.
Keep radar, optical, DEM and context layers clipped to the same footprint so they are easier to compare, archive and reuse.
Keep markers, tiles, temporal coverage, jobs and exports attached to the account instead of losing context inside local folders.
Lucida is designed as an expandable acquisition hub. Current workflows can cover the sources below, and additional sensors/providers are planned as the service grows.
Subset outputs keep source metadata while pointing to the generated local files. Teams can inspect image dates, orbit direction, frame, angle and the files available inside each subset.
Lucida connects acquisition, transformation, analysis and delivery in a single interface built for repeated satellite data operations.
Track consistent imagery over the same footprint across time.
Combine radar, DEM and contextual layers around named targets.
Centralize requests, outputs and exports instead of scattering files across folders.
Lucida is designed to evolve beyond acquisition into analysis-ready enhancement and detection workflows over consistent multi-sensor, multi-temporal image stacks.
Sign in to recover your tiles, markers, jobs and exports in the same Lucida environment used to centralize radar, optical and supporting geospatial layers.
Each login opens a private operational space. Users only see the tiles, points, jobs and exports attached to their own Lucida session.
Authenticate with your internal Lucida credentials.
Cloudflare Access Back to landing pageInspect session tiles, products and actions without leaving the workflow.
| Name | Tile | Country | Products | Sensors | Points | Last run |
|---|
| Sensor | Image date | Direction | Orbit | Frame | Angle | Product | Size | Details | Session |
|---|
Follow active processing, sensor progress and recent acquisition history.
Manage persistent project contexts, tiles, markers and acquisition history.
The export starts only after confirmation.
| Login | Name | Tokens | Email verified | Role | FTP export | Advanced features |
|---|
Job history grouped by job and tile.
Lucida centralizes acquisition requests and session tracking for authorized users.
Lucida centralizes satellite acquisition planning, tile-based products, job tracking and project history. The current candidate prepares immutable plans first; provider discovery, processing and export remain separate approval-gated operations.
Depending on the selected sensors and workflow, Lucida can use datasets or services provided by ASF / NASA Earthdata, Google Earth Engine, Copernicus / Copernicus Data Space Ecosystem, JAXA, OpenStreetMap-derived layers, DEM providers and other geospatial data sources.
Availability, licensing, access credentials, latency, processing delays, cloud cover, orbital coverage and product quality depend on the upstream provider. A prepared plan is not an availability result or a guarantee that products can be downloaded or processed.
Lucida interface and session tooling are part of the Missing Aero workflow. Source datasets remain subject to their respective provider terms, attribution requirements, redistribution limits and copyright notices. Lucida is not a replacement for official provider documentation or licensing rules.
Generated products and previews must be validated before scientific, operational, legal or safety-critical decisions. Users are responsible for ensuring that exported data is used according to the applicable upstream terms.