Re: RFC Postal Routing Package

Matt K wrote:

OT, but the way I see it, there's two things that can happen: the customer enters their code wrong, or the code is not in the DB (which gets updated at most every month). Either way the worst thing you'll have to do is fall back on a traditional street/city/state form.

Yeah. Right. With my current implementation this would work. It also tries to propose addresses if nothing matches.

Apologies - it was late :) There are two (or three) separate parts to what you're proposing: translating post codes into addresses and back again, and the part that deals with interpreting handwriting. (Well, along with the checksum/barcode part too). I think this would be most useful if we made those separate packages rather than a complete application.

I personally don't think that we need handwriting interpretation yet. In my applications the user always enters his address somehow. No need to decode. But maybe I have forgotten an important part. At least that's a little bit too much for my skills.

What we'll need: 1. A common database model, capable of handling the PC data from

     multiple countries

2. A descision on how to access it: DB, MDB, DBO, etc 3. A common API for using the data Do you already have a db model? Do you want me to send you the Royal Mail docs?

Yeah. I am allready trying to do this database model with germany and austria. A common model willl never be possible. I am now trying to build independent drivers with common API methods. So the database model is fully independent. It's somehow like the infrastructure of the database abstraction classes in DB/MDB. I don't need royal mail right now. But I would love to see ppl adding their own drivers as son as I am done with the infrastructure :) greetings -- Daniel Khan