Is TacticalJSON necessary?

[spatialillusions]

I have so far looked into:

• NVG (both XML and JSON based)
• MSDL
• ADEM

I have also looked into MOGIE but I can't find any final result of that.

So I haven't found anything that I think is easy enough to use, and easy to use in web and thick clients. But if anyone has a good suggestion please tell me, because writing specifications is not the most fun you can have.

What I'm looking for is something:

• Fast and easy to parse in a web browser
• Supported by GDAL so that you can use ogr2ogr to move between formats. (Also supported by GDAL will make it possible to use in most desktop clients, because everyone uses GDAL.)

[kjellmf]

I really like your idea of using GeoJSON as a starting point. Most of the standards that I am aware of use XML (MSDL and C-BML). SISO is currently working on a new version of MSDL and C-BML and some of the material available from the SISO website may be of interest, especially the underlying data model that they use (MIM) https://www.sisostds.org/StandardsActivities/DevelopmentGroups/C2SIMPDGPSG-CommandandControlSystems.aspx

[spatialillusions]

I will check out MIM, would be nice to share concepts with MSDL, at least it should be possible to reuse property names as much as possible.

Update:
Tried to registrer at MIMworld https://www.mimworld.org/portal/projects/welcome/wiki/Welcome, but since I don't have a sponsor or belong to an organization I'm out of luck.

[kerryrobinson]

@spatialillusions Has there been any more movement or interest in this in the last 3 years? I also see the value in using GeoJSON to exchange tactical overlays for the reasons you mention above and I'm wondering if we could find some synergy to validate the need for a new specification like TacticalJSON.