Image-based mutation recognition is an innovation of NEO from 2001 and has been our core business ever since. We continue to innovate and, by 2021, we have succeeded in automating image recognition of mutations and now achieve operational reliability.
Maintenance of maps
You can update maps in two ways. You start with a new sheet and draw a new map, or you look at what has changed since the previous edition and change only what has changed. In practice, creating a new map is smart if more than 25% of the objects on your map have changed. When your file is in better shape, it makes sense to process the mutations. But in the Netherlands, even that is a lot of work, because on average about 8% of the map objects undergo a 'physical persistent change', a mutation. So you have to be careful, because if you don't update your map for about three years, you'd better start all over again. Of course, you can also update other information files with mutation signalling.
The work process with change signalling
Updating map objects is labour-intensive and precise work. So is detecting and interpreting the changes, but very different in nature. It is then smart to perform change detection and interpretation in a separate action. We call that action change detection: Where does a map object change (was/is) and what should the follow-up action be?
In modern map keeping, quality assurance becomes an important step (completeness, correctness and accuracy). This step can be carried out by increasing the assurance that all mutations are signalled and that at the beginning of a new cycle it is checked that all signals have been processed. Signalling, mapping and checking are then the three steps in the work process.
Why change alerts?
- Imagery is becoming increasingly important and topical;
- Automated change signalling significantly speeds up the work process;
- Change notification is a very good way to gain control over the card maintenance process.
- High quality, and fast delivery times. By using AI and Deep Learning and working object-oriented, we enable one-time collection and multiple use.
We wrote out the service in our Mutation Signalling guidebook and are very proud of the result.
