Integrations and outputs
Designed to fit existing road-management workflows.
Inspech structures visual inspection information so it can be reviewed in the platform and used in supported GIS, reporting and road-management workflows.
The route from validated assessment to downstream use is defined for the operating context—without treating every export as a native integration or every visual finding as an engineering decision.
Validated inspectionOutput workspace
Road section 042Inspector-validated visual assessmentImagery · location · finding · classification · cycle
Structured information layer↓
Configured for the workflowProfessional decisions remain downstream
One validated evidence baseReview→Report→Export→Exchange
Supported output routes
Use the same validated evidence in the workflows around Inspech.
Different teams need different views of the same inspection record. Inspech keeps the relationship between evidence, location and professional validation intact.
Platform review
Inspect imagery, road sections, findings and validation context together in the georeferenced Inspech environment.
Reports
Use structured inspection information, section-level findings and visual evidence in professional reporting workflows.
GIS and geodata
Bring supported geographic outputs and coordinate-based results into mapping and spatial-analysis workflows.
OGC API Features
Access configured feature resources for inspections, reports, report sections and distresses through supported API routes.
PMS / AMS workflows
Exchange or export validated information for established road-management processes without implying a native connector where none exists.
Availability is configuration-specific.Formats, fields, coordinate systems, API resources and exchange routes are confirmed for the intended workflow.
Input qualificationCompatibility is validated, not assumed
ImageryCoverage · resolution · perspective
Location contextRoute · road section · positioning
Assessment methodTaxonomy · classification · validation
Required outputsReport · geodata · API · exchange
Compatible inputs
Start with the output decision, not only the camera.
Inspech works with compatible road imagery from accessible camera configurations and validated professional capture workflows. The capture setup must preserve the image quality and location context required by the inspection objective.
Before operational use, the route, standard, geometry, coordinate system and required downstream information are agreed. This prevents an apparently successful upload from producing an unusable result later in the workflow.
Proven configurations can move quickly. New configurations require validation.
GIS and geodata
Preserve road-section context beyond the platform.
Inspech organises imagery and findings geographically. Supported geodata outputs allow validated information to be used in mapping, analysis and road-management workflows while retaining its relationship to the road network.
01Map and section views
Review locations, routes, sections and findings in their geographic context.
02Supported geometries
Use the available centreline, section or polygon representation configured for the project.
03Coordinate outputs
Confirm the required reference system and transformation for the delivery market.
04Export structure
Align fields and identifiers with the downstream GIS or reporting purpose.
Network layerValidated sections
010203
Selected road sectionSection 042 · validatedGeometry and attributes preserved
GeometryCoordinatesAttributesIdentifiers
Reporting and evidence
Move from isolated findings to a structured inspection record.
Reports should preserve enough context for the reader to understand the scope, road section, visible evidence and status of professional validation.
Inspection overview
Summarise scope, route, method, cycle and validated inspection status.
Section-level findings
Present findings by road section with the applicable classifications and context.
Visual evidence
Keep relevant source imagery connected to the reported observation.
Professional provenance
Make clear that recommendations were reviewed and the assessment was validated.
Inspection→Road sections→Findings→Visual evidence→Validated report
OGC API FeaturesConfigured resources
GETinspectionsInspection scope and cycle context
GETreportsConfigured report resources
GETreport-sectionsSection-level information
GETdistressesValidated visual findings
Availability and schemas are workflow-specificStandards-based access
API resources
Standards-based access to configured feature information.
Where configured, Inspech exposes supported resources through OGC API Features. This allows downstream applications to request geographic inspection information in a standards-based way.
The available collections, fields, identifiers and access arrangements are confirmed for the operating workflow. The API exposes information; it does not transfer responsibility for its professional interpretation.
Use the API whena repeatable, machine-readable exchange is required.Use an export whena controlled project or reporting handoff is sufficient.
PMS, AMS and system fit
A defined exchange route—not an assumed connector.
Inspech complements the systems and engineering information already used to manage the network.
Designed to complementLCMS · IRI · FWD · skid resistance · pavement engineering · GIS · PMS · AMS
Standards and country outputs
Publish verified support, qualify readiness and validate everything else.
Standards support is not a universal compatibility claim. The applicable method, taxonomy, coordinate system and output configuration must fit the intended market and workflow.
MarketStatusCurrent website treatment
NetherlandsVerified
CROW visual assessment support
The exact method, defect taxonomy and output configuration are confirmed for the project.
BelgiumVerified
OCW support
Use the verified configuration applicable to the inspection scope.
BrazilVerified
DNIT 006/03 and DNIT 008/03
Additional or stricter state requirements, including São Paulo where applicable, are aligned separately.
United KingdomReadiness
PAS2161 workflow and coordinate outputs
Readiness, reporting and coordinate-output support are available for evaluation; the complete workflow is not yet presented as validated.
InternationalVerified
PCI / ASTM D6433
Use the supported PCI configuration and confirm the applicable project requirements.
Other marketsValidate
Configurable taxonomy
A specific standard and output configuration is validated before operational use.
Specific version, scope and delivery details are confirmed during workflow design or Operational Validation.
Frequently asked questions
What GIS, IT and asset-management teams usually need to know.
The detailed output specification is agreed against the actual downstream purpose—not inferred from a generic integration list.
Does Inspech connect directly to every PMS or AMS?
No. Inspech supports defined export, API and exchange routes. A native connector should only be assumed when it has been specifically confirmed for the relevant system and workflow.
Which GIS formats and coordinate systems are available?
Supported geodata formats and coordinate systems depend on the project configuration and market. The required geometry, reference system and field structure are confirmed before delivery.
What is available through the API?
Supported OGC API Features resources can expose configured inspection, report, report-section and distress information. Availability and field definitions are agreed for the workflow.
Can reports include visual evidence?
Yes. Reporting workflows can use structured findings at inspection and road-section level together with the relevant visual evidence and validation context.
Does an export become an engineering decision?
No. Inspech exports validated visual condition information. Engineers and asset managers remain responsible for interpretation, prioritisation and maintenance decisions.
How do we confirm compatibility?
Operational Validation uses representative imagery, standards, output requirements and downstream systems to confirm the complete path before scale-up.
Validate the complete information path
Start with the decision and work back to the required output.
Use a representative route and real downstream requirements to confirm imagery, standards, geometry, reports, exports, API resources and system fit before operational use.
Include in Operational Validation
- Target GIS, PMS, AMS or reporting workflow
- Required geometry and coordinate system
- Reports, fields and visual evidence
- API resources or controlled exports
- Acceptance criteria and ownership