Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railML 2 railML 2
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 50
    • Issues 50
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • railML.orgrailML.org
  • railML 2railML 2
  • Issues
  • #307
Closed
Open
Issue created Mar 17, 2017 by Deleted User@deleted-user

Extension of stop descriptions (de: Erweiterung der Haltezwecke)

Description

It shall be possible to specify all activities that are planned for a stopas part of the stopDescription - e.g. using a fixed list of enumeration values. For this the existing stop activities from different countries shall be analyzed and then unified/merged.

Suggested change:

  • solution has been discussed and agreed during the development phone conferences
  • a sub-element will be introduced to hold the stopActivities

Background

Besides the existing attributes such as @commercial, @stopOnRequest, @onOff, etc. it shall be possible to provide the reason/purpose of stop not just as a free-text field that is currently availble using the attribute @purpose.

Links

  • Forum discussion
  • Mićo Mićić (SBB) (de/en), November 2016: Haltezwecke / Stop descriptions
  • Wiki Documentation
  • TT:stopActivities (NEW)
  • TT:stopActivity (NEW)
  • TT:stopDescription (Needs to be updated when 2.4 is released)

Changes in railML 2.4

All activities taking place during a stop can be documented using the new enumeration values for the type of activity taking place at a stop.

railML elements

The following new elements are available:

  1. railml/timetable/trainParts/trainPart/ocpsTT/ocpTT/stopDescription/stopActivities
  2. railml/timetable/trainParts/trainPart/ocpsTT/ocpTT/stopDescription/stopActivities/stopActivity
  3. railml/timetable/trainParts/trainPart/ocpsTT/ocpTT/stopDescription/stopActivities/stopActivity/@type The following XSD file(s) have been updated:
  4. timetable.xsd
  5. timetableTypes.xsd

Development Branch

In order to facilitate the development a branch of railML 2.3 called 'stop-activity' was created - all ongoing development work for this ticket is done in this branch:

  • railML/railML2/branches/stop-activity stop-activity

Changesets in branch

  • [changeset:"742/railML"] - New branch for stop activity definition.
  • [changeset:"743/railML"] - First version of stopActivity element and enumeration values
  • [changeset:"744/railML"] - Corrected typos
  • [changeset:"770/railML"] - Update of the documentation links for stop activities
  • Diff: 742:770

Changesets in trunk

  • [changeset:"776/railML"] - Merged changes from branches\stop-activity: New element added to , closes #307 (closed)
### Documentation Tasks
* Document the changes for 2.4
* Create the wiki pages for `stopActivities ` and `stopActivity`
Assignee
Assign to
Time tracking

railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany