You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the latest GeoPortal conference, I got in touch with some from Queen Mary Uni who have developed an address matching algorithm called ASSIGN. The code is open source and they are keen for people to use it.
Long term, if there are more accurate matching algorithms out there, why should try to use/integrate them into our work.
I now have access to their online matching tool.
I think it would be a good idea to match a sample of records and see how the accuracy compares to some of our own matches.
Even if the algorithm/process is not appropriate for this work, it could even lead to ideas of how to improve our own code/logic.
The text was updated successfully, but these errors were encountered:
From the latest GeoPortal conference, I got in touch with some from Queen Mary Uni who have developed an address matching algorithm called ASSIGN. The code is open source and they are keen for people to use it.
Long term, if there are more accurate matching algorithms out there, why should try to use/integrate them into our work.
I now have access to their online matching tool.
I think it would be a good idea to match a sample of records and see how the accuracy compares to some of our own matches.
Even if the algorithm/process is not appropriate for this work, it could even lead to ideas of how to improve our own code/logic.
The text was updated successfully, but these errors were encountered: