I've been mulling this over in the last few days, but it appears to me
the biggest issue at present is one of documentation, specifically
putting things into context and more importantly making them easily
found.
So far nothing seem to fulfill the above criteria, the wiki allows
people to easily d
> From there if an API could be created for editors we could do things
> like mousing over a tag in JOSM/potlatch then throws up a page of text
> describing the tag.
>
> Any tags the are entered that aren't in the database could generate a
> prompt asking people to document it on the spot, alternat
2009/10/18 Mike N. :
>> From there if an API could be created for editors we could do things
>> like mousing over a tag in JOSM/potlatch then throws up a page of text
>> describing the tag.
>>
>> Any tags the are entered that aren't in the database could generate a
>> prompt asking people to docume
On 18/10/2009 12:01, John Smith wrote:
> 2009/10/18 Mike N. :
>>> From there if an API could be created for editors we could do things
>>> like mousing over a tag in JOSM/potlatch then throws up a page of text
>>> describing the tag.
>>>
>>> Any tags the are entered that aren't in the database coul
John Smith:
> the wiki allows
> people to easily document things, but you can't easily find them and
> I'm talking about everyone here, especially those that are only likely
> to use the map features page.
Can you give an example here? I actually don't know what situation you
are thinking about. A
On Sun, Oct 18, 2009 at 8:32 AM, David Earl wrote:
> On 18/10/2009 12:01, John Smith wrote:
>> That's a good point, having some kind of API for tags would make it
>> possible to have translations with very little extra effort from a
>> programming point of view.
>
> Indeed. See my message from ear
On 18/10/2009 14:53, Anthony wrote:
> On Sun, Oct 18, 2009 at 8:32 AM, David Earl
> wrote:
>> On 18/10/2009 12:01, John Smith wrote:
>>> That's a good point, having some kind of API for tags would make it
>>> possible to have translations with very little extra effort from a
>>> programming point
On Sun, Oct 18, 2009 at 10:08 AM, David Earl wrote:
> Which is why I am seeing if we can find a middle way: one that makes
> tags more accessible and manageable in automated fashion, but doesn't
> limit people's freedom to innovate and suggest by example.
A "middle way" is usually either 1) a "so
>> the wiki allows
>> people to easily document things, but you can't easily find them and
>> I'm talking about everyone here, especially those that are only likely
>> to use the map features page.
>
> Can you give an example here? I actually don't know what situation you
> are thinking about. Answ
Mike N.:
> The case I run into is "How do I tag y" - the wiki is well laid out, but
> the answer is often not as accessible as it should be. I tried to tag law
> offices in a meaningful way. Searching for Lawyer, Legal, Barrister even in
> the proposed pages brought up nothing. I can't bel
2009/10/18 David Earl :
> On 18/10/2009 14:53, Anthony wrote:
>> On Sun, Oct 18, 2009 at 8:32 AM, David Earl
>> wrote:
>>> On 18/10/2009 12:01, John Smith wrote:
That's a good point, having some kind of API for tags would make it
possible to have translations with very little extra effo
On 18/10/2009 15:59, Anthony wrote:
> On Sun, Oct 18, 2009 at 10:08 AM, David Earl
> wrote:
>> Which is why I am seeing if we can find a middle way: one that makes
>> tags more accessible and manageable in automated fashion, but doesn't
>> limit people's freedom to innovate and suggest by example
> Why google? There is a search box in the wiki that I'd use first:
> http://wiki.openstreetmap.org/index.php?title=Special:Search&search=lawyer
>
> First hit is the abandoned proposal amenity=lawyer. Unfortunately,
> there's a lot of ODBL and licensing results, too, so maybe we could
> introduce a
On 18/10/2009 17:30, Peteris Krisjanis wrote:
> What we need is - this list where all people who cares about tagging
> (and it already shows that most tagging decissions will be made in
> this part of community) and some kind of wiki book 'OSM Mapping for
> dummies' where could be collected know-ho
Hi!
Peteris Krisjanis schrieb:
>> The discussions over the last few months indicate a lot of people feel
>> there needs to be a more formal tag approval process.
>
> I think not a lot, but majority. Most of us want consistent map data,
> even that "another camp".
+1
> However, I think there is
My main points from my original post still stands, I feel that the
wiki is inadequate to deal with the task of maintaining an index of
tag definitions properly, it is simply too much effort to be useful
for less common tags because you have to spend too much time searching
which takes time away fro
On Mon, 19 Oct 2009, Tobias Knerr wrote:
> Mike N.:
> > The case I run into is "How do I tag y" - the wiki is well laid out,
> > but the answer is often not as accessible as it should be. I tried to
> > tag law offices in a meaningful way. Searching for Lawyer, Legal,
> > Barrister even in the
> Searching the wiki is tedious, at least someone else realised that a
> formal
> search engine did it more efficiently, and has let me know.
http://www.google.com/#hl=en&source=hp&q=insurance+site%3Awiki.openstreetmap.org&aq=f&aqi=&oq=&fp=c807e9ccc08a197a
In this case, it found the relevant r
2009/10/19 Mike N. :
> The case I run into is "How do I tag y" - the wiki is well laid out, but
> the answer is often not as accessible as it should be. I tried to tag law
> offices in a meaningful way. Searching for Lawyer, Legal, Barrister even in
> the proposed pages brought up nothing. I c
I've coded up a VERY VERY basic proof of concept:
http://tags.bigtincan.com
So far you can search for a specific tag name, view the description of
the tag, add a tag and add values for a tag and a description of the
value.
As an example I added the 'highway' tag, and 'motorway' value and
copied
20 matches
Mail list logo
