Update project references

pierotofy · pierotofy · commit 1ecb8deb25ff · 2026-04-16T14:06:09.000-04:00
diff --git a/scripts/options-flags.template.md b/scripts/options-flags.template.md
@@ -3,7 +3,7 @@ title: Options & Flags
 template: doc
 ---
 
-This is the complete list of options available in [ODM](https://github.com/WebODM/ODM). 
+This is the complete list of options available in [ODX](https://github.com/WebODM/ODX). 
 
 
 :::note
diff --git a/scripts/update_options_flags.py b/scripts/update_options_flags.py
@@ -4,12 +4,12 @@
 from string import Template
 
 SCRIPT_DIR = os.path.dirname(__file__)
-DEFAULT_URL = "https://raw.githubusercontent.com/WebODM/ODM/master/opendm/config.py"
+DEFAULT_URL = "https://raw.githubusercontent.com/WebODM/ODX/master/opendm/config.py"
 
-parser = argparse.ArgumentParser(description='Extract ODM arguments and generate a Markdown reference page.')
+parser = argparse.ArgumentParser(description='Extract ODX arguments and generate a Markdown reference page.')
 parser.add_argument('input', type=str, nargs='?',
                     default=DEFAULT_URL,
-                    help='URL to ODM\'s config.py')
+                    help='URL to ODX\'s config.py')
 args = parser.parse_args()
 
 url = args.input
@@ -116,7 +116,7 @@ def get_opt_choices(opt):
 
 # --- build markdown ---
 
-print("Found %s ODM options" % len(options))
+print("Found %s ODX options" % len(options))
 
 if len(options) == 0:
     print("No options found")
diff --git a/src/content/docs/architecture.md b/src/content/docs/architecture.md
@@ -5,9 +5,9 @@ template: doc
 
 [WebODM](https://github.com/WebODM/WebODM) is composed of several components.
 
-- [ODM](https://github.com/WebODM/ODM) is a command line toolkit that processes aerial images. Users comfortable with the command line are probably OK using this component alone.
-- [NodeODM](https://github.com/WebODM/NodeODM) is a lightweight interface and API (Application Program Interface) built directly on top of [ODM](https://github.com/WebODM/ODM). Users not comfortable with the command line can use this interface to process aerial images and developers can use the API to build applications. Features such as user authentication, map displays, etc. are not provided.
-- [WebODM](https://github.com/WebODM/WebODM) adds more features such as user authentication, map displays, 3D displays, a higher level API and the ability to orchestrate multiple processing nodes (run jobs in parallel). Processing nodes are simply servers running [NodeODM](https://github.com/WebODM/NodeODM).
+- [ODX](https://github.com/WebODM/ODX) is a command line toolkit that processes aerial images. Users comfortable with the command line are probably OK using this component alone.
+- [NodeODX](https://github.com/WebODM/NodeODX) is a lightweight interface and API (Application Program Interface) built directly on top of [ODX](https://github.com/WebODM/ODX). Users not comfortable with the command line can use this interface to process aerial images and developers can use the API to build applications. Features such as user authentication, map displays, etc. are not provided.
+- [WebODM](https://github.com/WebODM/WebODM) adds more features such as user authentication, map displays, 3D displays, a higher level API and the ability to orchestrate multiple processing nodes (run jobs in parallel). Processing nodes are simply servers running [NodeODX](https://github.com/WebODM/NodeODX).
 
 ![webodm](https://cloud.githubusercontent.com/assets/1951843/25567386/5aeec7aa-2dba-11e7-9169-aca97b70db79.png)
 
@@ -16,5 +16,5 @@ WebODM is built with scalability and performance in mind. While the default setu
 ![Architecture](https://user-images.githubusercontent.com/1951843/36916884-3a269a7a-1e23-11e8-997a-a57cd6ca7950.png)
 
 A few things to note:
- * We use Celery workers to do background tasks such as resizing images and processing task results, but we use an ad-hoc scheduling mechanism to communicate with NodeODM (which processes the orthophotos, 3D models, etc.). The choice to use two separate systems for task scheduling is due to the flexibility that an ad-hoc mechanism gives us for certain operations (capture task output, persistent data and ability to restart tasks mid-way, communication via REST calls, etc.).
+ * We use Celery workers to do background tasks such as resizing images and processing task results, but we use an ad-hoc scheduling mechanism to communicate with NodeODX (which processes the orthophotos, 3D models, etc.). The choice to use two separate systems for task scheduling is due to the flexibility that an ad-hoc mechanism gives us for certain operations (capture task output, persistent data and ability to restart tasks mid-way, communication via REST calls, etc.).
  * If loaded on multiple machines, Celery workers should all share their `app/media` directory with the Django application (via network shares). You can manage workers via `./worker.sh`
diff --git a/src/content/docs/contributing.md b/src/content/docs/contributing.md
@@ -52,7 +52,7 @@ Directories of interest are listed as follow:
 Directory | Description
 --------- | -----------
 `/app`	  | Main application, includes the UI components, API, tests and backend logic.
-`/nodeodm`| Application that bridges the communication between WebODM and [NodeODM](https://github.com/WebODM/NodeODM). Includes its own unit tests and models.
+`/nodeodx`| Application that bridges the communication between WebODM and [NodeODX](https://github.com/WebODM/NodeODX). Includes its own unit tests and models.
 `/webodm` | Django's main project directory. Setting files are here.
 
 ### Frontend
diff --git a/src/content/docs/index.mdx b/src/content/docs/index.mdx
@@ -12,7 +12,7 @@ WebODM has officially decoupled from OpenDroneMap! [Read the announcement](https
 
 :::
 
-[WebODM](https://github.com/WebODM/WebODM) is a user-friendly, commercial grade software for drone image processing. Generate georeferenced maps, point clouds, elevation models and textured 3D models from aerial images. It supports multiple engines for processing, currently [ODM](https://github.com/WebODM/ODM), [MicMac](https://github.com/OpenDroneMap/NodeMICMAC/) and [LGT](https://webodm.net/lgt).
+[WebODM](https://github.com/WebODM/WebODM) is a user-friendly, commercial grade software for drone image processing. Generate georeferenced maps, point clouds, elevation models and textured 3D models from aerial images. It supports multiple engines for processing, currently [ODX](https://github.com/WebODM/ODX), [MicMac](https://github.com/OpenDroneMap/NodeMICMAC/) and [LGT](https://webodm.net/lgt).
 
 ![image](https://user-images.githubusercontent.com/1951843/174504773-f8d8febb-7a45-4d9c-89b6-7d2404c5b8fd.png)
 
diff --git a/src/content/docs/installation.md b/src/content/docs/installation.md
@@ -100,17 +100,17 @@ To install WebODM on a Qnap NAS:
 
 ### Manage Processing Nodes
 
-WebODM can be linked to one or more processing nodes that speak the [NodeODM API](https://github.com/WebODM/NodeODM/blob/master/docs/index.adoc), such as [NodeODM](https://github.com/WebODM/NodeODM), [NodeMICMAC](https://github.com/OpenDroneMap/NodeMICMAC/), [ClusterODM](https://github.com/WebODM/ClusterODM) and [Lightning](https://webodm.net). The default configuration includes a "node-odm-1" processing node which runs on the same machine as WebODM, just to help you get started. As you become more familiar with WebODM, you might want to install processing nodes on separate machines.
+WebODM can be linked to one or more processing nodes that speak the [NodeODX API](https://github.com/WebODM/NodeODX/blob/master/docs/index.adoc), such as [NodeODX](https://github.com/WebODM/NodeODX), [NodeMICMAC](https://github.com/OpenDroneMap/NodeMICMAC/), [ClusterODM](https://github.com/WebODM/ClusterODM) and [Lightning](https://webodm.net). The default configuration includes a "node-odx-1" processing node which runs on the same machine as WebODM, just to help you get started. As you become more familiar with WebODM, you might want to install processing nodes on separate machines.
 
 Adding more processing nodes will allow you to run multiple jobs in parallel.
 
 You can also setup a [ClusterODM](https://github.com/WebODM/ClusterODM) node to run a single task across multiple machines with [distributed split-merge](https://docs.opendronemap.org/large/?highlight=distributed#getting-started-with-distributed-split-merge) and process dozen of thousands of images more quickly, with less memory.
 
-If you don't need the default "node-odm-1" node, simply pass `--default-nodes 0` flag when starting WebODM:
+If you don't need the default "node-odx-1" node, simply pass `--default-nodes 0` flag when starting WebODM:
 
 `./webodm.sh restart --default-nodes 0`.
 
-Then from the web interface simply manually remove the "node-odm-1" node.
+Then from the web interface simply manually remove the "node-odx-1" node.
 
 
 
@@ -159,7 +159,7 @@ To add IPv6, simply run:
 `./webodm.sh restart --ipv6`
 
 Note: When using `--ssl` mode, you cannot pass an IP address to the hostname parameter; you must set up a DNS AAAA record. Without `--ssl` mode enabled, access the site at (e.g., http://[2001:0db8:3c4d:0015::1]:8000). The brackets around the IPv6 address are essential!
-You can add a new NodeODM node in WebODM by specifying an IPv6 address. Don't forget to include brackets around the address! e.g., [2001:0db8:fd8a:ae80::1]
+You can add a new NodeODX node in WebODM by specifying an IPv6 address. Don't forget to include brackets around the address! e.g., [2001:0db8:fd8a:ae80::1]
 
 ## Common Troubleshooting
 
@@ -230,7 +230,7 @@ If a particular hook / signal for your plugin does not yet exist, [request it](h
 
 ## Hardware Requirements
 
-To run a standalone installation of WebODM (the user interface), including the processing component ([NodeODM](https://github.com/WebODM/NodeODM)), we recommend at a minimum:
+To run a standalone installation of WebODM (the user interface), including the processing component ([NodeODX](https://github.com/WebODM/NodeODX)), we recommend at a minimum:
 
 * 100 GB free disk space
 * 16 GB RAM
@@ -257,4 +257,4 @@ A CPU with more cores will speed up processing, but can increase memory usage. G
 
 WebODM runs best on Linux, but works well on Windows and Mac too.
 
-WebODM by itself is just a user interface and does not require many resources. WebODM can be loaded on a machine with just 1 or 2 GB of RAM and work fine without [NodeODM](https://github.com/WebODM/NodeODM). You can use a processing service such as [webodm.net](https://webodm.net) or run NodeODM on a separate, more powerful machine.
+WebODM by itself is just a user interface and does not require many resources. WebODM can be loaded on a machine with just 1 or 2 GB of RAM and work fine without [NodeODX](https://github.com/WebODM/NodeODX). You can use a processing service such as [webodm.net](https://webodm.net) or run NodeODX on a separate, more powerful machine.
diff --git a/src/content/docs/options-flags.md b/src/content/docs/options-flags.md
@@ -3,7 +3,7 @@ title: Options & Flags
 template: doc
 ---
 
-This is the complete list of options available in [ODM](https://github.com/WebODM/ODM). 
+This is the complete list of options available in [ODX](https://github.com/WebODM/ODX). 
 
 
 :::note
@@ -484,7 +484,7 @@ Skip generation of a full 3D model. This can save time if you only need 2D resul
 
 ## skip-band-alignment
 
-When processing multispectral datasets, ODM will automatically align the images for each band. If the images have been postprocessed and are already aligned, use this option.
+When processing multispectral datasets, automatically align the images for each band. If the images have been postprocessed and are already aligned, use this option.
 
 **Default:** `False`
 
diff --git a/src/content/docs/reference/processingnode.md b/src/content/docs/reference/processingnode.md
@@ -13,7 +13,7 @@ template: doc
     "port": 80,
     "api_version": "1.0.1",
     "engine_version": "0.6.0",
-    "engine": "odm",
+    "engine": "odx",
     "last_refreshed": "2017-03-01T21:14:49.918276Z",
     "queue_count": 0,
     "max_images": null,
@@ -30,15 +30,15 @@ template: doc
 ```
 
 Processing nodes are associated with zero or more tasks and
-take care of processing input images. Processing nodes are computers or virtual machines running [NodeODM](https://github.com/WebODM/NodeODM) or any other API compatible with it.
+take care of processing input images. Processing nodes are computers or virtual machines running [NodeODX](https://github.com/WebODM/NodeODX) or any other API compatible with it.
 
 Field | Type | Description
 ----- | ---- | -----------
 id | int | Unique Identifier
 online | bool | Whether the processing node could be reached in the last 5 minutes
 hostname | string | Hostname/IP address
 port | int | Port
-api_version | string | Version of NodeODM currently running
+api_version | string | Version of NodeODX currently running
 engine_version | string | Version of processing engine currently being used
 engine | string | Lowercase identifier of processing engine
 last_refreshed | string | Date and time this node was last seen online. This value is typically refreshed every 15-30 seconds and is used to decide whether a node is offline or not
@@ -56,7 +56,7 @@ help | Description of the option
 name | Name that identifies the option. This is the value you pass in the `name` key/value pair when creating a set of options for a new [Task](/reference/task/)
 type | Possible values are `int`, `float`, `string`, `bool`
 value | Default value if the option is not specified
-domain | Restriction of the range of values that this option allows. Examples are `float`, `negative integer`, `percent`, `float: 0 <= x <= 10`, etc. for all possible values, check [NodeODM's odmOptions.js code](https://github.com/WebODM/NodeODM/blob/master/libs/odmOptions.js#L135)
+domain | Restriction of the range of values that this option allows. Examples are `float`, `negative integer`, `percent`, `float: 0 <= x <= 10`, etc. for all possible values, check [NodeODX's odxOptions.js code](https://github.com/WebODM/NodeODX/blob/master/libs/odxOptions.js#L135)
 
 
 ### Add a processing node
@@ -142,5 +142,5 @@ Display the common options available among all online processing nodes. This is
 
 Use this list of options to check whether a particular option is supported by all online processing nodes. If you use the automatic processing node assignment feature for processing tasks, this is the list you want to display to the user for choosing the options to use during processing.
 
-<aside class="notice">While WebODM is capable of handling processing nodes running different versions of NodeODM, we don't recommend doing so. When all processing nodes use the same NodeODM version, the output of this API call will be identical to the <b>available_options</b> field of any node.</aside>
+<aside class="notice">While WebODM is capable of handling processing nodes running different versions of NodeODX, we don't recommend doing so. When all processing nodes use the same NodeODX version, the output of this API call will be identical to the <b>available_options</b> field of any node.</aside>
 
diff --git a/src/content/docs/reference/task.md b/src/content/docs/reference/task.md
@@ -94,7 +94,7 @@ Parameters are the same as above.
 
 `POST /api/projects/{project_id}/tasks/import`
 
-Import task that have been processed by another WebODM instance (or via [webodm.net](https://webodm.net) or NodeODM)
+Import task that have been processed by another WebODM instance (or via [webodm.net](https://webodm.net) or NodeODX)
 
 Parameter | Required | Default          | Description
 --------- | -------- | -------          | ----------
diff --git a/src/content/docs/tutorials/large-datasets.md b/src/content/docs/tutorials/large-datasets.md
@@ -14,7 +14,7 @@ Split-merge works in WebODM out of the box as long as the processing nodes suppo
 Splitting a dataset into more manageable submodels and sequentially processing all submodels on the same machine is easy! Just use `--split` and `--split-overlap` to decide the average number of images per submodel and the overlap (in meters) between submodels respectively:
 
 ```bash
-docker run -ti --rm -v /my/project:/datasets/code webodm/odm --project-path /datasets --split 400 --split-overlap 100
+docker run -ti --rm -v /my/project:/datasets/code webodm/odx --project-path /datasets --split 400 --split-overlap 100
 ```
 
 If you already know how you want to split the dataset, you can provide that information and it will be used instead of the clustering algorithm.
@@ -33,7 +33,7 @@ will create 3 submodels. Make sure to pass `--split-overlap 0` if you manually p
 
 ## Distributed Split-Merge
 
-WebODM can also automatically distribute the processing of each submodel to multiple machines via [NodeODM](https://github.com/WebODM/NodeODM) nodes, orchestrated via [ClusterODM](https://github.com/WebODM/ClusterODM).
+WebODM can also automatically distribute the processing of each submodel to multiple machines via [NodeODX](https://github.com/WebODM/NodeODX) nodes, orchestrated via [ClusterODM](https://github.com/WebODM/ClusterODM).
 
 ![ClusterODM](/images/clusterodm.webp)
 
@@ -45,25 +45,25 @@ The first step is start ClusterODM:
 docker run -ti -p 3001:3000 -p 8080:8080 webodm/clusterodm
 ```
 
-Then on each machine you want to use for processing, launch a NodeODM instance via:
+Then on each machine you want to use for processing, launch a NodeODX instance via:
 
 ```bash
-docker run -ti -p 3000:3000 webodm/nodeodm
+docker run -ti -p 3000:3000 webodm/nodeodx
 ```
 
-Connect via telnet to ClusterODM and add the IP addresses/port of the machines running NodeODM:
+Connect via telnet to ClusterODM and add the IP addresses/port of the machines running NodeODX:
 
 ```bash
 $ telnet <cluster-odm-ip> 8080
 Connected to <cluster-odm-ip>.
 Escape character is '^]'.
 [...]
-# node add <node-odm-ip-1> 3000
-# node add <node-odm-ip-2> 3000
+# node add <node-odx-ip-1> 3000
+# node add <node-odx-ip-2> 3000
 [...]
 # node list
-1) <node-odm-ip-1>:3000 [online] [0/2] <version 1.5.1>
-2) <node-odm-ip-2>:3000 [online] [0/2] <version 1.5.1>
+1) <node-odx-ip-1>:3000 [online] [0/2] <version 1.5.1>
+2) <node-odx-ip-2>:3000 [online] [0/2] <version 1.5.1>
 ```
 
 At this point, simply use the `--sm-cluster` option to enable distributed split-merge.
@@ -93,7 +93,7 @@ ASR VIEWCMD <number of images> - View command used to create a machine
 !! - Repeat last command
 ```
 
-If the NodeODM instance wasn't active when ClusterODM started, you can perform a `NODE UPDATE`:
+If the NodeODX instance wasn't active when ClusterODM started, you can perform a `NODE UPDATE`:
 
 ```
 # NODE UPDATE
@@ -143,7 +143,7 @@ info: Can write to S3
 info: Found docker-machine executable
 ```
 
-You should always have at least one static NodeODM node attached to ClusterODM, even if you plan to use the autoscaler for all processing. If you setup auto scaling, you can't have zero nodes and rely 100% on the autoscaler. You need to attach a NodeODM node to act as the "reference node" otherwise ClusterODM will not know how to handle certain requests. For this purpose, you should add a "dummy" NodeODM node and lock it:
+You should always have at least one static NodeODX node attached to ClusterODM, even if you plan to use the autoscaler for all processing. If you setup auto scaling, you can't have zero nodes and rely 100% on the autoscaler. You need to attach a NodeODX node to act as the "reference node" otherwise ClusterODM will not know how to handle certain requests. For this purpose, you should add a "dummy" NodeODX node and lock it:
 
 ```bash
 telnet localhost 8080
diff --git a/src/content/docs/tutorials/using-docker.md b/src/content/docs/tutorials/using-docker.md
diff --git a/src/content/docs/tutorials/using-singularity.md b/src/content/docs/tutorials/using-singularity.md
