<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
On 6/25/2018 3:22 PM, Jmapb wrote:<br>
<blockquote type="cite"
cite="mid:701c746a-4de9-96a7-6e57-304a6f3ca6af@gmx.com">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<p>On 6/24/2018 6:22 PM, Paul Allen wrote:<br>
</p>
<blockquote type="cite"
cite="mid:CAPy1dOL8b9YbnEkA82t3EVcFHTN_fd+LKh6e=_-BYeJX53ejPg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div class="gmail_quote"><br>
<div>Map it as the main shop type and ignore the rest.
Or use semicolon-separated values in the shop=, with
the<br>
</div>
<div>main shop type first. Or map each function as a
node in a different place in the building.<br>
<br>
</div>
<div>There's no good way of doing it, just various bad
ways with different advantages and disadvantages.<br>
<br>
-- <br>
</div>
<div>Paul<br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
The variety of this I usually use is: Map it as the main shop
type, and list all services under the description= tag. <br>
<br>
shop=shoe_repair<br>
description=shoe polishing and repair, watch repair, key copying<br>
<br>
But that probably won't help when you're looking to get a key
copied and don't think to check the description tag of the shoe
repair shop around the corner. As you say, no good way to do this,
just various bad ways.<br>
<br>
jmb<br>
</blockquote>
<br>
Pardon the self-reply, but actually, this might be a case where a
shop=shoe_repair could also be tagged craft=key_cutter. Don't see
why not. jmb<br>
</body>
</html>