I would add in the wiki that if the tag cave:name=* is absent, name=* can
be considered to be the name of the cave and the entrance. That way we are
consistent with the way the name tag was used until now.
Janko
sri, 7. ruj 2016. u 12:25 Martin Koppenhoefer
napisao je:
2016-09-07 12:08 GMT+02:00 Richard :
> 16477 of natural=cave_entrance + name out there. Redefining the meaning of
> name at this point might not be a good idea.
>
it is at the most a "re-redefining" because originally on the cave entrance
page there was no mention of "name"
On Wed, Sep 07, 2016 at 12:15:16AM +0200, ksg wrote:
>
> > Am 06.09.2016 um 09:44 schrieb Martin Koppenhoefer :
> >
> > 2016-09-03 14:46 GMT+02:00 Martin Koppenhoefer :
> > Are there any objections to make clear on the cave entrance page that
> >
2016-09-07 0:15 GMT+02:00 ksg :
> I understand your intention to remove the inconsistent semantics in
> cave:ref vs name. But redefining a name tag that is already widespread used
> (22k objects) is tricky. I would suspect that many cave entrances have no
> specific names,
On Sat, Sep 03, 2016 at 02:46:40PM +0200, Martin Koppenhoefer wrote:
>
>
> sent from a phone
>
> > Il giorno 31 ago 2016, alle ore 12:23, Richard ha
> > scritto:
> >
> > Apparently such ids are already used in OSM
> > (https://www.openstreetmap.org/node/1049851511).
>
> Am 06.09.2016 um 09:44 schrieb Martin Koppenhoefer :
>
> 2016-09-03 14:46 GMT+02:00 Martin Koppenhoefer :
> Are there any objections to make clear on the cave entrance page that "name"
> on a cave entrance object is the name of the cave
What about renderers? Should they render name or cave:name? If a small cave
has only one entrance, is it right to name that entrance by the name of the
cave? It's probably going to be used that way.
We should tell Nominatim to start indexing cave:name tags.
Janko
uto, 6. ruj 2016. u 09:47
2016-09-03 14:46 GMT+02:00 Martin Koppenhoefer :
> Are there any objections to make clear on the cave entrance page that
> "name" on a cave entrance object is the name of the cave entrance?
>
Thank you all for your contributions, I have now modified the cave entrance
sent from a phone
> Il giorno 31 ago 2016, alle ore 12:23, Richard ha
> scritto:
>
> Apparently such ids are already used in OSM
> (https://www.openstreetmap.org/node/1049851511).
yes, this thread is about the name tag
Are there any objections to make clear on the
On Tue, Aug 30, 2016 at 10:27:00PM +0200, ksg wrote:
>
> In Austria and the adjacent Bavarian Alps of Germany exist a rather
> elaborated hierarchical index of caves (Österreichisches Höhlen Verzeichnis
> (ÖHV) = Austrian Cave Index) -
> http://hoehle.org/downloads/SD_10_Handbuch.pdf. The
> Am 30.08.2016 um 13:39 schrieb Richard :
>
> So what does cave:ref really mean? Should that say something like
> "unique cave identifier"?
> Shouldn't cave:ref be subtyped for example as "cave:ref:at" or
> "cave:ref:fr" for austrian resp french ids to prevent id clashes?
sent from a phone
> Il giorno 30 ago 2016, alle ore 13:39, Richard ha
> scritto:
>
> added that to the description, the docs still need tweaking.
> German cave_entrance description lacks any mention of "cave:ref".
> The english says "number in a cave cadastre" which is
In Spain there isn't any cave cadastre. Each speleology club give a name
and/or ref to the caves they found in their explaration area. Each club has
its own system to name the new caves. So it could be need to specify also
the club in the ref?
It will be cave:ref:es:CEA=A-111 for a cave explored
On Mon, Aug 29, 2016 at 05:20:19PM +0200, Martin Koppenhoefer wrote:
>
>
> sent from a phone
>
> > Il giorno 29 ago 2016, alle ore 12:24, Richard ha
> > scritto:
> >
> > are you saying we should use "cave:ref" just to avoid the use of a relation?
>
>
> according to the
sent from a phone
> Il giorno 29 ago 2016, alle ore 20:25, Kevin Kenny
> ha scritto:
>
> . I find that I wind up creating multipolygons for my own sanity, even where
> I could create a compact polygon by tracing adjacent ways. I'm much more
> comfortable
On Mon, Aug 29, 2016 at 11:20 AM, Martin Koppenhoefer <
dieterdre...@gmail.com> wrote:
>
> > Why? Is there a new trend to avoid relations at all cost?
>
> it's actually an old rule. Relations, being expensive, should be avoided
> where not necessary. They are also less reliable, because you can
sent from a phone
> Il giorno 29 ago 2016, alle ore 12:24, Richard ha
> scritto:
>
> are you saying we should use "cave:ref" just to avoid the use of a relation?
according to the wiki, that's the standard fag to add to a cave entrance for
referring to the cave ref
On Sun, Aug 28, 2016 at 04:56:13PM +0200, Martin Koppenhoefer wrote:
> 2016-08-28 15:23 GMT+02:00 Richard :
>
> > As the cave may have other cave-wide attributes there may be other reasons
> > to have a relation for it.
> >
>
>
>
> no, you just need an object for the cave,
2016-08-28 15:23 GMT+02:00 Richard :
> As the cave may have other cave-wide attributes there may be other reasons
> to have a relation for it.
>
no, you just need an object for the cave, and with natural=cave you will
have this object (could be a node or a way, clearly a
On Sun, Aug 28, 2016 at 02:32:53PM +0200, Martin Koppenhoefer wrote:
>
>
> sent from a phone
>
> > Il giorno 28 ago 2016, alle ore 13:31, Richard ha
> > scritto:
> >
> > So if you have several cave entrances belonging to a cave you could have
> > a relation specifying
sent from a phone
> Il giorno 28 ago 2016, alle ore 13:31, Richard ha
> scritto:
>
> So if you have several cave entrances belonging to a cave you could have
> a relation specifying the name of the cave and entrances with own names.
isn't the relation only needed until
On Sat, Aug 27, 2016 at 03:59:11PM +0200, Martin Koppenhoefer wrote:
> It seems not very consistent that the wiki suggests the tag "cave:ref" for
> the ref of the cave but "name" for the name of the cave.
>
> http://wiki.openstreetmap.org/wiki/Tag:natural%3Dcave_entrance
>
> I would suggest
22 matches
Mail list logo