Update LandOps.xml GeoMessage file on Ops Server to use unique _id field instead of unique designation
- Dominant language
- Python
- Stars
- 33
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
The LandOps.xml tracks simulation file doesn't have a unique _id per track as per the GeoMessage 1.1 specification. While the GeoEvent service will always update the features in the database listening to this message, the Vehicle Commander and Squad Leader apps both expect the _id value to be unique in order to update a graphic (not the unique designation field). Therefore those apps show repeated tracks on the display.
Esri Saudi Arabia kindly updated this file so that the _id was unique per track. I've attached the updated file to this Issue.
[newLandOps.zip](https://github.com/Esri/ops-server-config/files/93527/newLandOps.zip)
Contributor guide
Research direction
Read the existing LandOps.xml configuration and compare it with the attached newLandOps.zip file. Verify that each track uses a unique _id as required by GeoMessage 1.1, then confirm the Vehicle Commander and Squad Leader displays no longer show repeated tracks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- xml
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100