On 17 July 2015 at 23:08, moltonel 3x Combo <[email protected]> wrote: > On 17/07/2015, Colm Moore <[email protected]> wrote: >> Adding individual Eircodes shouldn't be a problem. Adding the whole database >> is another matter. Facts can't be copyrighted, databases can. > > And yet there's little value in mapping just a fraction of the > Eircodes. Before starting the job, we need to make sure that we're > leagally allowed to finish it. If we can't have all the Eircodes in > OSM, we should have none.
If it helps somebody locate a house, then it is of value: it is just an alternative way of referencing a place. The eircodes are of particular value where a house has no name/number at all (which many do where I live) -- how am I supposed to find them on OSM? >> On 17 July 2015 11:30:55 GMT+01:00, Simon Poole <[email protected]> wrote: >>>What better way to ignore than come to the conclusion that the data >>>can't be included in OSM and needs to be removed when it turns up? >> >> Whatever the merits or de-merits of the system, it is the official post code >> system. I map a lot of business. Some of them (gambling, e-cigarettes), I >> would prefer not to map, but on OSM I'm a mapper, not an activist. > > I strive to map impartially too, wether I like the place or not. But > postcode are not the same thing, because they're not physical. We > always think twice before adding non-physical data to OSM. And in the > particular case of Eircode: > * It's a list of IDs (useless on its own) created and curated by a > private 3rd-party > * It has an impressive list of technical flaws which make it a > non-starter for many usecases Given it's a list of unique codes for all addresses across the country, you can use it as a primary key in a table and populate that table with other data like a internally created routing code, loc8, openpostcode or whatever else you like. It's quite easy to rationalise the data into something routable, usable or relevant to ones needs. The needs can vary per organisation. I personally don't need a sequencing system to find a house whereas the companies that do can invent their own to suit their needs or translate to a sequencing system that has already been designed to suite their needs. > * It's brand-new, and we don't know how much real-world usage it'll get > * Mirroring it in OSM is a huge amount of work and a lot of data > (which will qualify as bloat if it isn't useful) Putting house names and numbers into OSM is also a huge amount of work, but that hasn't stopped efforts to do that. _______________________________________________ Talk-ie mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-ie
