Template talk:Wikidata ___location map
 | This template does not require a rating on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||
| ||||||||||||||||||||||
_-_The_Noun_Project.svg){kind=small}
Alt text
editHi Mike! Thanks for the great template. Understand that alt text is autogenerated for the ___location map. Would you be able to add support for custom alt text (similar to how caption functions at the moment)? Thanks in advance! Rehman 11:20, 30 July 2017 (UTC)
- @Rehman: I've now added support for manual alt= tags. Alt tags aren't supported on Wikidata at the moment, they're under discussion at d:Wikidata:Property proposal/alt. Thanks. Mike Peel (talk) 16:44, 30 July 2017 (UTC)
- Thanks Mike! Appreciate the quick action. Rehman 02:17, 31 July 2017 (UTC)
Using the Kartographer extension
editHello. Is it possible to have an option to opt-out of the old "___location maps" method, and instead make use of the Kartographer Extension? I tried using the mapframe on my sandbox, and it seems to be working beautifully. Can we add it to this template, so that wikidata-infoboxes can use it too? I personally prefer the old ___location maps to be removed completely, but of course, that is something to talk about. Cheers, Rehman 04:45, 15 August 2018 (UTC)
fallback default map vs. mapframe
editToday I learned that {{Wikidata ___location map}} exists :)
The Wikipedia:Mapframe maps in infoboxes has been going on for a while now, with more recent RFCs about it from 2020.
More recently I've shepherded a lot of onByDefault changes, to make sure we show geolocation when ___location maps are missing, which they often are.
I don't know what the safest choice for the fallback default map is, this one, or the map frame, or both. --Joy (talk) 14:53, 16 August 2025 (UTC)
- I checked the talk pages of the six infobox templates listed here, and there's several mentions of mapframes.
- Indeed, the implementations at Infobox power station, Infobox museum and Infobox UNESCO World Heritage Site were already changed to include mapframe.
- Maybe we should do something for consistency here, like deprecate this template in favor of mapframe?
- Looks like the only people who edited this were @Mike Peel in 2017, @Garzfoth in 2017, @Frietjes in 2018, so I'm adding pings here because it might go under the radar otherwise.
- --Joy (talk) 15:20, 16 August 2025 (UTC)
- Joy, I agree that having both on a page like Pine Bluff Observatory seems unnecessary, and the mapframe version is more flexible/interactive. Frietjes (talk) 16:02, 18 August 2025 (UTC)
- The main difference is context - a ___location map is often a country map, which is zoomed out a lot, while a mapframe is by default a much higher zoom. I wonder if we should just have a low mapframe-zoom default in these cases instead. --Joy (talk) 21:58, 18 August 2025 (UTC)
- the mapframe map in Apache Point Observatory is pretty useless without being zoomed out a bit. Frietjes (talk) 22:14, 18 August 2025 (UTC)
- Exactly. In the meantime I came across {{infobox lighthouse}} which sets a default zoom of 5, maybe we should just copy that for observatories and telescopes. --Joy (talk) 22:18, 18 August 2025 (UTC)
- the mapframe map in Apache Point Observatory is pretty useless without being zoomed out a bit. Frietjes (talk) 22:14, 18 August 2025 (UTC)
- The main difference is context - a ___location map is often a country map, which is zoomed out a lot, while a mapframe is by default a much higher zoom. I wonder if we should just have a low mapframe-zoom default in these cases instead. --Joy (talk) 21:58, 18 August 2025 (UTC)
- Joy, I agree that having both on a page like Pine Bluff Observatory seems unnecessary, and the mapframe version is more flexible/interactive. Frietjes (talk) 16:02, 18 August 2025 (UTC)