oscarBravo wrote: » Intuitive? You think postcodes should be intuitive? Let's see: I have an acquaintance with the postcode "8700". What does that tell you, intuitively? How about "SY16 1AD"? Or "80112"? "3343810"?
Patww79 wrote: » This post has been deleted.
plodder wrote: » Hardly. It couldn't be Belfast (BT), Dundee (DD), or Oxford (OX) could it? or Liverpool (L) or Manchester (M). Do you think you could guess where the following Eircode routing keys are: A41, T21, H91, F31, E21, P25?
TheChizler wrote: » And that point brings us back to people's problems with the business model (which IMO currently includes an adequate number of free lookups) and not a problem with the design.
plodder wrote: » TheChizler wrote: » And that point brings us back to people's problems with the business model (which IMO currently includes an adequate number of free lookups) and not a problem with the design. It is a problem with the design because: a) the number of free lookups is only for use by people, not software and its not for commercial use. b) the app which has been provided to cater for some use cases (which it does admirably) doesn't cater for all use cases. The web site I linked to above wouldn't be possible with Eircode unless it was hosted by someone who already has an Eircode subscription.
plodder wrote: » It is a problem with the design because: a) the number of free lookups is only for use by people, not software and its not for commercial use. b) the app which has been provided to cater for some use cases (which it does admirably) doesn't cater for all use cases. The web site I linked to above wouldn't be possible with Eircode unless it was hosted by someone who already has an Eircode subscription.
ukoda wrote: » It's not at all a design problem. You know perfectly well that eircode data can be released for free if they so choose. There was a decision made to monetise it. That decision could be reversed and the design would not have to change. They would simply publish the ECAD somewhere and presto it's now a 'free' postcode for all purposes. No design changes needed.
plodder wrote: » Releasing the data (or some of it) for free would certainly mitigate many of the problems, but as you well know also, the decision to use a random code and no hierarchy was partly to prevent people from making use of the system without having the database. PDVerse admitted this. So, you can call it a design feature. I call it a design problem.
ukoda wrote: » Call it what you want, but it is wrong to claim or insinuate that eircode cannot be 'free' because of the way it's designed. That is simply not true. The way it's designed allows for it to either be free or monetised. It was decided to monetise it. And it can be decided to release it for free and there is nothing in the design to stop the ECAD being published on some government website.
plodder wrote: » I have never insinuated or claimed it. I've spent the last couple of months calling for some data to be released for free...
ukoda wrote: » Your post above clearly says it's a design problem that software can't look up eircode for free. It's not. It's a political decision that stops 'free' use of eircode.
The ECAD will work perfectly well with software and doesn't give a crap if it's paid for or not.
D.L.R. wrote: » Not sure why you're so angry that I don't think eircode is a well designed system. But whatever, its my opinion. Design by committee, too many cooks, take your pick.
plodder wrote: » Let me explain it this way. Eircode was designed in such a way that all practical usage of it revolves around a database and there is very little useful information to be derived from collections of Eircodes without having access to the database. That is not the case with the UK postcode. So, it is not simply a political question as to whether the database should or should not be monetised. It is tied directly to the design of the code. Therefore, that is a design problem in my opinion. Of course, but the fact that there is an ECAD was a design decision. You don't need access to anything like the ECAD to make use of the UK postcode for sorting/grouping locations. That is a design issue.
dictionary.com wrote: Intuitive: easy to understand or operate without explicit instruction
Some UK postcode areas: Belfast (BT), Dundee (DD), or Oxford (OX) or Liverpool (L) or Manchester (M). Eircode routing keys: A41 (Ballyboughal Dublin), P17 (Kinsale), H91 (Galway) , R42 (Birr), F42 (Roscommon), Y21 (Enniscorthy)
plodder wrote: » Well you do come across as a bit angry. But, that's by the way. In this context, I'd say easy to recognise without being told in advance. Do you not think the UK ones are more intuitive? Granted to be fair the D codes are, in the same vein as the UK ones (as in D stands for Dublin, rather than we are already familiar with them), but it's the rest of the system ...
ukoda wrote: » It does not meet the criteria of the definition of intuitive as it would have to be deciferable without instruction and there's no way you can tell what DD stands for unless someone tells you or you look it up. You can guess. But that's different.
plodder wrote: » Okay. Let's be even more specific. If we define intuitive in this context as meaning that if you understand that UK postcode areas (a bit like Irish car reg plates) are formed from the initial or final letters of syllables or words in the names of the relevant placecould you then infer or in some cases guess that: L stands for Liverpool M for Manchester OX for Oxford. I think you could If you didn't know that SY was actually Shrewsbury, that's fine. We are talking in general terms and having learned this, we can see the pattern and we are comparing with a system that is considerably less intuitive, because it is largely random. Why is Kinsale P17 and the surrounding areas P72, T12, and P43? If there is a pattern there, I don't see it.
plodder wrote: » Well you do come across as a bit angry. But, that's by the way.
Do you not think the UK ones are more intuitive?
oscarBravo wrote: » How? And, from their perspective, why? Remember: An Post didn't want a postcode.
oscarBravo wrote: » OK, scouts' honour: don't look these up. Intuitively, what areas do these British postcodes refer to - ME? SD? SM? TD? ZE?
Now, leaving that aside for a second, I can concede that the UK postcode system is mostly more intuitive than the Irish one. Yes, you can often guess roughly where a postcode might be. The idea that the Irish postcode system is - and I quote - "shockingly bad" for no other reason than that you can't match the first few characters to a location using guesswork is, with the greatest of respect, a very stupid criticism. I'm still waiting for someone to tell me what's intuitive about "8700", "80112" or "3343810". Or is every postcode system outside of the UK also "shockingly bad"?
plodder wrote: » I'd heard of one them before ZE = Zetland. An old name for the Shetland islands. Of course, none of them are intuitive. And I never said that all of them are anyway. Fair enough, but I'm somewhat familiar with the UK system. I've no idea where those other ones are from.
plodder wrote: » oscarBravo wrote: » Intuitive? You think postcodes should be intuitive? Let's see: I have an acquaintance with the postcode "8700". What does that tell you, intuitively? How about "SY16 1AD"? Or "80112"? "3343810"? SY = Shrewsbury area (quite intuitive) SY16 = "SY16 area covering the areas of Newtown, Powys.The area contains approximately 6,935 households with a population of about 16,021 (2011 census)" SY16 1AD (see it here) It's as intuitive as it can be. You could take a list of all the top level postcode areas in the UK, and hazard a guess at where many of them are, or you could learn them off easily (if you wanted). But, more important, all of the above is free information. It can be presented/used any way you like. You are not restricted by the particular capabilities of an app (that could be withdrawn at any time). You only pay for information down at the household level in the UK.
sondagefaux wrote: » As your example shows, the SY postcode covers addresses in Wales (Powys). Shrewsbury is in England. I'm not convinced that a postcode derived from the name of a town in England is 'intuitive' when it's used for addresses in Wales... Hazard a guess where many of them are? NW = certain parts of north-west London. NE = certain parts of north-east London? No - Newcastle-upon-Tyne WC = Winchester? No - West Central London BT = Belfast, but also every address in Northern Ireland... Can't really see why an address in Co. Armagh with a BT postcode is 'intuitive'...
plodder wrote: » Once you understand their system (like ours) is based around 'post towns' rather than administrative areas, I think it makes sense. I don't recall you complaining about that aspect of Eircode. And of course there are always anomalies - London's areas being the biggest. But, it doesn't change the overall point, especially since Dublin's preexisting codes didn't have the same problem. It's a bit like looking at the car reg plate system and saying they aren't intuitive at all because one or two of them might be ambiguous. (WD could have been Wexford or Waterford for example).
plodder wrote: » sondagefaux wrote: » As your example shows, the SY postcode covers addresses in Wales (Powys). Shrewsbury is in England. I'm not convinced that a postcode derived from the name of a town in England is 'intuitive' when it's used for addresses in Wales... Hazard a guess where many of them are? NW = certain parts of north-west London. NE = certain parts of north-east London? No - Newcastle-upon-Tyne WC = Winchester? No - West Central London BT = Belfast, but also every address in Northern Ireland... Can't really see why an address in Co. Armagh with a BT postcode is 'intuitive'... Once you understand their system (like ours) is based around 'post towns' rather than administrative areas, I think it makes sense. I don't recall you complaining about that aspect of Eircode. And of course there are always anomalies - London's areas being the biggest. But, it doesn't change the overall point, especially since Dublin's preexisting codes didn't have the same problem. It's a bit like looking at the car reg plate system and saying they aren't intuitive at all because one or two of them might be ambiguous. (WD could have been Wexford or Waterford for example).