Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Itinerary
Itinerary
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 20
    • Issues 20
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PIM
  • ItineraryItinerary
  • Issues
  • #10

Closed
Open
Opened Dec 30, 2019 by Robin Seidel@rseidel

Select active backends by drawing the shape of the trip on a map

This would only be possible if each backend was to provide a polygon for the territory information is delivered for. Now either by using the shape of the trip provided by the tickets imported into itinerary or by sketching out the trip on a map, all backend that intersect would be automatically activated an the rest of them deactivated. This should then reduce the amount of information send back and forward. Such a feature may also be shared with ktrip and make the search list of possible stations a much shorter one.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: pim/itinerary#10