-
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
Aligning MultiPointTripPolicyGroup with TripPolicyGroup #333
Conversation
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.
There is a BaseTripPolicyGroup
which is used by MultiPointTripPolicyGroup
and TripPolicyGroup
only. In my opinion all elements belonging to both MultiPointTripPolicyGroup
and TripPolicyGroup
should be put into BaseTripPolicyGroup
. With the current state of this change the OptimisationMethod
-choice would be aligned but at least ConsiderElevationData
makes sense in MultiPointTripPolicyGroup
as well, right? With the current definition of ItModesToCover
in my opinion it does not make sense to add it to MultiPointTripPolicyGroup
as well, which would mean all elements are part of BaseTripPolicyGroup
, only TripPolicyGroup
has the additional ItModesToCover
and only MultiPointTripPolicyGroup
has the additional MultiPointType
.
ConsiderElevationData
must be moved in front of ItModesToCover
in order to have it in BaseTripPolicyGroup
, but it was only recently added, so its no big deal, right?
@trurlurl Can you do all the changes according to Stephan or should I do it? And yes: They should be harmonized fully. |
Working on it. |
… to BaseTripPolicyGroup ItModesToCover is left in each PolicyGroup as it has a different meaning (and thus documentation) for MultiPointTripPolicyGroup and TripPolicyGroup
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.
will update again
Does this make sense for a |
I could imagine that it could make sense when distributing a search for monomodal trips by calling OJPMultiPointTripRequest for parts of the trip - and that these parts should also be monomodal. |
@sgrossberndt I think you are right about ItModesToCover. That shouldn't be done in MPTR |
I think we can define MPTR that it is used in the middle of distributed trip planning and I think if one ones monomdal trips through Europe, one does this directly on one iv trip planner. |
Shouldn't the recent additions to the TripParams also be available to MultiPointTripRequest?
OptimisationMethods, ItModesToCover, ConsiderElevationData