The school I added has: https://avondalees.dekalb.k12.ga.us which is county owned and operated as well as https://avondaleelementary.org which is not operated by the county. I didn’t know if there was a good way to tag it so i put the county run one as website= and the non-county run site as contact:website=. Is there a better way to tag this? The note saying the same things as this post is seen here.
My approach would be to treat the school-operated website as a primary one and so mark it with website= key, while use the website:{appropriate_suffix}= for the other.
Would {appropriate_suffix} be like operator? Or is that more for the operator’s site not the site operated by the operator?
First of all, it’s not required to add all related websites. OSM isn’t a web directory, portal, or search engine.
website= should be the closest to the feature: website=https://avondaleelementary.org (it’s by the School Foundation)
Details
website:*= would be equally confusing whether it should be *:website= as in operator:website= and network:website= , which are the *:website= of the operator:*= and network:*= entities themselves, not the feature. The closest I can think of is eg *_website= from rcn_name= etc for a point’s _name= inside the rcn_*= system. There’s exactly 1 closest to a mall_website= I’m thinking about for shops in malls. mall_website_shop_link | Keys | OpenStreetMap Taginfo
The problem with the 308 alt_website= following *_name= is not being specific, and lack of extensibility ( name= has these confusing alt_short_name= vs short_alt_name= without using some logic). old_website= is worse, as old_operator= is completely indistinguishable between was:operator= previously vs operator:old_name= renamed only.
Adding multiple links could be a data structure question. url= already has thousands of number-suffixed url:*= , with one of them redirected to the main article. But I don’t like it anyway. https://wiki.openstreetmap.org/w/index.php?title=Key:url:1&redirect=no
With all these said, I should emphasize adding multiple websites is unnecessary. The trouble only happens when the feature doesn’t have its own page. Either case, you could simply throw it into url= if it really needs to be in OSM. Otherwise, wikidata= should be used. The nearby =school already has one that can be added. Museum School of Avondale Estates - Wikidata
My suggestion above was somewhat informed by situation in Poland, where public bodies often do have a separate website in addition to main one. In such cases the secondary website is part of Bulletin of Public Information system. I have edited several objects (this one for example), where I used website for the primary site and website:bip for the one belonging to BIP system
as is adding single websites, but it is also helpful and informative.
For this, at least *:bip= can’t be used. It’s the Bila language.
Certainly, a feature could have a page in a government department, open data portal, and even another geodata or map domain. But OSM isn’t suitable for linking to all of them.
For cultural (heritage) features, it is common around here that the place has a page on the cultural ministry and also has a website “on its own”. Both are relevant urls which may also have additional referrers. I agree we cannot collect all links about a feature, but two is often appropriate. website and url can represent it even without multiple values.
I did say url= can be added. In your case, the specific heritage:website= should be used.
Maybe one want to add that either website or contact:website would be used.
If there happen to be both, I wonder if the values differ. (I think they shouldn’t)
I would use “heritage:website” for official sites that are about the heritage protection, while the pages I was writing about are giving general information.
Then you have 3 websites, getting many. Maybe a *:url= towards description:url= , but for official info, not description= by OSM users.
41 tourism:website | Keys | OpenStreetMap Taginfo
- On
heritage=for touristic info, differing fromheritage:website= - Tourist agency websites for attractions and accomodations