Add education=* tags just like healthcare=*?

On iD, when tagging an object with amenity=hospital or doctors or pharmacy (and probably anything related to healthcare), we get an “incomplete tags” warning which adds the healthcare=* tag as well.

My understanding is that the long-term objective is to add healthcare=* to all these objects, and then to deprecate the amenity=* tags from said objects. Now I don’t know for how long this has been going on, but it sounds good to me.

The education=* key is now also in the same, “long-term objective” situation. However, the iD editor doesn’t show any warning when tagging say an amenity=school or amenity=university.

Is this because it’s a very recently-approved proposal? Is this planned in an update in the near future? (if someone could point me to the right Github repository, it would be great). If so, can I start adding education=* to all the education objects I encounter, at least in my area?

1 Like

Hi Ilias, thanks for bringing this up. (I’m the one who wrote the approved education tag proposal.) The PR to support the education tag in iD is open here. Seems like it hasn’t moved forward yet because it’s a relatively large PR and maintenance on the repo is intermittent. It doesn’t mean you can’t use the tag.

Typically the best way to encourage apps to support a tag in OSM is to use the tag as widely as possible. If there is local support in your country to add education tags to all education facilities then I’d say go ahead and do it. If you are worried about disrupting things then you could propose an automated edit.

2 Likes

Hi Quincy, thanks a lot for your answer. I’ll talk with my local community in Morocco to add the education tag to all educational facilities. Great work, hope the PR will be merged soon.

Hm, so it does.

How does it help to add a duplicate tag such as healthcare=doctor with exactly the same meaning as amenity=doctors, or the equivalent for education?

My experience is that you have to do a bunch of extra processing - if you’re looking for amenity=doctors and find healthcare=doctor, you need to check that amenity is not already set to something else before processing it.

The same will apply to education and any other proposed double tagging.

I think the idea is to eventually migrate away from amenity=* without breaking anything for data consumers right now. I’d imagine once there’s a critical mass of healthcare= and education= tags, the duplicate amenity= tags could be removed all at once?

(I’m not familiar with either tagging scheme yet, so I could be mistaken)

3 Likes

also you get problems like amenity=pharmacy healthcare=pharmacy - marking as disused changes only amenity · Issue #905 · Zverik/every_door · GitHub where mapper for one reason or another changed only of keys

2 Likes

or just process amenity=doctors and ignore presence of healthcare=doctor in any case (which is safe as it is added basically only by pointless validator rules)

It’s not safe to do that.

1 Like

It is mostly safe

And some of this are outdated, badly tagged etc - more often than normally tagged. Further reducing value of processing them.

left: all healthcare=doctor - right: ones without amenity=doctors

At the time (voting on the education proposal) it was pointed out that the healthcare tagging hadn’t actually delivered on its promises, and that basing anything new on its supposed “success” was misguided.

Not to mention that what was actually approved doesn’t make any sense as a tag re-organisation and extension (which is different from healthcare for which the extensions work well).

So continuing to ignore it is the best action.