Vincent Pottier wrote: > Le 02/04/2010 09:01, Lester Caine a écrit : >> Looking at the post code data that has just been 'open sourced' by the UK >> government I am beginning to realise part of the problem here. We are >> trying to >> create a generic solution when in reality there are distinct >> differences country >> to country. >> >> "How are they defined" ... In the UK by a list of house numbers and >> names which >> the Post Office still maintains copyright on, so the OSOpenData >> 'postcode' >> information only has a lat/lon reference (codepoint), and NO address >> data. One >> can draw areas around the group of houses that form a postcode, but >> that is not >> the right way of handling them. The OSOpenData list needs to be >> augmented with a >> lower layer of 'house' objects. ANY boundary drawn around that group >> will be >> arbitrary
> In that case the postal_code_area relation would be a list of houses > rather than a polygon. Actually that still needs to be agreed. Do you add the 'postcode' as a tag to each house, or just create a relation for a post code? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk// Firebird - http://www.firebirdsql.org/index.php _______________________________________________ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
