[Tagging] stock effluent disposal sites

[Kyle Hensel]

I’m a bit concerned about using a subtag with amenity=sanitary_dump_station, because it the original approval process (https://wiki.osm.org/Proposed_features/Sanitary_Dump_Station) strongly implied that the tag is _only_ for human waste.

So a subtag would contradict the definition of the main tag, which would be quite misleading.
Presumably some data consumers like opencampingmap.org would take note of the new tag definition, but many people wouldn’t.

Maybe we just need a separate tag like amenity=livestock_effluent_dump_station ?


From: stevea<mailto:steveaOSM at softworkers.com>
Sent: Tuesday, 22 March 2022 10:23
To: Tag discussion, strategy and related tools<mailto:tagging at openstreetmap.org>
Subject: Re: [Tagging] stock effluent disposal sites

On Mar 21, 2022, at 1:27 PM, Kyle Hensel <K.y.l.e at outlook.co.nz> wrote:
> Is it appropriate to use amenity=sanitary_dump_station for facilities that can only be used by livestock trucks? I asked on the osm-us slack, but no one had an answer.
> It is illegal for campervans/RVs to use these facilities.
>
> I was thinking something like amenity=sanitary_dump_station + access=no + livestock=designated, but opencampingmap.org ignores access=no

First of all, with politeness to the site and how / what it decides to render, I'll say that "opencampingmap.org ignoring access=no" might be an interesting datum, but it shouldn't exclusively drive what might emerge as "more correct tagging."  I would get in touch with opencampingmap.org's author and discuss this with her / him / them (pointing back to this thread).

The hangup might be that access=no would apply to everybody (except perhaps the owner, as it sometimes does on other nodes or polygons so tagged), but you want it to only apply to "non-livestock users."  So it seems prudent to coin (develop, make up) a tag that better specifies these semantics.  While I agree that livestock=designated is a good start (and may likely end up being one of the good tags that "sticks" to this semantic), questions remain how to "prohibit everybody else."

An access=no tag doesn't seem right, so something like a class of sanitary_dump_station users (recreational vehicles, livestock waste trucks, private "privy haulers," which pump out septic systems and what are sometimes around here called "honey bucket trucks," municipal sewage treatment plants who temporary overflow — not likely, but I'm imagining a more rich, fuller set of members of the class...) seems correct to develop and establish.  These kinds of categories can be difficult to fully initially establish without wide research, so "a good start" is a good start, and it can be left open for other values.  This (key sanitary_dump_station_users=* — again, I'm "imagining this out loud") might be specified (in a wiki page) to include values separated by semicolons, so that

sanitary_dump_station_users=livestock_waste_truck

could denote livestock_waste_truck users as the ONLY users included at this sanitary dump station, and

sanitary_dump_station_users=livestock_waste_truck;recreational_vehicles

could denote livestock_waste_truck users that include both kinds of users.

Again, these are imaginary examples, but they do indicate how tags (coordinated with a renderer which might actively pay attention to such tagging) might be developed.
_______________________________________________
Tagging mailing list
Tagging at openstreetmap.org
https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.openstreetmap.org%2Flistinfo%2Ftagging&data=04%7C01%7C%7C93f19dbd894d415e49d908da0b811a74%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637834946384159060%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=uh%2FwpMEcDHaxJIBdcRAHIjoG8I7oQWAFa%2BxwgJyfNmk%3D&reserved=0

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20220321/1c875804/attachment-0001.htm>