|
Flankerk -> KML-INST Tool (11/18/2013 11:28:24 AM)
|
This is a small programme written to allow placemarks in the likes of Google Earth to be quickly imported into Command:-
Attached below is the guide on how to use it:-
KML transfer utility
The KML transfer utility enables you to import positions of real facilities saved as KML in an Earth browser (like Google Earth) to Command.
CREATE KML FILE (IN GOOGLE EARTH)
Start with creating a folder for each .kml you are planning to transfer to Command. If you name the folder with the same name as you are planning to use for the .inst you faciliate your future work. Then start to add place marks for those facilities you will import into Command. The name of the place mark will be transferred to Command and you can choose to use the database name, like:
A/C Open Parking Spot (1x Medium Aircraft)
You could also add a number to the name som that it's possible to identify each unique facility:
A/C Open Parking Spot 1 (1x Medium Aircraft)
Some times the facility has a authentic designation and then it could be used:
A/C Open Parking Spot H 3 (1x Medium Aircraft)
(Sub folders might be used to organize the place marks but the information about the sub folders will not be transferred.)
When you are done in Google Earth then you should save the folder(s) as .kml; conveniently to the Command Modern Air Naval Operations KML Transfer folder.
TRANSFER KML TO RAW INST
Run the KMLTransfer.exe program that you find in the KML Transfer folder. Now you are able to load any .kml file (with the Load KML button) and then you can save the locations as an .inst file (with the Save locs button).
EDIT INST FOR COMMAND
In order to make it possible to import the facilites into Command you will have to edit the raw .inst file; both the file header, footer and the member records.
File header:
{"DB_ID":0, "FormatVersion": 0, "MemberRecords":[
The default DB_ID is 0 but that will not be accepted by Command so you will have to chage it to:
1 for DB3K ("DB_ID":1) or
2 for CWDB ("DB_ID":2)
File footer:
],"ValidFrom":"", "ValidUntil":"", "Name":"", "Comments":""}
The meta information in the file footer is presented in the Import dialog. All these fields could be left empty (""). ValidFrom and ValidUntil are text fields that informs the player which years the facilities should be used and Name and Comments gives additional information.
The information about the individual facilities are found in the member records:
{"Member_DBID": 10000,
"MemberType": "Command_Core.Facility",
"MemberName": "Place mark 1",
"ParentGroupName": "Name of KML",
"Longitude": 0,
"Latitude": 0,
"Altitude": 0,
"Loadout ID": 0,
"Orientation": 0}
Member_DBID is presented in the Database Viewer and if you would like to import Place mark 1 above as a large building you will find this description in the Database Viewer:
#115 - Building(Large) -- Generic(Generic),0-0, -
Member_DBID should then be changed to 115:
"Member_DBID": 115,
(Note that all fields, as well as facility members, must be separated by a comma.)
It's possible to change MemberName from the name of the place mark, given in Google Earth.
ParentGroupName is the name of the .kml folder created in Google Earth. For facility groups, like air bases, this should be the name of the group:
"ParentGroupName": "Airbase Alpha",
For other types of facilities ParentGroupName should be replaced by null:
"ParentGroupName": null,
When you have made these changes you can save the file and move it to desired sub folder in the ImportExport folder.
Jakob Wedman
There is planned to be a demonstration of its use on Baloogan's site.
We could do with year specific files being built up for all areas [8D]
In effect building up air defences and radar sites for each year that imagery is available.
I plan to finish up Chinese defences before moving onto Taiwanese. I am sure there are many others that need doing. (Greece, Turkey, Japan, North Korea, South Korea, Syria, Iran to name a few)
For units in close proximity, such as airbases you normally find you are best off with custom overlays though it is possible to build an airbase in Google Earth then import. The KML tool works at its best when its dispersed objects that need to be imported.
As it picks up the name along with the exact location, you can accurately place say a radar site, name it specifically in Google Earth, and it will be imported with the correct location and name into Command.
From my point of view I find the simplest naming convention is to stick with the classification according to the database.
Flanker
|
|
|
|
