Inspection workspace
Capture or upload evidence, create a reviewable deficiency list and export a self-contained report. AI findings are preliminary inspection aids and require review.
1 · Inspection details
Upload completed photos or video, submit for analysis, review quick results, then save the inspection. Data Hub, map, dashboard and advanced editing are designed for desktop.
Enter the confirmed milepoints for the actual roadway/direction/county/inspection type inspected. Leave blank if unknown: individual defect GPS alone does not establish inspected mileage. Split inspections at county boundaries and use matching FDOT milepoint references.
Optional verified inspection start/end GPS (all four coordinates)
For Timestamp-app videos, RoadSift attempts to read on-screen decimal GPS coordinates from each AI finding’s evidence frame. It never assigns the same device GPS to every frame. Check the extracted coordinates against each saved evidence image.
2 · Add photo or video
Mixed mode identifies every visible asset category in each photo. Review categories and findings before downloading separate reports.
3 · Analyze or add a finding
Photo inspections analyze all uploaded photos together in batches and combine related findings into one inspection. Video inspections use sampled frames rather than continuous frame-by-frame analysis. RoadSift records deficiencies only; clean imagery creates no finding.
AI findings start as Field Verification Required. Confirm the applicable measurements and field evidence before choosing a definitive result.
Inspection findings 0
Findings are kept in this browser until you save the inspection to the Data Hub. The original videos are never saved to the hub.
This page shows quick inspection results and a downloadable report. Use RoadSift on desktop for the full Data Hub, roadway mapping, dashboard, inspection history and advanced editing.
Open full RoadSift workspace (desktop recommended)No findings yet. Add a photo, select it and record a defect.
Excel workbooks use your inspection columns. Category reports embed their evidence photos and can be printed or saved as PDF. The self-contained HTML report still embeds the photos directly. Internal standards/audit mappings stay in the Data Hub and are not displayed in the normal report.
Inspection capabilities and limits
Available now: inspection views, photo/video review, GPS, saved inspections and JPEG evidence in the hosted Data Hub, edit history, county/direction filters, map, dashboard, and downloadable reports and CSV. Video files are not saved.
AI: With the RoadSift AI connection configured, RoadSift automatically analyzes video in groups of up to 12 sampled frames. At the default 0.5-second interval, a five-minute video sends 600 frames across 50 requests. This can take time and incur API costs; it is not continuous full-frame video analysis.
Inspection standards: RoadSift uses the configured maintenance standards and internal visual/measurement rules behind the scenes. It records only deficiencies; conditions requiring measurements, sample counts or other verification remain Field Verification Required.
GPS from frame: During AI inspection, attempts to read decimal coordinates printed on the evidence image. Unreadable or missing coordinates stay blank and need review. This is not GPS track extraction from video metadata.
Not yet: Inspection access requires sign-in and administrator approval. No verified individual asset inventory, lane-level route geometry, GPS track extraction, official sample-level ratings or true network-wide inspection percentage. FDOT map lines require an Internet connection.
2026 FDOT MRP · Complete characteristic reference
Open full MRP handbook (PDF)All handbook MRP characteristics are indexed and linked to the original full handbook pages. The selected inspection category is mapped below; some app categories are maintenance alerts rather than a separate official MRP characteristic. AI flags are preliminary, not official sample scores.
My Data Hub · saved inspections
Search, open and edit inspections. Evidence frames are saved as JPEGs; original videos are not retained. Updates are explicitly saved and each revision is recorded.
* Inspected mileage is estimated from inspector-entered milepoint intervals; inspections without confirmed segment limits are excluded. Repeat coverage for the same asset/direction/county is merged. This is NOT total network % coverage.
| Record | Roadway | County | Asset | Milepoints | Findings | Open | Inspector | Updated (UTC) | Audit |
|---|---|---|---|---|---|---|---|---|---|
| Loading saved inspections… | |||||||||
Roadway map · SR 589 / SR 568 / SR 570
Use the filters in Data Hub to select county, roadway, direction and asset. Real FDOT road centrelines load when the FDOT service is reachable. Directional reviewed stretches share the road centreline and are not separate lane-level geometry. GIS boundaries/milepoint matches require field verification.
An inspection does not count as reviewed coverage unless its route, direction, county, inspection type and start/end milepoints have been entered. Symbols show saved findings only when they have GPS coordinates. A point on the map is not proof that an entire roadway section was inspected. FDOT data may lag recent extensions.