Being a Sierra Club member in California, it seems to me that the Yosemite
Decimal System (YDS) [1], originally created by the Sierra Club is made to
order for this. Classes 1 through 3 are basically hiking, 4 is transitional and
5 is technical climbing. My understanding having been exposed to
On Sat, May 23, 2020 at 9:11 PM Tod Fitch wrote:
>
> Being a Sierra Club member in California, it seems to me that the Yosemite
> Decimal System (YDS) [1], originally created by the Sierra Club is made to
> order for this. Classes 1 through 3 are basically hiking, 4 is transitional
> and 5 is
On Sun, 24 May 2020 at 11:11, Tod Fitch wrote:
> Being a Sierra Club member in California, it seems to me that the Yosemite
> Decimal System (YDS) [1], originally created by the Sierra Club is made to
> order for this. Classes 1 through 3 are basically hiking, 4 is transitional
> and 5 is
On Fri, May 22, 2020 at 6:10 PM Mario Frasca wrote:
>
> in reality, I wish we could review the whole setting. and have
> `amenity=healthcare` followed by `healthcare=*` to specify further.
>
> I find the whole repetition confusing, and quite error prone.
>
Agreed. Although, I'm not even sure if
On 5/23/20 5:59 PM, Kevin Kenny wrote:
On Sat, May 23, 2020 at 5:42 PM John Willis via Tagging
wrote:
=path is such a horrible catch-all tag and one that is extremely entrenched - I
am surprised no one has implemented a path=trail subtag, similar to sidewalk,
so we can separate all the
@Dolly,
Since the referral health centers (centres de santé de référence) are
supposed to have at least one doctor in the DRC, they have mainly been
mapped with amenity=doctors. Actually the same tag has also often been used
to map even the more "basic" health centers without doctors. This could
On Sat, 23 May 2020 at 15:53, Tomas Straupis
wrote:
> 2020-05-23, št, 04:51 Jarek Piórkowski rašė:
> > See also: not rendering roads or hamlets in very sparsely populated
> > areas because we have one map style which needs to accommodate central
> > European densities.
>
> OSM-Carto is a very
On Sun, 24 May 2020 at 07:42, John Willis via Tagging <
tagging@openstreetmap.org> wrote:
> =path is such a horrible catch-all tag and one that is extremely
> entrenched - I am surprised no one has implemented a path=trail subtag,
> similar to sidewalk, so we can separate all the hiking trails
I tag for the use of the 'path/road/etc'.
If it is for a walker then I tag the width for the walker, usually this
is the width at ground level but there are ones where the smaller width
is at hip level (rocks) so I tag the width there.
A width of 0.3 me3ans I have to remove my pack and push it
Name of a route, if one exists.
May 23, 2020, 18:17 by winfi...@gmail.com:
> In the end, what will be left in the name tag exactly?
>
> Polyglot
>
> On Sat, May 23, 2020 at 5:53 PM Peter Elderson <> pelder...@gmail.com> >
> wrote:
>
>> I am trying to improve on the name-tag mess in the many
As it is the minimum width that will limit passage, I would prefer to
see the minimum with tagged not the average width.
On 23/5/20 3:23 am, Daniel Westergren wrote:
In the short term, it's okay to tag an estimated, average width.
If it's 1 to 0.3 meters, use 0.5 - this still shows a
On Sat, May 23, 2020 at 5:42 PM John Willis via Tagging
wrote:
>
> =path is such a horrible catch-all tag and one that is extremely entrenched -
> I am surprised no one has implemented a path=trail subtag, similar to
> sidewalk, so we can separate all the hiking trails and other “hiking” paths,
I was under the impression that the consensus was that a route name should be
in a route relation that holds all the segments and that the segment names, if
different from the route name, were on the segment.
Has that consensus changed or has my impression been wrong?
Cheers!
Tod
> On May 23,
=path is such a horrible catch-all tag and one that is extremely entrenched - I
am surprised no one has implemented a path=trail subtag, similar to sidewalk,
so we can separate all the hiking trails and other “hiking” paths, and then
apply different hiking limitations you wouldn’t expect to
May 23, 2020, 20:41 by kevin.b.ke...@gmail.com:
> On Fri, May 22, 2020 at 4:31 AM Mateusz Konieczny via Tagging
> wrote:
>
>> It is extremely rare - if there is single access road to a private residence
>> then it is a driveway no matter whatever it is paved asphalt road or
>> something that
YM routes tagged as superroute? Or all routes with relation members?
Peter Elderson
Op za 23 mei 2020 om 21:08 schreef Jo :
> By the way, superroute relations in JOSM now show continuity correctly if
> the last node of the last way is the same as the first node of the first
> way in two
The refs for the routes I check are sparse, but they are signed here and
there. The legs/sections have the same ref, e.g. LAW12, but nowhere on the
streets can you find the section numbers. They are found on the official
website and in the printed guides. Sometimes they were added to the ref,
but
By the way, superroute relations in JOSM now show continuity correctly if
the last node of the last way is the same as the first node of the first
way in two sequential route relations. (It was a feature request I made and
someone developed it).
Jo
On Sat, May 23, 2020 at 8:47 PM Kevin Kenny
Agree on what?
That leisure=common needs a replacement ? Yes.
that replacement must be different from what needs to be replaced ?
it seems logical to me but some people think that replacing a
depreciated tag by itself will solve the problems that led to its
depreciation.
Le 22.05.20 à 15:46,
> For now, I just want an alternative for the section/segment/leg numbers or
> refs that are often in the name tag now.
> They are there to get neat ordered lists in tools and applications. That
> seems to work fine, but it abuses the name tag, which I am told is a problem
> for searching
True, this route relation business tends to get more complicated all the
time, because the reality is getting more complex all the time.
But, with care, a lot can be done. Consistent tagging, and nudging
exceptions back to the mainstream, will help applications and tools
developers to adapt,
On Fri, May 22, 2020 at 4:31 AM Mateusz Konieczny via Tagging
wrote:
> It is extremely rare - if there is single access road to a private residence
> then it is a driveway no matter whatever it is paved asphalt road or
> something that requires tractor to pass.
>
> Maybe it would matter in case
For now, I just want an alternative for the section/segment/leg numbers or
refs that are often in the name tag now.
They are there to get neat ordered lists in tools and applications. That
seems to work fine, but it abuses the name tag, which I am told is a
problem for searching routines. A name
On Sat, May 23, 2020 at 1:46 PM Yves wrote:
> While the original question was about a good tag to record the section
> number, whick look like a reference, I would be tempted to answer Jo that to
> know which country you're in, you should look at Your OSM Database!
> Joke aside, such a cross
oh, I'm mapping public transport too much. I actually did mean to write
superroute.
Jo
On Sat, May 23, 2020 at 7:44 PM Yves wrote:
> While the original question was about a good tag to record the section
> number, whick look like a reference, I would be tempted to answer Jo that
> to know
While the original question was about a good tag to record the section number,
whick look like a reference, I would be tempted to answer Jo that to know which
country you're in, you should look at Your OSM Database!
Joke aside, such a cross border route makes a good candidate for a super route.
I would say the route name goes on the routemaster relation. That way it's
possible to differentiate in the names of the route relations and make them
more specific. That's probably not what Peter is proposing though.
Jo
On Sat, May 23, 2020 at 7:40 PM Tod Fitch wrote:
> I was under the
So in the case of a route that passes through The Netherlands, Belgium and
France, the part in The Netherlands and Flanders will have the same name
(in Dutch)? And the parts in Wallonia and France will have the same name as
well, but in French instead? No indication which country/region they are
Hold on to your hat In the name tag I will store...The Name Of The
Route!
Op za 23 mei 2020 om 18:18 schreef Jo :
> In the end, what will be left in the name tag exactly?
>
> Polyglot
>
> On Sat, May 23, 2020 at 5:53 PM Peter Elderson
> wrote:
>
>> I am trying to improve on the name-tag
In the end, what will be left in the name tag exactly?
Polyglot
On Sat, May 23, 2020 at 5:53 PM Peter Elderson wrote:
> I am trying to improve on the name-tag mess in the many hiking/foot routes
> in Nederland. All kinds of information is packed in those names. I am not
> doing any cleaning
I am trying to improve on the name-tag mess in the many hiking/foot routes
in Nederland. All kinds of information is packed in those names. I am not
doing any cleaning (yet) until all this information can be stored in proper
tags and is handled or scheduled by significant renderers/data
The proposal for keywords for electric bicycles is now open for voting:
https://wiki.openstreetmap.org/wiki/Proposed_features/ElectricBicycles
Thank you very much, people who participated in the discussion and
Thank you very much in advance for adding your vote!
Jan
> Very well put! If I understand correctly, to do this without heavy
> pre-processing,
> the information would have to be in the tags?
> Would it have to be in the tags of every individual way, or would a tag on
> an encompassing area (e.g. landuse=residential) be sufficient?
Correct.
Tomas Straupis:
> 2020-05-23, št, 04:51 Jarek Piórkowski rašė:
> > See also: not rendering roads or hamlets in very sparsely populated
> > areas because we have one map style which needs to accommodate central
> > European densities.
> OSM-Carto is a very well done DATA VISUALISATION. It is
34 matches
Mail list logo
