On 12/10/18 12:57, Dave Swarthout wrote:
What I'm learning by reading this thread over again is that there is a
lot of confusion about relations in the context I'm interested in.
Group or site, whether one or the other will render or, more
importantly for me at least, is whether the object will
Hi all,
It seems that many new mappers use this tag for pedestrian crossings on ways
instead of highway=footway + footway=crossing.
In the past I tried to improve the wiki to make clear that the tag
highway=crossing should not be used on ways
but obviously that did not work.
In November 2015
On 12.10.2018 09:25, Gerd Petermann wrote:
> In November 2015 I fix nearly all such ways, since then the number increased
> again to 488. I don't know about iD, but JOSM prints a warning
> when you use this tagging, still many edits were made with JOSM. I wonder if
> that means that we should acc
On 12.10.2018 09:25, Gerd Petermann wrote:
>> In November 2015 I fix nearly all such ways, since then the number increased
>> again to 488.
the best is to first try to understand where it comes from: look for
recent cases, check the editor tag, ask the user how/why he chose this
>> I wonder i
>Do we really need to re-declare the month ranges each time? I would
>think that
>
> opening_hours=Jun-Sep: Mo-Sa 10:00-18:00; Su10:00-12:00; Nov-Mar:
>Mo,Tu,Th,Fr 10:00-12:00, 15:00-17:00; Sa 10:00-12:00; Apr-May: Mo-Fr
>10:00-12:30,15:00-18:00; Sa 10:00-12:30; Su 10:00-12:00; Oct: Mo-Fr
>10
If they are going to make it complex ... retaliate and make it simple?
opening_hours="see the web site."
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
Am 11.10.2018 um 23:47 schrieb Jmapb:
> ...
> Lengthening the field would be great, but failing that I suppose
> opening_hours_1 is an ok stopgap, though it's unlikely there's any
> end-user software that will look for it. One thing I'd recommend,
> though, is not to end truncate the value mid-cla
> Am 12.10.2018 um 01:27 schrieb Simon Poole:
>> We have a number of keys for which the values can easily exceed 255
>> chars besides opening_hours, lane destinations and conditional
>> restrictions are good candidates. Not to mention changeset tags. With
>> other words it is a general problem whic
I am really impressed by the key opening hours
https://wiki.openstreetmap.org/wiki/Key:opening_hours
However, it is just at my threshold of understanding. I can read the examples
and adapt it for my needs.
In Japan, I was surprised to see shops that are "closed Tuesdays" or similar. I
can tag
On Thu, 11 Oct 2018 at 11:28, Martin Koppenhoefer
wrote:
>
> no, I would remove only those from "vending", which are not about vending.
> E.g. parcels and excrement bags. Those that are about dispensers could get a
> dispensing tag, those that offer completely different services like parcel
> d
A useful tool to verify the expressions is
http://openingh.openstreetmap.de/evaluation_tool/ (is listed on the
page you link)
Only open on the third Saturday: Sa[3] 10:00-13:00
Closed on Tuesdays: Tu off
so e.g. open all week from 9am to 5pm, except Tuesdays: Mo-Fr
09:00-17:00; Tu off
should
Hi!
On Fri, 12 Oct 2018 at 13:33, John Willis wrote:
>
> - Can someone type me the necessary tag value for such a monthly calendar
> dependant item? "Open on the 3rd Saturday from 10am-1pm"
The n-th weekday of the month can be written by appending the number
(1 for 1st, 2 for 2nd, ..., -1 for l
Thanks to both Marc & Markus.
^___^
Javbw
> On Oct 12, 2018, at 9:08 PM, Marc Gemis wrote:
>
> A useful tool to verify the expressions is
> http://openingh.openstreetmap.de/evaluation_tool/ (is listed on the
> page you link)
___
Tagging mailing l
> opening_hours="see the web site."
If one doesn't intend to tag the opening hours, then one better uses the
"website" tag [1] and not the "opening_hours" one.
But it would be a pity one doesn't document opening hours due to a technical
limitation.
As to improving (thinking out loud here...),
Hi,
On 10/12/2018 12:54 PM, Tobias Knerr wrote:
> I agree that this problem calls for a general solution, as it's not
> specific to opening hours.
The "problem" in my eyes is people even wanting to store more than 255
characters in a tag value. Don't do it.
Yes I can see how use cases can be con
Hi all,
I have another scenario of "combined" waste baskets.
How should I tag the ref of a waste_basket integrated into the information
pillar of a public_transport=platform?
For separate waste baskets, I'm following the scheme of
amenity=waste_basket
waste=trash
ref=B101
Where the "B101" is
Le 12. 10. 18 à 19:49, Torbjörn K a écrit :
> After re-reading the wiki on public_transport=platform
> waste_basket=yes
on https://wiki.openstreetmap.org/wiki/Tag:public_transport%3Dplatform
it's bin=yes (but that doesn't solve the question about the ref)
> waste_basket:ref=B42
Imho this one is
Am 12.10.2018 um 18:37 schrieb Frederik Ramm:
> Hi,
>
> On 10/12/2018 12:54 PM, Tobias Knerr wrote:
>> I agree that this problem calls for a general solution, as it's not
>> specific to opening hours.
> ...
>
> Or can we afford to just skip mapping that detail?
>
It is all fine and dandy for us t
Regarding the general workaround of defining some common tag extension
scheme, the idea sounds good at first, but I think this cannot be the
solution after all.
Because, let's not fool ourselves, the application support for an
extension syntax will be almost non-existent. Just look at the support
f
That looks like a nice improvement.
Additionally, I've always wondered why we need to enter :00 after
every hour and zero pad the hours? The shops themselves usually post
the opening hours as 9-17 - why can't we use this human friendly
abbreviation? I don't feel that it would be that much harder t
Bkill, at least in Italy hydrants are strong enough that it is impossible to
brake them using only its key and human force. Anyway, if you think this tag is
usefull, ok, map it.
I'm sure that also in Hungary OSM could help firefighters if hydrants mapping
will become capillar. We in Italy have o
https://github.com/opening-hours/opening_hours.js/issues/270
Thinking loud, I like a set of subcategories.
Basic set for a year, others for the fast change.
I find this a practical understandable solution.
From: OSMDoudou
Sent: Friday, October 12, 2018 5:22 PM
To: 'Tag discussion, strategy and
On Fri, Oct 12, 2018 at 11:24 PM Allroads wrote:
> https://github.com/opening-hours/opening_hours.js/issues/270
> Thinking loud, I like a set of subcategories.
> Basic set for a year, others for the fast change.
> I find this a practical understandable solution.
>
Until I took a look at the gith
It is already part of the specification that "Mo-Fr 9-17" is possible.
Alas, QA tools / the openinghours evaluation tool emit a warning in this
case: "Time range without minutes specified. Not very explicit! Please
use this syntax instead "9:00-17:00"."
Not sure why that is not seen as explicit.
O
sent from a phone
> On 12. Oct 2018, at 09:13, Warin <61sundow...@gmail.com> wrote:
>
> Why not bet both ways?
> Make both a site and a group relation.
why not a multipolygon? I agree that you don’t need additional tags for a group
relation, just type=group, a name and the members, but for
>
> why not a multipolygon? I agree that you don’t need additional tags for a
> group relation, just type=group, a name and the members, but for a site you
> would need something that describes the site, a tag for a group of water
> areas, so as long as all the members are areas (or parts), a multi
Sure but if anyone has something to say that is directly related to my proposal
it would be best to discuss it there.
Other than that, is it complete enough to move it from Draft to Proposed?
‐‐‐ Original Message ‐‐‐
On Friday, October 12, 2018 3:21 AM, Warin <61sundow...@gmail.com> wrot
27 matches
Mail list logo
