Understand the work.
Plan the next step.
Explore project examples, follow a Studio workflow and prepare the questions that help define a useful roadway project.
Follow SR 163 from capture to review.
See how imagery, LiDAR and a draft measurement sheet help explain an observation on one route.
Explore examples ↗02 / MAPSTERSTUDIOExplore the workspace.
Compare imagery, point clouds, assets and study views.
See the software ↗03 / DEMONSTRATIONSFollow a real roadway.
Watch recorded examples of the tools working with captured roadway data.
Watch demonstrations ↗04 / OUR METHODCenterline Assurance.
Read about the method behind our centerline study workflow.
Explore the method ↗Get started in MapsterStudio.
A first review follows four steps. The views and records available depend on your project and account access.
- Find your route. Sign in to Studio and use Routes or the map to find the area you want to review.
- Open the context. Use the available imagery and Atlas point cloud to inspect the same location. Check the capture date before treating a condition as current.
- Review the observation. Inspect the asset or zone record, compare views and use the appropriate measurement tool where the data supports it.
- Share the result. Take a snapshot or open Reports for the study outputs available to your project. Include the location and relevant context for the next person.
The knowledge-base button in Studio opens workflow guidance while you work. For help with your project, use the contact details below. Looking for SignMaster, RailMaster, PaintMaster or CurveMaster? Visit MasterMind software support.
How we check our work.
Follow the checks behind the roadway record: positioning, timestamps, camera and LiDAR alignment, route review and field verification where it matters.
Questions to bring to your project.
What should we provide to scope a project?
A route list or area map, approximate mileage, the assets or questions of interest, existing data and required outputs. Tell us about deadlines, seasonal constraints and the systems that will receive the results.
Can we start with one route or a smaller study?
Discuss a defined starting area with us. Scoping a specific route, asset type or study makes it easier to agree coverage and evaluate the resulting deliverables before planning a wider program.
How long does a project take?
Timing depends on coverage, collection conditions, study type and review requirements. Ask for a schedule covering capture, processing, review and delivery, rather than only a field-collection date.
Can we use the results in our GIS?
GIS exports are part of several existing Mapster study workflows. Agree the file format, coordinate system, attribute fields and destination software before work begins; confirm any direct integration separately.
Who owns the data, and what access is included?
The project agreement should state ownership and permitted use, deliverable formats, software access, retention and any ongoing fees. Confirm those terms in the proposal; they are not inferred from a website example.
What training and support should we plan for?
Define the users and workflows that need a walkthrough, who will manage access, and the support arrangements required after delivery. Existing users can open the knowledge base inside Studio.
Can a study prove every asset is compliant?
A study documents observations and supports review against its agreed criteria. Its coverage, inspection method and acceptance process should be explicit. Engineering decisions and any necessary field checks remain part of the project.
Can the roadway record be updated?
A new capture or targeted follow-up can be scoped when construction, resurfacing or vegetation changes the conditions. Agree the extent, timing and cost of an update as part of that work.