How to tag a Deer Processing facility?

After a bit of research I think this seems not desirable. I’ve found multiple examples of small meat processing businesses that handle both game animals and domestic animals. Here is an article about one:

Key quote:

Unlike commercial processors, who are licensed to cut meat that may be sold at grocery stores, farmers markets or restaurants, Kidder cannot sell the meat he cuts.

Like all of Vermont’s 35 or so custom-exempt processors, Kidder is licensed to butcher meat only for the personal use of those who raised or hunted the animal, or for those who have bought live animals from farmers under a state law that permits the sale of a limited number direct to consumers.

So this kind of processor is distinct from a larger commercial facility because it is small scale and the resulting meat is for personal use only, not for sale to the general public. The customer can bring game animals they hunted or domestic animals they raised. I’m sure regulations vary around the world, but I imagine a similar kind of distinction may exist exist in other countries as well.

Given this, I think more general term animal_processing should be appropriate. I also see meat_processing was suggested earlier. That could work too. Many other craft key values end in “er” like painter, builder, engraver, plumber. Since this sort of business can be called a “game processor” or “meat processor” it might be nice for the tag value to use *_processor as well for consistency.

Can you elborate on the distinction you are making here? Though these processing facilities are sometimes not businesses, many of them are. The customer brings the animal, pays for the service of having it processed, and then takes away the meat.

Say craft=cleaning | Tags | OpenStreetMap Taginfo mixes both place of work and office, in result HQ office building of cleaning company gets tagged as craft=

if some slaughterhouse chain has HQ office where bunch of people in suits work, and no butchers at all are there. Then ideally it would have distinct tags than place where deer et all are butchered. For example office may be tagged as office=company company=

I see. I guess I thought that was already clear as the craft key page says:

craft=* is used for workshops producing small amounts of goods on demand and by order, and for the workplaces of tradespersons such as electricians and gardeners

This does not describe a corporate office headquarters where only administrative work is done. But if using craft=* for offices is a common mistake, then it would be good to explicitly document that offices should always be tagged with office=* even if the company provides craft=* services at other locations.

yes, but in practice specific tags override platonic ideals of key= descriptions, so I am proposing to clearly mention how purely administrative offices should be marked

such degradation definitely happened with many craft= at least in part, if not nearly all

Could that then be confused with other activities not involving meat? e.g. somebody who shears a backyard flock of sheep / alpacas, or somebody doing small-scale tanning of hides?

Potentially. If we think that would be likely, that would be a good reason to prefer meat_processor instead.

From what I understand, a building should not itself be a point of interest. If it was built to house a specific type of animal such as chicken, that should be represented in the building=* key, or with something like building:use=*, not another key like this.

From the key:building wiki:

For functions in the building (e.g. police station, church, townhall, museum) you should add object with tags like amenity=*, tourism=*, shop=*

If the goal is to describe the function in the building, then animal=* would therefore become a top level key, which contradicts its use as a property in the case of pasture and in the case of the meat processor.

As for pastures, I’m fine with the use of animal=* to describe the grazing animal, although I’m hesitant to further muddy the meaning of the key by appending it to a use case like this.

I moved the proposal to now be craft=meat_processing to be able to specify other types of animals. I also amended that animal=* should be used to describe what is being processed. Let me know your thoughts.

https://wiki.openstreetmap.org/wiki/Proposal:Craft%3Dmeat_processing

I have created an RFC thread.

[RFC] Feature Proposal – craft=meat_processing - General talk / Tagging general discussion - OpenStreetMap Community Forum

At least from a UK point of view, “meat processing” would very much indicate industrial scale processing. We’d call the caft-level people butchers. (They may or may not be associated with a high street butchers shop.) So craft=butcher or craft=butchery would make more sense.

To me, meat_processing implies an industrial process, not craft.

That’s absolutely true, but I suspect that the UK may (now) be a bit of an outlier worldwide.