Road Profiles (ProfilingPRO)
Import ProfilingPRO CSV or GeoJSON profiles, merge split runs automatically, and export survey-grade elevation data.
What Are Road Profiles?
Road profiles are high-resolution chainage/elevation datasets captured in the field (for example with ProfilingPRO or GNSS equipment). Unlike the automatic route elevation profile, road profiles carry survey-grade vertical data with a declared vertical datum, making them suitable for grounding analysis and CAD deliverables.
What You Need to Know
ProfilingPRO is a Windows survey application for oversize and heavy transport. A survey-grade GNSS receiver on a moving truck measures the road surface; it is not a DEM estimate. It records elevation corrected for antenna height, grade over the selected smoothing baseline, horizontal turn radius, vertical curvature (K and crest/sag), and per-point receiver quality. With a second receiver it also measures crown/cross-slope and precise heading and records the diagnostics needed to judge those measurements.
RoadScope imports the measured profile, its surveyed trace, curvature/radius/crown channels, point quality and dual-receiver diagnostics, provenance, geometry-alert stretches, and recording-session events. Empty values stay not measured: a blank radius is not changed to “straight”, and blank crown is not changed to zero. Session events such as no fix, receiver failover, stale data, or write/storage trouble describe reliability during the drive and cannot be recreated from road geometry.
Two distinctions matter when reviewing the result. First, grade colours are fixed absolute bands: green below 10%, blue from 10% to below 12%, amber from 12% to below 14%, red from 14% to below 16%, and black at 16% or above. Cab alarm thresholds are operator settings carried in provenance; they do not change those colours. Second, scrape, tight-turn, compound-curve, crown, and superelevation alerts can depend on the load dimensions used in ProfilingPRO. Read them with that load provenance, not as unconditional properties of the road.
Datum and baseline are part of the measurement. Check the declared horizontal/vertical datum before overlaying another dataset or transforming coordinates, and compare grades only when their smoothing baselines are understood. Float or standalone quality can still support differential grade review, but absolute elevation and dual-receiver crown require the quality context shown by RoadScope.
Syncing from ProfilingPRO
Profiles captured with the ProfilingPRO mobile app upload to your survey automatically through the cloud integration — no manual file transfer. Synced profiles appear in the Road Profiles panel with a measured source label (RTK, GNSS, or NMEA log) and their datum metadata intact, and behave exactly like imported profiles from there on: view, merge, link to a route, and export.
Importing a Profile
1. Open the Road Profiles panel from your project map
2. Click Import a CSV profile and select one or more ProfilingPRO profile exports
3. Confirm the vertical datum (ellipsoidal or orthometric + geoid model) and the data source
4. Review the preview chart, then save
ProfilingPRO profile data imports directly from detail CSV, full-session CSV, and profile GeoJSON exports. Detail and full-session CSV files provide chainage and elevation; for a full-session file, RoadScope uses the embedded profile records rather than the interleaved raw GNSS fixes. # metadata headers (datum, geoid, source) are read automatically. Files with latitude/longitude columns can be projected onto a route corridor at import time.
A profile GeoJSON can be imported even after another GIS tool has stripped its properties: RoadScope derives chainage from the LineString coordinates and reads elevation from the coordinate Z values. When the original properties are present, it also keeps the supplied chainage, elevation, timestamps, and quality context.
Provenance Sidecars
Select a matching *_provenance.json sidecar with its profile export whenever you have one. RoadScope pairs the files automatically and uses the sidecar as the authoritative source for vertical datum/geoid information, RTK-fixed percentage, smoothing, and other survey provenance. If no file or sidecar declares a datum, the profile is clearly flagged as undocumented instead of assuming one.
Multi-File Import with Automatic Merge
Long runs are often auto-split into ~50 km files. The import picker accepts multiple files at once:
segment N of M markers from the filename, metadata, or provenance sidecar; unmarked files use natural filename order (run_2 before run_10)Files with different vertical datums or geoid models are refused — mixing vertical referentials would corrupt elevations.
Files That Are Deliberately Not Imported
ProfilingPRO summary and alerts exports are derived from the same source profile, while gnss_raw files contain raw fixes whose antenna-height treatment is not suitable for a road profile. RoadScope recognizes these files and explains why they are skipped; choose the detail CSV, full-session CSV, or profile GeoJSON instead. Malformed or truncated profile files are refused without a partial import — for example, a GeoJSON point_count that does not match its coordinates is treated as truncated.
Merging Existing Profiles
Already imported the pieces separately? Select 2 to 10 profiles in the Road Profiles panel and click Merge. Profiles are joined in your selection order, a new profile named "(merged Ă—n)" is created, and the originals are kept untouched.
One Profile Workspace
Importing opens the saved profile directly. Its workspace provides Add files, Join, Split, Trim and Remove interval, without returning to an unrelated panel. Add files uses the same import validation and boundary preview, saves the added recording as a source, then creates a combined derived profile. The original remains unchanged. If the join fails after import, the saved recording is identified so you can retry the join rather than import it again.
Selecting Recording Intervals
You can also edit without opening ProfilingPRO or Road Profiles: select a displayed measured trace on the map, or use Split, Join or Erase section on a saved measured-profile chart. Check the selected profile name when traces overlap. The map-local editor provides previews, chainage controls, Undo, Cancel and named saves. Join uses another saved profile on the same map, optionally reversed. Saved copies remain accessible on the map; originals are unchanged. Terrain estimates and read-only viewers do not offer these editing actions.
Set interval endpoints with the chart handles or exact chainage fields. With measured geographic coordinates, the map and chart show the same selected interval and distinguish retained and removed parts. At repeated or overlapping driving locations, choose the intended pass using its chainage range and available recording timestamps, quality or segment information. The map does not silently choose a decimated sample. If measured coordinates are absent, edit by chainage; linked-route projection is not treated as recording evidence.
Use Remove interval to remove a stop, detour or repeated pass manually. Choose Keep gap to retain original chainage and mark a break, or Re-chain for continuous chainage. Neither option invents elevations, smooths measurements or automatically removes repeated driving. Review the pending result, apply it, and use Undo/Redo as needed.
Saving Derived Results
Saving replays the operations on full-resolution source measurements on the server. Surviving quality, timestamp and other measurement channels stay aligned with their samples, and the originals remain unchanged. The result opens with source lineage. Split validates both parts before saving; if only one part is saved, the editor identifies that result and allows retrying only the missing part or opening the saved result. An interrupted network response can leave the outcome uncertain: check saved profiles before repeating a request.
Linking to a Route Corridor
Attach a profile to one of your routes to enable chainage-to-map projection (required for GeoJSON export) and optional resampling at a fixed step. Note: resampling a merged profile removes its segment split metadata, since the original file boundaries no longer map to real samples.
Exporting — Complete or Split by Segment
Export formats: CSV, GeoJSON, SVG, PNG, LandXML, and DXF. If the profile was created by a merge, a Scope selector appears in the viewer: export the complete profile or any individual source segment. Segment exports keep the merged chainage so they stay consistent with the corridor projection and the complete export.
Vertical profile DXF is a long-section drawing, not a horizontal map alignment: X is stored chainage and Y is elevation, both in metres at true 1:1 scale. It may look flatter than the exaggerated screen chart. Choose Station (1+250.000) or Kilometres (1.25 km) and label spacing in metres; leave spacing blank for automatic spacing. More than 2,000 intervals is rejected with a request for wider spacing. PROFILE geometry keeps every full-resolution sample; STATIONS, ELEVATIONS, AXES and TEXT layers carry references, units and datum. Retained gaps produce separate polylines. Full and selected-segment exports never rebase chainage or infer elevations. Any earlier explicit edit/rebase is already part of the stored profile. Use CAD coordinate inspection to read exact measured points; labels are rounded for display.
The vertical datum always travels with the deliverable (CSV header, GeoJSON properties, SVG legend, DXF text, LandXML coordinate system). ProfilingPRO CSV and GeoJSON deliverables also keep supplied grade, horizontal radius, K/curvature, crown, quality, timestamps, and dual-receiver diagnostic channels; absent readings remain empty/null. Provenance headers carry available baseline, thresholds, reliability, and load context. LandXML export is refused when the datum is unknown.
Grounding Check & Report
The viewer includes a grounding verdict based on a two-support model (interaxle spacing + ground clearance): a crest between the supports can ground the load, while a dip actually improves clearance. Generate the Road Profile report from the Reports Hub for a formatted deliverable with the chart, grounding verdict, and datum declaration.