MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Shortline_Interchange_Reference",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "61": {
                "pageid": 61,
                "ns": 0,
                "title": "Recover Train Information",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "When 2 trains couple together, only one set of information is saved with the new train so formed. (a train is defined as a single FYM entity, it can be a single car or a number of engines and cars)\n\n\nThis information consists of the following:\n\n1. The Train Symbol\n\n2. The TSAR Reference\n\n3. The Train Originator\n\n4. The Date and Time of Dispatch\n\n5. The notes associated with this train.\n\n6. Block information specified for this train.\n\nItems 3 and 4 are used internally by both FYM and TrainFinder and cannot be entered directly by a player.\n\n\nUsually the information discarded is of no importance. However, there are times when it is important to be able to recover this information and apply it to a train e.g.\n\nA. Following the unintentional coupling of 2 trains (with or without damage)\n\nB. When engines are replaced on a train and the train is to retain it's original identity.\n\nTo assist you with this, FYM stores up to 150 data sets (items 1 to 5 above) and provides an easy and convenient way of applying a data set to a train. Discarded data is not retained for cars being humped.\n\n\n'''A. An unintentional coupling of 2 trains\n'''\nWhile doing some run throughs I didn't notice that the lead train (NS 395-16) was moving slower than the autorack train (NS 28Q-28) and unfortunately the 2 trains coupled - luckily at a relative velocity < 20mph so no damage ensued. (How to handle damaged trains will be covered under s separate topic).\n\nNow I have 1 train NS 395-16 and all the information for NS 28Q-28 has disappeared. Clearly I can't just run this as 1 train (Each was bound for a different destination). So I must get back the original trains including all the information associated with them.\n\n'''A.1 Separate the trains'''\n\nUncouple the 2 trains as you would ordinarily and move them slightly apart. If you select each in turn and open the Train Information form you will notice that both have identical data sets for items 1, 2 and 5 above (Items 3 and 4 will also be identical but not visible to you).\n\n'''A.2 Determine which train has the incorrect information'''\n\nWith the Train Information form open select any unit in the list and click on the History Tab.  The last entry for that unit's History will give the correct Train symbol if this is now different to that which appears in the 'Train:' box (top left) then this is the train with the incorrect information.\n\n'''A.3 Assign the correct information to the train'''\n\nPress the 'i' button in the 'TSAR Data Recovery' section. This will open the Train Name and Information form.\n\nFrom the list of trains in the left hand box, select the one which corresponds to the correct Train Symbol in the unit's History. In this case we select NS 28Q-28. FYM will store up to 150 such data sets in any logon session.\n\nTo apply the selected data set to the train simply press COPY.\n\nYou now have the correct information assigned to both trains involved in this incident. Both trains can now continue on their way.\n\n'''B. Engine replacement and retaining original data'''\nThis section covers the situation where a train arrives at your yard and you decide (for whatever reason) to replace the engines before sending it on it's way.\n\nWhen the engines are attached the train will assume the information of the engines and the original (and correct) information will be discarded. To recover this information you should proceed as in A2 and A3 above. Step A2 may be ignored if you know the original Train Symbol.\n\nIt is important that you use this method rather than just re-applying a TSAR to the train. The player who applies the TSAR is assumed to be the originator of the train. Clearly if a TSAR is re-applied to a train it will invalidate this assumption. So in order that TrainFinder can track a train throughout it's journey from source to destination it is important that the originator and date/time as initially recorded (when the TSAR reference is set) are kept with the train."
                    }
                ]
            },
            "62": {
                "pageid": 62,
                "ns": 0,
                "title": "Second Sections or Extra Trains",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "It is necessary to use a second or extra section symbol on a train. For these cases, edit the symbol (free text) according to the information on this page. The system varies by railroad. In no case should you append a letter to the end of the symbol.\n\n\n==Burlington Northern Santa Fe==\n\nSymbols are a-bbbccc#-%%e:\n\na-train type\n\nbbb-origin\n\nccc-destination\n\n(#) section ID\n\n%%-date originated\n\ne-symbol-specific code\n\n\nPrimary Symbol: a-bbbccc1-%%e\n\nSecond Section: a-bbbccc2-%%e\n\nExtra Section: a-bbbccc3-%%e\n\nNote that these only apply to manifest trains. Intermodal, vehicle and unit trains not referenced below, while using the same format as manifest trains, do not use the same section numbers. Please refer to the individual TSARs for variations. Locals and yard jobs use a different code entirely as can also be seen in the TSARs. \n\nFor some unit trains, BNSF uses a serial number instead of #-%%, starting with 0-01. FYM simulates this by using day-of-year as a default, but you may change it. Increment this serial number by one for each extra train.  Manifest train originating at intermediate points are typically section 4, but may also use section 3.  \nThe last letter is not a section code. The last letter code is an internal mechanism used by BNSF and the logic behind its use has no place in FYM. Its meaning varies from train type to train type and can mean anything from an alternate routing to what kind of commodity a particular work train could be carrying. Please use the section # field for extra trains, not this last-letter code.\n\n\n==Canadian National==\n\nCN symbols are of the form CN AxxxBC-NN (e.g. M30131-29), where \"C\" is the section symbol. For second or extra sections replace the 1 with 2, 3, etc.\n\n\n==Canadian Pacific==\n\nPrimary Symbol: xxx\n\nSecond Section: 2-xxx\n\nThird Section, etc - 3-xxx\n\n\n==CSX==\n\nPrimary Symbol: Qxxx\n\nSecond Section:\tXxxx\n\nFor extra sections of unit trains or yard jobs, select a new job number. Typical choices are to increment the number by one (U243 becomes U244) or substitute 9 for the first digit of the job (Y102 becomes Y902).\n\n\n==Kansas City Southern==\n\nInsert a \"2\" after the main symbol and before the date. For example, second IDAAT is IDAAT2\n\n\n==Norfolk Southern==\n\nPrimary Symbol\t- Extra Symbol\n\n0xx - Rxx\n\n1xx - Mxx\n\n2xx - Ixx\n\n3xx - Wxx\n\n4xx - Xxx\n\n5xx - Yxx\n\n6xx - Zxx\n\n7xx - Qxx\n\n8xx - Sxx\n\n9xx - Oxx\n\nFor locals, select a new job number. For example, second A31 could be A99.\n\n\n==Union Pacific==\n\nPrimary Symbol\tExtra Symbol\ntssdd\ttssddX\n\nAdd X after the destination symbol.\n\n==Shortlines and Regionals==\n\nFor shortlines and regional railroads, choose your own system. \n\nSuggestions:\n\n--prepend \"2-\" (like CP)\n\n--prepend \"second \" (like \"second local job\")\n\n--insert a 2 at the end of the symbol but before the date (like KCS)\n\n--change the job number (like CSX)\n\n===Indiana Harbor Belt===\n\nThe IHB has a symbol they use for extra sections (they do not run second sections) for road trains only.\n\nAppend the alpha part of the symbol with an 'X' (example: BA2 would become BAX2)"
                    }
                ]
            }
        }
    }
}