-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implementing MODES OF OPERATION from FU 44 #379
Conversation
Things we don't want to do are now in: #380 |
49fe0fa
to
025e046
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to wait for our discussion and the solution for demandResponsive
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry I'm late to this discussion, and try to catch-up
To Malte: demandResponsive is not always Continuous; for example Virtual Lines are demandResponsive and have schedules. You can't really link them as both situation occur. And to me that sounds really weird to mess the category just because the attribute we need (GeoPosition) is only in one of these categories.
One other thing I find a bit confusing is that IndividualModesOfOperationEnumeration and PrivateModesEnumeration ere in fact compbinations of (vehicle)mode and mode of operation. Also in PrivateModesEnumeration we have things like taxi/appBookedTaxi/sharedTaxi/prebookedTaxi but a single taxi service (mode of operation) can offer all these services (plus hailed taxi, but I guess that this is the "taxi" value), so we are mixing the mode of operation and the booking&service description.
I know that the NeTEx MODEs are far from perfect and often blurry, but I have the feeling that we are replacing a blurry sition by another blurry one.
OJP/OJP_ModesSupport.xsd
Outdated
</xs:annotation> | ||
<xs:restriction base="xs:string"> | ||
<xs:enumeration value="walk"/> | ||
<xs:enumeration value="commuterCarPooling"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this Continuous: there is most often a scheduled pick up time !
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Aurige comes with the pickup being a PLACE and not a SITE ELEMENT. We don't have the tools for that in OJP. So perhaps you want to weight in on that. Perhaps we need to have some enum values in both enumerations "demandresponsive" for TimedLeg (line based) and ContinuousLeg (for area non-stop based). This might also be true for commutercarPooling. Should I update accordingly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
@trurlurl @herlitze @normanoffel @Aurige :
|
MODE_OF_OPERATION.xlsx
Can you pls check quickly and give me your input on that part? |
64ecb1c
to
90ee4ff
Compare
The plan sounds good to me, as far as I understand it:
|
Yes, that's about it. |
OJP/OJP_JourneySupport.xsd
Outdated
<xs:annotation> | ||
<xs:documentation>Contains the Vehicle reference of the vehicle. In Transmodel this may be the VEHICLE Id.</xs:documentation> | ||
<xs:documentation>Reference to an Operating Day.</xs:documentation> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you want to do OPERATING DAY here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
Mapping OJP 1.0 modes to OJP 2.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
!
OJP/OJP_ModesSupport.xsd
Outdated
<xs:documentation>ALTERNATIVE MODE OF OPERATION for SINGLE JOURNEY with a paid driver. Often more than a single SINGLE JOURNEY.</xs:documentation> | ||
</xs:annotation> | ||
</xs:enumeration> | ||
<xs:enumeration value="privateLift"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
did you check this one with a native English speaker ... all the searches I did are connecting PrivateLift to a privately owned lift in your own apartment !!
Also shouldn't this be in PERSONAL MODE OF OPERATION ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
asked native English speakers. No response yet. Moved it to PERSONAL MODE OF OPERATION.
OJP/OJP_ModesSupport.xsd
Outdated
<xs:documentation>Specialisation of the demand responsive ALTERNATIVE MODE OF OPERATION for AREA related offers.</xs:documentation> | ||
</xs:annotation> | ||
</xs:enumeration> | ||
<xs:enumeration value="school"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
School services are in CONVENTIONAL MODES in TM (in fact demand responsive and flexible services too, but these ones are both in CONVENTIONAL and ALTERNATIVE in OJP) ... but that is not a big deal ! (but maybe worth mentioning it somewhere).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moved "school" to ConventionalModeOfOperation.
Updated comments on enum to clarify which might occur in both CONVENTIONAL and ALTERNATIVE MODE OF OERATION:
OJP/OJP_ModesSupport.xsd
Outdated
</xs:annotation> | ||
</xs:element> | ||
<xs:group ref="siri:PtModeChoiceGroup" minOccurs="0" maxOccurs="unbounded"/> | ||
</xs:sequence> | ||
</xs:complexType> | ||
<xs:complexType name="PrivateModeFilterStructure"> | ||
<xs:complexType name="ModeAndModeAndOperationFilterStructure"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ModeAndModeAndOperationFilterStructure or ModeAndModeOfOperationFilterStructure
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
- ModeAndModeOfOperationFilterStructure misspelling - privateLift to PersonalModeOfOperation - Improved comments on some MODE OF OPERATION. Especially when they can be used for ALTERNATIVE MODE OF OPERATION and CONVENTIONAL.
@Aurige privateLift seems ok to the native English speakers. They also want it in AlternativeMode. What do you think? Move it back there? And then it is usage of a different driver that is the main criterion to have something in Alternative and not in Personal. |
Additionally, The association from NAVIGATION PATH to ACCESS MODE should be removed and replaced with an association between NAVIGATION PATH and PERSONAL MODE.
Maybe:

NAVIGATION PATH --> traversable by --> PERSONAL MODE
PERSONAL MODE --> suitable for --> NAVIGATION PATH
Current state of affairs
List in Transmodel
dynamicCarPooling
longDistanceCarPooling
stationlessVehicleSharing
peerToPeerCarSharing
taxicab
sharedTaxi
commercialCarSharing
carSharingClub
cycleSharing
chauffeuredCar
taxi
netex_modeOfOperation_support
Modes of Operation:
scheduled
flexible
alternative
vehicleRental
vehicleSharing
vehiclePooling
personal
other
Enums of SubModesOfOperation:
flexible
<xsd:enumeration value="flexibleRoute"/>
<xsd:enumeration value="flexibleArea"/>
<xsd:enumeration value="demandResponsive"/>
rental:
<xsd:enumeration value="vehicleHire"/>
<xsd:enumeration value="vehicleLease"/>
sharing:
<xsd:enumeration value="carSharingClub"/>
<xsd:enumeration value="peerToPeerCarSharing"/>
<xsd:enumeration value="vehicleSharing"/>
pooling
<xsd:enumeration value="taxi"/>
<xsd:enumeration value="appBookedTaxi"/>
<xsd:enumeration value="sharedTaxi"/>
<xsd:enumeration value="prebookedTaxi"/>
<xsd:enumeration value="chaffeuredVehicle"/>
<xsd:enumeration value="dynamicCarPooling"/>
<xsd:enumeration value="longDistanceCarPooling"/>
personal
<xsd:enumeration value="commuterCarPooling"/>
<xsd:enumeration value="ownCar"/>
<xsd:enumeration value="privateLift"/>
scheduled
<xsd:enumeration value="scheduledService"/>
<xsd:enumeration value="eventBasedService"/>