Valar Logo
  • Blog
  • Contact
Log inTalk to Sales

Changelog

Updates we ship, in plain language. Hero features first, then the steady stream of improvements, fixes, and API changes that keep mission-critical work moving.

24 July 2026

Observing conditions and two-way area geometry

See the observing conditions on every overflight opportunity

Every AOI overflight opportunity now shows what the acquisition will actually be like, not only when it happens. A new imaging-quality view brings three readings together: the sun-glint angle (how close your viewing direction sits to the Sun's mirror reflection off the target), the Sun at the target (its elevation, bearing, apparent local solar time, and whether the ground was in day, twilight, or night), and the modelled ground sample distance (the size on the ground a single pixel spans, with the full curve and both footprint dimensions). Together they let you weigh lighting and resolution before you task an opportunity. The ground sample distance reading appears once you record a payload's pixel pitch and focal length.

  • Overflight events docs →

Bring areas in from your own tools, and take them back out

Areas of Interest are now a two-way exchange with the tools your team already uses. You can import a boundary straight from a KML or KMZ file (Google Earth's native format) alongside the existing GeoJSON path, replace an existing area's boundary from a file without deleting and recreating it, and export any area back out as GeoJSON or KML. Import also surfaces what it changed or dropped, so the stored area matches the file you supplied.

  • Create an AOI docs →
Improvements
  • Area import validation: a boundary VALAR cannot use (an edge spanning more than 90 degrees, a ring enclosing a pole, or an antimeridian crossing) is now rejected with a specific reason that names the offending part, and an area that can never produce overflights now says so instead of showing an empty list.
  • Boundary density limits: when a boundary has more vertices or pieces than the ceiling, the refusal now names both your file's count and the limit, so you know whether to trim a few points or reach for a different source.
Fixes
  • Measurement upload: uploading measurements for a spacecraft that cannot be resolved now returns a clear "not found" instead of a misleading "forbidden".
  • Conjunctions: a conjunction that disappears while its details are being computed now returns a clean "not found" instead of an error.
API
  • Spacecraft: the list endpoint now accepts NORAD ID, COSPAR ID, name, or an external key as filters, so an integrator holding any of them can resolve a spacecraft's permanent identifier in one call; each spacecraft also carries a settable external key, immutable once set.
  • Payloads: a payload can now carry a detector pixel pitch and an optical focal length, both optional, which feed the new modelled ground sample distance readings.
16 July 2026

Orbit-age trust and self-serve ephemeris reporting

Know when to trust an orbit

Every VALAR product that runs on a spacecraft's orbit (ground-station passes, ground-track and Keplerian plots, area-of-interest overflight, orbital events, attitude, and maneuver planning) now shares one view of how fresh that orbit is. Each spacecraft carries a single orbit-age status (nominal, degraded, or stale), computed the same way everywhere against a staleness threshold you set once in Settings. When an orbit ages past it, products no longer refuse to run: they warn you and let you proceed consciously, or explain plainly why they cannot. When no fresh precise orbit is available, VALAR falls back to the latest public-catalog orbit and says so. A persistent orbit-data-age footer, a cheatsheet status badge, and proactive status-change alerts keep the fleet's trustworthiness visible.

  • Orbit age docs →

Self-serve ephemeris push

Operators with standing orbit-reporting obligations to the Space-Track and EU-SST catalogs can now meet them without leaving VALAR. Set up an ephemeris push task once (choose the spacecraft, the destination catalog, and the cadence) and VALAR builds the orbit ephemeris and delivers it on schedule. No more exporting a file by hand and logging into an external portal every reporting cycle. Each task keeps a delivery history, so you can confirm exactly what was sent and when.

  • Ephemeris push task docs →
Improvements
  • Public-catalog orbit fallback: when a spacecraft's own precise orbit ages out, VALAR now automatically falls back to its latest public-catalog TLE (from Space-Track or CelesTrak) so passes, plots, overflight, and the rest keep working, clearly flagged as running on a fallback orbit instead of going dark.
  • Archived spacecraft stay out of the way: archiving a spacecraft now takes full effect across the workspace. Archived craft drop out of spacecraft pickers and are excluded from orbit determination, overflight, conjunction screening, and alerts, and the spacecraft list defaults to active-only with an Archived badge on the rest.
  • Permanently delete a spacecraft: a new danger-zone flow on the spacecraft detail page lets you permanently remove a spacecraft and all of its data. Before anything is deleted, VALAR shows exactly what will be removed and asks you to type the spacecraft's id to confirm.
  • Faster with large fleets: the Ground Track and Keplerian Elements pages load noticeably faster when many spacecraft are selected.
Fixes
  • Keplerian Elements: opening the Keplerian Elements page no longer gets stuck in a reload loop; the page loads reliably again.
  • Maneuver export: exporting a maneuver plan that contains no maneuvers now produces a valid file instead of an error.
16 June 2026

Areas of Interest and advanced spacecraft components

Areas of Interest

Track the places that matter to your mission. Areas of Interest is a new way to define geographic regions (draw them on the map, enter coordinates, or upload a GeoJSON file) and see exactly when each of your spacecraft can observe them. Overflight predictions use your payload's actual sensor field of view instead of a fixed elevation cutoff, so the access windows reflect what each instrument can genuinely see, and every event flags when the Sun or Moon intrudes into that field of view, calling out the blinded interval so you can filter down to the windows you can actually use.

  • Areas of Interest docs →
  • Overflight events →

Advanced spacecraft components

The Advanced geometry page now lets you build a far more faithful spacecraft model. Add the onboard payloads your craft carries (each sensor with its mounting direction and field-of-view shape), pick a regular-prism bus shape, and configure each solar panel independently (size, mounting, orientation, single- or double-sided). Every change is reflected live in the 3D viewer, and a payload's field of view feeds directly into your overflight predictions.

  • Spacecraft docs →
Improvements
  • Configurable attitude export: export attitude ephemeris in your choice of representation (quaternions or Euler angles), rotation convention, and reference frame including the local-orbital (LVLH) frame, or both representations together, in the standard CCSDS Attitude Ephemeris Message (AEM) format.
Fixes
  • Ground-station passes: the elevation-mask radar plot on the stations page and the New Station dialog displays correctly again.
  • Spacecraft forms: creating or editing a spacecraft now surfaces validation problems clearly instead of failing without explanation.
  • Areas of interest: status and tag filters now also apply to the map, not just the list.
API
  • State Vectors: you can now list state vectors for more than 50 spacecraft in a single request without hitting an error.
27 May 2026

Evaluate CAM candidates against other future conjunctions

Evaluate a CAM candidate's impact on other future conjunctions

After Valar's CAM Optimization wizard picks a candidate avoidance maneuver, you can now check what that maneuver would do to OTHER future conjunctions on the same spacecraft — does it nudge the closest approach further away, does it raise the probability of collision somewhere else, or does it eliminate the encounter altogether? The new Future Impact step shows one secondary conjunction at a time in a side-by-side comparison table that lines up the pre-maneuver and post-maneuver values for miss distance, probability of collision, time of closest approach, and a criticality shield, with the change between them highlighted in safety colours so green always means safer. When a post-maneuver value carries a caveat (covariance frame unsupported, geometry near the horizon edge, aspect-ratio fallback, and so on) the table shows it inline as a badge so you know exactly when to trust the comparison.

  • CAM Optimization →
  • Conjunction computation →
Improvements
  • Reorganized spacecraft detail page — the spacecraft detail page has been rebuilt around fidelity tier: Identifiers, the Cannonball drag-and-SRP model, Advanced geometry, and a Danger Zone for destructive actions each live in their own card you can edit independently. Creating a new spacecraft now happens in a dialog you can open from anywhere in the app, with per-field validation as you type.
  • Reference frame badges on every plot — every frame-bearing plot — ground tracks, orbital-element plots, ephemeris plots, attitude Euler-angle plots, attitude quaternion components — now carries a small badge next to its title naming the reference frame its axes are drawn in, with a tooltip explanation and a link to the reference-frame catalog. The badge updates in lock-step when a plot lets you switch frames mid-session.
  • Spacecraft list performance — listing many spacecraft with detailed advanced-geometry panels is materially faster.
Fixes
  • Maneuver mass calculation — looking up a spacecraft's mass at a maneuver's epoch no longer errors when the spacecraft has no configured dry mass; the lookup returns cleanly instead of crashing the call.
  • Spacecraft NORAD ID editing — editing a spacecraft whose NORAD catalog number arrived as a numeric value (for example from an OPM import) no longer crashes the form; the field is normalised to a string before the editor renders.
  • Midnight timestamps — labels showing the exact moment 00:00:00 UTC now render their date part correctly in every place a timestamp appears.
21 May 2026

Spacecraft attitude modes, visualization, and export

Define, visualize, and export your spacecraft's attitude

Your spacecraft's orientation is now a first-class part of the platform. Choose how each spacecraft points from five built-in modes — Earth-pointing, Sun-pointing, velocity-tracking, inertial-pointing, and free drift — or define your own custom modes, then schedule transitions between them over time. A dedicated attitude workspace plots the resulting quaternions and Euler angles, and you can import or export a complete attitude profile as a CCSDS AEM file to exchange with other ground systems. Attitude feeds the physics too — when a spacecraft has a defined attitude profile, atmospheric drag and solar radiation pressure are computed against how it is actually oriented.

  • Attitude modes overview →
  • Attitude visualization →
  • Attitude ephemeris export →
Improvements
  • Operator-typed drag and SRP areas — set each spacecraft's atmospheric-drag and solar-radiation-pressure cross-sections directly, in square metres, instead of relying on a single derived effective-area value. The two areas are entered independently on the spacecraft's Platform settings and feed straight into orbit predictions.
Fixes
  • Conjunctions — conjunction cards and the alert timeline no longer break when an alert's miss distance is missing or non-numeric; the value is now omitted cleanly instead of erroring the view.
  • State vector import — when an import is rejected, the error notification now shows the specific reason returned by the platform instead of a generic failure message.
  • Spacecraft selectors — the spacecraft filter and picker dropdowns now cap their height and scroll on long fleets, and behave consistently everywhere they appear.
12 May 2026

Doppler (range-rate) measurements in orbit determination

Doppler (range-rate) measurements in OD

Doppler is now a first-class measurement type alongside range and angles. Pick DOPPLER in the OD measurement-type selector, set the two-way convention on each ground-station sensor, and inspect a dedicated Doppler residuals tab on every OD result. CCSDS TDM blocks containing DOPPLER_INSTANTANEOUS rows ingest into the same OD pipeline as range and angles — VALAR normalises the producer-side observable to the internal one-way / two-way MEAN range-rate convention and carries band, transponder-delay, and correction-state metadata through to the solver.

  • Doppler in TDM →
  • Orbit determination →
Fixes
  • TDM measurement imports — multi-block TDM uploads now correctly preserve the sensor ID declared on each block, so per-block measurements no longer collapse onto the first block's sensor.
API
  • Legacy /api-docs Swagger UI retired — the legacy customer-facing OpenAPI group at /api-docs and its Swagger UI have been removed. The current API reference lives at docs.valar.space/api-reference.
4 May 2026

Event triggers and orbital events on the burn plan

Event-driven task triggers

Automated Orbit Determination tasks now support an Event trigger type that fires the moment new measurements arrive — filtered by measurement type, sensor, minimum count, and a debounce window. OD runs automatically as soon as fresh data is ready, so your solutions stay current without operator intervention.

  • Task automation docs →

Burn plan timeline with orbital events

A new timeline view places every burn for every spacecraft on a Gantt-style chart anchored to a UTC axis, with eclipse umbra/penumbra bands, apsis crossings, ascending and descending nodes, and South Atlantic Anomaly transits overlaid as bands and markers — so each burn sits in its full lighting, geometry, and radiation context. A Display popover toggles each event type independently, and a new Export Schedule dialog ships every selected event for a chosen window as a Spacecraft Schedule File (.ssf) for downstream automation and ground-segment handover.

  • Burn plan timeline docs →
  • SSF format reference →
Improvements
  • State vector comparison — place two state vectors side by side on the Keplerian elements page to validate a new orbit determination against a previous solution, sanity-check a freshly imported OPM, or compare your latest fit against a public TLE without leaving the platform.
  • Tasks runs page — every scheduled, manual, and event-driven task run reports into a single filterable Runs page in the Tasks section, giving you a top-level audit trail across spacecraft, status, and trigger source.
Fixes
  • Scheduled orbit determinations — orbit determinations triggered by a task now reliably save their resulting orbit solution and state vector, instead of completing silently without writing the result.
  • Measurements import — TDM uploads with a mix of valid and invalid entries now correctly surface per-file errors so you can see exactly which entries were rejected and why.
  • Orbit solution cleanup — deleting an orbit solution now succeeds in all cases, and OPM imports tolerate a wider range of file formatting.
  • Spacecraft pages — restored full-page scrolling on the spacecraft detail and new-spacecraft pages, which had been clipped under the previous fixed-height layout.
30 April 2026

A new place to follow what we ship

VALAR ships often. From today, every meaningful update lands on this page. Entries are dated, written by humans, and kept short. We post weekly, on the weeks we have something worth announcing. The list below is the canonical record of what we have shipped.

Every entry follows the same shape. A hero block at the top carries the headline change: the one operators should know about that week. Beneath it, three optional sections gather everything else, collapsed by default so the page stays scannable, ready to expand for the parts that matter to you.

Improvements

Refinements to existing capabilities. New options on existing endpoints, additional fields surfaced in the UI, performance gains, and operator flows that work a little better than they did last week. Anything that tightens existing behaviour without changing its contract.

Fixes

Bugs caught and corrected. Regressions reverted, latent issues resolved before they reach a customer. We try to be specific about the failure mode so operators can quickly recognise whether a past surprise has been addressed.

API

Endpoint additions, schema changes, new query parameters, deprecation notices, and any field-level changes that affect API consumers and SDK users. Breaking changes call themselves out explicitly, so anyone integrating with VALAR can spot them at a glance.

A given week may only have Improvements, or only Fixes. Empty sections are simply omitted. Permalinks are stable, so you can bookmark or share an individual entry and the link will keep working as the list grows.

Ready to Transform Your Operations?

Experience the future of flight dynamics with Valar. Get started today and see how we can help you manage your spacecraft more efficiently.

Talk to Sales
Valar Logo

40.4378° N, 3.6795° W
Maria de Molina 39, 28006 Madrid, Spain

© VALAR SPACE, S.L. 2022 - 2026. All rights reserved.

Product

  • Orbits
  • Maneuvers
  • Space Traffic

Resources

  • Documentation
  • Changelog
  • About

Legal

  • Terms of Service
  • Privacy Policy
  • Cookie Policy