> shouldn’t we be tagging *all of these* as man_made=incinerators

Yes, I agree this would be helpful. I imagine that most incinerators are
built primarily to dispose of trash. The electrical generation is a
side-benefit but probably doesn’t pencil out financially alone.
On Fri, Feb 15, 2019 at 11:57 AM John Willis via Tagging <
tagging@openstreetmap.org> wrote:

>
> On Feb 13, 2019, at 4:25 PM, Martin Koppenhoefer <dieterdre...@gmail.com>
> wrote:
>
> man_made=incinerator
>
>
>
> Thanks everyone for all the feedback. I will tag them as a
> man_made=incinerator.
>
> Then, shouldn’t we be tagging *all of these* as man_made=incinerators?
> (power and non-power generating alike?)
>
> There shouldn’t be any key/value incompatibility.
>
> for a modern incinerator complex which handles both burnable and
> unburnable waste:
>
> man_made=incinerator
> power=generator
> generator:source=waste
> amenity=waste_transfer_station
> (in fact, the only conflict I see is that amenity=recycling &
> amenity=waste_transfer_station can’t be on the same landuse, which is an
> often shared job here in Japan, but that is for another day).
>
> I feel this should be the main tag for all incinerators. if they produce
> power via a form of waste disposal, then the additional power generation
> tags should be added.
>
> There are obviously power plants (and other industrial processes) that are
> purpose-built to use unrecyclable waste as a fuel (tire-burning smelters,
> etc), but all of these incinerators around me are primarily for getting rid
> of the garbage generated by a city.
>
> I feel we should clarify the tagging scheme to tag *all* these
> incinerators as man_made=incinerator and add the power generation when
> necessary.
>
>
> Javbw
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to