Javbw
> On May 16, 2017, at 4:29 PM, Tobias Wrede <l...@tobias-wrede.de> wrote: > > May I suggest to focus the proposal on the frontend for now? The front end is the most difficult part, and having a proposal that covers the chain and many permutations is important. For example, I would _never_ go to a UPS sort facility to ship a package, but I imagine some do in other countries. But tagging a giant commercial warehouse with a package window as "shop=courier" seems wrong. People may come to the courier=* wiki page to tag a courier's warehouse that they see their package is at. Being able to tag it is important. I have added regional_hub warehouses in google Maps when I find my package is first accepted into the tracking system there. People search for where those facilities are all the time. How people use these different services is really complicated too. I would never go to a 7-11 in the US to ship a package, but in Japan, people do. In the US, there are no local delivery centers (at least with FedEx/UPS - they do local sorting on the trucks themselves; they meet in random parking lots and trade packages) the local hub is the last place you will find a big group of trucks. In Japan, they have many tiny delivery centers, where tiny trucks deliver packages and customers can also ship packages at a small retail counter. This is in place of a shop=courier. In urban Tokyo, I imagine they have shop=courier, but out here in suburban/rural we do not. We have a "village hub" and a small retail office combined (for each service), called delivery_centres. A box shop may offer many shipping options, but a delivery_centre is part of the courier's infrastructure, so it is for a single operator. Having all these pieces laid out allows you to choose the pieces your country and region uses and add options to existing businesses to fit local situations as well. Choosing one aspect and one way means people will shoehorn other things into narrow definitions. (I.E.: shop=courier on a warehouse). So shop=courier for "retail" locations, but then you would also need the ability to tag a completely separate business that also accepts or acts as a shipping counter or pick-up point for a courier. I can ship my Amazon package to any combini near my house and pick it up from them when I want. Name=FamilyMart Shop=convenience Courier:ships:kuronekoyamato=yes Courier:ships:sagawa=no Courier:pickup:kuronekoyamato=yes Courier:pickup:sagawa=yes Courier:pickup:Amazon=yes (Amazon is doing more and more shipping itself and also is "the courier" for more and more goods in some countries lately). Guy on a bike service (I imagine they have an storefront somewhere that serves as their little rest stop or the scheduling office, the smallest location we could map). Name=speedy bike messengers Shop=courier Courier:type=messenger Courier:service=local Courier:maxweight=5kg I thought about splitting messengers out to shop=messengers, but I imagine the line between a messenger And a guy doing courier work in a car is so thin that they should be included. After thinking about it a bit, I think we should limit this to non-freight/logistics and create a separate logistics=*for trucking/freight/etc later. But you should be able to tag a commercial warehouse as part of the courier=* tag. Javbw. _______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
