Address sometimes parsed as two separate parts

[lukevanin]

Occurs when the scanned text data contains recognisable address data interleaved with other data. The app does not recognise that the two parts of data are related.

The addresses should be merged into a single entity. Separate addresses should stay disjointed.

Possible solutions:

1. Use coordinate proximity to determine relationship.
2. Merge by matching data with corresponding missing fields. E.g. If A has a street but no country, and B has a country but no street, then the addresses can be merged.

This may be resolved using Microsoft Vision API which groups information differently.

Alternatively, allow user to select addresses to merge. Use case:

1. Tap on address.
2. Tap merge button on context menu.
3. List of all other addresses appears.
4. Tap address to merge into.
5. Show preview of merged address. Corresponding fields which both contain content are concatenated. Alternatively user can control the field merging by selecting the fields to be included.
6. A new object is created with the merged data. The merged objects are deleted.

[lukevanin]

Mostly resolved by using Microsoft Vision API for OCR instead of Google.