though this round is about surface=fine_gravel (previous was about
surface=gravel)
while surface=gravel old page claimed that it is for track ballast-sized chunks,
current surface=fine_gravel page describes it as duplicate of surface=compacted
Jan 7, 2023, 03:03 by fors...@ozonline.com.au:
>
Le 06/01/2023 à 23:24, osm.sanspourr...@spamgourmet.com a écrit :
|crossing_strip| - Bande franchissable (tablier pour camions)
L’idée me plaît, mais est-ce qu’on est sûr de vouloir partir sur cette
clé ? J’ai peur que le sens soit trop obscur et que ce soit rapproché du
highway=crossing.
Hi all
Gravel was discussed on talk_au back in March 2021. For anybody
interested its back in discussion at
https://community.openstreetmap.org/t/surface-fine-gravel-is-it-for-loose-gravel-or-duplicate-of-surface-compacted/7533/3
Tony
___
sent from a phone
> On 6 Jan 2023, at 23:34, Niels Elgaard Larsen wrote:
>
> Maybe we could maintain a list of tags that are practical permanent unique
> identifiers. And then have a tool that for most objects could generate a url
> (https or geo) that references that object using that tag.
Bonjour !
J'ai également le même problème. Je reçois que certains mails, par
exemple j'ai que la réponse du sujet "bac à marée" et je trouve ça très
étrange ...
On 1/6/23 16:28, leni wrote:
Bonjour et Bonne Année 2023
J'ai envoyé deux messages sur la liste qui ne semblent pas être arrivés
Sören Reinecke:
> way/node/relation ids in OSM are unstable, not promised to be stable
and anything relying on their stability can break at any point
Right, I know that OSM ids are not stable. The same applies to
coordinates too. If a restaurant puts a 'geo' link on their online pdf
menu card
Bonjour,
une discussion sur le sujet a eu lieu sur
https://community.openstreetmap.org/t/mini-roundabout/7524/51
Au final je propose et ça à l'air de plaire :
|crossing_strip| - Bande franchissable (tablier pour camions)
Avec no comme valeur par défaut sur les "vrais" giratoires et yes sur
Le 06.01.23 à 16:28, leni a écrit :
Bonjour et Bonne Année 2023
Avez-vous eu un problème similaire ?
je n'ai pas vu tes 2 messages (ou alors Alzaimer)
je n'ai rien vu en anomalie (je recois copie des messages d'erreurs
tordues que la liste revoit parfois)
Cordialement,
Marc
Le 6 janvier 2023 15:49:53 GMT+01:00, "Sören Reinecke" a
écrit :
>
>Better would be to have a separate FOSS platform for storing POI information
>using a permanent identifier connected to OSM somehow e.g. by a key
>"somepoiplatformid". But no one created such a platform yet.
>
Probably
Bonjour et Bonne Année 2023
J'ai envoyé deux messages sur la liste qui ne semblent pas être arrivés
sur la liste : je ne les ai pas reçus et je ne les vois pas dans
l'archive (j'y trouve bien le bac à marée que j'ai également reçu).
Je ne sais pas où ils ont été bloqués !!! Avez-vous eu un
Ok, sry. I messed up with my example. I wanted to explain that using
coordinates is not stable either because they don't point directly to the POI,
they just point to the physical reference of the ground on earth.
But at the end we may clarify strongly that osm ids are not stable and keep
On Fri, 2023-01-06 at 13:47 +, Ed Loach wrote:
> > Good point. Also consider that OSM ids have an advantage over
> > coordinates, because if an OSM object gets deleted then a query for
> > that id will return "Not found". That in itself is valuable
> > information
> > to a data consumer.
>
>
> Good point. Also consider that OSM ids have an advantage over
> coordinates, because if an OSM object gets deleted then a query for
> that id will return "Not found". That in itself is valuable information
> to a data consumer.
But rather than being deleted, they may become a different thing,
Jan 6, 2023, 11:50 by valin...@gmx.net:
> To sum up: Coordinates can be used in the same wrong way as OSM id as
> they're both not sufficient enough for the use case most people are
> using it (indirectly).
>
But coordinates can be used correctly (shop updating their location
when their
On Fri, 2023-01-06 at 11:50 +0100, Sören Reinecke wrote:
> To sum up: Coordinates can be used in the same wrong way as OSM id as
> they're both not sufficient enough for the use case most people are
> using it (indirectly). Coordinates are already part of the 'geo' URI
> scheme. There is no
Hi,
On 06.01.23 11:50, Sören Reinecke wrote:
Right, I know that OSM ids are not stable. The same applies to
coordinates too. If a restaurant puts a 'geo' link on their online pdf
menu card with the coordinates to their shop then this is in the same
manner unstable as osm id.
No. The
> way/node/relation ids in OSM are unstable, not promised to be stable
and anything relying on their stability can break at any point
Right, I know that OSM ids are not stable. The same applies to
coordinates too. If a restaurant puts a 'geo' link on their online pdf
menu card with the
17 matches
Mail list logo
