Optimisation method shortest path #219
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Add additional transfer time.
Rename InfoURL to InfoUrl
* Extend BaseTripMobilityFilterGroup with NoSight At this moment we cannot filter journeys for visibility impaired users. This commit add the filter option.
* Added WaitDuration to ExchangePointsResultStructure
A proto product is a fare product, which shall not be shown to the user directly. Instead it carries fare product related information, which can be processed further. Can be used for tariffing in a distributed environment (e.g. EU-Spirit), where OJP services can deliver only parts of a fare product.
Added DistributorInterchangeId in LegBoardStructure and FeederInterchangeId in LegAlightStructure. This way, an arbitrary identifier for feeding service at alighting and distributing service at boarding can be transported, which is independent from JourneyRef. Using the same interchange IDs means that the interchange is in fact a stay-seated scenario. This can be used in distributed environments (e.g. EU-Spirit) in order to recognize, that two systems refer the same line/service while they still use their own internal references.
In an distributed environment (e.g. EU-Spirit), the process of place identification can be a two-steps process. In the first step, a topographic place (e.g. city, municipality) is identified from the user's input. In the second step, the system related to the topographic place is queried for places. In order to do so, the topographic places from the first step need to carry the information, to which system they relate.
In a distributed environment (e.g. EU-Spirit), a location information request can refer to several regional systems. In order to allow the requesting client to restrict the meant systems, a filter of system IDs can be used in InitialInputStructure.
* Add TravisCI and xmllint scripts automated checks (#68) * Improve Travis xmllint * Use only one find for xsd and xml, remove unused wsdl * Change indent from one space to one tab * Enforce UTF-8 encoding * Use NULL-bytes to separate files when iterating * Remove XMLSpy comments * Use better variable name * Remove tagging from Travis commit script * Make Travis fail commit script on changed ref * Allow Travis to push updates to all branches except master * Travis CI update to fix linting issues Co-authored-by: haeckerbaer <[email protected]>
* Omit unsused requests and responses Deleted LocationInformationRequest, LocationInformationResponse, ExchangePointsRequest, ExchangePointsResponse, FareRequest, FareResponse and their respective structure definitions in order to avoid confusion with the actually used request and delivery structures.
* Change all ResponseContexts to a single structure (the previous abstract) * Introduce LocationInformationResponseContext * ExchangePointResponseContext * FareResponseContext
Added the optional content filters "IncludePlaceContext" and "IncludeSituationsContext" into "TripContentFilterGroup", "TripInfoContentFilterGroup", and "StopEventsContentFilterGroup" with default set to true. This way a requestor may request responses without places or situations stored in the response contexts respectively.
More precise description of the "IncludeCalls" parameter for "TripInfoRequest".
Added optional "NoBoardingAtStop" and "NoAlightingAtStop" to "StopCallStatusGroup" with default set to false. If set to true, these elements show that at a call no boarding or no alighting is allowed respectively.
According to TRANSMODEL a location is only a geographical position, while a place has a location along with other attributes. Within OJP the two terms were used inconsistently. This commit distinguishes the two terms properly. In most cases the term location was replaced by the term place. This applies to type and element names but also to annotations. This commit addresses issue #44.
Previously the published name of a service should have been stored in the element "PublishedLineName" in ServiceGroup. As the term line is misleading here, the element is renamed to "PublishedServiceName". It shall contain the name of a service which is communicated to the customer. Additionally a new optional element "TrainNumber" is introduced which can store the number of a service (usually a train) according to NeTEx.
* Rename OJP_LocationSupport.xsd to OJP_PlaceSupport.xsd * Rename OJP_Locations.xsd to OJP_Places.xsd * Changed the references to renamed files OJP_Places.xsd and OJP_PlaceSupport.xsd.
Set a default value of "anyPoint" for MultiPointType within MultiPointTripPolicyGroup. This default value causes that the response doesn't necessarily have to contain a trip result for each of the given origins or destinations, which is the expected behaviour, if MultiPointType ist not given.
Added an Extension element of type xsd:any in DatedServiceStructure and ContinousServiceStructure.
Added a simple type HierarchyEnumeration. Added a content filter IncludeStopHierarchy into the StopEventContentFilterGroup. This way a requestor can choose, which parts of the stop hierarchy of the referenced place will be included into the StopEvent response. Default is that the server determines which related stops are included, which is the legacy behaviour.
Added types for product category codes and references according to NeTEx and SIRI to OJP_Common.xsd. Added ProductCategoryStructure into OJP_JourneySupport.xsd. Added an element of this type into the ServiceGroup.
In OJP_RequestSupport: added PlacesStructure and changed element Places in ResponseContextStructure accordingly.
Introduced within OJP_JourneySupport.xsd the complex types ServiceArrivalStructure and ServiceDepartureStructure. Changed within CallAtStopStructure, LegBoardStructure, LegAlightStructure, and LegIntermediateStructure the respective element ServiceArrival to the type ServiceArrivalStructure and the element ServiceDeparture to the type ServiceDepartureStructure. Main reason was to eliminate structured elements within an appropriate definition of a complex type, in order to enable automatic documentation generation.
Introduced within OJP_Common.xsd the complex types AreaStructure and LinkProjectionStructure. Changed TopographicPlaceStructure.Area to type AreaStructure. Changed TrackSectionStructure.LinkProjection to type LinkProjectionStructure. Main reason was to eliminate structured elements without appropriate definitions of complex types for enabling automatic documentation.
* Removed annotations in choices * Travis CI update [skip ci] Co-authored-by: Travis CI User <[email protected]>
Remove incorrectly appended dot from element name `MinimumBookingPeriod.`
Co-authored-by: Günter Matthias (IT-SWE-CC3-TS2 - Extern) <[email protected]>
As explained in detail in docs/README.md the rendering of the documentation tables has received a complete overhaul by @jmaerki removing the interim asciidoc step and fixing the known rendering issues. * Mandatory elements in bold (#136) Improve code reuse. * Table for single element types. (#140) * Better build-up of tables to avoid asciidoc syntax problems. (#137) * Enumerations list their possible values. (#134) Fixed a problem with automatic table headers. Fixed a problem with nested structures and table building. * Fixed filename in documentation. (#139) * Typo: Removed trailing dot from element name. (#139) * Full cross-references for all locally defined elements. (#139) * Mandatory elements in bold also on first column. (#136) * Improved anchor and links for schema's h2. (#139) * Enabled section/chapter numbering. (#133) * Unified depth handling. Properly document attributes. * Fixed bad selection for generating text. * Additional column for choices (a-z) as in previous Word-based documentation. (#143) * Separate stylesheet for checking XML Schema conventions or mistakes in the OJP Schemas. (#153) * Just drop the current version * Rewrite of the documentation generation: new stylesheets generate an intermediate XML files and from that directly an HTML file without going through asciidoc.css. ojp-to-asciidoc.xsl is not basically obsolete and can be deleted when all issues are resolved. Refs now resolve their type information. (#138) * Added documentation for the generation process. Cleanup for the stylesheets. Deprecated the old ojp-to-asciidoc.xsl. * Ignore generated intermediate file. * Added link to deployed HTML file on GitHub Pages. * Removed project-specific link again. * Added substitutionGroup attribute handling. * Added some color to check-ojp-schemas.sh. Set exit code based on check results. Integrate into travis CI. (#153) * Typo. (#154) * Added missing options for resolved groups. (#165) * Removed obsolete stylesheet. (#154) * More cleanup according to feedback. (#154)
Both were extensions at SBB to bring more information to the customers. In principle those are view elements.
This reverts commit 1532a7a.
This reverts commit fa683c9.
ue71603
requested review from
skinkie,
Aurige,
herlitze,
kgrimme and
markus-meier-sbb
sgrossberndt
changed the title
|
Documentation updated. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixes: #213