The itinerary table in the visualization frontend has been updated to accept and store the arrivalPos parameter. This data is kept in a newly added hidden cell with the rest of the journey details, making the arrival coordinates easily accessible when triggering an action like visualizing a pickup. It partially addresses issue #107 by ensuring destination coordinate data is retained in the UI.