ASAsense Documentation (staging) - Recent changes [en]

MediaWiki:Mainpage

Thomas — Wed, 14 Oct 2026 13:54:56 GMT

Main page = English version (logo, sidebar and / link straight to /en)

New page

Main Page/en

PAVEsense - Export Formats/en

FuzzyBot — Wed, 14 Oct 2026 12:07:49 GMT

Updating to match new version of source page

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	We regularly refer to the SCCR indicators. These are the relative indicators macro1, macro2, mega1, mega2 and waviness.		We regularly refer to the SCCR indicators. These are the relative indicators macro1, macro2, mega1, mega2 and waviness.

	For information on the interpretation of the indicators and the convergence criteria, see the [[~~PaveSense~~/en#Kwaliteitsindicatoren\|PAVEsense user manual]].		For information on the interpretation of the indicators and the convergence criteria, see the [[PAVEsense/en#Kwaliteitsindicatoren\|PAVEsense user manual]].

	{\| class="wikitable"		{\| class="wikitable"

PAVEsense - IRI Correlation/en

FuzzyBot — Wed, 14 Oct 2026 12:07:49 GMT

Updating to match new version of source page

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	''Valid from PAVEsense version 8 (November 2024)''		''Valid from PAVEsense version 8 (November 2024)''

	The ASAsense eIRI values are calculated from the road profile measured with the accelerometer in the sensor box. We combine the measurements of the different passes and take the '''average''' eIRI of all passes that meet the [[~~PaveSense~~/en#Convergentie\|convergence criterion]].		The ASAsense eIRI values are calculated from the road profile measured with the accelerometer in the sensor box. We combine the measurements of the different passes and take the '''average''' eIRI of all passes that meet the [[PAVEsense/en#Convergentie\|convergence criterion]].

	==== Comparison with reference measurements in the Port of Antwerp ====		==== Comparison with reference measurements in the Port of Antwerp ====

Main Page/en

FuzzyBot — Wed, 14 Oct 2026 12:07:48 GMT

Updating to match new version of source page

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	== PAVEsense ==		== PAVEsense ==

	The [[~~PaveSense~~/en\|PAVEsense user manual]] explains how to assess and monitor road quality in the PAVEsense portal:		The [[PAVEsense/en\|PAVEsense user manual]] explains how to assess and monitor road quality in the PAVEsense portal:

	# [[~~PaveSense~~/en#Inleiding\|Introduction]]		# [[PAVEsense/en#Inleiding\|Introduction]]
	# [[~~PaveSense~~/en#Kwaliteitsindicatoren\|Quality indicators]]		# [[PAVEsense/en#Kwaliteitsindicatoren\|Quality indicators]]
	# [[~~PaveSense~~/en#Convergentie\|Convergence]]		# [[PAVEsense/en#Convergentie\|Convergence]]
	# [[~~PaveSense~~/en#Automatische_kalibratie\|Automatic calibration and lead time for new data]]		# [[PAVEsense/en#Automatische_kalibratie\|Automatic calibration and lead time for new data]]
	# [[~~PaveSense~~/en#Het_portaal\|The portal]]		# [[PAVEsense/en#Het_portaal\|The portal]]
	# [[~~PaveSense~~/en#De_tabelweergave\|The table view (Data table)]]		# [[PAVEsense/en#De_tabelweergave\|The table view (Data table)]]
	# [[~~PaveSense~~/en#De_kaartweergave\|The map view (Map)]]		# [[PAVEsense/en#De_kaartweergave\|The map view (Map)]]
	# [[~~PaveSense~~/en#Annotaties\|Annotations]]		# [[PAVEsense/en#Annotaties\|Annotations]]
	# [[~~PaveSense~~/en#Exporteren\|Exporting (Export)]]		# [[PAVEsense/en#Exporteren\|Exporting (Export)]]
	# [[~~PaveSense~~/en#Meetdekking\|Measurement coverage (Coverage)]]		# [[PAVEsense/en#Meetdekking\|Measurement coverage (Coverage)]]
	# [[~~PaveSense~~/en#Veelgestelde_vragen\|Tips and frequently asked questions]]		# [[PAVEsense/en#Veelgestelde_vragen\|Tips and frequently asked questions]]

	Further reading:		Further reading:

PAVEsense - Export Formats/nl

Thomas — Wed, 14 Oct 2026 12:07:45 GMT

nl translation

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	We verwijzen geregeld naar de SCCR-indicatoren. Dat zijn de relatieve indicatoren macro1, macro2, mega1, mega2 en waviness.		We verwijzen geregeld naar de SCCR-indicatoren. Dat zijn de relatieve indicatoren macro1, macro2, mega1, mega2 en waviness.

	Voor informatie over de interpretatie van de indicatoren en de convergentiecriteria, zie de [[~~PaveSense~~/nl#Kwaliteitsindicatoren\|PAVEsense-gebruikershandleiding]].		Voor informatie over de interpretatie van de indicatoren en de convergentiecriteria, zie de [[PAVEsense/nl#Kwaliteitsindicatoren\|PAVEsense-gebruikershandleiding]].

	{\| class="wikitable"		{\| class="wikitable"

PAVEsense - IRI Correlation/nl

Thomas — Wed, 14 Oct 2026 12:07:43 GMT

nl translation

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	''Geldig vanaf PAVEsense versie 8 (november 2024)''		''Geldig vanaf PAVEsense versie 8 (november 2024)''

	De eIRI-waarden van ASAsense worden berekend op basis van het wegprofiel dat wordt opgemeten aan de hand van de accelerometer in de sensorbox. We combineren hierbij de metingen van de verschillende passages en nemen het '''gemiddelde''' van de eIRI van alle passages die voldoen aan het [[~~PaveSense~~/nl#Convergentie\|convergentiecriterium]].		De eIRI-waarden van ASAsense worden berekend op basis van het wegprofiel dat wordt opgemeten aan de hand van de accelerometer in de sensorbox. We combineren hierbij de metingen van de verschillende passages en nemen het '''gemiddelde''' van de eIRI van alle passages die voldoen aan het [[PAVEsense/nl#Convergentie\|convergentiecriterium]].

	<span id="Comparison_with_reference_measurements_in_the_Port_of_Antwerp"></span>		<span id="Comparison_with_reference_measurements_in_the_Port_of_Antwerp"></span>

PAVEsense - IRI Correlation

Thomas — Wed, 14 Oct 2026 12:07:29 GMT

Thomas marked PAVEsense - IRI Correlation for translation

Main Page/nl

Thomas — Wed, 14 Oct 2026 12:07:27 GMT

nl translation

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	== PAVEsense ==		== PAVEsense ==

	De [[~~PaveSense~~/nl\|PAVEsense-gebruikershandleiding]] legt uit hoe u de wegkwaliteit beoordeelt en opvolgt in het PAVEsense-portaal:		De [[PAVEsense/nl\|PAVEsense-gebruikershandleiding]] legt uit hoe u de wegkwaliteit beoordeelt en opvolgt in het PAVEsense-portaal:

	# [[~~PaveSense~~/nl#Inleiding\|Inleiding]]		# [[PAVEsense/nl#Inleiding\|Inleiding]]
	# [[~~PaveSense~~/nl#Kwaliteitsindicatoren\|Kwaliteitsindicatoren]]		# [[PAVEsense/nl#Kwaliteitsindicatoren\|Kwaliteitsindicatoren]]
	# [[~~PaveSense~~/nl#Convergentie\|Convergentie]]		# [[PAVEsense/nl#Convergentie\|Convergentie]]
	# [[~~PaveSense~~/nl#Automatische_kalibratie\|Automatische kalibratie en termijn voor nieuwe data]]		# [[PAVEsense/nl#Automatische_kalibratie\|Automatische kalibratie en termijn voor nieuwe data]]
	# [[~~PaveSense~~/nl#Het_portaal\|Het portaal]]		# [[PAVEsense/nl#Het_portaal\|Het portaal]]
	# [[~~PaveSense~~/nl#De_tabelweergave\|De tabelweergave (Data table)]]		# [[PAVEsense/nl#De_tabelweergave\|De tabelweergave (Data table)]]
	# [[~~PaveSense~~/nl#De_kaartweergave\|De kaartweergave (Map)]]		# [[PAVEsense/nl#De_kaartweergave\|De kaartweergave (Map)]]
	# [[~~PaveSense~~/nl#Annotaties\|Annotaties]]		# [[PAVEsense/nl#Annotaties\|Annotaties]]
	# [[~~PaveSense~~/nl#Exporteren\|Exporteren (Export)]]		# [[PAVEsense/nl#Exporteren\|Exporteren (Export)]]
	# [[~~PaveSense~~/nl#Meetdekking\|Meetdekking (Coverage)]]		# [[PAVEsense/nl#Meetdekking\|Meetdekking (Coverage)]]
	# [[~~PaveSense~~/nl#Veelgestelde_vragen\|Tips en veelgestelde vragen]]		# [[PAVEsense/nl#Veelgestelde_vragen\|Tips en veelgestelde vragen]]

	Verder lezen:		Verder lezen:

PAVEsense - Export Formats

Thomas — Wed, 14 Oct 2026 12:07:24 GMT

Thomas marked PAVEsense - Export Formats for translation

Main Page

Thomas — Wed, 14 Oct 2026 12:07:20 GMT

Thomas marked Main Page for translation

Roads AI

Thomas — Wed, 14 Oct 2026 12:03:03 GMT

Redirect to PAVEsense

← Older revision		Revision as of 12:03, 14 October 2026
Line 1:		Line 1:
	#REDIRECT [[~~PaveSense~~]]		#REDIRECT [[PAVEsense]]

PAVEsense

Thomas — Wed, 14 Oct 2026 12:03:02 GMT

Thomas marked PAVEsense for translation

PaveSense

Thomas — Wed, 14 Oct 2026 12:02:34 GMT

Thomas completed renaming of translatable page PaveSense to PAVEsense Rename PaveSense to PAVEsense

PaveSense/nl

FuzzyBot — Wed, 14 Oct 2026 12:02:09 GMT

FuzzyBot moved page PaveSense/nl to PAVEsense/nl without leaving a redirect Part of translatable page "PaveSense"

Show changes

PaveSense/en

FuzzyBot — Wed, 14 Oct 2026 12:02:09 GMT

FuzzyBot moved page PaveSense/en to PAVEsense/en without leaving a redirect Part of translatable page "PaveSense"

Show changes

PaveSense

Thomas — Wed, 14 Oct 2026 12:02:08 GMT

Thomas moved page PaveSense to PAVEsense Rename PaveSense to PAVEsense

Show changes

Main Page/en

FuzzyBot — Wed, 14 Oct 2026 11:48:40 GMT

Updating to match new version of source page

← Older revision		Revision as of 11:48, 14 October 2026
Line 20:		Line 20:
	Further reading:		Further reading:

	* [[~~Roads AI~~ - Export Formats/en\|Export formats: meaning of the exported fields]]		* [[PAVEsense - Export Formats/en\|Export formats: meaning of the exported fields]]
	* [[~~Roads AI~~ - IRI Correlation/en\|eIRI correlation with reference measurements]]		* [[PAVEsense - IRI Correlation/en\|eIRI correlation with reference measurements]]

	== AMBIsense ==		== AMBIsense ==

Main Page/nl

Thomas — Wed, 14 Oct 2026 11:48:37 GMT

nl translation

← Older revision		Revision as of 11:48, 14 October 2026
Line 20:		Line 20:
	Verder lezen:		Verder lezen:

	* [[~~Roads AI~~ - Export Formats/nl\|Exportformaten: betekenis van de geëxporteerde velden]]		* [[PAVEsense - Export Formats/nl\|Exportformaten: betekenis van de geëxporteerde velden]]
	* [[~~Roads AI~~ - IRI Correlation/nl\|eIRI-correlatie met referentiemetingen]]		* [[PAVEsense - IRI Correlation/nl\|eIRI-correlatie met referentiemetingen]]

	== AMBIsense ==		== AMBIsense ==

Main Page

Thomas — Wed, 14 Oct 2026 11:48:19 GMT

Thomas marked Main Page for translation

Roads AI - IRI Correlation

Thomas — Wed, 14 Oct 2026 11:47:23 GMT

Thomas completed renaming of translatable page Roads AI - IRI Correlation to PAVEsense - IRI Correlation Rename Roads AI to PAVEsense

Roads AI - IRI Correlation/en

FuzzyBot — Wed, 14 Oct 2026 11:47:21 GMT

FuzzyBot moved page Roads AI - IRI Correlation/en to PAVEsense - IRI Correlation/en without leaving a redirect Part of translatable page "Roads AI - IRI Correlation"

New page

<languages/>
[[File:Port of Antwerp Groundtruth vs eIRI measurements of ASAsense.jpg|thumb|eIRI ASAsense vs IRI reference]]

''Valid from PAVEsense version 8 (November 2024)''

The ASAsense eIRI values are calculated from the road profile measured with the accelerometer in the sensor box. We combine the measurements of the different passes and take the '''average''' eIRI of all passes that meet the [[PaveSense/en#Convergentie|convergence criterion]].

==== Comparison with reference measurements in the Port of Antwerp ====

The correlation was made using reference data that we kindly received from the Port of Antwerp. After applying some corrections for GPS drift, we observe a correlation (R² factor) of 70%. Given that we measure after the damping of the vehicle and across several passes, whereas the reference data is recorded once and always along one side of the vehicle, we consider this a good correlation factor. More important, however, is the effect on the analysis. There is a very good similarity between the reference data and the ASAsense data: the worse roads in the reference data also come out as bad in the ASAsense data, and the good ones as good.

[[File:Distributie eIRI vs referentie.png|thumb|eIRI ASAsense compared with the PoA distribution]]

When we look at the overall distribution of the data, we also see a very strong agreement.

Below we have also compared the "driving quality" indicator with the reference measurements. We analyse this with a "confusion matrix", a standard approach for classification problems. Quality is mainly predicted in neighbouring quality labels, as the confusion matrix shows. For example, of the roads whose true label is "very good", 96% are predicted as "good" or "very good".

==== Development ====

===== PAVEsense version 8 =====

The alignment of the measured data was improved. As a result, peaks now coincide better at the correct location. This makes averaging over different passes a more effective way to obtain the final result. Moreover, it is a simpler method and also works when there are few passes over the same location. The following table shows the R² of the new version compared with the previous one. We also see that the prediction of ''Driving Quality'' has improved significantly compared with the previous version. The table was created with the same data for v7 and v8, which makes comparison possible.

{| class="wikitable"
! eIRI version
! R² (dtw-aligned)
|-
| PAVEsense v7 and earlier
| 0.61
|-
| from PAVEsense v8
| '''0.7'''
|}

[[File:Driving quality confusion matrix.png|thumb|eIRI driving quality confusion matrix, normalised on the true label]]

===== PAVEsense version 7 and earlier =====

In PAVEsense v7 and earlier, the 85th percentile was used to combine different passes into one measurement. This version under-reported the measured eIRI, so many roads ended up in a better category than in reality.

[[File:PAVEsense v7 driving quality confusion matrix.png|thumb|PAVEsense v7 (older software) driving quality confusion matrix, normalised on the true label]]

Roads AI - IRI Correlation/nl

FuzzyBot — Wed, 14 Oct 2026 11:47:21 GMT

FuzzyBot moved page Roads AI - IRI Correlation/nl to PAVEsense - IRI Correlation/nl without leaving a redirect Part of translatable page "Roads AI - IRI Correlation"

New page

<languages/>
[[File:Port of Antwerp Groundtruth vs eIRI measurements of ASAsense.jpg|thumb|eIRI ASAsense t.o.v. IRI-referentie]]

''Geldig vanaf PAVEsense versie 8 (november 2024)''

De eIRI-waarden van ASAsense worden berekend op basis van het wegprofiel dat wordt opgemeten aan de hand van de accelerometer in de sensorbox. We combineren hierbij de metingen van de verschillende passages en nemen het '''gemiddelde''' van de eIRI van alle passages die voldoen aan het [[PaveSense/nl#Convergentie|convergentiecriterium]].


==== Vergelijking met referentiemetingen in de haven van Antwerpen ====

De correlatie werd gedaan met behulp van referentiedata die we van de haven van Antwerpen mochten ontvangen. Met behulp van enkele correcties voor de GPS-drift merken we een correlatie (R²-factor) van 70% op. Gezien het feit dat we meten na de demping van de wagen, over verschillende passages heen, terwijl de referentiedata eenmalig wordt opgemaakt en telkens langs één zijde van de wagen, beschouwen we dit als een goede correlatiefactor. Belangrijker nog is echter wat het effect is op de analyse. Er is een zeer goede gelijkenis tussen de referentiedata en de ASAsense-data: de slechtere wegen in de referentiedata komen ook in de ASAsense-data terug als slecht, de goede als goed.

[[File:Distributie eIRI vs referentie.png|thumb|eIRI ASAsense t.o.v. PoA-distributie]]

Als we de totale distributie van de data bekijken, zien we ook een zeer sterke overeenkomst.

We hebben hieronder ook de "driving quality"-indicator vergeleken met de referentiemetingen. Dit analyseren we met een "confusion matrix", een standaardaanpak voor classificatieproblemen. De kwaliteit wordt voornamelijk voorspeld in naburige kwaliteitslabels, wat zichtbaar is in de confusion matrix. Bijvoorbeeld: van de wegen die als echt label "zeer goed" hebben, wordt 96% voorspeld als "goed" of "zeer goed".


==== Ontwikkeling ====


===== PAVEsense versie 8 =====

Het aligneren van de gemeten data werd verbeterd. Hierdoor vallen pieken nu beter samen op de juiste locatie. Daardoor is het nemen van het gemiddelde over verschillende passages een effectievere manier om tot het eindresultaat te komen. Bovendien is dit een eenvoudigere manier, die ook werkt wanneer er weinig passages over dezelfde locatie zijn. In de volgende tabel is de R² afgebeeld van de nieuwe versie ten opzichte van de vorige. We merken ook dat het voorspellen van de rijkwaliteit (''Driving Quality'') significant verbeterd is ten opzichte van de vorige versie. De tabel is gemaakt met dezelfde data voor v7 en v8, wat vergelijking mogelijk maakt.

{| class="wikitable"
! eIRI-versie
! R² (dtw-gealigneerd)
|-
| PAVEsense v7 en vroeger
| 0,61
|-
| vanaf PAVEsense v8
| '''0,7'''
|}

[[File:Driving quality confusion matrix.png|thumb|eIRI driving quality confusion matrix, genormaliseerd op het ware label]]


===== PAVEsense versie 7 en vroeger =====

In PAVEsense v7 en vroeger werd het 85ste percentiel gebruikt om verschillende passages samen te nemen tot één meting. Deze versie onderrapporteerde de gemeten eIRI, waardoor veel wegen in een betere categorie terechtkwamen dan in werkelijkheid.

[[File:PAVEsense v7 driving quality confusion matrix.png|thumb|PAVEsense v7 (oudere software) driving quality confusion matrix, genormaliseerd op het ware label]]

Roads AI - IRI Correlation

Thomas — Wed, 14 Oct 2026 11:47:20 GMT

Thomas moved page Roads AI - IRI Correlation to PAVEsense - IRI Correlation Rename Roads AI to PAVEsense

New page

<languages/>
<translate>

[[File:Port of Antwerp Groundtruth vs eIRI measurements of ASAsense.jpg|thumb|eIRI ASAsense vs IRI reference]]


''Valid from PAVEsense version 8 (November 2024)''


The ASAsense eIRI values are calculated from the road profile measured with the accelerometer in the sensor box. We combine the measurements of the different passes and take the '''average''' eIRI of all passes that meet the [[PaveSense/en#Convergentie|convergence criterion]].

==== Comparison with reference measurements in the Port of Antwerp ==== 


The correlation was made using reference data that we kindly received from the Port of Antwerp. After applying some corrections for GPS drift, we observe a correlation (R² factor) of 70%. Given that we measure after the damping of the vehicle and across several passes, whereas the reference data is recorded once and always along one side of the vehicle, we consider this a good correlation factor. More important, however, is the effect on the analysis. There is a very good similarity between the reference data and the ASAsense data: the worse roads in the reference data also come out as bad in the ASAsense data, and the good ones as good.


[[File:Distributie eIRI vs referentie.png|thumb|eIRI ASAsense compared with the PoA distribution]]


When we look at the overall distribution of the data, we also see a very strong agreement.


Below we have also compared the "driving quality" indicator with the reference measurements. We analyse this with a "confusion matrix", a standard approach for classification problems. Quality is mainly predicted in neighbouring quality labels, as the confusion matrix shows. For example, of the roads whose true label is "very good", 96% are predicted as "good" or "very good".

==== Development ==== 

===== PAVEsense version 8 ===== 


The alignment of the measured data was improved. As a result, peaks now coincide better at the correct location. This makes averaging over different passes a more effective way to obtain the final result. Moreover, it is a simpler method and also works when there are few passes over the same location. The following table shows the R² of the new version compared with the previous one. We also see that the prediction of ''Driving Quality'' has improved significantly compared with the previous version. The table was created with the same data for v7 and v8, which makes comparison possible.


{| class="wikitable"
! eIRI version
! R² (dtw-aligned)
|-
| PAVEsense v7 and earlier
| 0.61
|-
| from PAVEsense v8
| '''0.7'''
|}


[[File:Driving quality confusion matrix.png|thumb|eIRI driving quality confusion matrix, normalised on the true label]]

===== PAVEsense version 7 and earlier ===== 


In PAVEsense v7 and earlier, the 85th percentile was used to combine different passes into one measurement. This version under-reported the measured eIRI, so many roads ended up in a better category than in reality.


[[File:PAVEsense v7 driving quality confusion matrix.png|thumb|PAVEsense v7 (older software) driving quality confusion matrix, normalised on the true label]]
</translate>

Roads AI - Export Formats

Thomas — Wed, 14 Oct 2026 11:47:16 GMT

Thomas completed renaming of translatable page Roads AI - Export Formats to PAVEsense - Export Formats Rename Roads AI to PAVEsense

Roads AI - Export Formats/en

FuzzyBot — Wed, 14 Oct 2026 11:47:16 GMT

FuzzyBot moved page Roads AI - Export Formats/en to PAVEsense - Export Formats/en without leaving a redirect Part of translatable page "Roads AI - Export Formats"

New page

<languages/>
PAVEsense data (formerly ''Roads AI'') can be exported from the portal in CSV and ESRI Shapefile format. Below is a list with the meaning of all fields.

We regularly refer to the SCCR indicators. These are the relative indicators macro1, macro2, mega1, mega2 and waviness.

For information on the interpretation of the indicators and the convergence criteria, see the [[PaveSense/en#Kwaliteitsindicatoren|PAVEsense user manual]].

{| class="wikitable"
! CSV field name
! Meaning
|-
| recipe_id
| The version of the software used for the export. All data within the same recipe_id are comparable. SCCR indicators are not comparable when the recipe_id differs.
|-
| gen_date
| The date on which the export took place
|-
| month
| The month the data relates to
|-
| segment_id
| The internal ID of the road segment concerned
|-
| road_name
| The name of the road, if it exists and is known to the system
|-
| sccr_first
| The date of the oldest measurement used to determine the SCCR indicators
|-
| sccr_last
| The date of the most recent measurement used to determine the SCCR indicators
|-
| sccr_conv
| Have the SCCR values converged?
|-
| v_85_kmh
| The reference speed (85th percentile of the measured speeds)
|-
| macro1
| Macro1 indicator
|-
| macro2
| Macro2 indicator
|-
| mega1
| Mega1 indicator
|-
| mega2
| Mega2 indicator
|-
| waviness
| Waviness indicator
|-
| macro1_ns
| Macro1 indicator – non-scaled
|-
| macro2_ns
| Macro2 indicator – non-scaled
|-
| mega1_ns
| Mega1 indicator – non-scaled
|-
| mega2_ns
| Mega2 indicator – non-scaled
|-
| wavi_ns
| Waviness indicator – non-scaled
|-
| iri_first
| The date of the oldest measurement used to determine the IRI indicator
|-
| iri_last
| The date of the most recent measurement used to determine the IRI indicator
|-
| iri_conv
| Have the IRI measurements converged?
|-
| iri_min
| The minimum measured IRI
|-
| iri_50perc
| The 50th percentile of the IRI measurements
|-
| iri_85perc
| The 85th percentile of the IRI measurements
|-
| iri_max
| The largest measured IRI value
|-
| iri_avg
| The average IRI value
|-
| iri_sterr
| The standard deviation of the measured IRI values
|-
| iri_rq
| The driving quality (from Poor to Very Good)
|-
| iri_rq_int
| The driving quality (from 1 to 5, with 1 Poor and 5 Very Good)
|-
| surf_conv
| Have the surface determinations converged?
|-
| surf_best
| Most likely estimated surface type
|-
| surf_src
| The source used to determine the surface type '''(TODO: document the meaning of the sources)'''
|-
| geometry
| The geometry of the road segment, in [[wikipedia:Well-known_text_representation_of_geometry|WKT]]
|-
| authority
| The road authority responsible for this road segment
|}

Roads AI - Export Formats/nl

FuzzyBot — Wed, 14 Oct 2026 11:47:16 GMT

FuzzyBot moved page Roads AI - Export Formats/nl to PAVEsense - Export Formats/nl without leaving a redirect Part of translatable page "Roads AI - Export Formats"

New page

<languages/>
PAVEsense-data (eerder ''Roads AI'') kan via het portaal geëxporteerd worden in CSV- en ESRI Shapefile-formaat. Hieronder vindt u een lijst met de betekenis van alle velden.

We verwijzen geregeld naar de SCCR-indicatoren. Dat zijn de relatieve indicatoren macro1, macro2, mega1, mega2 en waviness.

Voor informatie over de interpretatie van de indicatoren en de convergentiecriteria, zie de [[PaveSense/nl#Kwaliteitsindicatoren|PAVEsense-gebruikershandleiding]].

{| class="wikitable"
! Veldnaam CSV
! Betekenis
|-
| recipe_id
| De versie van de software die gebruikt is voor de export. Alle data binnen hetzelfde recipe_id zijn vergelijkbaar. SCCR-indicatoren zijn niet vergelijkbaar wanneer het recipe_id verschilt.
|-
| gen_date
| De datum waarop de export plaatsvond
|-
| month
| De maand waarop de data betrekking heeft
|-
| segment_id
| Het interne ID van het betreffende wegsegment
|-
| road_name
| De naam van de weg, indien deze bestaat en gekend is door het systeem
|-
| sccr_first
| De datum van de oudste meting gebruikt voor het bepalen van de SCCR-indicatoren
|-
| sccr_last
| De datum van de recentste meting gebruikt voor het bepalen van de SCCR-indicatoren
|-
| sccr_conv
| Zijn de SCCR-waarden geconvergeerd?
|-
| v_85_kmh
| De referentiesnelheid (85e percentiel van de opgemeten snelheden)
|-
| macro1
| Macro1-indicator
|-
| macro2
| Macro2-indicator
|-
| mega1
| Mega1-indicator
|-
| mega2
| Mega2-indicator
|-
| waviness
| Waviness-indicator
|-
| macro1_ns
| Macro1-indicator – niet geschaald
|-
| macro2_ns
| Macro2-indicator – niet geschaald
|-
| mega1_ns
| Mega1-indicator – niet geschaald
|-
| mega2_ns
| Mega2-indicator – niet geschaald
|-
| wavi_ns
| Waviness-indicator – niet geschaald
|-
| iri_first
| De datum van de oudste meting gebruikt voor het bepalen van de IRI-indicator
|-
| iri_last
| De datum van de recentste meting gebruikt voor het bepalen van de IRI-indicator
|-
| iri_conv
| Zijn de IRI-metingen geconvergeerd?
|-
| iri_min
| De minimaal opgemeten IRI
|-
| iri_50perc
| Het 50e percentiel van de IRI-metingen
|-
| iri_85perc
| Het 85e percentiel van de IRI-metingen
|-
| iri_max
| De grootste opgemeten IRI-waarde
|-
| iri_avg
| De gemiddelde IRI-waarde
|-
| iri_sterr
| De standaardafwijking op de opgemeten IRI-waarden
|-
| iri_rq
| De driving quality (van Poor naar Very Good)
|-
| iri_rq_int
| De driving quality (van 1 tot 5, met 1 Poor en 5 Very Good)
|-
| surf_conv
| Zijn de bepalingen van het oppervlak geconvergeerd?
|-
| surf_best
| Meest waarschijnlijk ingeschatte oppervlaktetype
|-
| surf_src
| De bron die werd gebruikt voor de bepaling van het type oppervlak '''(TODO: betekenis bronnen documenteren)'''
|-
| geometry
| De geometrie van het wegsegment, in [[wikipedia:Well-known_text_representation_of_geometry|WKT]]
|-
| authority
| De wegbeheerder verantwoordelijk voor dit wegsegment
|}

Roads AI - Export Formats

Thomas — Wed, 14 Oct 2026 11:47:15 GMT

Thomas moved page Roads AI - Export Formats to PAVEsense - Export Formats Rename Roads AI to PAVEsense

New page

<languages/>
<translate>

PAVEsense data (formerly ''Roads AI'') can be exported from the portal in CSV and ESRI Shapefile format. Below is a list with the meaning of all fields.


We regularly refer to the SCCR indicators. These are the relative indicators macro1, macro2, mega1, mega2 and waviness.


For information on the interpretation of the indicators and the convergence criteria, see the [[PaveSense/en#Kwaliteitsindicatoren|PAVEsense user manual]].


{| class="wikitable"
! CSV field name
! Meaning
|-
| recipe_id
| The version of the software used for the export. All data within the same recipe_id are comparable. SCCR indicators are not comparable when the recipe_id differs.
|-
| gen_date
| The date on which the export took place
|-
| month
| The month the data relates to
|-
| segment_id
| The internal ID of the road segment concerned
|-
| road_name
| The name of the road, if it exists and is known to the system
|-
| sccr_first
| The date of the oldest measurement used to determine the SCCR indicators
|-
| sccr_last
| The date of the most recent measurement used to determine the SCCR indicators
|-
| sccr_conv
| Have the SCCR values converged?
|-
| v_85_kmh
| The reference speed (85th percentile of the measured speeds)
|-
| macro1
| Macro1 indicator
|-
| macro2
| Macro2 indicator
|-
| mega1
| Mega1 indicator
|-
| mega2
| Mega2 indicator
|-
| waviness
| Waviness indicator
|-
| macro1_ns
| Macro1 indicator – non-scaled
|-
| macro2_ns
| Macro2 indicator – non-scaled
|-
| mega1_ns
| Mega1 indicator – non-scaled
|-
| mega2_ns
| Mega2 indicator – non-scaled
|-
| wavi_ns
| Waviness indicator – non-scaled
|-
| iri_first
| The date of the oldest measurement used to determine the IRI indicator
|-
| iri_last
| The date of the most recent measurement used to determine the IRI indicator
|-
| iri_conv
| Have the IRI measurements converged?
|-
| iri_min
| The minimum measured IRI
|-
| iri_50perc
| The 50th percentile of the IRI measurements
|-
| iri_85perc
| The 85th percentile of the IRI measurements
|-
| iri_max
| The largest measured IRI value
|-
| iri_avg
| The average IRI value
|-
| iri_sterr
| The standard deviation of the measured IRI values
|-
| iri_rq
| The driving quality (from Poor to Very Good)
|-
| iri_rq_int
| The driving quality (from 1 to 5, with 1 Poor and 5 Very Good)
|-
| surf_conv
| Have the surface determinations converged?
|-
| surf_best
| Most likely estimated surface type
|-
| surf_src
| The source used to determine the surface type '''(TODO: document the meaning of the sources)'''
|-
| geometry
| The geometry of the road segment, in [[wikipedia:Well-known_text_representation_of_geometry|WKT]]
|-
| authority
| The road authority responsible for this road segment
|}
</translate>

PaveSense

Thomas — Wed, 14 Oct 2026 10:26:11 GMT

Thomas marked PaveSense for translation

ASAsense Binary Table (ABT) format/en

FuzzyBot — Wed, 14 Oct 2026 10:25:42 GMT

Updating to match new version of source page

New page

<languages/>
The ASAsense Binary Table (ABT) format is an alternative to the CSV format, but for binary data with fixed row lengths. The structure is as follows:

{| class="wikitable"
! name
! length (bytes)
! type
! allowed values
! explanation
|-
| file_type
| 1
| u8
| 1
| The internal number of the file type and version
|-
| n_cols
| 4
| u32
| 1-u32::max
| The number of columns
|-
| col_widths
| 4 × n_cols
| u32[n_cols]
| 1-u32::max per column
| n_cols u32 integers describing the byte width of the columns
|-
| metadata_length
| 4
| u32
| 0-u32::max
| The length of the metadata field (can be 0 if it is to be skipped)
|-
| metadata
| metadata_length
| char[]
| string of fixed length (so no '\0' character marks the end of the string)
| JSON-encoded metadata
|-
| data
| variable, until EOF
| byte[]
| any
| The actual data
|}

The JSON metadata should be an object with the following structure:

{| class="wikitable"
! field
! required
! type
! explanation
|-
| n_rows
| false
| number
| The number of rows in the file, if known upfront (can be omitted for streaming data)
|-
| comment
| false
| string
| A free string
|-
| columns
| true
| a list of column definition objects
| A list of objects describing the columns in more detail (should have n_cols entries)
|-
| extra
| false
| JSON object
| A JSON object that can be specified freely
|}

A "column definition object" should have the following format:

{| class="wikitable"
! field
! required
! type
! explanation
|-
| name
| false
| string
| An optional name of the column
|-
| comment
| false
| string
| A free string
|-
| datatype
| true
| string
| An identifier for the datatype of the column
|}

The datatype identifiers can be anything, but the reader should support at least the following:

{| class="wikitable"
! identifier
! description
|-
| utf8
| Interpret the data as a UTF-8 string (with fixed length; it does not need to be terminated with '\0')
|-
| int
| Interpret the data as a signed integer
|-
| uint
| Interpret the data as an unsigned integer
|-
| float
| Interpret the data as floating-point data (only possible for 4- or 8-byte fields)
|-
| bool
| Boolean value (0 = false, anything else = true)
|-
| numtype/div
| "div" should be replaced by any floating-point number. The data is first interpreted as "numtype" (int, uint or float) and then divided by "div". This is mainly useful for storing decimal numbers in integer fields.
|-
| unix_timestamp(numtype/div)
| Interprets the data as specified within the brackets (so any numtype, with optional divider), but takes into account that it is a Unix timestamp (seconds since the Unix epoch, 1 January 1970 at UTC)
|}

Other, unknown datatype identifiers should be treated by the reader as opaque binary data (bytes).

== Common extra metadata fields ==

In many ABT files used by ASAsense, the following extra metadata fields will be found:

{| class="wikitable"
! Field name
! Field type
! Default value
! Description
|-
| sorted_by_timestamp
| bool
| true
| Indicates whether the data in the ABT file is sorted by timestamp (column 1)
|-
| frame_width_s
| float
| NaN
| Indicates the frame width of one sample (for example the sampling period or spectrogram frame width)
|}

== CLI tool for ABT handling ==

To make the ABT format easier to use, a few precompiled binaries are available:
* Linux
** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.zip Ubuntu 22.04 x86_64]
** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.zip Ubuntu 20.04 x86_64]
* [http://asasense.com/abt-binaries/abt-cli-win11-x64.zip Windows 11 x64]
The MD5 sums of the ZIP files are as follows:
adcd6a227861bb6b188ef8c5748faae8 abt-cli-ubuntu-20.04-x86_64.zip
6f4c63cbd7416ead026f170c97b3ab89 abt-cli-ubuntu-22.04-x86_64.zip
39db54827d2634262d9d666b4262b212 abt-cli-win11-x64.zip

AMBIsense/en

FuzzyBot — Wed, 14 Oct 2026 10:25:40 GMT

Updating to match new version of source page

New page

<languages/>
== Data formats ==

Within the AMBIsense solution, measurements of the 1/3-octave band spectrum are performed. The results of these measurements can be exported in multiple formats:

* as a self-explanatory CSV table;
* as one of the following very simple, yet efficient proprietary binary formats:
** a phen1 file: a very restrictive format that keeps small datasets as small as possible, while maintaining random access on row level;
** an [[ASAsense Binary Table (ABT) format/en|ABT]] file: a binary table format with fast and efficient random access (both on row and column level).

== Instant measurements ==

The AMBIsense sensors can be configured to send instant measurements to a dedicated MQTT broker. These have the following structure:

* audio measurements (8 messages / s):
** topic: <code>/instant/<deviceName>/measurements</code>
** payload, in msgpack:
*** timestamp: float
*** dBA: float (sound level)
* classifications (frequency depends on the model):
** topic: <code>/instant/<deviceName>/classification/<modelId>/<modelVersion></code>
** payload, in msgpack:
*** timestamp: float
*** confidences: float[] for each class

PaveSense/en

FuzzyBot — Wed, 14 Oct 2026 10:25:30 GMT

Updating to match new version of source page

Show changes

Main Page/en

FuzzyBot — Wed, 14 Oct 2026 10:25:27 GMT

Updating to match new version of source page

New page

<languages/>
Welcome to the ASAsense documentation site. Here you will find all the information you need to use the ASAsense applications.

== PAVEsense ==

The [[PaveSense/en|PAVEsense user manual]] explains how to assess and monitor road quality in the PAVEsense portal:

# [[PaveSense/en#Inleiding|Introduction]]
# [[PaveSense/en#Kwaliteitsindicatoren|Quality indicators]]
# [[PaveSense/en#Convergentie|Convergence]]
# [[PaveSense/en#Automatische_kalibratie|Automatic calibration and lead time for new data]]
# [[PaveSense/en#Het_portaal|The portal]]
# [[PaveSense/en#De_tabelweergave|The table view (Data table)]]
# [[PaveSense/en#De_kaartweergave|The map view (Map)]]
# [[PaveSense/en#Annotaties|Annotations]]
# [[PaveSense/en#Exporteren|Exporting (Export)]]
# [[PaveSense/en#Meetdekking|Measurement coverage (Coverage)]]
# [[PaveSense/en#Veelgestelde_vragen|Tips and frequently asked questions]]

Further reading:

* [[Roads AI - Export Formats/en|Export formats: meaning of the exported fields]]
* [[Roads AI - IRI Correlation/en|eIRI correlation with reference measurements]]

== AMBIsense ==

* [[AMBIsense/en|AMBIsense: data formats and instant measurements]]
* [[ASAsense Binary Table (ABT) format/en|The ASAsense Binary Table (ABT) format]]

Main Page/nl

Thomas — Wed, 14 Oct 2026 10:24:37 GMT

nl translation

New page

<languages/>
Welkom op de documentatiesite van ASAsense. Hier vindt u alle nodige informatie voor het gebruik van de ASAsense-toepassingen.

== PAVEsense ==

De [[PaveSense/nl|PAVEsense-gebruikershandleiding]] legt uit hoe u de wegkwaliteit beoordeelt en opvolgt in het PAVEsense-portaal:

# [[PaveSense/nl#Inleiding|Inleiding]]
# [[PaveSense/nl#Kwaliteitsindicatoren|Kwaliteitsindicatoren]]
# [[PaveSense/nl#Convergentie|Convergentie]]
# [[PaveSense/nl#Automatische_kalibratie|Automatische kalibratie en termijn voor nieuwe data]]
# [[PaveSense/nl#Het_portaal|Het portaal]]
# [[PaveSense/nl#De_tabelweergave|De tabelweergave (Data table)]]
# [[PaveSense/nl#De_kaartweergave|De kaartweergave (Map)]]
# [[PaveSense/nl#Annotaties|Annotaties]]
# [[PaveSense/nl#Exporteren|Exporteren (Export)]]
# [[PaveSense/nl#Meetdekking|Meetdekking (Coverage)]]
# [[PaveSense/nl#Veelgestelde_vragen|Tips en veelgestelde vragen]]

Verder lezen:

* [[Roads AI - Export Formats/nl|Exportformaten: betekenis van de geëxporteerde velden]]
* [[Roads AI - IRI Correlation/nl|eIRI-correlatie met referentiemetingen]]

== AMBIsense ==

* [[AMBIsense/nl|AMBIsense: dataformaten en directe metingen]]
* [[ASAsense Binary Table (ABT) format/nl|Het ASAsense Binary Table-formaat (ABT)]]

Roads AI - IRI Correlation/en

FuzzyBot — Wed, 14 Oct 2026 10:24:36 GMT

Updating to match new version of source page

New page

AMBIsense/nl

Thomas — Wed, 14 Oct 2026 10:24:23 GMT

nl translation

New page

<languages/>

== Dataformaten ==

Binnen de AMBIsense-oplossing worden metingen van het 1/3-octaafbandspectrum uitgevoerd. De resultaten van deze metingen kunnen in meerdere formaten worden geëxporteerd:

* als een zelfverklarende CSV-tabel;
* als een van de volgende zeer eenvoudige, maar efficiënte eigen binaire formaten:
** een phen1-bestand: een zeer beperkend formaat dat kleine datasets zo klein mogelijk houdt, met behoud van willekeurige toegang op rijniveau;
** een [[ASAsense Binary Table (ABT) format/nl|ABT]]-bestand: een binair tabelformaat met snelle en efficiënte willekeurige toegang (zowel op rij- als op kolomniveau).


== Directe metingen ==

De AMBIsense-sensoren kunnen zo worden ingesteld dat ze directe metingen naar een eigen MQTT-broker sturen. Deze hebben de volgende structuur:

* audiometingen (8 berichten / s):
** topic: <code>/instant/<deviceName>/measurements</code>
** payload, in msgpack:
*** timestamp: float
*** dBA: float (geluidsniveau)
* classificaties (frequentie hangt af van het model):
** topic: <code>/instant/<deviceName>/classification/<modelId>/<modelVersion></code>
** payload, in msgpack:
*** timestamp: float
*** confidences: float[] voor elke klasse

ASAsense Binary Table (ABT) format/nl

Thomas — Wed, 14 Oct 2026 10:24:21 GMT

nl translation

← Older revision		Revision as of 10:24, 14 October 2026
Line 99:		Line 99:
	\|}		\|}

	~~<div lang="en" dir="ltr" class="mw~~-~~content-ltr">~~		De datatype-identificaties kunnen willekeurig zijn, maar de lezer moet minstens de volgende ondersteunen:
	~~The datatype identifiers can be anything~~, ~~but the reader should support at least the following~~:
	~~</div>~~

	~~<div lang="en" dir="ltr" class="mw-content-ltr">~~
	{\| class="wikitable"		{\| class="wikitable"
	! ~~identifier~~		! identificatie
	! ~~description~~		! beschrijving
	\|-		\|-
	\| utf8		\| utf8
	\| ~~Interpret the~~ data ~~as a~~ UTF-8 string (~~with fixed length~~; ~~it does not need to be terminated with~~ '\0')		\| Interpreteer de data als een UTF-8-string (met vaste lengte; hoeft niet te eindigen op '\0')
	\|-		\|-
	\| int		\| int
	\| ~~Interpret the~~ data ~~as a signed integer~~		\| Interpreteer de data als een geheel getal met teken
	\|-		\|-
	\| uint		\| uint
	\| ~~Interpret the~~ data ~~as an unsigned integer~~		\| Interpreteer de data als een geheel getal zonder teken
	\|-		\|-
	\| float		\| float
	\| ~~Interpret the data as floating-point~~ data (~~only possible for~~ 4~~- or~~ 8~~-byte fields~~)		\| Interpreteer de data als kommagetal (alleen mogelijk voor velden van 4 of 8 bytes)
	\|-		\|-
	\| bool		\| bool
	\| ~~Boolean value~~ (0 = false, ~~anything else~~ = true)		\| Booleaanse waarde (0 = false, al het andere = true)
	\|-		\|-
	\| numtype/div		\| numtype/div
	\| "div" ~~should be replaced by any floating-point number~~. ~~The~~ data ~~is first interpreted as~~ "numtype" (int, uint or float) ~~and then divided by~~ "div". ~~This~~ is ~~mainly useful for storing decimal numbers~~ in ~~integer fields~~.		\| "div" moet worden vervangen door een willekeurig kommagetal. De data wordt eerst geïnterpreteerd als "numtype" (int, uint of float) en daarna gedeeld door "div". Dit is vooral nuttig om decimale getallen in velden met gehele getallen op te slaan.
	\|-		\|-
	\| unix_timestamp(numtype/div)		\| unix_timestamp(numtype/div)
	\| ~~Interprets the~~ data ~~as specified within the brackets~~ (~~so any~~ numtype, ~~with optional divider~~), ~~but takes into account that it is a~~ Unix ~~timestamp~~ (~~seconds since the~~ Unix epoch, 1 ~~January~~ 1970 at UTC)		\| Interpreteert de data zoals tussen de haakjes aangegeven (dus elk numtype, met optionele deler), maar houdt er rekening mee dat het om een Unix-tijdstempel gaat (seconden sinds de Unix-epoch, 1 januari 1970 om UTC)
	\|}		\|}
	~~</div>~~

	~~<div lang="en" dir="ltr" class="mw-content-ltr">~~		Andere, onbekende datatype-identificaties moeten door de lezer als ondoorzichtige binaire data (bytes) worden behandeld.
	~~Other~~, ~~unknown~~ datatype ~~identifiers should be treated by the reader as opaque binary~~ data (bytes).
	~~</div>~~

	<~~div lang~~="~~en" dir="ltr" class="mw-content-ltr~~">		<span id="Common_extra_metadata_fields"></span>
	== ~~Common~~ extra ~~metadata fields~~ ==		== Veelgebruikte extra metadatavelden ==
	~~</div>~~

	~~<div lang="en" dir="ltr" class="mw-content-ltr">~~		In veel ABT-bestanden die ASAsense gebruikt, vindt u de volgende extra metadatavelden:
	In ~~many~~ ABT ~~files used by~~ ASAsense, ~~the following~~ extra ~~metadata fields will be found~~:
	~~</div>~~

	~~<div lang="en" dir="ltr" class="mw-content-ltr">~~
	{\| class="wikitable"		{\| class="wikitable"
	! ~~Field name~~		! Veldnaam
	! ~~Field type~~		! Veldtype
	! ~~Default value~~		! Standaardwaarde
	! ~~Description~~		! Beschrijving
	\|-		\|-
	\| sorted_by_timestamp		\| sorted_by_timestamp
	\| bool		\| bool
	\| true		\| true
	\| ~~Indicates whether the~~ data in ~~the~~ ABT ~~file~~ is ~~sorted by timestamp~~ (~~column~~ 1)		\| Geeft aan of de data in het ABT-bestand gesorteerd is op tijdstempel (kolom 1)
	\|-		\|-
	\| frame_width_s		\| frame_width_s
	\| float		\| float
	\| NaN		\| NaN
	\| ~~Indicates the frame width of one~~ sample (~~for example the sampling period or~~ spectrogram ~~frame width~~)		\| Geeft de framebreedte van één sample aan (bijvoorbeeld de bemonsteringsperiode of de framebreedte van een spectrogram)
	\|}		\|}
	~~</div>~~

	<~~div lang~~="~~en" dir="ltr" class="mw-content-ltr~~">		<span id="CLI_tool_for_ABT_handling"></span>
	== CLI tool ~~for~~ ABT ~~handling~~ ==		== CLI-tool voor ABT-bestanden ==
	~~</div>~~

	~~<div lang="en" dir="ltr" class="mw~~-~~content-ltr">~~		Om het werken met het ABT-formaat te vereenvoudigen, zijn enkele voorgecompileerde programma's beschikbaar:
	~~To make the ABT format easier to use~~, ~~a few precompiled binaries are available~~:
	~~</div>~~
	* Linux		* Linux
	** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.zip Ubuntu 22.04 x86_64]		** [http://asasense.com/abt-binaries/abt-cli-ubuntu-22.04-x86_64.zip Ubuntu 22.04 x86_64]
	** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.zip Ubuntu 20.04 x86_64]		** [http://asasense.com/abt-binaries/abt-cli-ubuntu-20.04-x86_64.zip Ubuntu 20.04 x86_64]
	* [http://asasense.com/abt-binaries/abt-cli-win11-x64.zip Windows 11 x64]		* [http://asasense.com/abt-binaries/abt-cli-win11-x64.zip Windows 11 x64]
	~~<div lang="en" dir="ltr" class="mw~~-~~content~~-~~ltr">~~		De MD5-sommen van de ZIP-bestanden zijn als volgt:
	~~The MD5 sums of the ZIP files are as follows~~:
	~~</div>~~
	adcd6a227861bb6b188ef8c5748faae8 abt-cli-ubuntu-20.04-x86_64.zip		adcd6a227861bb6b188ef8c5748faae8 abt-cli-ubuntu-20.04-x86_64.zip
	6f4c63cbd7416ead026f170c97b3ab89 abt-cli-ubuntu-22.04-x86_64.zip		6f4c63cbd7416ead026f170c97b3ab89 abt-cli-ubuntu-22.04-x86_64.zip
	39db54827d2634262d9d666b4262b212 abt-cli-win11-x64.zip		39db54827d2634262d9d666b4262b212 abt-cli-win11-x64.zip

Roads AI - IRI Correlation/nl

FuzzyBot — Wed, 14 Oct 2026 10:24:17 GMT

Updating to match new version of source page

New page

Roads AI - Export Formats/en

FuzzyBot — Wed, 14 Oct 2026 10:24:11 GMT

Updating to match new version of source page

New page

Roads AI - Export Formats/nl

Thomas — Wed, 14 Oct 2026 10:23:50 GMT

nl translation

New page

PaveSense/nl

Thomas — Wed, 14 Oct 2026 10:23:36 GMT

nl translation

Show changes

Roads AI - IRI Correlation

Thomas — Wed, 14 Oct 2026 10:23:23 GMT

Thomas marked Roads AI - IRI Correlation for translation

Roads AI - Export Formats

Thomas — Wed, 14 Oct 2026 10:23:16 GMT

Thomas marked Roads AI - Export Formats for translation

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	== PAVEsense ==		== PAVEsense ==

	The [[~~PaveSense~~/en\|PAVEsense user manual]] explains how to assess and monitor road quality in the PAVEsense portal:		The [[PAVEsense/en\|PAVEsense user manual]] explains how to assess and monitor road quality in the PAVEsense portal:

	# [[~~PaveSense~~/en#Inleiding\|Introduction]]		# [[PAVEsense/en#Inleiding\|Introduction]]
	# [[~~PaveSense~~/en#Kwaliteitsindicatoren\|Quality indicators]]		# [[PAVEsense/en#Kwaliteitsindicatoren\|Quality indicators]]
	# [[~~PaveSense~~/en#Convergentie\|Convergence]]		# [[PAVEsense/en#Convergentie\|Convergence]]
	# [[~~PaveSense~~/en#Automatische_kalibratie\|Automatic calibration and lead time for new data]]		# [[PAVEsense/en#Automatische_kalibratie\|Automatic calibration and lead time for new data]]
	# [[~~PaveSense~~/en#Het_portaal\|The portal]]		# [[PAVEsense/en#Het_portaal\|The portal]]
	# [[~~PaveSense~~/en#De_tabelweergave\|The table view (Data table)]]		# [[PAVEsense/en#De_tabelweergave\|The table view (Data table)]]
	# [[~~PaveSense~~/en#De_kaartweergave\|The map view (Map)]]		# [[PAVEsense/en#De_kaartweergave\|The map view (Map)]]
	# [[~~PaveSense~~/en#Annotaties\|Annotations]]		# [[PAVEsense/en#Annotaties\|Annotations]]
	# [[~~PaveSense~~/en#Exporteren\|Exporting (Export)]]		# [[PAVEsense/en#Exporteren\|Exporting (Export)]]
	# [[~~PaveSense~~/en#Meetdekking\|Measurement coverage (Coverage)]]		# [[PAVEsense/en#Meetdekking\|Measurement coverage (Coverage)]]
	# [[~~PaveSense~~/en#Veelgestelde_vragen\|Tips and frequently asked questions]]		# [[PAVEsense/en#Veelgestelde_vragen\|Tips and frequently asked questions]]

	Further reading:		Further reading:

← Older revision		Revision as of 12:07, 14 October 2026
Line 4:		Line 4:
	== PAVEsense ==		== PAVEsense ==

	De [[~~PaveSense~~/nl\|PAVEsense-gebruikershandleiding]] legt uit hoe u de wegkwaliteit beoordeelt en opvolgt in het PAVEsense-portaal:		De [[PAVEsense/nl\|PAVEsense-gebruikershandleiding]] legt uit hoe u de wegkwaliteit beoordeelt en opvolgt in het PAVEsense-portaal:

	# [[~~PaveSense~~/nl#Inleiding\|Inleiding]]		# [[PAVEsense/nl#Inleiding\|Inleiding]]
	# [[~~PaveSense~~/nl#Kwaliteitsindicatoren\|Kwaliteitsindicatoren]]		# [[PAVEsense/nl#Kwaliteitsindicatoren\|Kwaliteitsindicatoren]]
	# [[~~PaveSense~~/nl#Convergentie\|Convergentie]]		# [[PAVEsense/nl#Convergentie\|Convergentie]]
	# [[~~PaveSense~~/nl#Automatische_kalibratie\|Automatische kalibratie en termijn voor nieuwe data]]		# [[PAVEsense/nl#Automatische_kalibratie\|Automatische kalibratie en termijn voor nieuwe data]]
	# [[~~PaveSense~~/nl#Het_portaal\|Het portaal]]		# [[PAVEsense/nl#Het_portaal\|Het portaal]]
	# [[~~PaveSense~~/nl#De_tabelweergave\|De tabelweergave (Data table)]]		# [[PAVEsense/nl#De_tabelweergave\|De tabelweergave (Data table)]]
	# [[~~PaveSense~~/nl#De_kaartweergave\|De kaartweergave (Map)]]		# [[PAVEsense/nl#De_kaartweergave\|De kaartweergave (Map)]]
	# [[~~PaveSense~~/nl#Annotaties\|Annotaties]]		# [[PAVEsense/nl#Annotaties\|Annotaties]]
	# [[~~PaveSense~~/nl#Exporteren\|Exporteren (Export)]]		# [[PAVEsense/nl#Exporteren\|Exporteren (Export)]]
	# [[~~PaveSense~~/nl#Meetdekking\|Meetdekking (Coverage)]]		# [[PAVEsense/nl#Meetdekking\|Meetdekking (Coverage)]]
	# [[~~PaveSense~~/nl#Veelgestelde_vragen\|Tips en veelgestelde vragen]]		# [[PAVEsense/nl#Veelgestelde_vragen\|Tips en veelgestelde vragen]]

	Verder lezen:		Verder lezen: