Vistumbler has some command line options, but I'm not sure they would help with an all in one script.
To Import a single vs1 file into a new vistumbler session you can use
There is also command line export options
Export.exe /db="%temp%/Vistumbler/db.mdb" /t=d /f="C:\PathToFile\Output.VS1"
Export.exe /db="%temp%/Vistumbler/db.mdb" /t=z /f="C:\PathToFile\Output.VS1"
Export Detail CSV:
Export.exe /db="%temp%/Vistumbler/db.mdb" /t=cd /f="C:\PathToFile\Output.csv"
Export Summary CSV:
Export.exe /db="%temp%/Vistumbler/db.mdb" /t=cs /f="C:\PathToFile\Output.csv"
Export.exe /db="%temp%/Vistumbler/db.mdb" /t=k /f="C:\PathToFile\Output.kml" /a /d /p (note: /a is active aps, /d is dead aps, /p is the track)
The main issue I think is going to be getting the mdb filename, since each file imported with the command line above is going to be inserted into a new database which you will not know the name of. you could look in %temp%/vistumbler/ for the file, but you won't know which belongs to the file you are importing. I'm sure some tweaks could be made to make this a little better for scripting, like allowing the mdb filename to be set by command line
Export.exe isn't really documented, but you can see all the switchs in the source code
https://github.com/RIEI/Vistumbler/blob ... Export.au3
(look a lines 67 - 128)
The main switches you needs are /t (file type) , /db (the location of the vistumbler database), and /f (the location of the output file). There are other switches needed depending on the file type being created.
EDIT: I have also made some scripts to import a directory of VS1s into an sqlite database or a mysql database when I was working on geocoding kmls that may be helpful
https://github.com/RIEI/Vistumbler/blob ... ortVS1.au3
https://github.com/RIEI/Vistumbler/blob ... _MySQL.au3