Download ppt - WP3 Status Review

GNSS for Innovative road Applications

Company’s

logo

WP3 Status Review

WP 3.2.2 Trials execution: launch of activities

10th March

Lisbon

GNSS for INnovative Road Applications


Company’s

logo21/04/23 Page 2PRESENTATION TITLE VERDANA (9)

• Exhaustive trials campaing started 2nd week of March

• GMV vehicle already performing tests, navteq car will follow soon

• GMV exhaustive trials expected to be finished by last week of march/first of april.

• Navteq trials conclusion to be discussed yet

• Exhaustive trials routes being tested & evaluated

• Slight modifications and possible changes to be submitted to TRL for approval

• Exhaustive routes data, in GINA format, to be submitted daily to Avego for analysis in GMV case, weekly for Navteq

• Possible changes in geo-object to be discussed with TRL

Exhaustive trials


Company’s

logo

End2End Trials

• End2End trials scheduled to be started by last week of march

• OBUs production under course after some delays due to providers related troubles

• All OBUs expected to be installed within March

• End2End core system to be operational by the end of March

• End2End trials volunteers and geo-objects already completed

• OBUs will upload received data in GINA format in a daily basis and stored in the project ftp server

• Possible SW or Data changes to be updated remotely in the OBUs

• Installation and maintenance issues to be deal with by approved installators in the Netherlands.

• Analysis of the data could be performed by Avego once the data begins to be stored in GMV ftp server


Company’s


Development to start after E2E development ends

Fleet Management– GIS Map with real-time vehicle positioning

Incident Management– Automatic detection of time taken from incident detection to arrival

on site. Contract obligations enforcement

– Provide reports with information regarding specific sites and times monitored per day

Still waiting on AENOR authorization for vehicle usage

AENOR trials


Company’s


Enforcement trials not succesfully concluded as scheduled

APRN system integration completed

OBU Enforcement Module not integrated

OBU/APRN Communication Integration to be concluded in remote tests between GMV & GMV-SKY

Remote tests to be started by next week, final live test to be performed after remote tests succesfully concluded

Final tests location to be discussed between GMV & GMV-SKY

Enforcement Trials


Company’s

logo

The following actions have been undertaken by the project team in order to prepare for trials evaluation and reporting:

Data formats and outputs from test vehicles agreed Sample reference (truth) data provided to Avego Geo-Objects provided to Avego Avego analysis HUB set up to perform the following Exhaustive-

trials data analysis:

21/04/23 Page 6PRESENTATION TITLE VERDANA (9)

Preparation for trials evaluation:


Company’s


Preparation for trials evaluation:

Agreed Data Format:

- One File per Journey

- Files will be named as per agreed format

routeId-date-starttime-endtime-deviceId.txt

- Files will have the following fields

Field DescriptionWEEK GPS Week

GPS_SECOND GPS Second

LAT OBE Latitude (WGS84 LatLon)

LON OBE Longitude (WGS84 Latlon)

TRUE_LAT Truth Latitude

TRUE_LON Truth Longitude

DIST Distance measured based on OBE positions

TRUE_DIST Distance Measured based on Truth positions

HPL HPL from EGNOS

NSATS Number of Satallites in View

GEO_OBJECTX 1- in geoobject 0-outside geoobjectAs measured by OBE

TRUE_GEO_OBJECTX

1- in geoobject 0-outside geoobjectAs measured by Truth


Company’s

logo

For each of the OBU configurations the following will be evaluated and analysed against truth:

Charging Performance – (To be confirmed). – Variation in charge, over Geo-Objects/routes/daily runs/entire data

set– Under/over charging assessment inline with GMAR– Under/over charging inline with Dutch targets


Preparation for trials evaluation: Exhaustive


Company’s



Metric Description Calculation Aggregation

Journey Distance Accuracy

Deviation in the overall calculated length of the journey between the truth and test devices.

Truth Distance – OBE Distance

DayRouteOverall

Absolute Journey Distance Accuracy

Absolute value of the distance accuracy.

|Distance Accuracy| DayRouteOverall

Geoobject Distance Accuracy

Deviation in the calculated length of the geoobject usage between the truth and test devices.

(Truth Distance Exit Point – Truth Distance Entry Point) – (OBE Distance Exit point – OBE Distance Entry Point)

DayRouteGeoobjectOverall

Absolute Geoobject Distance Accuracy

Absolute value of the geoobject distance accuracy.

|Geoobject Distance Accuracy|

DayRouteGeoobjectOverall

Each Distance Accuracy metric will be calculated per Journey:


Company’s




Position Accuracy Per epoch distance between the Truth and test positions

Dist( (LAT,LON), (TRUE_LAT, TRUE_LON)

DayRouteOverall

Cross Track Accuracy

Per epoch distance between the test position and line struck thru truth positions.

CrossTrack( (LAT, LON), line(TRUE_LAT, TRUE_LON))

DayRouteOverall

Availability Distribution function of accuracy.

Day Route Overall

Continuity Gaps in time (number and length) in OBE position solutions.

DayRouteOverall

Each metric will be calculated per Journey:


Company’s




TTFF Time between journey start (from file name) and first position solution of OBE.

Day RouteOverall

Journey Start Distance Accuracy

Take the max time to first fix across all journeys and calculate the positional accuracy within this time for all journeys

Day RouteOverall

Journey Start Position Accuracy

As above for position accuracy between the test and truth device.

Day RouteOverall

Each metric will be calculated per Journey:


Company’s


Preparation for trials evaluation: ExhaustiveMetric Description Calculation Aggregation

EGNOS Availability

Distribution function of HPL. HPL DayRouteOverall

Integrity Risk Percentage of readings where the distance between the truth and test positions is greater than the HPL.

Position Accuracy > HPL

DayRouteOverall

Satellites in View Distribution of the count of satellites in view

NSAT DayRouteOverall

Incorrect Geoobject Identification

Distance recorded incorrectly in geoobject as % of overall chargable distance for that geoobject.

Where GEOOBJECT_X = 1TRUTH_GEOOBJECT_X = 0

DayRouteOverallGeoobject

Missed geoobject identification

Distance not recorded in geoobject as % of overall chargable distance for that geoobject.

Where GEOOBJECT_X = 0TRUTH_GEOOBJECT_X = 1

DayRouteOverallGeoobject


Company’s

logo

For each of the OBU configuration (GPS or GPS and EGNOS) the following will be evaluated and analysed over all participants and Geo-Objects:

Position (AVEGO)– Analysis of impact of size of protection levels on Geo-Object

identification (on EGNOS enabled devices) Distance (AVEGO)

– Distance variations from the “truth”– Analysis of variations in distance through Geo-Objects

Availability of satellites per zone/area (CENIT)– Signal interference (e.g. urban canyons)– Signal Occultation (e.g. tunnels)

For the purpose of End-to-end trials where no reference data is available for comparison, “truth” for lengths of Geo-Objects will be derived from map data.


Preparation for trials evaluation: End-to-End


Company’s

logo


Charging (AVEGO)– Analysis of variation in charges for known Geo-Object charges

Driver reaction (Aenor)– Assess driver willingness to change driving habits (questionnaire)– Gather general feedback on charging zones/fees/etc…– For drivers with fixed habits/routes compare data for different days

(e.g. charges, distances) Value Added Services (Aenor)

– Usefulness– Ease of use – Suggested improvements




Company’s

logo


SISNeT (CENIT)– Evaluation of SISNeT as a platform for transmitting integrity

information– Analysis of latency of corrections and its potential impact on real-time

VAS. Interference (CENIT)

– Availability of signal during the trial over whole data set Complexity of installation (GMV) Crossing of the Dutch border (CENIT) Lessons learned (CENIT)




Company’s

logo

Following analysis of trial data by Avego, TRL will produce trial evaluation report as D3.3-Trials data package, evaluation and results report and D3.4-Market trial report (including technical and user-experience assessment)

Expected delivery for of the report is at T0+21


Preparation for trials reporting:


Company’s

logo

Thank you