Forum:SectorData template

From Traveller Wiki - Science-Fiction Adventure in the Far future
Jump to navigation Jump to search
Forums: Index > Watercooler > SectorData template

As both User:ssteve and User:Maksim-Smelchak have noticed I've been working on the Template:StellarData and the Template:StellarDataQuery. The StellarData template takes all of the data from both the T5 Second Survey data, and the generated information from the Trade Map generator, and puts it into the database in a "Cargo table".

Cargo is, if you have been following along, is part of the Semantic Mediawiki extensions. Cargo specifically allow putting data (like the Survey Data) into the database in a way that is easy to query.

The StellarDataQuery is the base query to format this data into something very nice looking for the individual world page.

What isn't visible from here is the Trade Map Generator (see Trade map summary for the output) is enhanced to generate the data pages and upload them automatically. Right now I'm going through them one by one, so I can find any of the problems, bugs, issue, missing part, etc. The next time I run the Trade map generator process I will be throwing several sectors worth of stellar data pages into the wiki.

There are several clean up tasks that need to be done to make this work smoothly.

  1. Races/summary -> All of the races pages need to have their Infobox Template updated to Template:SophontData. This new template is also a Cargo template, and puts the information into a database table, but the same template also shows the data on the page as well.
  2. Category:Ludography -> Many of the book and magazine entries need to be updated to use Template:InfoboxBook2. This again, is a cargo template, pushing the data into a table in the database. The Template:Ludography cite uses this data to format a correct citation for books, which should be used in the Template:Sources.

I would like to push off the task of updating all the world article with the Template:StellarDataQuery until after I've uploaded the stellar data pages.

If you have feedback on what better we could (or should) capture in these templates, please let me know. It is possible, though sometimes painful, to make changes to data captured in these templates. I would like to do it as few times as possible.

Tjoneslo (talk) 15:39, 17 April 2016 (EDT)

Tjoneslo, I think we should add a climate box.
Maksim-Smelchak (talk) 11:15, 19 April 2016 (EDT)

Nobility Placement & Climate (2016)[edit]

I would like to note that the rough template currently being used:

  1. UWP + synopsis data
  2. description
    1. stellar data
    2. GURPS world data (sometimes)
  3. history
    1. Trade data (sometimes)
    2. historical excerpts
    3. world government excerpts
  4. references
  • Description was designed for astrographical and planetological data that practically doesn't change (gravity, density, etc.)
  • History was designed for sophontilogical (anthropological) data that changes (government, population, economy, etc.)
  • References can use anything including the new citation items. I would like to implement them when they are ready.

The nobility function was designed to fit in the history area. It looks a bit odd under the synopsis in front of description. Wanted to point that out.

Also, climate, a kind of tag (Tp, Co, Ho, etc.) [Temperate, cold, hot, etc.] used for trade codes would be logical to add to the set.

The climate data is readily added using the SJG GURPS Trav data although due to changes it should be reviewed by someone in the know. Planet size changes, etc. sometimes make the original calculations off.

Alphabetical Trade Codes (2016)[edit]

I also wanted to bring up the issue that the trade code sequences are an awful mess. It would make sense to alphabetize them. Na Wa Pi, for instance, could become Na Pi Wa. The irregular and semi-random nature of these codes makes it hard for newer users to know how to allocate them. I have been watching that happen in Knoellighz Sector.

I took a look at the various Trade Classifications -> Summary Synopsis Paragraphs (2015), and totally agree with you. It almost makes sense to redo those trade summaries to make them easier to use. Ssteve (talk) 21:46, 18 April 2016 (EDT)
The automated process that generates the data pages always sorts the list of codes. So the ones that are not in correct order should removed and replaced with ones that are. Also, if the set uses one (or more) of the details codes (see list below) it should be removed (or not created). The SectorDataQuery uses the Template:Trade summary generated codes/paragraphs, not the ones on the big table. So if you have a world with no summary it may be because the Trade summary is missing and should be created according to these rules.
Once we get most of them in, I'll regenerate the Summary Synopsis paragraphs table from the underlying data. I just want to keep the existing table for reference until that task is complete. Tjoneslo (talk) 08:12, 19 April 2016 (EDT)

Could we get a brief rundown[edit]

I think I may have figured it out by trial and error, but I am still not very comfortable on what to put where:

pcode = Planetary trade code (single) vs. codes = Trade codes (Comma list)
What codes are used in details = Details codes (Comma list); Pz and Cp are two of them, are there additional ones?Ssteve (talk) 21:55, 18 April 2016 (EDT)
Trade codes: classic designations made in groups such as Ag Ga Ni Pi, etc. Very common and used on almost every world.
Secondary codes: Not used as commonly, Cp, Cx, Pz, Fo, etc. Also climate codes: Tp. Co, Ho, etc.
Base codes: N, S, W, D, etc. Uncommon.
Maksim-Smelchak (talk) 22:12, 18 April 2016 (EDT)

What you think of as the remarks codes or trade codes are divided into four parts:
* pcode -> Single trade code from: 'As', 'De', 'Fl', 'He', 'Ic', 'Oc', 'Va', 'Wa' -> Used to set the background color behind the name. If two or more apply, selected the rarer one. E.g. As worlds are always Va, but not the reverse. Use As in this case.
* sophonts -> The sophont notifiers. E.g. (Dyrone) for home worlds, DroyW or Droy2 for non-homeworld population. Also a comma separated list if there is more than one.
* details -> A comma separated list of the codes from this list: 'Cp', 'Cx', 'Cs', 'Mr', 'Da', 'Di', 'Pz', 'An', 'Ab', 'Fo', 'Re', 'Sa', 'Tz', 'Lk' -> These are the comment codes. You recommended the climate codes be added to this list, and they will be.
* code -> A comma separated list of the codes, in alphabetic order, that do not go in the sophonts or details list. So the code "As,Lo,Va" should always be in that order.
Hope that makes more sense. Tjoneslo (talk) 08:04, 19 April 2016 (EDT)

Need some help here with colonies[edit]

As you may have noticed; I've been doing some data entry work on Empty Reaches. The question I have is how do I get the "owning" world to show up in the relevant world as per SectorData template?

The SectorData template will show The governance of this world is from when the value in (World)/data |details =O:, but I have tried various formats and cannot get the owning world to show on the relevant (world) page. Ssteve (talk) 05:02, 19 April 2016 (EDT)

Worlds in question are listed below:

0305	Suezkha (world)	O:0206
1905	Daerrdha	O:2103
2204	Rhoe	O:2504
1205	Oesae	O:1106
1306	Larraez	O:1206
2804	Thuellrue	 O:2704
1911	Shaliir	O:2009
2411	Dakamii	O:2009
2816	Khollok	O:3116
1229	Urmair	O:1230
0238	Kali	O:0338
0340	Gagukam	O:0338
1836	Aisha	O:2036
2434	Niketan	O:2036
1039	Dheeraj	O:1139
The layout for the "O:" needs to include a four letter abbreviation of the sector where hex for the world is located. Since you seem to be working in Empty Quarter Sector, your code is "Empt". So all of these need to be updated to "O:Empt-XXXX", where XXXX is the hex number. The longer O: code is valid for cross sector border colonies. For this case the underlying look up template needs to have the sector reference to get the correct world reference to make the link correctly.
Also the link won't show up if the owning world isn't in the database. Tjoneslo (talk) 07:52, 19 April 2016 (EDT)
I have pre-written code that I can share if you wish. Some of the QLI O:codes use a slightly different format.
I also use a C:code for the colonies, which is very helpful when reconciling the O:lists.
Maksim-Smelchak (talk) 11:18, 19 April 2016 (EDT)

Should I insert the C:code even if it isn't listed on the TravellerMap data set? Ssteve (talk) 12:09, 19 April 2016 (EDT) (Things that make you go HMMM...)

The template understands the "C:<sect>-XXXX" similar to the "O:" codes, so please feel free to add them as you see fit. I'm updating the Stellar Data generator to add them to the data set. Tjoneslo (talk) 14:07, 19 April 2016 (EDT)
The C:codes are not currently canon to my knowledge. Thomas would know better. I just find it impossible to reconcile the whole mess without them. Hopefully they will become canon in the future.
Maksim-Smelchak (talk) 14:38, 19 April 2016 (EDT)