Skip to content
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

Freight (Carriers): Simplify Carriers(Plan)Analysis? #3754

Open
kt86 opened this issue Mar 3, 2025 · 1 comment
Open

Freight (Carriers): Simplify Carriers(Plan)Analysis? #3754

kt86 opened this issue Mar 3, 2025 · 1 comment
Assignees
Labels
maintenance things that should be done to improve code and UI

Comments

@kt86
Copy link
Contributor

kt86 commented Mar 3, 2025

Currently, we have different columns for Shipments and Services in the Analysis.

Image

I think, that it would be sufficient to only have nuOfJobs... with these values, because one Carrier can only handle either Shipments or Services. We could then add a column defining the type of jobs.

The advantage of this would be, in working with the results, e.g. for Visualization / dashboards. We avoid doing things twice for both types.
@rewertvsp What do you think?

(Putting this in the inbox for the hackathon)

@kt86 kt86 added the maintenance things that should be done to improve code and UI label Mar 3, 2025
@kt86 kt86 self-assigned this Mar 3, 2025
@kt86 kt86 moved this to inbox / to discuss in MATSIM advanced weekly hackathon Mar 3, 2025
@rewertvsp
Copy link
Contributor

Yes, we can change this. This also reduces columns, which is fine too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance things that should be done to improve code and UI
Projects
Status: inbox / to discuss
Development

No branches or pull requests

2 participants