Re: [Tagging] Nursing homes

On Fri, 23 Mar 2018 09:06:14 +1000 Graeme Fitzpatrick wrote: > about > the way something has rendered? Not sure where to mention this, so any > suggestions welcome! Have you tried loading affected areas in JOSM and running validator? And fixing reports mentioning real

Re: [Tagging] Nursing homes

On Fri, 23 Mar 2018 09:06:14 +1000 Graeme Fitzpatrick wrote: > The places I've looked at are: Can you link OSM object? Example of link - https://www.openstreetmap.org/node/5323052454 ___ Tagging mailing list

Re: [Tagging] Nursing homes

On 23.03.2018 09:03, Mateusz Konieczny wrote: On Fri, 23 Mar 2018 09:06:14 +1000 Graeme Fitzpatrick wrote: The places I've looked at are: Can you link OSM object? Example of link - As said, there were just tagging errors like building tag on campus, or building

Re: [Tagging] Nursing homes

2018-03-23 0:27 GMT+01:00 Philip Barnes : > On Thu, 2018-03-22 at 19:19 -0400, Greg Troxel wrote: > > In the US, nursing home is basically for people who need skilled > > nursing, which means one or more of > > unable to self-transfer > > > > need an nurse to administer

[Tagging] Parking Fees

Can anyone point me in the direction of a car park example with a parking fee that is time dependant, such as first three hours free then next hour £2 .. Thanks Jonathan http://bigfatfrog67.me ___ Tagging mailing list Tagging@openstreetmap.org

Re: [Tagging] Parking Fees

I just parked in the Triangle Parking for the UW Medical Center in Seattle, WA. The first 30 minutes are free. They also have a flat rate after 5pm of $5.00 although it's not listed on their website. https://www.uwmedicine.org/uw-medical-center/campus/directions There are a number of parking

Re: [Tagging] wetap specific tags

On 24/03/18 00:09, Volker Schmidt wrote: The automatic "source=wetap" is not correct. If you check with the app that a fountain is working, and that sets source=wetap, this is factually wrong. Also the concept of source=whateverapp is not correct, when whateeverapp is a tool to enter data

Re: [Tagging] wetap specific tags

On 23/03/2018 13:11, Martin Koppenhoefer wrote: actually, this isn't an import but an app. Even so, I'd still comment on the changeset made by the person who pressed the button in the app so that they know that there is a problem.  Also of course you can try raising issues in github

Re: [Tagging] wetap specific tags

On 23/03/2018 12:32, Martin Koppenhoefer wrote: I noticed that the wetap app sets tags in a "wetap" name space for properties for which we already have established tags. Here's an example: https://www.openstreetmap.org/node/304151931/history Personally, I'd ask the question of the person who

[Tagging] wetap specific tags

I noticed that the wetap app sets tags in a "wetap" name space for properties for which we already have established tags. Here's an example: https://www.openstreetmap.org/node/304151931/history Specifically, it sets the tag wetap:status=working (IMHO for an amenity this is implied, otherwise it

Re: [Tagging] wetap specific tags

2018-03-23 14:00 GMT+01:00 Andy Townsend : > On 23/03/2018 12:32, Martin Koppenhoefer wrote: > >> I noticed that the wetap app sets tags in a "wetap" name space for >> properties for which we already have established tags. Here's an example: >>

Re: [Tagging] wetap specific tags

2018-03-23 14:09 GMT+01:00 Volker Schmidt : > And this raises the obvious question: Do we have any way of tagging "tag > value verified by survey today" ? This would be helpful in many situations. > I am thinking about the repeated discussions about explicily tagging > default

Re: [Tagging] wetap specific tags

The automatic "source=wetap" is not correct. If you check with the app that a fountain is working, and that sets source=wetap, this is factually wrong. Also the concept of source=whateverapp is not correct, when whateeverapp is a tool to enter data which come from the user of the app. So in most

Re: [Tagging] wetap specific tags

On Fri, 23 Mar 2018 13:32:45 +0100 Martin Koppenhoefer wrote: > The tags are not documented AFAIK. > > What is your opinion for this, shall we tolerate alternative tagging > to be introduced systematically by third party apps, when there is > already an established tag

Re: [Tagging] wetap specific tags

2018-03-23 15:05 GMT+01:00 Andy Townsend : > On 23/03/2018 13:11, Martin Koppenhoefer wrote: > > > actually, this isn't an import but an app. > > > Even so, I'd still comment on the changeset made by the person who pressed > the button in the app so that they know that there is

Re: [Tagging] wetap specific tags

No, obviously, not in the sense that we do that systematically, but the problem exists in real terms. Drinking water is in many places of the world one of hose pieces of information that would be nice to be able to tag: have been here today, it's still working. Petrol stations is another. Or in