Re: [Tagging] discrepancy in shop definition and "wholesale" value
wholesale=* (not wholesaler=*) is in the never-approved shop=wholesale proposal and has 677 usages. https://taginfo.openstreetmap.org/keys/wholesale#values Perhaps a wiki entry for wholesale=* is needed, with cross-references between that and shop=wholesale On Tue, Mar 6, 2018 at 6:55 PM, Paul Allen wrote: > > > On Tue, Mar 6, 2018 at 5:39 PM, Martin Koppenhoefer < > dieterdre...@gmail.com> wrote: > > Any more opinions how to handle it? Would we better "kick out" wholesale >> from shop or change the definition for shop? >> > > My feeling, as an English speaker, is that a wholesaler is not a retailer, > and that shop=wholesale is a contradiction. > > We already make a distinction between shops (selling goods) and offices > (selling services, though other types of office exist). I'd go with > wholesaler=*. And maybe expand access to access=trade (wholesaler deals > only with registered traders) and access=public (anyone can shop there). > Something along those lines. > > Of course, there will always be grey areas. > > -- > Paul > > > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > > ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] discrepancy in shop definition and "wholesale" value
Regarding Althio's comment: This is exactly the sort of confusion caused by using the word "wholesale" in shop=wholesale. These are not wholesalers. They are retailers who use the word "wholesale" as a marketing tool. (Even if the parent company has wholesale activities, these particular premises sell at retail.) Typically they will, for example, sell detergent in boxes of 5 kg instead of 1 kg. Or a liter of ketchup. Hence the (USA) term "big box". So they are "wholesale-sized" but not wholesale in the sense of their sales mechanism. (The wholesale=* tag is for wholesalers.) I would not change the definition of shop to avoid retail. "shop=wholesale" describes a particular kind of retailer. (We might want to add that last sentence to the wiki.) John On Wed, Mar 7, 2018 at 8:34 AM, althio wrote: > > I am happy with shop=wholesale and would prefer to change slightly the > definitions and descriptions ["A place selling products or services", no > mention of retail] on pages > https://wiki.openstreetmap.org/wiki/Shops > https://wiki.openstreetmap.org/wiki/Key:shop > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > > ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Tagging for an American Wild & Scenic river
Here's the tagging I used for the Unalakleet River in western Alaska. Only the upper reaches of this river are designated Wild and Scenic. The way for the protected portion is included in a large shapefile I downloaded some time ago that contains all the Wild &Scenic rivers in the U.S. I invented the protection_title because it seems so logical but I invite ideas about this tag and other tagging scenarios. I intend to use this as a model for the other W&S rivers in Alaska, of which there are probably 15 or 20 name=Unalakleet River operator=Bureau of Land Management, Anchorage Field Office protected=perpetuity protection_title=Wild and Scenic River related_law=Public Law 96-487 (ANILCA) scenic=yes site_ownership=federal source:position=DigitalGlobe;BLM shapefile waterway=river website=http://www.rivers.gov/rivers/unalakleet.php wikidata=Q763999 wikipedia=en:Unalakleet River Comments, suggestions? On Mon, Feb 5, 2018 at 10:22 AM, Graeme Fitzpatrick wrote: > > On 5 February 2018 at 06:11, Kevin Kenny > wrote: > >> It's not clear what The Right Thing might be when >> a Wild River is mostly embedded within a Wilderness Area >> (protect_class=1b); it winds up appearing as if the river corridor loses >> protection as it transits the class 1, but that's surely not the case, >> > > You wouldn't think so, would you? > > You'd think that if the river enters a higher rated protected area, then > the higher rating would apply to the river as well? > > Any idea of how "big" an area the Wild River protection covers? eg is it > just the water itself / the river banks / "50m" back on each side / a strip > "1k" wide etc? > > Is it possible to add the =protected tag to the waterway itself, or draw a > long skinny box along the protected length of the river concerned, stopping > as it enters a class 1 park then re-starting on the other side - pretty > time-consuming though :-( > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > > -- Dave Swarthout Homer, Alaska Chiang Mai, Thailand Travel Blog at http://dswarthout.blogspot.com ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature proposal - RFC - Aviation obstacle light
> On Mar 8, 2018, at 6:27 AM, Warin <61sundow...@gmail.com> wrote: > > airmark:light I think is better. there are already approach lights, PAPI lights, etc. I think saying that these are obstacle / hazard warning lights is appropriate. Beyond mapping runways and terminal buildings, The airmark stuff is very specific because people flying planes all use extremely specific language for things to avoid confusion. Javbw. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Feature proposal - RFC - Aviation obstacle light
Date: Thu, 8 Mar 2018 08:27:42 +1100 From: Warin <61sundow...@gmail.com> >* > conditional tagging could be used .. *>* > light_source:conditional=high intensity flashing white *>* > light at sunrise-sunset:low intensity flashing red light at sunset-sunrise* > The day/night is the conditional thing .. and there is already a syntax > for that. So no need to invent another syntax to do the same job in a > different way. What I wanted to avoid is the long "high intensity flashing white light" part where alle attributes are combined into one line. The conditional part would work, and I am fine with that (although I have only seen it for opening hours and for access so far). It would look like this: airmark=obstacle_light + airmark:light:colour:conditional=white@sunrise-sunset;red@sunset-sunrise + airmark:light:character=flashing + airmark:light:intensity:conditional=high@sunrise-sunset;low@sunset-sunrise In most cases tagging will be a lot simpler, for example for an ordinary steady red light: airmark=obstacle_light + airmark:light:colour=red + airmark:light:character=fixed > The syntax for the light ... has that not already been done for seamark? Yes, and I am modeling the proposal on that. Several (sub)keys are used to fully describe all attributes of the light. > As the obstacle is not being tagged - leave that word out. What is being > tagged is a warning light for aircraft .. so airmark:light I think is > better. I am fine with that. We still need to have airmark=obstacle_light in the first line in the examples above because there are many other different aeronautical lights, and we need to denote that the light is marking an obstacle. The other attributes could use the airmark:light key, as in the examples above. I will copy your input to the discussion page for the proposal to keep all comments in one place. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Tag:shop=shotball
Hi, there's already https://wiki.openstreetmap.org/wiki/Tag:shop%3Dweapons How about a subtag weapon:type=* The corresponding sport is here : https://wiki.openstreetmap.org/wiki/Tag:sport%3Dshooting Cheers, Thilo Am 08.03.2018 um 13:00 schrieb Александр Львов: > https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:shop%3Dshotball > > > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Tag:shop=shotball
https://wiki.openstreetmap.org/wiki/Proposed_features/Tag:shop%3Dshotball ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Feature Proposal - RFC - autodrome
https://wiki.openstreetmap.org/wiki/Proposed_features/autodrome ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
