Attribute, where you can specify importer's side unique id for various objets in data import. Can be used to later modify previously imported data.
Atribūts, kurā var norādīt importētāja puses unikālu identifikatoru dažādiem objektiem datu importā. Izmantojams, lai vēlāk varētu modificēt iepriekš importētus datus.
Attribute "name" has to be a predefined custom field name in the system. Custom fields with unrecognized names will be ignored.
Atribūtam "name" jāsatur iepriekš sistēmā definētas specializētās vērtības nosaukums. Specializētās vērtības, kuru nosaukums netiks atpazīts, tiks ignorētas.
The daily report (<daily> element) returns data for the chosen period, grouping the data by days. The element consists of one or several <day> sub-elements, representing the data about respective day, as well as total calculations for the selected period.
Atskaite "pa dienām" (<daily> elements) atgriež mašīnas datus par izvēlēto periodu, sagrupējot datus pa dienām. Elements sastāv no viena vai vairākiem <day> apakš-elementiem, atgriežot datus par attiecīgo dienu, kā arī kopējos aprēķinus par izvēlēto periodu.
Odometer import can contain one or more <odometer_value> elements. Each <odometer_value> element must contain <car_reg_no>, <date>, <distance> and <recalculate_period> fields.
Odometra imports drīkst saturēt vienu vai vairākus <odometer_value> elementus. Katram <odometer_value> elementam obligati ir jāsatur <car_reg_no>, <date>, <distance> un <recalculate_period> laukus.
When exporting routes from SkyFMS system, one can get information about stopping points of car and driven routes between those points. When exporting data about specified time period, one <route> element is returned for each car. This element contains one or more <route_stopping> (describes stop point), <route_driving> (describes driving) and <route_dataloss> (describes data loss) sub-elements.
Eksportējot ceļazīmes informāciju no SkyFMS sistēmas, tiek atgriezta informācija par transportlīdzekļu stāvēšanas punktiem un brauktajiem maršrutiem starp šiem punktiem. Eksportējot datus par norādīto laika periodu, katram transportlīdzeklim tiek atgriezts viens <route> elements, kurš satur vienu vai vairākus <route_stopping> (apraksta stāvēšanu), <route_driving> (apraksta braukšanu) un <route_dataloss> (apraksta datu zudumus) apakšelementus.
SkyFMS data import/export document contains <skyfms> root element, followed by one or more refuelings (<fuel_in>), objects (<object>), routes (<route>), task routes (<task_route>) odometer values (<odometer_value>) and/or speedings reports(<speedings_report>).
SkyFMS datu importa/eksporta dokuments satur <skyfms> saknes elementu, kam seko viena vai vairākas degvielas uzpildes (<fuel_in>), objekti (<object>), ceļazīmes (<route>), darba uzdevumi (<task_route>) odometra vērtības (<odometer_value>) un/vai ātruma pārkāpumu atskaites(<speedings_report>).
For task route import, XML document must contain one or more <task_route> elements with one or more <task_target> sub-elements.
When exporting task route information from SkyFMS system, one can get information about previously imported or manually created task routes. In exported task routes, <task_target> elements will contain the same id value as specified in import.
Darba uzdevumu importam XML dokumentā jāievieto viens vai vairāki <task_route> elementi, kas satur vienu vai vairākus <task_target> apakšelementus.
Eksportējot darba uzdevumu informāciju no SkyFMS sistēmas, tiek atgriezta informācija par iepriekš importētajiem vai sistēmā manuāli ievadītiem darba uzdevumiem. Atgriežot informāciju par importētajiem darba uzdevumiem, <task_target> elementiem tiek norādīta tāda pati id atribūta vērtība, kāda ir bijusi importā.
value comes from list: {'wgs84'|'degrees'|'lks92'|'object_ref'|'address'}
Documentation
Specifies format for point element. Possible values:
* wgs84 - Semicolon separated longitude and latitude in WGS84/NMEA format. Example: "5601.0318,N;01211.3503,E".
* degrees - Semicolon separated longitude and latitude in degrees. Example: "56.01755;12.19302".
* lks92 - Semicolon separated X and Y coordinates in LKS-92 (1992. gada Latvijas ģeodēziskā koordināšu sistēma) format. Example: "433500;357011".
* object_ref - Reference to a previously imported object. Not possible in object import. Example: "OBJECT_1".
* address - Address, specifying street and number (or house name) and then, after comma, a region (for example, town, village). Example: "Rūpniecības iela 52, Rīga".
Nosaka formātu <point> elementam. Iespējamās vērtības:
* wgs84 - Ar semikolu atdalīts garums un platums WGS84/NMEA formātā.
* degrees - Ar semikolu atdalīti garuma un platuma grādi.
* lks92 - Ar semikolu atdalītas X un Y koordinātes 1992. gada Latvijas ģeodēziskajā koordināšu sistēmā (LKS-92).
* object_ref - Norāde uz sistēmā jau esošu objektu. Nav iespējams objektu importā.
* address - Adrese, vispirms norādot ielu un numuru (vai mājas nosaukumu), un pēc komata - reģionu (pilsētu, pagastu, ciemu vai novadu).
Value must be an identificator of fuel station owner defined in system. In case value is absent, or non-existent id is provided, fuel station owner will be indicated as "Cits". The defined identificators can be found at "http://www.skyfms.com/client_www/index.php?tool=Public&subtool=station_owners&action=list"
Vērtībai jāsatur sistēmā definētas DUS identifikators. Vērtības neesamības vai sistēmā neeksistējošas vērtības gadījumā DUS tiks norādīts kā "Cits". Definētie identifikatori atrodami "http://www.skyfms.com/client_www/index.php?tool=Public&subtool=station_owners&action=list"
The XML Instance Representation table above shows the schema component's content as an XML instance.
The minimum and maximum occurrence of elements and attributes are provided in square brackets, e.g. [0..1].
Model group information are shown in gray, e.g. Start Choice ... End Choice.
For type derivations, the elements and attributes that have been added to or changed from the base type's content are shown in bold.
If an element/attribute has a fixed value, the fixed value is shown in green, e.g. country="Australia".
Otherwise, the type of the element/attribute is displayed.
If the element/attribute's type is in the schema, a link is provided to it.
For local simple type definitions, the constraints are displayed in angle brackets, e.g. <<pattern = [1-9][0-9]{3}>>.
If a local element/attribute has documentation, it will be displayed in a window that pops up when the question mark inside the attribute or next to the element is clicked, e.g. <postcode>.
Abstract(Applies to complex type definitions and element declarations). An abstract element or complex type cannot used to validate an element instance. If there is a reference to an abstract element, only element declarations that can substitute the abstract element can be used to validate the instance. For references to abstract type definitions, only derived types can be used.
Collapse Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32). Then, collapse contiguous sequences of space characters into single space character, and remove leading and trailing space characters.
Disallowed Substitutions(Applies to element declarations). If substitution is specified, then substitution group members cannot be used in place of the given element declaration to validate element instances. If derivation methods, e.g. extension, restriction, are specified, then the given element declaration will not validate element instances that have types derived from the element declaration's type using the specified derivation methods. Normally, element instances can override their declaration's type by specifying an xsi:type attribute.
Nillable(Applies to element declarations). If an element declaration is nillable, instances can use the xsi:nil attribute. The xsi:nil attribute is the boolean attribute, nil, from the http://www.w3.org/2001/XMLSchema-instance namespace. If an element instance has an xsi:nil attribute set to true, it can be left empty, even though its element declaration may have required content.
Prohibited Derivations(Applies to type definitions). Derivation methods that cannot be used to create sub-types from a given type definition.
Prohibited Substitutions(Applies to complex type definitions). Prevents sub-types that have been derived using the specified derivation methods from validating element instances in place of the given type definition.
Replace Whitespace PolicyReplace tab, line feed, and carriage return characters with space character (Unicode character 32).
Substitution GroupElements that are members of a substitution group can be used wherever the head element of the substitution group is referenced.
Substitution Group Exclusions(Applies to element declarations). Prohibits element declarations from nominating themselves as being able to substitute a given element declaration, if they have types that are derived from the original element's type using the specified derivation methods.
Target NamespaceThe target namespace identifies the namespace that components in this schema belongs to. If no target namespace is provided, then the schema components do not belong to any namespace.