Verification of the map structure
After creating the navigation area, you need to ensure that the physical dimensions of the map are correct. This information is indicated at the bottom of the web panel window. Afterward, you need to check that parts of the map unable for location are covered by the Barriers tool from the Navigine system web panel. While drawing barriers, you should be guided by the following:
- Barriers should cover the entire area outside the perimeter of the exterior walls of the building. This will allow the positioning algorithms to keep the focus on the possible area inside the facility.
- Barriers inside the building shouldn’t be constructed in a way to leave too narrow paths. So, when drawing barriers around doors, it’s better to step back from the door frame and leave free space. Besides, when drawing a large object in the middle of the corridor, you better make it a little narrower. Compliance with these recommendations will ensure smooth positioning. As result, the flow of particles projecting the estimation of the user's position will be eddying freely around obstacles.
The following figures show examples of correct and incorrect rendering of Barriers.
While using routes (graphs), make sure the routes are connected, so all edges must be linked to other parts of the route map. An example of an improper situation is shown in the following figure.
Positioning quality control procedure
To assess the positioning quality and ensure that all beacons are placed correctly, it is essential to carry out the procedure of recording logs. Logs must be collected for each sublocation: due to a comprehensive analysis, it will be possible to find out any sharp jumps, the degree of smooth positioning, and repeatability of results.
For the log to be informative, you must comply with the following terms:
* The duration of the log recording is at least 2 minutes. This is necessary for the solution to converge to the true one.
* The route must cover the entire available area where the object may be located and where the beacons are deployed. This will prove that all beacons are correctly configured and working.
* The route must start and end at the same point. This will allow you to evaluate the quality.
* The time of the start and end of logging is clocked. This allows to receive additional logs from other devices recorded same time, same place.
The following figure shows an example of a bad and a good route for log recording.
We recommend making the following sequence of actions:
1. Schematically draw a route.
2. Fix the start time of the log recording.
3. Open the Navigine app.
4. Select the active location, go to the “Navigation mode" section, choose "Recording plain log”.
5. Follow the planned route.
6. Finish recording the log.
7. Mark the end time of the log recording.
Furthermore, you need to send the recorded log along with the description to Navigine. You can do this by using the “Logs" tab and “Share or send” dialogue directly from the Navigine app.
Here is the example of the table which can be filled in during collecting logs:
| Location ID |
Route scheme |
|
| Sublocation ID | ||
| Start time of the recording | ||
| Finish time of the recording | ||
| Device model |
In some cases, you’ll need a log recording using the ‘Polyline log’ tool.
Polyline log measurement
1. Go to «Add beacons mode» and click on the “measure log along polyline” button (see Fig.1) in the bottom right corner.
2. After that you will see a menu (Fig.1) for specifying a polyline (a route you will take while recording the log).
3. A polyline is presented by a set of points that you will have to specify in this menu. Please note that starting point will be created at the position of the cursor upon clicking on the bottom right button. Other points are specified by moving the cursor to the proper place and clicking “Add point”. After the last point is specified, you click “Finish”. If you made some mistakes and want to cancel this line, simply click on the bottom right button again.
4. Now you have to go to the start point. At that point, you click “Start Measuring” (Fig.2) and start walking along the route and at the same time. Our processing algorithms assume constant velocity motion, so please don’t make stops during log recording and try to keep approximately the same speed during walking.
5. Each time you pass another checkpoint (vertex), you click “Checkpoint” (Fig.3) in the application, so the application can bind your current position to the current time label. All passed points and sections will be marked with green color.
6. After the last checkpoint you will be shown the name of the resulting log file and you can click “Finish” (Fig.4).
7. The file will be located in the same folders as regular log files (documents/Navigine/$Location_id$/).
Compared to a regular log (containing all incoming signals/sensors information), this type of log also contains info about the reference (real) path with blinded timestamps. Having this info gives us more opportunities to debug problems and tune navigation parameters
