Citizens of the Imperium

Citizens of the Imperium (http://www.travellerrpg.com/CotI/Discuss/index.php)
-   Software (http://www.travellerrpg.com/CotI/Discuss/forumdisplay.php?f=95)
-   -   Traveller Universe and The Traveller Map (http://www.travellerrpg.com/CotI/Discuss/showthread.php?t=29821)

tancred April 30th, 2013 11:40 AM

Import file for Traveller Universe and The Traveller Map
 
1 Attachment(s)
I only just learned that the Traveller Map can export its sector data files.
Unfortunately, the format that it uses does not match any of the included import filters provided by Traveller Universe. (The files exported by The Traveller Map use much larger fields for the system name and the comments, for example.)

Until now. I built an IEL file that can read the files exported by The Traveller Map and import them into the Traveller Universe database.

A few corrections to the data are still needed; those are below since I can't upload but one file.
Enjoy!

Using the TravellerMap.iel to import Traveller Map files to Traveller Universe
(Rename TravellerMap.iel.txt to TravellerMap.iel.)
1. Put the TravellerMap.iel file into your Universe install folder, wherever the other .iel files are.
2. Register TravellerMap.iel with Traveller Universe Manager.
You must put in an extension for your import files. You can use sec or one of the ones used by the
other iel files, but a unique extension (perhaps map) is suggested. Do NOT put the period before the
extension.

This process must be done only once, the first time you wish to use the import.

Now you are ready to get a sector file, modify it for use by Universe, and import it.

1. Use the Travellermap API to download a sector file by using a URL such as this:
http://www.travellermap.com/SEC.aspx?sector=Gn'hk'r
The text after the = is the sector name, including punctuation (if any).
This opens a web page containing the sector information. Copy the info and paste it into a text file.
Save the file with the extension you used to register the .iel; name it for the sector to make it
easy to keep track of.
2. Cut out all the information at the top, down to this line:
1-25: Name
Paste all that information into another text file and save it, perhaps as sector name-data. This
may contain such useful information as the subsector names, alternate language sector names, etc.
It also contains the allegiance codes, which you need to check before importing the sector.
You can use all the other information after importing.
3. Paste in a sector name tag in this format:
<sector name>
4. If the sector file contains star data (not all do) AND you want to import it (it isn't required), you
must modify it. The Traveller Map exports stellar data in the format F0V (for example); Universe
expects it in the form F0 V (F0spaceV).
A global search and replace is the easiest way to do this.
Watch out for the dwarf codes; D is sometimes found in the UWP and should not be replaced; it will cause
an import error if you do replace it in the UWP.
You will need to handle all the stellar sizes, V, D, I, II, III, IV, etc.
5. Remove any blank lines at the end of the file, below your system data. If you do not they will cause
the import to fail.
6. Verify that the allegiance codes found in your data do not duplicate existing codes already in Universe.
If necessary, you can create new ones.
Note that Traveller Universe IS case-sensitive when dealing with allegiance codes, so that Ve is NOT the
same as VE, for example.
7. Import the file into Traveller Universe.
8. Use the data you saved in step 2 to update alternative sector names, subsector names, etc.

77topaz April 30th, 2013 06:10 PM

Actually, a considerable number of sectors of TravellerMap do have stellar data in the F0spaceV format. Also, you should probably change the name of one of these threads in order to limit confusion etc.

tancred April 30th, 2013 06:20 PM

I saw that after I posted, that some do have spaces in the stellar data.
But the first 20 or so sectors I downloaded, and the last 8 or 10, don't.

In any case, the stellar data isn't required, though Universe will complain if it isn't in the right format.
And it doesn't seem to be able to determine the "world type" without it either.

Frankymole May 2nd, 2013 07:20 AM

I got multiple errors where there was an Ownership hex reference in the remarks ("O:nnnn") - and sadly I'd deleted Solomani Rim from Sample 4, and I don't know how to get back the original now :(

Deleting Ownership and any remarks over 4 characters might work... haven't tried yet...

Here's a sample of the error log:

"IMPORT REPORT
=============

Import File = C:\Program Files\Universe\SolomaniRim.map

New remark = Da
E0106 (aka 0116): This system owned by another (0215)
E0106 (aka 0116): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
New remark = Ph
New remark = Ga
New remark = Fo
New remark = He
New remark = Pi
New remark = Pz
M0302 (aka 0332): This system owned by another (0233)
M0302 (aka 0332): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
A0501 (aka 0501): Lost remark =O:0502
New remark = Oc
A0502 (aka 0502): Invalid remark ((Gurungan)) ... max remark length = 4
A0502 (aka 0502): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
E0508 (aka 0518): This system owned by another (0617)
E0508 (aka 0518): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
New remark = Pa
A0604 (aka 0604): This system owned by another (0704)
A0604 (aka 0604): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
I0604 (aka 0624): This system owned by another (0524)
I0604 (aka 0624): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
M0602 (aka 0632): This system owned by another (0533)
M0602 (aka 0632): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
M0610 (aka 0640): This system owned by another (0639)
M0610 (aka 0640): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
E0707 (aka 0717): This system owned by another (0617)
E0707 (aka 0717): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
I0701 (aka 0721): This system owned by another (0723)
I0701 (aka 0721): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
B0110 (aka 0910): This system owned by another (1110)
B0110 (aka 0910): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
F0102 (aka 0912): This system owned by another (1011)
F0102 (aka 0912): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
J0104 (aka 0924): This system owned by another (0923)
J0104 (aka 0924): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
N0202 (aka 1032): This system owned by another (1034)
N0202 (aka 1032): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
New alignment = IV
N0306 (aka 1136): Lost remark =O:1337
N0310 (aka 1140): Invalid remark ((minor)) ... max remark length = 4
N0310 (aka 1140): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
B0405 (aka 1205): This system owned by another (1207)
B0405 (aka 1205): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
F0404 (aka 1214): This system owned by another (1216)
F0404 (aka 1214): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
New remark = Cs
N0407 (aka 1237): This system owned by another (1339)
N0407 (aka 1237): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
N0409 (aka 1239): This system owned by another (1339)
N0409 (aka 1239): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
F0508 (aka 1318): This system owned by another ()
F0508 (aka 1318): Error = System location error
F0510 (aka 1320): Error = System location error
F0510 (aka 1320): Error = System location error
J0504 (aka 1324): Error = System location error
J0507 (aka 1327): This system owned by another (1326)
J0507 (aka 1327): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
N0605 (aka 1435): This system owned by another (1537)
N0605 (aka 1435): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
B0809 (aka 1609): This system owned by another (1710)
B0809 (aka 1609): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
mC0105 (aka 1705): This system owned by another (1804)
C0105 (aka 1705): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
G0107 (aka 1717): Invalid remark ((Vegans)) ... max remark length = 4
G0107 (aka 1717): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
O0102 (aka 1732): Lost remark =Pz
O0102 (aka 1732): Lost remark =Mr
K0207 (aka 1827): Invalid remark ([Solomani]) ... max remark length = 4
K0207 (aka 1827): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
K0210 (aka 1830): Invalid star data [F0D]
K0309 (aka 1929): Lost remark =Pz
K0309 (aka 1929): Lost remark =Mr
K0410 (aka 2030): This system owned by another (1830)
K0410 (aka 2030): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
O0502 (aka 2132): This system owned by another (1931)
O0502 (aka 2132): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
K0703 (aka 2323): This system owned by another (2227)
K0703 (aka 2323): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
C0805 (aka 2405): This system owned by another (2205)
C0805 (aka 2405): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
G0808 (aka 2418): This system owned by another (2518)
G0808 (aka 2418): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
L0107 (aka 2527): Invalid remark ((Chips)0) ... max remark length = 4
L0107 (aka 2527): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
P0106 (aka 2536): This system owned by another (2636)
P0106 (aka 2536): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
D0203 (aka 2603): This system owned by another (2703)
D0203 (aka 2603): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.

...

D0802 (aka 3202): Error = (-2147217887) Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.
Detail line mask match failure (line 412)

... aborted!"


-----------------
Chopping out Ownership, Remarks over 4 characters, and fixing some spacing glitches gave me the rather shorter error log:


"Import File = C:\Program Files\Universe\SoloRim.map

O0102 (aka 1732): Lost remark =Pz
O0102 (aka 1732): Lost remark =Mr
K0309 (aka 1929): Lost remark =Pz
K0309 (aka 1929): Lost remark =Mr

... done!"


No idea what "Lost remark" means!

77topaz May 2nd, 2013 07:48 AM

I think the "lost remark" comments must be due to the system not knowing those Trade Classifications (which are mainly T5 ones, and thus the system you're using might be out of date).

EDIT: Hmm... it may also signify that there are too many classifications too handle - does the system use fixed field widths? That might be part of the problem.

Frankymole May 2nd, 2013 10:51 AM

Thanks - looking at the Universe database's data card boxes, there only seems to be enough space for 4 trade classifications.

It did accept Pz and Mr for worlds with 4 or less classifications.

I guess I will find out what Pz and Mr mean once the T5 book and CD-ROM arrive on these shores :) Edit: Ah, here they are: http://wiki.travellerrpg.com/Trade_classification. Puzzle sounds interesting.

Out of interest, is there a source somewhere for standard *.SEC or *>TUX files with older rules sets' trade classifications? (The ones that came with Universe are probably good enough, I expect - being from about 2004; I've got a zipped copy of Galactic on my drive too; but it only has about 12 sectors - .SEC files - and Solomani Rim isn't one of them!).

Bit weird about the Ownership issue.

Some discussion about the various types of .SEC files is on this thread, which might prove interesting or useful too when I have time to delve.

tancred May 2nd, 2013 11:19 AM

Universe does only allow 4 Trade classifications, as far as I know, and it also rejects Remarks that are longer than 4 characters.
One of the sectors I downloaded had "Foul-Atmosphered" as a comment, and it choked on that.
I edited the Remarks and added "FA" as a code for that, then changed the long comment to the code and it took it.

I have been able to import systems that were owned by another, and it usually just remarks "This system owned by another."

You should be able to copy the database back in off the CD.
I've tended to backup my database everytime I make a change, in case I do get too many errors and want to roll it back.

Unfortunately, the only way I can think of that you could get back just one sector (SolRim) would be to install the original database under a new name (use the TU Manager if you can), export the sector, then import it into your main database.

If for some reason you can't do that, let me know; I'll be happy to send you the sec file for SolRim. Mine is still the default from the original database.

EDIT: Yes, the import logic for Universe does use fixed field widths, which Hemidian talks about in the linked thread in the previous post.
That was the whole reason for coming up with this IEL file. Traveller Map's widths are different from any of the ones that come with Universe, and I got tired of having to edit the files to make them comply with Universe's "Standard" IEL (which they are closest to).

I've never seen "Lost Remark". The only thing I can think of is that it does only allow a certain number of remarks. The Trade Classifications are normally auto-generated by the program; you can't assign them if you manually enter a system.
The only classifications / Remarks you can enter by hand are the manual ones, like for a Prison planet or one of those.

Oh, and if you import any Zhodani sectors that use the "U" or "F" travel zone codes, you will want to add these 2 lines to the IEL:
Translation=tas_zone,"U","A"
Translation=tas_zone,"F","R"

Hemidian sent me those because those codes throw an error on the import, and you end up having to manually enter the entire system...

Frankymole May 3rd, 2013 07:01 AM

Thanks, I managed to get the sector back from the CD. Re-installing and even renewing the database didn't work, oddly, but pasting it over did. There must be some kind of database cache I didn't manage to find. Anyway, as I've just started up, there wasn't anything customized that I was worried about overwriting.

I would've though "foul atmosphere" didn't need a remark as a polluted atmos must fall under one of the standard codes like 7 or 9!

tancred May 3rd, 2013 10:25 AM

I thought the same thing, but one of the sectors did have that in the remarks.

Glad you got the database back. Just remember to back it up every time you make changes.
I currently have 5 backup copies of mine, since I've doubled it in size by importing sectors off the map.
(No, I'm not paranoid or anything; just a programmer...)

If you do download and import any of the sectors from The Traveller Map, be sure and check the Allegiance codes before you import.
I've found that there is a LOT of overlap; a lot of sectors will use the same code for different entities, and Universe does expect them to be unique.
But since it's case-sensitive, FA is different from Fa, to pick just one example.

Frankymole May 3rd, 2013 10:06 PM

Good point; I think I'll create my own offline updated list of Allegiances so that I can check each new intended import before it goes in.

Is there a nice graphical program anyone can recommend, that can output subsectors to look like the symbols/fonts on the Traveller Map, as Universe doesn't quite match (it has more old-fashioned fonts and jazzy coloured world symbols; also, doesn't show Allegiance codes on the hexes of the displayed subsector maps)?


All times are GMT -4. The time now is 02:00 AM.

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2010-2013, Far Future Enterprises. All Rights Reserved.