Hans-Jörg just provided a very nice OA presentation at Foss4G. It was very well attended.
We got also the opportunity to discuss the implementation of the QA concept within OA.
We have basically two solutions:
1. Client side: at every address update, the client will use the reference geocoding services (Google, Bing and Yahoo) and determine if the address is correct or not. Than the QA information is transferred to the server and stored in a QA table
Pros: use current code, limited risk in regard of the number of allowed requests of G, B and Y, possibility to inform client
Cons: performance, load of external library (-> license issue)
2. Server side: at every address update in the PostGis database, a server component will use the reference geocoding services (Google, Bing and Yahoo) and determine if the address is correct or not.Than the QA information stored in a QA table.
Pros: possibility to make batch check, performance, since it's asynchro
Cons: risk in regard of the number of allowed requests of G, B and Y, need to rewrite almost everything
Now, the question: what do you think is the best approach ?
Cu,
Cédric
--