Hi Andrés A. You changed the outer edge of Kisangani to natural=wood. Previously it was landuse=residential, which to me and previous mappers in the area was the correct tagging for the urban area because we see Kisangani as a town not a forest. I am going to return it to landuse=residential. If you have strong feelings about keeping it as natural=wood please respond here. - thanks Craig

I don't support adding a land use tag to a legal boundary polygon. The two data types are both useful but are unrelated - on a GIS they would be different layers. My approach is that the land use mapping should flow over and ignore the legal boundary of any reserve.

Looking at the tag wiki for ref, for the full text string it would probably be best to use a ref tag like:
ref:KE:krb=UCB6 Nairobi

Error: 2026 version above should be 2016 version.
I can help to change the tags if you're ok with that proposal above. I can change all the ref tags to krb-ref and then put abbreviated 2016 style class codes into the ref tags. I will ignore the 2021 Bu or Cu codes for now.

I see they are making a shorter classification - the 2021 system is A, B, C, Bu, Cu. I guess they also hit the long text string problem of the 2026 version...

Thanks for the link to the KRB site - very useful. I was confused as I had not seen any of these UCB codes on Nairobi road signs yet, but maybe that is expecting too much, too fast!
My concern with these codes is that the rendering on osm.org generates a big box because the ref string is so long - which then makes the map ugly. And ugly maps are not user friendly.
What to do? Maybe use an abbreviated version.
Put the full string in in a dedicated krb-ref tag like this "krb_ref=UCB3 Nairobi R3" and a short user friendly version in the general purpose ref tag like this: "ref=UCB3"
Any ideas/thoughts?