Remove an Axis tour stop without deleting its camera preset

Bottom line: Remove the tour membership that is no longer required without assuming the underlying preset should also be deleted. Review the remaining route and any independent uses of that camera position before changing either object.

Source fact: documented behavior

Axis’s Guard tour API distinguishes preset tours, configured from PTZ preset positions, from recorded tours that replay a recorded sequence of PTZ movement.

For a preset tour, the documentation removes a tour entry through its GuardTour.G#.Tour.T# parameter group and separately directs deletion of the camera’s preset position to /axis-cgi/com/ptzconfig.cgi.

For a nonrandom preset tour, Position defines the visiting order from the lowest position value upward, while WaitTimeViewType supplies the unit for WaitTime.

What the source does not establish

Do not apply preset-tour membership operations to a recorded-tour object. Keep deletion of a shared camera preset as a separate approved change. Do not infer uninterrupted coverage from the surviving list of stops, and avoid treating a display-order screenshot as proof of the final camera movement or dwell times.

Applicability questions

• Is this a preset tour or a recorded tour on the actual device?
• Which tour entry refers to the stop being retired?
• Is the underlying preset used by another tour, operator or event workflow?
• Which remaining order and dwell times must the operator accept?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends changing tour membership first and reviewing preset deletion only as a separately scoped lifecycle decision.

1. Read the current tour and match each entry to its referenced preset, position value and dwell-time unit. Record the approved route before editing it. Ask the operator owner to identify the stop being retired and the intended next destination. Check other known consumers of the underlying preset before considering a deletion; mark unreviewed dependencies instead of assuming the preset is unused.
2. In an approved maintenance window, remove only the identified membership through the supported preset-tour workflow. Read the resulting tour configuration back and compare every remaining reference, position value and dwell-time unit with the intended route. Keep random and nonrandom behavior explicit. Do not replace the whole route from an old example merely to remove one entry.
3. Run a controlled observation of the revised tour where authorized. Confirm the visited positions and dwell behavior with an operator, then check that the retained preset remains available to its separately approved consumers. If removing the entry exposes an unacceptable coverage gap, stop the change and restore the approved route or redesign it with the owner. Schedule any underlying-preset retirement independently.

Verification and evidence

Retain the before-and-after membership list, referenced preset identifiers, intended route and observation record. Identify the exact object removed and the objects deliberately retained. Have another reviewer follow the reference from tour entry to preset so the evidence distinguishes a membership change from deletion of the camera position.

Use a proposed desk case in which two tours refer to the same preset and only one tour should lose the stop. Ask the reviewer to choose the narrowly scoped change before any live edit. Treat this as a planning exercise until the device-specific check and authorized movement observation have actually been completed.

Official references

• Guard tour API — Axis Communications; official VAPIX documentation.

Source review completed October 29, 2026. Recheck the official documentation and the deployed device’s capabilities before changing production settings.