PAVEsense

Version 2.1 – 24 September 2026 · Applies to the portal portal.asasense.com

This manual helps you assess and monitor road quality in the ASAsense PAVEsense portal (portal.asasense.com). You will learn how to look up results, compare months, add field knowledge with annotations, check measurement coverage and export data. The explanation follows the Data table, Map, Export and Coverage tabs of a measurement area. The areas and features available to you depend on your subscription and access rights.

Introduction

Schematic overview of the ASAsense PAVEsense measurement system (formerly "Roads AI")

The PAVEsense road-quality measurement system (formerly Roads AI) consists of a fleet of vehicles fitted with sensor boxes. The roads to be measured are driven by this fleet during the everyday use of the vehicles. In this way the measurement system collects rolling-noise and vibration measurements. These measurements are sent securely, and with respect for privacy, to the ASAsense data centre, where they are processed.

The result is a set of quality indicators per road section that map the condition of the road network. These indicators are updated monthly and offered in the portal at two levels of detail: per road (from junction to junction, called road in the portal) and per segment of about 20 metres (segment). Besides consulting the results, the new portal also lets you add annotations (for example a completed repair or a changed surface type) and monitor the measurement coverage of the area.

Quality indicators

The measurement system is based on the observation that ageing roads both sound louder and cause stronger vibrations. Several characteristic wavelengths can be distinguished in the road surface: from ravelling and small potholes to undulation of the road on a larger scale. The vibration and noise measurements are combined and shifted in the frequency domain according to the speed of the vehicle. Anyone who has accidentally driven over the rumble strip of a motorway knows this phenomenon: the pitch clearly changes as you drive slower or faster. The relation is frequency = speed / (3.6 × length), with the frequency in hertz, the speed in km/h and the wavelength in metres.

The five length scales (roughness classes) of PAVEsense

With this in mind, PAVEsense reports a selection of length scales that are relevant for analysing the condition of the road:

• Macro1 (8 cm to 20 cm): an indication of early degradation of the top layer – ravelling, delamination, loose chippings, …
• Macro2 (20 cm to 60 cm): an indication of more advanced degradation of the top layer – cracks, potholes, …
• Mega1 (60 cm to 140 cm): unevenness that affects the driving experience – larger potholes, rutting, but also limited longitudinal undulations.
• Mega2 (140 cm to 3 m): larger unevenness – deep rutting, longer undulations, …
• Waviness (3 m to 5 m): longitudinal evenness over long distances, mainly relevant for roads driven at high speed.

There is no strict separation between the scales: many defects visible in Macro2 also show up in Macro1 and Mega1, and vice versa. Classes that are far apart are not linked, however: ravelling of the top layer is visible in Macro1, not in Waviness.

For the indicators Macro1 up to and including Waviness, the values of a location are compared with the values of all roads that were measured at the time the calibration model for your area was last trained. The smoothest road gets a 0 and the roughest or most undulating road a 1 (the percentiles of a cumulative distribution). This makes it easy to see which roads are in good or poor condition relative to the rest.

Besides these five texture indicators, PAVEsense also reports the following interpreted parameters:

• 

  Illustration of the IRI scale for different pavements

  eIRI (estimated International Roughness Index, expressed in m/km): an international measure of road roughness as it acts on a vehicle. Roughness is expressed as the vertical movement of the suspension (in metres) per kilometre travelled. The higher the IRI, the less comfortable the road and the lower the speed at which it can still be driven comfortably. This is an important measure of the current quality of the pavement, including the foundation. On the detail page of a road, the 85th percentile of the eIRI is shown next to the average (eIRI (85th pct)).

• 

  Speed-related IRI thresholds according to Yu et al. (National Taipei University of Technology)

  Driving Quality: an interpreted version of the eIRI in which the driven speed is linked to the IRI to determine whether the road still fulfils its function. This uses the table from the research of the National Taipei University of Technology. The speed used is the 85th percentile of all measurements on the road section (85 % of the vehicles drive slower than this speed). The classes are Very Good, Good, Fair, Mediocre and Poor.
• Reference speed: the 85th percentile of the measured driving speeds on the road section, in km/h. This speed is used to determine the Driving Quality and is in itself a useful indication of how the road is used.
• Surface Type: the type of pavement – asphalt, concrete, brick, cobblestone or other. The surface type is estimated automatically from the measurements. As long as this estimate still changes between successive measurement rounds, the portal shows the label ESTIMATE. You can record the surface type yourself with an annotation of type Surface. The applicable annotation takes precedence over the estimate and is marked on the detail page with ANNOTATED. A current annotation may differ from the surface type in a monthly report; see Current surface type and monthly report.
• Authority (road authority): the body that manages the road (for example the city or municipality, the Flemish Agency for Roads and Traffic (AWV) or a private owner). This lets you limit the results to the roads you are responsible for.

We recommend focusing initially on:

• Macro2 for prioritising top-layer maintenance;
• Driving Quality / eIRI for prioritising full maintenance (including foundation works).

Convergence

Results are delivered per month. The month (for example 2026-09, shown in the portal as Last results) indicates up to when measurements were taken into account. The measurements of the past month are always included, but for road sections that were not driven enough in that month, older measurements may also be used.

For the texture indicators Macro1 up to and including Waviness, the following convergence criterion applies:

• only consider measurements with a driving speed between 20 km/h and 130 km/h;
• take at least the measurements of the past 30 days into account;
• if at least 2 measurements by at least 2 different vehicles were made in this period, check whether
  • the speed differs by less than 30 % from the 85th-percentile speed;
  • the standard deviation of the noise level in certain frequency bands is below 4 dB;
  • the standard deviation on the 1 m band is below 4 dB (this length scale corresponds to low-frequency noise, depending on the driven speed);
• if the criterion is not met, also consider earlier measurements until it is. The maximum age of a measurement is 500 days (for very rarely driven streets).

For the eIRI, the same passes are selected as for the texture indicators; the average eIRI over those passes is reported as the eIRI value of the location. Research shows that this gives the best correlation with reference measurements.

Non-converged results are delivered as well, but they are more sensitive to noise and incidental events (a branch on the road, a vehicle briefly driving onto the verge to pass oncoming traffic, …). In the portal the convergence status is visible in three places:

• on the map you can filter on SCCR converged (convergence of the texture indicators Macro1–Waviness) and on Surface converged (the surface-type estimate is stable);
• on the detail page of a road or segment, Texture measured and eIRI measured carry the label ESTIMATE as long as the corresponding results have not yet converged;
• the automatically estimated surface type carries the same label as long as the estimate is not yet stable. If a Surface annotation is in effect, the detail page shows ANNOTATED. This confirms an annotation of the surface type, not the convergence of the measured values.

Automatic calibration and lead time for new data

After a sensor has been installed in a measurement vehicle, measurements are collected immediately, without any intervention by the user or driver. Not everything can be processed right away, however.

For the scales Macro1 up to and including Waviness, the data must first be calibrated against other measurements at the same locations. This happens automatically, but requires enough overlapping measurements (around ten thousand). Allow about three months. From the fourth month on you receive the processed measurement data of these sensors, retroactively: previously measured months are then updated with the calibrated data as well.

The eIRI and the Driving Quality are calculated directly from the recorded vibration data. No calibration is needed for these: these indicators can be available after regular processing, without waiting for the calibration period of the texture indicators.

The portal

Open your measurement area via PAVEsense → Areas. To assess a street, look it up in Data table and open the detail page. Use Map for a spatial overview, Coverage to see where the measurement fleet has driven and Export to analyse the data further.

Logging in and navigation

Log in at portal.asasense.com with the e-mail address and password you received from ASAsense. Use Forgot password to request a new password; with Remember me for 30 days you stay logged in on your device.

After logging in, the dark sidebar on the left contains the PAVEsense section with Areas (your measurement areas) underneath. Click the name of an area to open it; if you have access to several areas, they are all listed here. The sidebar can be collapsed and expanded with the arrows at the top to make more room for the map or table. The sidebar also contains:

• User Profile: your name, e-mail address and the option to set a new password (fill in New Password and click Save);
• Documentation: a link to this documentation;
• Logout: log out.

Devices, Vehicles, Trips, Device Handlings, Interventions and Annotation Types are also grouped under PAVEsense, insofar as your account has access to them. Existing links to the former sections are redirected to the new location.

At the top of every page a breadcrumb trail (for example Pavesense / Areas / 8 / Table) shows where you are; each part can be clicked to go back.

The area page

Once an area is open, you see the name of the area at the top and four tabs:

• Data table: the table view, for sorting and filtering roads or segments on the measured parameters;
• Map: the map view with colour coding, filters and charts;
• Export: exporting the results as CSV, Excel or ESRI shapefile;
• Coverage: the measurement coverage of the road network (how many passes per road section).

To the right of the tabs are three elements that appear on every tab:

• Annotation edits: an overview of recent bulk edits of annotations, with the option to undo an entire group at once (see Annotations);
• Last results: the month of the most recent results (for example 2026-09);
• Data version: the version number of the dataset shown by the portal. Mention this number when you contact ASAsense with a question about the results.

Road network and history

PAVEsense keeps track of the relationship between successive versions of the road network. A small shift in geometry, a changed source numbering or a corrected road direction therefore does not have to produce a new road: the road can be recognised as the same road, keeping its linked measurements. A successor is also searched for roads that have been retired.

The supplied road data contain validity dates; only valid roads are included in the customer data. A changed number of roads therefore does not automatically mean that measurements have been lost. When comparing, check the selected month as well as the road or segment identification and the validity of the road network.

Accessing PAVEscan files

Besides the monthly PAVEsense results from the measurement fleet, your area may also have the results of a PAVEscan measurement campaign: a one-off, detailed survey of the road network with a measurement vehicle. These files are listed under the heading PAVEscan files:

• if the area also has PAVEsense results, you will find them on the Export tab, below the PAVEsense export;
• if the area only has PAVEscan data, they are shown directly on the area page.

The files are grouped per measurement campaign. With a single campaign, the period is shown in brackets in the heading; with several campaigns, each period gets its own subheading. For each campaign you will find:

• a small QGIS project (ZIP file) in which the IRI, rutting (Rutting) and VC2.5 are already loaded from CSV files. Unzip the file and open the .qgz file in QGIS to get a styled map straight away;
• the individual CSV files (Individual CSV Files), for use in your own GIS package, spreadsheet or analysis application. Large files are stored compressed, but your browser decompresses them automatically during the download: you always receive a plain CSV file.

Click a file name to start the download. The larger datasets of a campaign, such as the georeferenced images and the LAS point clouds, are too large to offer through the portal. They are available on request via info@asasense.com.

Scales and colours

Most results are numerical values:

• Macro1 up to and including Waviness are expressed as a value between 0 (best road) and 1 (worst road);
• the eIRI is a value greater than 0 (in m/km) without a hard upper limit: the higher, the rougher the road;
• the Driving Quality and the surface type are classes.

To show numerical results on the map, you choose a colour scale with a lower and upper limit (Gradient). Values at or below the lower limit are blue; above it the colour runs through green and yellow to red for values at or above the upper limit.

A linear scale (lower limit 0, upper limit 1) spreads the colours evenly over the full range:

You can also colour everything below a certain threshold blue and only let the colour vary above it. This shows more detail in the roads that score worse. With lower limit 0.8 and upper limit 1, this is called the 80/20 scale:

In the portal the colour scale defaults to 0.5 – 1 for Macro1–Waviness and to 0 – 10 for the eIRI. Both limits can be adjusted freely in the Appearance panel of the map (see Appearance). For the Driving Quality and the surface type the map uses a fixed class legend.

The table view (Data table)

The Data table tab shows the most recent results (the month shown under Last results) in table form. This is the quickest way to find the roads or segments that score well or poorly on a given parameter, or to look up a street by name.

Columns

By default the table shows the following columns per row: Road Id (or Segment Id), Road Name, Surface Type, Reference speed, Macro1, Macro2, Mega1, Mega2, Waviness, eIRI, Driving quality and Authority. An empty cell means there is no result (yet) for that parameter, for example because the eIRI could not be calculated for that road section. On narrower screens the table can be scrolled horizontally.

With the eye icon (Select displayed columns in the table) you choose which columns are shown: switch a column's toggle off to hide it. You can also drag the columns into a different order using the handle to the left of each column name.

Road or segment

With the road / segment toggle on the right of the filter bar you choose the level of detail:

• road: one row per road (from junction to junction), with a numerical Road Id;
• segment: one row per segment of about 20 m, with a Segment Id of the form map-61-0-l1 (road 61, segment 0, lane 1).

For prioritisation per street, road level works best; to find the exact location of a defect within a street, switch to segment level.

Sorting

Click a column header to sort the table on that column. A first click sorts ascending (arrow up), a second click descending, and a third click removes the sorting. For example, sort descending on Macro2 to get the roads with the most worn top layer at the top.

Filtering

The filter bar above the table contains a button per filterable column. By default the filters ID, STREET NAME, SURFACE TYPE, REFERENCE SPEED and AUTHORITY are available. Click a button to open the filter:

• text filters (ID, STREET NAME, AUTHORITY): type (part of) the text and confirm with Enter; the table then only shows the rows that contain the text;
• choice filters (SURFACE TYPE, DRIVING QUALITY): pick a value from the list (-- None -- clears the choice);
• range filters (REFERENCE SPEED, MACRO1, MACRO2, MEGA1, MEGA2, WAVINESS, eIRI): enter a minimum and/or maximum.

An active filter can be recognised by the value in brackets on the button, for example STREET NAME (Klaproos). Filters that are not in the bar can be added with the funnel icon on the far left (Filter on other columns not shown): switch on the toggle of the desired column and the corresponding filter button appears in the bar. With the reset icon (Remove all filters) you clear all filters at once.

Example: to find all concrete roads with a Macro2 above 0.9, choose SURFACE TYPE = Concrete, add the MACRO2 filter via the funnel and enter Min value = 0.9 there.

Pagination

At the bottom of the table you choose the number of rows per page (Items per page: 10, 20, 50, 100, 200, 500 or 1000) and page through with the arrows. The counter (for example 1 – 10 of 3091) shows how many rows match the current filters.

Opening a row

Click a row (for example on the street name) to open the detail page of that road or segment, with all values, a small map and the annotations.

Selecting and annotating rows

Use the checkboxes to the left of the rows to select one or more roads or segments. The checkbox in the column header selects all roads that match the current filters at once, including those on the following pages; so filter first (for example on street name) and then select everything. As soon as there is a selection, the yellow bar … roads selected appears above the table with the button Annotate … roads, which adds the same annotation to all selected rows at once. See Annotations for how this works.

The detail page of a road or segment

The detail page opens when you click a row in the table, or when you click a road on the map and choose View details. Use the arrow to the left of the name to go back.

Information panel

The INFO panel shows the values of the road or segment: surface type, reference speed, Macro1, Macro2, Mega1, Mega2, Waviness, eIRI, eIRI (85th percentile), Driving Quality and road authority. Below them are the measurement periods:

• Texture measured: the date or period of the measurements on which the texture indicators Macro1–Waviness are based;
• eIRI measured: the date or period of the measurements on which the eIRI is based.

The label ESTIMATE next to a measured value or measurement period indicates a result that has not yet converged; see Convergence. Hover over a label for an explanation. Also check the selected month: a historical page shows the measurement results of that month.

Current surface type and monthly report

Under Surface Type the detail page shows the currently applicable surface annotation, if there is one. It gets the label ANNOTATED and takes precedence over the automatic estimate. Hover over the label to see the date of the annotation and which surface type the monthly report still mentions.

The monthly report is a snapshot taken on the first day of the month. An annotation added later is already visible on the detail page, while the monthly report may still show the earlier value. Such a difference is therefore possible without the annotation having failed. The current surface label on the detail page also does not necessarily reflect the situation in a selected historical month.

Example: on 18 September you correct a road from asphalt to concrete. If this annotation is then valid, the detail page shows concrete with ANNOTATED. The snapshot of 1 September may still mention asphalt; the explanation next to the label makes this difference visible. When comparing months, keep the measured values and the current field knowledge apart.

Measurement history and historical months

The detail page of a road or segment contains monthly charts for eIRI and the macro and mega texture. This lets you look at trends and outliers without exporting first. The line chart with Waviness is the default view; the spread of the eIRI is shown as well.

1. Open the road or segment you want and look at the measurement history.
2. Zoom on the horizontal axis to view the relevant period. Zoom independently on the vertical axis to see differences in measured values more clearly.
3. Open the month you want to investigate. An older month can be recognised by Legacy Recording: this means you are viewing historical measurement results.
4. Check the measurement period and convergence before interpreting a change. Because of the convergence rules, successive monthly results may partly be based on the same passes.

If you first choose an older month via Month on the area map and then open a road, that month stays selected on the detail page. The month can be stored in the page link; save or share the link of the opened month to find the same result later. The recipient needs access to the area.

Example: to investigate the effect of a repair, compare the months before and after the intervention. Zoom in on that period, look at both the eIRI and the relevant texture indicator, and check that the measurements are from after the intervention. A more favourable colour alone is not enough: use the same colour scale when comparing and take convergence into account.

Photos

In the box Drop images here or click to upload you can add photos of the road or segment, for example of damage or a completed repair. Drag the files into the box or click it to select them. Photos with location data get their own pin on the small map.

Click a photo pin to open the corresponding photo and then browse through the photo carousel. This lets you link a visual observation to the location and the measurement results. A photo without location data does not in itself provide an exact position on the map.

Small map and segment navigation

The small map on the right shows the selected road or segment in blue (Current), the surrounding roads in orange (Surrounding) and roads without data dotted (No data). The buttons on the left of the map are zoom , full screen , a black-and-white basemap and the choice of basemap . Basemap layers, search and full screen work as on the area map and the coverage map; see Navigating the map. The Area map button takes you to the map of the area, centred on this road.

Above the information panel is the segment bar: per lane (1 LANE, 2 LANES, …) a button per segment (Seg 1, Seg 2, …). Click a segment to view the values of that 20 m segment; on a segment page, the button with the street name takes you back to the whole road. A segment for which no results are available yet shows a dash instead of a value.

Annotations on the detail page

The ANNOTATIONS panel shows the active annotations of the road or segment with their type, value and validity period. On a segment page, This segment and Road switch between the annotations of the segment itself and those of the whole road. Check this distinction before adding an annotation.

The button adds an annotation. Via (View history) you view the history. Earlier, superseded annotations can also be expanded via Show N earlier annotations, where N is the number of earlier annotations. This keeps the history available next to the current value. See Viewing and undoing annotations.

The map view (Map)

The Map tab shows the results on an interactive map. On the left are the map buttons and the search bar, at the top the Road / Segment toggle and the draw button, and on the right the panel with the display settings (Appearance) and the filters (Filters). The panel can be collapsed with the arrow on its edge to show the map across the full width. The dotted black line on the map is the boundary of your area.

Navigating the map

You can zoom in and out and drag the map as you are used to with other online maps (mouse wheel, double-click, dragging). The buttons on the left of the map:

Button	Function
	Zoom in / Zoom out.
	View fullscreen: the map in full screen; press Esc to return.
	Fit to data: fits the map to the data once. It is a one-off action; afterwards the map can still be dragged and zoomed freely.
	Black & white basemap: switches the grey basemap on or off, so the coloured roads stand out better.
	Layers: choose a basemap, such as Streets, Ortho or ESRI Satellite. The ortho sources are combined into a single Ortho layer for users. The available imagery depends on the location.

The controls for basemap layers, search, full screen and layers are the same on Map, Coverage and the small map on the detail page. Black and white is a setting of the map and works on all basemap layers. When you zoom in further, the road geometry is drawn in more detail, so bends and roundabouts keep their shape better.

Search

In the search bar at the top left (Search road/segment id, address or coordinates) you can enter three kinds of searches; confirm with Enter or the magnifying glass:

• a road or segment id, for example 63, road-63 or map-63-1-l1: the map zooms to that road or segment and highlights it;
• an address, for example Haagdoornsstraat or Stad 1, Hamont-Achel: the map zooms to the location and marks it with a green circle;
• coordinates (latitude, longitude in decimal degrees), for example 51.25, 5.55.

Search moves the map to a location; it does not set a data filter. A road you find may fall outside the displayed results because of your active filters. Adjust those filters if you also want to assess the road. Only locations within the boundaries of the area are accepted. The cross in the search bar clears the search and the marker.

Road or segment on the map

With the Road / Segment toggle at the top of the map you choose, just as in the table, whether the colours are shown per road (junction to junction) or per 20 m segment. The segment view shows more detail; the road view gives a calmer overview of the entire network.

Viewing the details of a road

Click a road or segment to open a pop-up with the name, the surface type, Macro2, Mega2, Waviness, the average eIRI, the Driving Quality, the 85th-percentile speed and the road authority (for a segment also the segment number and the lane). The View details button opens the detail page for the month selected on the map. For an older month, that page gets the label Legacy Recording; so you never jump unnoticed to the most recent results.

Appearance

At the top of the right-hand panel, under Color by, you choose which parameter determines the colour of the roads: Macro1, Macro2, Mega1, Mega2, Waviness, eIRI (avg), Speed (85th %), Driving Quality or Surface Type.

For numerical parameters you set the lower and upper limit of the colour scale under Gradient (see Scales and colours). For Macro1–Waviness both limits should be between 0 and 1; for the eIRI, 0 – 10 is a good choice. For the Driving Quality you choose the classes that act as the "best" and "worst" ends of the scale (by default Very Good to Poor). For Surface Type there is no gradient: the map then shows a fixed legend at the bottom left (Asphalt, Brick, Cobblestone, Concrete, Other, No data).

The appearance is independent of the filters: you can, for example, colour on Macro2 and filter on eIRI at the same time. When you change the choice under Color by, the loaded roads are recoloured immediately; your map position is kept.

Filters

Under Filters you limit which roads are shown on the map. The filters are cumulative. As soon as a filter is active, a counter appears next to the Filters heading with the button Clear, which clears all filters at once; each filter block with an active choice also gets its own counter and a Reset button.

• Month: the month of the results. By default the most recent month is selected; click another month (the list scrolls horizontally, back to the first month with results) to view the state of the road network at that time and so follow its evolution over time.
• Converged: SCCR converged (texture indicators) and Surface converged (surface type), each with Yes / No. Choose Yes to show only the results that meet the corresponding convergence criterion; click again to clear the choice.
• Surface Type and Driving Quality: bar charts with the number of roads per class. Click a bar to show only that class; click several bars to combine classes. Hover over a bar for the exact number. Use the arrow before the heading to collapse a block.
• Road Authority: the road authorities, with the number of roads per authority. Click an authority to show only its roads (for example only the municipal roads, without the regional roads).
• Speed (85 %), eIRI avg, Waviness, Mega1, Mega2, Macro1, Macro2: sliders with a lower and upper limit. Drag the handles to show, for example, only the roads with a Macro2 above 0.8.

Example: to find the municipal roads that qualify for a new top layer, choose Color by = Macro2, click your municipality under Road Authority, set SCCR converged to Yes and slide the lower limit of Macro2 to 0.8.

The map keeps data that has already been loaded. A narrower filter can therefore be applied immediately; when panning or zooming, only missing parts are fetched. Your zoom level is kept when filtering. A small loading indicator shows that data is being fetched while the map stays visible. Wait until loading has finished before assessing the new view.

Drawing to select roads

The draw button at the top right of the map (Draw across roads to bulk-annotate) activates drawing mode: the cursor becomes a crosshair. Hold down the mouse button and draw a line across the map; all roads the line crosses light up orange. At the bottom the bar … roads selected appears with the buttons Annotate … roads and Cancel. This lets you, for example, add a Repair annotation in one movement to all streets of a neighbourhood where the top layer was renewed. Check the selection in the annotation window and untick roads you do not want to change. Click the draw button again to leave drawing mode.

Comparing months on the map

Under Month, select the months you want to compare one after the other. Keep the parameter under Color by, the colour limits and the other filters the same, so you assess the same selection on the same scale. Open a road or segment to look at the change more closely in the measurement history.

Annotations

With annotations you add your own field knowledge to the results: observed damage, a completed repair, a temporary obstruction, a speed regime or the correct surface type. Annotations are visible on the detail page of the road or segment. Which annotations and types you can see or change depends on your access rights and your organisation's settings.

Adding an annotation

An annotation can be created in three ways: with the button on the detail page of a single road or segment, via the checkboxes and the Annotate … roads button in the table, or via a drawn line on the map. The window uses the same grouped type selection as the other annotation screens. Choose the appropriate group and type; the available values follow from that type. In the window you fill in:

• Type and Value:
  • Damage: choose the kind of damage from the list – rutting, longitudinal, transverse or alligator cracking, ravelling, potholes, subsidence, segregation, bleeding, edge damage, corner breaks, joint damage, faulting, scaling, polishing, heaving, missing, sunken or damaged elements, joint fouling, weed growth, flooding, contamination or Other;
  • Obstruction: free description, for example a road narrowing or work zone;
  • Repair: choose the intervention – overlay, milling and overlay, local repair, joint filling, surface sealing, slurry seal, crack injection, reprofiling, thin asphalt layer, surface treatment, concrete repair, element repair, base-layer replacement or Other;
  • Speed limit: the speed limit in km/h;
  • Surface: the surface type (Asphalt, Concrete, Brick, Cobblestone or Other). As long as this annotation is in effect, this surface type takes precedence over the automatic estimate. See Current surface type and monthly report.
• Date (from): the date from which the annotation applies (yyyy-mm-dd, or pick a date with the calendar);
• Valid until (optional, for annotations from the detail page or the map): the end date. Leave the field empty for an annotation without an end date; after the end date the annotation moves to the history;
• Reason (optional, for bulk annotations from the table): a short explanation, for example "road works";
• Temporary change (for bulk annotations from the table): tick this for a temporary change (for example road works), so the group can easily be undone in one go later.

For an annotation from the map, the window shows a small map of the selection at the top and the list Roads in selection; use the checkboxes to leave roads out of the selection. From the table, Review & confirm is followed by a summary; confirm with Confirm & save. A bulk annotation is applied to the selected roads or segments and grouped as a single edit. Before saving, check the number of locations, the level of detail and the validity dates.

Viewing and undoing annotations

The active annotations are shown on the detail page under Annotations. Open View history for the history; with Show N earlier annotations you can make earlier, superseded annotations visible again. The change history records who changed what and lets you revert a change, if you have the rights to do so.

Bulk edits can be found via Annotation edits at the top of the area page. Open the edit concerned, check which locations it covers and undo it in one go if necessary. This is useful, for example, after an incorrect bulk entry. Afterwards, check on one of the affected detail pages which annotation is now in effect.

For the surface type there is always one effective Surface annotation. When such a change is deleted or reverted, PAVEsense recalculates the applicable surface value. So do not assume a particular previous value without checking: the remaining annotations and their validity determine what applies now. The edit history is retained.

Managing annotation types and groups

Via PAVEsense → Annotation Types you can manage the available annotation types, insofar as your account has the rights to do so. Besides the standard types, your organisation can define its own types. Customer users can also create groups to bring related types together.

1. Open Annotation Types and choose the group the type belongs to, or create a suitable group.
2. Create a type or edit an existing one. Give it a clear meaning and set the allowed values according to the possibilities of the type.
3. Use the predefined choice lists where they fit your registration, including the available AWV and SB250 choices. This way colleagues use the same terms for similar observations.
4. Save the type. It becomes available in the grouped type selection for the users who have access to it.

Types also have a change history and the option to revert changes. A change to a type concerns the definition and the allowed values; an annotation records a concrete observation on a road or segment. Use the type history for the former and the annotation history for the latter.

Exporting (Export)

On the Export tab you download the results of a month for your own GIS or office application. With every export, check the month and the level of detail as well as the geographical extent.

1. Under Month and Year, choose the month you want to export.
2. Choose Road-level for one row per road with the road geometry, or Segment-level for one row per segment of about 20 m with the segment_id and the segment geometry.
3. Choose the format from the table below.
4. Check the extent in the export dialog. If a drawn region is present, it is used to limit the export geographically. Check that region if you need the whole area. A selection of roads for an annotation does not in itself confirm the export extent.
5. Start the download. While preparing, the portal shows a progress indicator. Wait until preparation and download have finished before starting the same export again.

Format	Use and points of attention
CSV	Text file for further processing in a GIS package, spreadsheet or other analysis application. CSV export is also available at segment level. Choose CSV when the result is too large for XLSX; a spreadsheet program may also apply its own row limit when opening a CSV.
Excel (XLSX)	Built on the server, so your browser does not have to convert large files itself. If the spreadsheet limit of 1,048,576 rows is exceeded, a message asks you to use CSV. Then choose CSV or limit the export extent.
ESRI Shapefile	Zipped file for QGIS, ArcGIS and others. The format limits column names to 10 characters, so names may be truncated.

The coverage map also has its own CSV download for the coverage data. That data describes passes; the results export describes the calculated road quality.

More export options, such as WMS, WFS and other GeoServer services, are available on request via info@asasense.com.

Measurement coverage (Coverage)

The Coverage tab shows how well the road network is covered by the measurement fleet, including the number of passes per road section. Use it to find streets that are not driven or rarely driven. A large number of passes is not in itself proof of good road quality or convergence; for that, look at the measurement results and the convergence status.

The separate page PAVEsense → Coverage is available depending on your subscription. The coverage view within a measurement area remains accessible to the customers who own that area. If you do not see access you expect, ask ASAsense to check your subscription and area access.

Legend and statistics

The menu button at the top right of the map opens the legend. For the pass view, the usual classes are 0 (black), 1–2 (red), 3–4 (orange), 5–6 (yellow), 7–8 (green) and 9 or more (blue). Use the checkboxes to show or hide a class; tick 0 passages to also see unmeasured roads. With Edit you adjust the colours and class limits. Always read the legend of the active layer.

Below the legend you can expand the Statistics panel. Per pass class it shows the number of kilometres of road, the covered length and percentage (Covered) and the total network length (Network). These figures are road length, not the number of streets. They follow the active filters and the selected geographical boundary.

With Show area you choose the boundary:

• Whole area: the full configured area; for a bounding box boundary this includes the rectangle around the area.
• Full city outline: only the network within the full municipal boundary.
• Sub-area or district: an available smaller boundary, for example to compare neighbourhoods.

The map dims the area outside the selected boundary and shows the relevant borders. A measurement area can also be set up with a complex boundary shape; filters and statistics follow that shape. For comparisons, use the same boundary, period and road categories. Otherwise a changed coverage percentage may result from a differently selected network.

Filters on the coverage map

The filter bar above the map works as in the table: click a button to open a filter, use the funnel icon to add extra filters and the reset icon to clear all filters. Available filters:

• Roadtype: the road categories (motorway, trunk, primary, secondary, tertiary, unclassified, residential, living street, the corresponding slip roads, road and uncoded/other). Remove a category with the cross or add one via the search field; this lets you, for example, look at the coverage of residential streets only;
• Surface: one or more surface types;
• Authority: the road authority;
• Daterange: the period in which the passes took place, with the shortcuts Last Week, Last Month and Last Year or a custom date range (dd/mm/yyyy – dd/mm/yyyy). This shows you, for example, which streets were driven in the past month;
• StateId and DeviceId: restriction to the passes of one particular sensor (identification as agreed with ASAsense).

The Roadtype and Surface filters support multiple choices and restrict both the map and the statistics. You can, for example, select residential streets with an asphalt surface and then choose one district under Show area to assess the coverage of exactly that network.

Click a road section for a pop-up with the road category and the number of passes. From the coverage map you can click through to the corresponding trips; see Viewing and downloading trips.

Layers

With the eye icon (Toggle layers) you manage which data layers are visible. The layer name and the corresponding legend indicate what the colours mean.

Layer or data	What it lets you assess
Passages, including Device Passages	How often a road section has been driven. Combine Device Passages with DeviceId if needed to view the passes of a particular sensor.
Device Count	How many different measurement vehicles have driven the road section. Read the legend of this layer for this.
Pavement Condition	The condition of the pavement. This layer has a quality meaning and must not be read as a number of passes. Use its own quality legend.

Among other things, the convergence criterion requires measurements from at least two vehicles. So use the number of vehicles alongside the number of passes, and check the other conditions on the results page. The map buttons for zoom, full screen, Fit to data, black and white, basemap layers and search work as on the map view; search moves the map and does not change the filters.

Exporting coverage data

The download icon in the filter bar (Download data as CSV) downloads the coverage data. In the download choice, select the required extent and, where offered, road or segment level. A drawn region, if present, may limit the export extent. Check the selection and wait for the progress indicator during preparation.

Trips and measurement fleet

Viewing and downloading trips

If your account has access to Trips, you can look up trips under PAVEsense and filter them on a road or segment. You can also go straight from the coverage map to the trips at a location. This lets you investigate which trips belong to a pass overview.

1. Open the trips from the coverage map or via PAVEsense → Trips.
2. Limit the list to the road or segment you are investigating and check the selection.
3. Start the available trip download. In the download dialog, choose the desired revision when a revision choice is offered; the download uses that version of the trip files.

At a location with many passes, the maximum amount of data the service returns may be reached. The portal shows a warning in that case. Treat the displayed list as possibly incomplete and do not base an overall conclusion on it. Narrow the selection where possible, or ask ASAsense for help if you need all trips.

Measurement fleet and support

For users with the appropriate rights, Devices (sensors), Vehicles, Device Handlings (handlings of sensors) and Interventions are grouped under PAVEsense. Use the breadcrumb trail to navigate between these overviews. When asking about a device or trip, mention the corresponding identification.

ASAsense support can consult this data as well as your areas and measurement coverage, and correct notes and installation details. This support role cannot create or delete devices, vehicles, handlings or interventions. This allows support to investigate many questions directly with limited change rights.

Processing of measurement data is more resilient to connection interruptions: receipt is only acknowledged after the data has been stored safely. This helps prevent loss when reconnecting. It is not a confirmation that every street already has enough measurements; use the coverage map and the convergence status for that.

Tips and frequently asked questions

Which parameter do I use to plan maintenance?

Use Macro2 to find worn top layers and Driving Quality or eIRI to assess overall driving and road quality, including possible problems in the foundation. Sort in the table or filter on the map and investigate the selected locations further.

Why does a street have no values or the label ESTIMATE?

There may be too few usable measurements, or the results do not yet meet the convergence criteria. Check Coverage, the measurement period and the convergence status. Texture indicators from new sensors require calibration first; eIRI can be available after regular processing without that waiting time.

How do I compare the condition with last year?

Open the detail page and look at the monthly charts, or choose an older month under Month on the map. A historical detail page carries the label Legacy Recording. Compare the same parameters and scales, and check convergence and measurement periods. For further analysis you can export both months.

Why does the surface type on the detail page differ from the monthly report?

The detail page shows the currently applicable annotation; the monthly report is a snapshot of the first day of the month. Hover over ANNOTATED to see the annotation date and the value from the monthly report.

Can I view only my own roads?

Filter on Authority in the table or on Road Authority on the map. For coverage statistics, also check the boundary under Show area.

The surface type of a street is wrong. How do I correct it?

Add an annotation of type Surface with the correct type and the correct start date. This can be done on the detail page or for a selection via the table or map. The applicable annotation takes precedence over the automatic estimate.

I accidentally added a group of annotations.

Open Annotation edits, check the affected locations and revert the edit. Afterwards, check which value applies on one of the affected detail pages.

I find a road via the search bar but see no measurement result on the map.

Search moves the map; active filters still apply. Check the month, filters, the level of detail and whether data is available.

Why does the map still look the same while loading?

The map stays visible while missing data is being fetched. The loading indicator shows that this is still in progress. Wait until loading has finished before assessing the new view.

My Excel export is too large. What now?

Choose CSV or limit the export extent. XLSX has a maximum of 1,048,576 rows; a spreadsheet program may impose the same limit when opening a CSV. Use a suitable GIS or analysis application for larger files.

Can I count all trips from the list at a location?

Not if there is a warning that the query limit has been reached. The list may then be incomplete. Narrow the selection or ask for support.

Contact

For questions about the portal, additional export options (WMS/WFS), extra users or new measurement areas, contact ASAsense via info@asasense.com.

When asking about results, mention the area name, road or segment id, selected month and Data version. For an error message, add the exact text and the action during which it appeared. For trips or devices, also mention the trip or device identification. This lets support investigate the same situation in a targeted way.