When QA’ing the maps, there are four primary things to look at:
...
This page helps you get started on the QA process and outlines in which cases an error needs to be solved by you/the customer or by MazeMap.
Please scroll to the bottom to see how to submit a QA support ticket or click here
| Anchor | ||||
|---|---|---|---|---|
|
1. The
...
Polygons
Our processing tool is powerful and accurate, but the output depends on the quality of the input (the CAD file). There might be cases where our processing tool misinterprets a drawing.
...
Please note that the POI title is not necessarily the same as the text shown in map. This depends on the setup in the POI list.
You can find more info about POI lists here https://mazemap.atlassian.net/l/c/j8vLiY7X and here https://mazemap.atlassian.net/l/c/hZL2d9mo
In case all of the following has been checked but something is still wrong, there might be a problem that will need to be handled by MazeMap:
...
Make sure that the paths are correct and follow footpaths and (not roads for vehicles. )
Check that stairs and ramps (both in buildings and outdoors) are marked as “Obstructions for wheelchairs”
Click on a building in the map or select a building in the selector here:
...
Make sure that there’s a node in each room and that floors are connected via stairs/lifts:
Make sure that the path network uses the correct exits/entries (beware of emergency exits):
You can test a path inside the path editor:
...