Two addresses for the same parcel: 588 Cedar Pl, Duncan, BC and 588 Cedar Ave, Duncan, BC

@mraross commented on [Fri May 05 2017](https://github.com/bcgov/api-specs/issues/197)

588 Cedar Pl and 588 Cedar Ave occupy the same parcel.

---

@mraross commented on [Fri May 05 2017](https://github.com/bcgov/api-specs/issues/197#issuecomment-299556742)


---

@mraross commented on [Fri May 05 2017](https://github.com/bcgov/api-specs/issues/197#issuecomment-299556934)

In the screenshot above, 588 Cedar Pl and 588 Cedar Ave occupy the same parcel. They came from two different sources. One of them is wrong.

---

@cmhodgson commented on [Fri May 05 2017](https://github.com/bcgov/api-specs/issues/197#issuecomment-299561280)

Can you think of a way we would programmatically tell the difference between this and for example your favorite, the Central Building, with valid addresses on 4 streets spanning 3 parcels?

---

@mraross commented on [Fri May 05 2017](https://github.com/bcgov/api-specs/issues/197#issuecomment-299562498)

The civic numbers are identical in this case. In general, the cases are:

1. Same civic numbers and suffixes, different something else.
- worth looking into

2. Different civic numbers and suffixes, same everything else.
- probably ok

3. Different everything.
- worth looking into

---

@cmhodgson commented on [Fri May 05 2017](https://github.com/bcgov/api-specs/issues/197#issuecomment-299600720)

We could potentially consider developing an address range QA process that put the points onto the parcel fabric and pointed out all of the potential issues.