# Evaluating Schematic Route Maps: Experimental Raw Data The files in this folder contain the whole data collected in the experiment. They are divided in two folders according to the the Tasks (RIO and Driving) plus some extra files in the root folder: 1.RIO: route instruction ordering task 2.Driving (navigation): driving task 3.Additional Files: R Scripts and other Data Frames in the root folder. ## 1. RIO Task Folder ### 1.1 RIO data Data collected from the RIO app. It contains the logs of the map usage. File names example: RIO-P21-route1-back: rio map use logs back way (collected from the app) RIO-P21-route1-out: rio map use logs outward way (collected from the app) Fields descriptions (non-trivial fields): interaction: log count iZoomScale: scale before the interaction eZoomScale: scale after the interaction topLeftX, topLeftY,bottomRightX,bottomRightY: Limits of the map on the viewport(what is visible). finger1X, finger1Y,finger2X,finger2Y: touch location of the fingers, used only for the navi experiment Compact fields: full_interaction:aggregated interactions coutn:number of aggregate logs in the full interaction duration: duration of the full interaction delta_time: time lapsed since last full interaction total_pan: pan in pixex of the full interaction init_zoom: scale before the full interaction final_zoom: scale after the full interaction topLeftX, topLeftY,bottomRightX,bottomRightY: Limits of the map on the viewport(what is visible). ### 1.2 Placement Rio Data collected from the recall and placement (memorability test) after the RIO task Fields descriptions (non-trivial fields): isFake: tells if the lm is foil recalled: did the participant recalled this landmark correctRecall: was the recall correct originalX, originalY: original location of the landmark userX, userY: user placement location distanceMap: dist from placement to original position confidence: User confidence of the placement ### 1.3 Placement Maps RIO Final maps of the placement. This maps are used to check if the placement were in the correct region (topology) The landmarks in red are the one placed by the user, the red line points to the original position of the landmark. ## 2 Driving (Navigation) Task ### 2.1 Navi Data Data collected from the Navigation app. It contains the logs of the map usage. Field descriptions: type: type of the log (interaction, show map or hide map) newTouch: is the log a new touch finger1X, finger1Y,finger2X,finger2Y: touch location of the fingers carX,carY,gpsLat,gpsLon,carSpeed: Position of the car icon, the map, location on the driving simulator, and car speed. ### 2.2 Plancement Navi Data collected from the recall and placement (memorability test) after the Driving task Fields descriptions (non-trivial fields): isFake: tells if the lm is foil recalled: did the participant recalled this landmark correctRecall: was the recall correct originalX, originalY: original location of the landmark userX, userY: user placement location distanceMap: dist from placement to original position confidence: User confidence of the placement ### 2.3 Placement Maps Navi Final maps of the placement. This maps are used to check if the placement were in the correct region (topology) The landmark in red are the one placed by the user, the red line points to the original position of the landmark. ### 2.4 Car Data Contains the logs register by the UNITY application. Contains information such as the car positions, wrong turns, and set backs (when the driver does out of the street and needs to set back on track) #### 2.4.1 Continuous UNITY logs on every second #### 2.4.2 Checkpoints (not used at all in the analysis) UNITY logs every time the drives crosses a route checkpoint ## 3 Additional Files: R Scripts and other Data Frames in the root folder. ### 3.1 Data frames: #### 3.1.1 df_landmarks This data frame contains information about the landmarks in the route maps. Description of the relevant fields: route_name: landmark's route (route1 or route2) landmark: landmark name lm_id: landmark id lm_short: short name shape: polygonal or pointlike type: global, local or at decision point posX,posY: position on non-schematic map x_posX,x_posY: position on schematic map lat,lon: geographic coordinates rio_mentioned: is the landmark mentioned in the RIO textual instructions visible_from_route,repeated: is the landmark visible from the route #### 3.1.2 df_topology_to_check_navi_1to54_filled2 & df_topology_to_check_rio_1to54_filled2 Those data frames were created from the analysis from placement maps generated from the placement after the Driving and the RIO tasks. It tells about the topological correctness of the placement of each landmark. Description of the relevant fields: file_id: id of the placement file route: route of the landmark participant_id: participant id that made this landmark placement lm_id: type.y: global or local right_side: was placed on the right side of the route? right_region: was the landmark placed on the right topological region? ### 3.2 R scripts used to process the raw data and create final data frames (aggregate and tyde data) used in the result analysis. #### 3.2.1 LoadNaviFilesScript.R R Script that loads Navi Data (Map application logs from the driving task). This script produces the following data frame used in the Result analysis: "df_navi_tidy_by_participant.RDS" #### 3.2.2 LoadRIOFilesScript.R R Script that loads RIO Data (Map application logs from the driving task). This script produces the following data frame used in the Result analysis: "df_rio_tidy_by_participant.RDS" #### 3.2.3 LoadPlacementDataScript.R R Script that loads Placement RIO and Placement Navi(Driving). This script produces the following data frames used in the Result analysis: "df_placement_rio_short.RDS" (d2_rio dataframe in the results analysis) "df_placement_navi_short.RDS" (d2_navi data frame in the results analysis) #### 3.2.3 LoadCarFilesScript.R R Script that loads the Car Data in the continuous folder. It is used to get the number of wrong turns made by each participant. The number of wrong turns are added to the "df_navi_tidy_by_participant.RDS" data frame using the result analysis. #### 3.2.4 LoadTopologyTableScript.R R Script that reads the df_topology_to_check_navi_1to54_filled2 & df_topology_to_check_rio_1to54_filled2 data frames. It is used to get the information if the landmarks were placed in the right topological region. This information is added to the "df_placement_rio_short.RDS" & "df_placement_navi_short.RDS" data frames used in the result analysis.