2010/7/1 John Smith :
> Not that I'm advocating this at all, and not that english names can't
> be used in the same manner for the purposes of translations, but there
> is several ways you could do this and have numbers that didn't
> conflict, for example you could use UUIDs, you could do a hierarc
On 1 July 2010 18:23, M∡rtin Koppenhoefer wrote:
> nobody will ever need more than 640 kB of RAM ;-)
I assume you are talking about how Yahoo generates WOEs, but I'd love
to see anyone that can exceed the capacity of UUIDs :)
> sure, there could be ways, but actually I don't see the benefit. I
2010/7/1 John Smith :
>> we already do this with presets, and I don't like the concept either
>> ;-), I'm using the english JOSM version because of this. Part of the
>> "problem" in this thread derives exactly from this (soccer vs
>> football).
>
> You disagree with the translation someone else mad
On 1 July 2010 19:08, M∡rtin Koppenhoefer wrote:
> no, I don't generally disagree with the translations, the thing is:
> (almost) every tag (at least of the ones in the presets) is documented
> in the wiki in English, many of these definitions are not translated
> into other languages. As long as
2010/7/1 John Smith :
> On 1 July 2010 19:08, M∡rtin Koppenhoefer wrote:
>> no, I don't generally disagree with the translations, the thing is:
>> (almost) every tag (at least of the ones in the presets) is documented
>> in the wiki in English, many of these definitions are not translated
>> into
On Thu, 1 Jul 2010, Steve Bennett wrote:
> What context are you thinking of? Forgive my ignorance, but if tagging
> leisure=pitch, don't the two codes use the same pitch?
in rural au - no
each code has its own grounds whether owned by a club or the council.
perhaps in the cities where space is more
In fact, the technique of having the user select from a list of words, but
actually storing the value as an arbitrary ID (generally numeric), is the
recommended technique in database design. It is called "normalizing the
database". Having the linking value be an ID value means that, should you
On Thu, Jul 1, 2010 at 8:08 AM, John F. Eldredge wrote:
> In fact, the technique of having the user select from a list of words, but
> actually storing the value as an arbitrary ID (generally numeric), is the
> recommended technique in database design. It is called "normalizing the
> database".
2010/7/1 Bill Ricker :
> On Thu, Jul 1, 2010 at 8:08 AM, John F. Eldredge
> wrote:
>>
>> In fact, the technique of having the user select from a list of words, but
>> actually storing the value as an arbitrary ID (generally numeric), is the
>> recommended technique in database design. It is calle
On 1 July 2010 22:29, Peteris Krisjanis wrote:
> Let's better clean up and "normalize" tags, improving schemas and relations.
+1
Lets not confuse tag normalisation with translations/indexing.
If the current translation of keys/values isn't sufficient then lets
improve it, but not at the cost of
On Thu, Jul 1, 2010 at 4:23 AM, M∡rtin Koppenhoefer
wrote:
> sure, there could be ways, but actually I don't see the benefit. I
> think it's cool that most tags are understandable directly in the xml
> without the need for any translation tables.
The benefit is precisely the removal of the thing
On Thu, Jul 1, 2010 at 8:08 AM, John F. Eldredge wrote:
> In fact, the technique of having the user select from a list of words, but
> actually storing the value as an arbitrary ID (generally numeric), is the
> recommended technique in database design. It is called "normalizing the
> database".
>
2010/7/1 Anthony :
> The benefit is precisely the removal of the thing you find cool. People
> won't think they understand a key/value simply because they see the name of
> the tag.
I see your point and it is valid sometimes, but often it is not. E.g.
amenity=post_box or oneway=yes. Or landuse
On 2 July 2010 02:01, M∡rtin Koppenhoefer wrote:
> Most of our tags are not disputed.
If it's a safe assumption that most tags are not disputed, do we turn
disputed tags into numbers?
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.open
On 15 June 2010 07:09, John Smith
> In fact I'd be tempted to call them a specialised college's and
> sub-tag from there.
In India colleges are mostly (99 %) bound by academic regulation from
higher education boards/ universities . Guessing it would be the same
elsewhere .
While I am looking for
2010/6/3 y...@o2.pl :
> Well maybe something like shop=vehicle_repair + repair:car=yes/no +
> repair:motorcycle/bicycle/etc=yes/no?
> I think that part of them repair many kind of vehicles.
Maybe some do . But in India they tend to be different .
If there is an idea of combining motorcycle and ca
On Thu, Jul 1, 2010 at 12:01 PM, M∡rtin Koppenhoefer wrote:
> 2010/7/1 Anthony :
>
> > The benefit is precisely the removal of the thing you find cool. People
> > won't think they understand a key/value simply because they see the name
> of
> > the tag.
>
> I see your point and it is valid somet
On 2 July 2010 02:33, pavithran wrote:
> If there is an idea of combining motorcycle and car tags then
> amenity=bicycle_parking can be changed ?
> http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dbicycle_parking
>
> Or are they better kept separate ?
I'm so tempted to say this should just be an
When people use power=generator, which is more common: tagging just the
building where the generator is housed, or tagging the entire facility
(including coal pile, gas tanks, offices, rail yard, etc.)? Whichever one
you do, how do you mark the other one, if at all?
--
...computer contrarian of
On Thursday 01 July 2010 20:52:58 Phil! Gold wrote:
> When people use power=generator, which is more common: tagging just the
> building where the generator is housed, or tagging the entire facility
> (including coal pile, gas tanks, offices, rail yard, etc.)? Whichever one
> you do, how do you ma
On Fri, 2 Jul 2010, pavithran wrote:
> On 15 June 2010 07:09, John Smith
>
> > In fact I'd be tempted to call them a specialised college's and
> > sub-tag from there.
>
> In India colleges are mostly (99 %) bound by academic regulation from
> higher education boards/ universities . Guessing it w
On 1 July 2010 22:08, John F. Eldredge wrote:
> In fact, the technique of having the user select from a list of words, but
> actually storing the value as an arbitrary ID (generally numeric), is the
> recommended technique in database design. It is called "normalizing the
> database". Having
22 matches
Mail list logo
