FarEarth Edge overview

1. Deployment options

• The current FarEarth Edge application is made available via container images for ARM64 and AMD64 platforms
• Other deployment options, such as native installation, can also be explored upon request
• In addition to the container images, processing ancillaries and calibration files are also required
• The size of the exported container image is approximately 580 MB
• All of which are made available on the FarEarth Cloud Platform

2. Deployment layout

The file locations inside the container image are organised as follows

Item	Description	Default location	Approximate size
FarEarth application	The FarEarth Edge binary	/opt/farearth/farearth	10 MB
Configuration files	Geometric calibration parameters	/var/farearth/calibration/**	100 KB
	Radiometric calibration parameters	/var/farearth/calibration/**	100 MB
Ancillary database	FarEarth Pernix spatial index	/var/farearth/pernix/**	2 GB
	Ground reference imagery chip archive	/var/farearth/pernix/**	50 GB
	Digital elevation model archive	/var/farearth/pernix/**	80 GB
	Planetary ephemeris archive	/var/farearth/pernix/**	100 MB

2.1. FarEarth application

• The FarEarth application and its runtime dependencies are tied to the version of the parent container image
• As such, a new container image upload will be necessary to update the application
• FarEarth Edge follows SemVer versioning, with the current version being 2.0.1:
  • Major version: 2
  • Minor version: 0
  • Patch version: 1
• Security and bug fixes will accompany patch releases
• While larger feature updates will be associated with minor version changes
• Major version changes will reflect significant updates which may not be backward compatible

2.2. Configuration files

• Every individual spacecraft and its individual sensors require unique calibration files
• FarEarth splits this into geometric and radiometric calibration files
• Initial uncalibrated files are available for pre-flight deployment
• Updates to the files will be available after in-flight calibration has been completed
• Subsequent updates will be available as continuous calibration is performed
• All configuration files are available in the FarEarth Cloud Platform
• It is recommended that the /var/farearth/calibration directory inside the container is mounted to a persistent local volume

2.3. Ancillary database

• The FarEarth Pernix spatial database consists of a single index file with adjacent archive directories
• Most data does not need to be updated once available on the target device
• It is recommended that it is uploaded pre-launch
• The total number of individual files will be in the order of around 200 individual zip files, depending on which archives are included
• Some planetary ephemeris processing ancillaries might require updates post-launch
• However, the upload size should be less than a few MB, and will only be necessary about once a year
• The ground reference imagery archive is only necessary if precision geolocation is required
• While the digital elevation model archive is required for terrain correction
• Both can be omitted if only systematic processing is necessary
• The resolution of the reference imagery can also be customised depending on the required processing accuracy
• The size of the archive can also be pruned by only including data over specific geographic areas
• It is recommended that the /var/farearth/pernix directory inside the container is mounted to a persistent local volume