<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2013-07-21 14:06, Pieren wrote :<br>
</div>
<blockquote
cite="mid:CAPT3zJpiLcPTKdRM9yj0U5u57YoDxqtoWGKu2_y=WG-N9jXACw@mail.gmail.com"
type="cite">On Sat, Jul 20, 2013 at 11:04 PM, Friedrich Volkmann
<a class="moz-txt-link-rfc2396E" href="mailto:bsd@volki.at"><bsd@volki.at></a> wrote:
<blockquote type="cite">Adresses are attributes of physical
objects, e.g. a parcel, a house, or a
part of a house.
</blockquote>
Parcels can be merged and deleted, houses can be replaced,
shops/restaurants/POI's may change at any time but the addresses
remain. It is more permanent as a simple 'attribute' than all the
'features' you mention.<br>
</blockquote>
Anecdote and fundamental discussion...<br>
<br>
When I built my house, I went to the town hall to get a number
assigned.<br>
I expected a problem because the houses on each side were nr 1 &
3.<br>
- No problem, sir, everything was planned, you get nr 2 [normally on
the other side]<br>
- ahem, there are 2 parcels between 1 and 3<br>
- No problem, sir, everything was planned, see (pulling plates), you
get nr 2a<br>
- ahem, I built my house on the second parcel<br>
- No problem, sir, then (swapping plates) it's nr 2b for you<br>
So did <strike>1</strike>I live at mystreet 2b.<br>
But only for a few years. The communes merged, street homonyms were
renamed and...<br>
all houses renumbered thoughtfully. I've lived at nr 5 since then.<br>
Only thing is, I almost lost a friend. The guy living at nr 26 :-)<br>
<br>
I hope you won't mind my feeling that my house is the object and the
numbers the attributes.<br>
<br>
Your speaking of objects and attributes delights me.<br>
That's exactly the way I think of the different features in OSM.<br>
Unfortunately, in the OSM tag definitions, there is no mention of
being an object or an attribute.<br>
And in practice there can be much confusion.<br>
<br>
An object is the physical thing. It's unique.<br>
An attribute is the different forms, usage etc... of the object. It
can be multiple.<br>
<br>
We've already talked of how to tag a château<br>
historical=castle<br>
It is strange to seem to say that a castle is "<i><b>a historica</b></i>l",
especially if it's not historical.<br>
In my mind, it should be:<br>
building=yes<br>
castle=yes (or =type IF AND ONLY IF any type is exclusive, e.g.
=château instead of...)<br>
château=yes<br>
hotel=yes (because château can be used as hotels in addition to
being château)<br>
historical=no (or yes or 1200?)<br>
<br>
<a href="http://www.openstreetmap.org/browse/way/180545448">Same
kind of problem here</a> with a sort of concrete basin, like a
swimming pool, where fishes to be fished are thrown<br>
This object is undoubtedly a piece of water:<br>
water=?<br>
But OSM seems to require that object to be called "<i><b>a natural</b></i>",
although it's not natural at all.<br>
Furthermore, I want to state that this water is made for leisure
with a an attribute "leisure=".<br>
And once again, Osmose clashes with saying that "<i><b>a leisure</b></i>"
is a conflicting <i><b>object</b></i> once again.<br>
<blockquote type="cite">
Tag en conflit<br>
Conflit entre les tags natural, leisure<br>
way 180545448 rawedit josm<br>
water = pond<br>
natural = water<br>
name = Pêcherie du Tultay<br>
leisure = fishing<br>
Erreur reportée le : 2013-07-23 <br>
</blockquote>
In my mind, that tagging should resemble this:<br>
water=basin<br>
natural=no<br>
phishing=yes<br>
leisure=yes (industrial=no)<br>
pay=yes<br>
drinks=yes (to spare a separate amenity object)<br>
talking=no<br>
bicycle=carefully ;-)<br>
<br>
Cheers,<br>
<br>
<table>
<tbody>
<tr>
<td>André.</td>
</tr>
</tbody>
</table>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>