Module talk:Location map/Archive 11

This is an archive of past discussions about Module:Location map. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.

I find that when no caption is given the text that follows the map flows round it rather than starting below it, Which can give ugly results when the map is large. Adding a caption solves the problem. E.g.

Umangi

Yambuya

Bomane

Djabir (Bondo)

Ibembo

Ekwangatana

Yakoma

Locations in the Congo

No problem when a caption is given. But when there is none, text flows awkwardly:

Umangi

Yambuya

Bomane

Djabir (Bondo)

Ibembo

Ekwangatana

Yakoma

Location map/Archive 11 (Democratic Republic of the Congo)

Scroll to the bottom of this window, click "Mobile view" and size the window to about 400px to see the effect – or just view this page on a phone.

Is this something that can / should be fixed? Aymatth2 (talk) 12:04, 4 November 2021 (UTC)

Hello everyone!

I am interested in knowing the procedure of creating a location map from scratch. (how to I establish the coordinates for the sides as well as the center)

Can anyone help me?

Cheers, DariusConopidovici (talk) 21:35, 16 November 2021 (UTC)

@DariusConopidovici: I suggest that you start with Template:Location_map/Creating_a_new_map_definition and Wikipedia:WikiProject Maps/Conventions/Location maps. There are additional resources at Wikipedia talk:Graphics Lab/Map workshop and the Commons:Graphic_Lab/Map_workshop. None of these seems to adquately address your question about finding the extent, lat/long boundaries in any detail. For me, I use the program QGIS which automatically provides this information for a given project. One limitation is that QGIS will not read in a SVG format. In this case, I created a raster image from the SVG. Then used the QGIS georeferencer. If you want more help, feel free to ping me. - DutchTreat (talk) 15:19, 4 December 2021 (UTC)

Thank you for your indication. I am QGIS user so I'll try to see how this can be worked out. Was also thinking about the BBOX corner coordinates of the image in WGS84 that can help with defining some borders. I ll do a couple of tests and I'll ping you if there is something to discuss in detail.Cheers and have a great weekend DariusConopidovici (talk) 22:24, 4 December 2021 (UTC)

@DariusConopidovici: The map I created in QGIS is called Module:Location map/data/New Zealand Wellington Region. Put a rectengle frame as a vector layer to use a clipping boundary. QGIS displays the bounding box coordinated in the layer properties. Good luck and enjoy the adventure of mapmaking. - DutchTreat (talk) 11:33, 5 December 2021 (UTC)

Thank you for your feedback! Any idea where I can find data that I can process and easily add to wiki (I am referring to administrative areas)? I know about GADM (https://gadm.org/data.html) and OSM but I am not very sure if that can be used here. What do you use? Have a great Sunday! DariusConopidovici (talk) 13:22, 5 December 2021 (UTC)

@DariusConopidovici: Use either OSM or Natural Earth Data (admin boundaries part of the "Cultural" section for each map scale). The license for GADM is restricted for commercial use. It is not a free license. The data cannot be used for Wikipedia projects. See details at Commons:Licensing. Hope this helps! - DutchTreat (talk) 12:09, 6 December 2021 (UTC)

@DutchTreat: So I made this Module:Location map/data/Gabon Woleu-Ntem. What do you think? How do I transform the PNG to SVG? Best regards DariusConopidovici (talk) 09:46, 7 December 2021 (UTC)

@DariusConopidovici: SVG is the preferred format. When you export from QGIS, you will want to choose the SVG format. Have you looked at this map? File:Gabon, administrative divisions - de - colored.svg I'm having some trouble reading the map that you created. The whole country of Gabon is not visible, I think. In the upper right, it would help to show the whole country in the highlight color with surrounding countries of Cameroon, Congo and Equatorial Guinea in grey. - DutchTreat (talk) 15:24, 7 December 2021 (UTC)

@DutchTreat: Thank you for the feedback. You mean that I should make a smaller frame in the map showing where the region is located in Gabon? (in the same manner that you showed that area on the Southern Island of New Zealand?). I'll get to work and fix it :). DariusConopidovici (talk) 19:07, 7 December 2021 (UTC)

@DariusConopidovici: After looking at these maps Commons:ser:Sting/Gallery: Location and locator maps, I think it is best to remove the inset map of the region from the upper right. You can see for both Algeria and Chad that no inset is used for each of the admin areas. - DutchTreat (talk) 12:08, 8 December 2021 (UTC)

Location marks should appear on the full-sized map when you open it. This seems like it should be technically simple to implement and it's strange that it's not already in place. I can't be the only person who's bothered by this, right? 2601:1C1:8800:1AF0:3D63:F167:97B9:EE48 (talk) 03:08, 25 February 2022 (UTC)

Not sure if this is the place to request this, but could we get a map for Tokelau? The “best” i found for List of villages in Tokelau is Oceania. Maybe even a Polynesia map would work better. The islands are just north of American Samoa, for context. --awkwafaba (📥) 03:20, 22 February 2022 (UTC)

@Obersachse, John Carter, and Dr. Blofeld: looping you in as you were involved in the earlier discussion. --awkwafaba (📥) 13:53, 24 February 2022 (UTC)

Ask this German editor here @Awkwafaba:. Where are you from?♦ Dr. Blofeld 21:56, 24 February 2022 (UTC)

@Dr. Blofeld: unfortunately not from anywhere that would instill enough knowledge of German to post on that page. Neither from Tokelau. --awkwafaba (📥) 02:43, 25 February 2022 (UTC)

He speaks English LOL.♦ Dr. Blofeld 07:17, 25 February 2022 (UTC)

At present the handling for secondaryModules seems to directly copy the options for marks from the smaller modules, without care about size. This is fine for real map markers, but for road overlays such as the one in Module:Syrian Civil War overview map (it's originally in the detailed map, but I moved it into the overview) it gets problematic when transcluded into Module:Syrian and Iraqi insurgency detailed map. Maybe we should do something to stretch these sort of size-sensitive not-quite-marks.

The following is a strawman proposal and is not a real edit request. At least not until someone else concurs that we need to do something about it. We should add a new {{location map~}} option to be ignored by the template called preserve_scale; this indicates the secondaryModules code should stretch the image to fit. Then we go into that code and write something like the following to actually do it:

	if dataModule.secondaryModules then
		for _,modname in ipairs(dataModule.secondaryModules) do
            local mod = mw.loadData(modname)
            -- ignoring multi-map for this prototype. also ignoring height stretch (because there's no "height" for {{location map~}}) and non equirectangular (because we can't do complex stretching and calculation is messy)
            local m_map = locmap.getMapParams(mw.getMapParams(mod.containerArgs[1]), frame)
            local m_width = mod.containerArgs.width
            -- calculate width of the mod's map under current frame's params (width left right)
            -- calculate scale ratio = width ratio
			for _,markArgs in ipairs(mod.marks) do
                if markArgs['preserve_scale'] ~= nil then
                   markArgs['width'] = markArgs['width'] * scale
                end
				marks[#marks + 1] = tostring(locmap.mark(frame, markArgs, map))
			end
		end
	end

Artoria2e5 🌉 14:03, 2 March 2022 (UTC)

I reported here that Module:Location map/data/USA Northeast was moved to Module:Location map/data/USA Midwest and Northeast and that has broken several articles. For example, Premier Hockey Federation is showing 'Lua error in Module:Location_map/multi at line 27: Unable to find the specified location map definition: "Module:Location map/data/USA Northeast" does not exist.' A discussion at Commons was mentioned in the edit summary. Any views on what should happen to fix the article errors? Possibilitis are to revert the move, or to fix the articles, or possibly to cop out by making an effective redirect at the original title. Johnuniq (talk) 06:33, 9 March 2022 (UTC)

I don't think a redirect is a cop out -- there are plenty of redirected location maps. — hike395 (talk) 07:40, 9 March 2022 (UTC)

OK, I created the redirect. Johnuniq (talk) 08:10, 9 March 2022 (UTC)

@Johnuniq: My apologies for breaking the articles and thanks for cleaning up my mess. I am used to automatically created redirects solving any issues when moving a page. While I don't expect to have to move any modules anytime soon, I will make sure to be more careful if I have to do so and seek a broader consensus. –Noha307 (talk) 04:39, 20 March 2022 (UTC)

No problem! Johnuniq (talk) 05:21, 20 March 2022 (UTC)

I was editing the Bhopal disaster and I would like to have the following: one map which shows the location of Bhopal within India and one that shows the location of the plant in Bhopal itself. What would be the best approach to it? PhotographyEdits (talk) 15:04, 9 April 2022 (UTC)

Should the template {{Location map data documentation}} have some instructions on use? – Reidgreg (talk) 18:58, 10 April 2022 (UTC)

This edit request to Template:Location map data documentation has been answered. Set the |answered= parameter to no to reactivate your request.

• A list of submaps here AXONOV (talk) ⚑ 09:03, 22 April 2022 (UTC)
  •  Done – also note that a separate, unprotected documentation (/doc) page has been created, so please check it and improve as necessary. P.I. Ellsworth - ed. ^put'r there 11:09, 22 April 2022 (UTC)

Lua error in Module:Location_map at line 422: No value was provided for longitude. in infobox at iSimangaliso Marine Protected Area, but there is a coordinate for the page, and several other pages for marine protected areas seem to work fine. · · · Peter Southwood ^(talk): 07:05, 10 July 2022 (UTC)

Ther error is because the coordinates were not included in the {{location map}} template. The article already had a map specified by |map_image=. If you want to replace that with a location map, the template supports that with |map= which I added within a comment. You can uncomment that and see the result. Or did you want to show both. MB 16:07, 10 July 2022 (UTC)

Also getting maybe a different problem at infobox of Trafalgar Marine Protected Area, where the position is displaying in the wrong place. the red dot is displayed at somewhere near 34S, 20E, while it should be at the position in the only {{coords}} template on the page, about 30S, 30E. · · · Peter Southwood ^(talk): 13:43, 10 July 2022 (UTC)

OK, I see you did want both maps so I have got it working by specifying the coords in {{location map}} in both articles. MB 16:22, 10 July 2022 (UTC)

Follow-up, the template will pull the coords from WD if they are present there. In iSimangaliso, there are no coords in WD which is why you were getting no map at all. In Trafalgar, there were WD coords but they were wrong, which explains why the dot was at the wrong location. I updated the later in WD. MB 16:35, 10 July 2022 (UTC)

MB, I was not aware that it took coords from WD. Was not expecting an outside context problem. I guess I missed that in the documentation. Thanks for fixing and letting me know what the problem was. It worked fine in a whole lot of other similar infoboxes, so there was no obvious reason to expect these two to be different. Cheers · · · Peter Southwood ^(talk): 16:56, 10 July 2022 (UTC)

See Lake District for an example. I have no idea why it's doing this. Can someone look into it? KaraLG84 (talk) 12:16, 11 August 2022 (UTC)

Hello, I've been working through the page listing all the articles with linting errors on and I've encountered this page which has been sat at the top of the list for a while.

It has a problem with the map that the linting tool says is down to this markup:

{{#invoke:Location map|top|Russia Bashkortostan|width=1000|float=center|caption=y}}

I've tried to fix it and learn how this template works but I'm stuck. Can anyone help? LicenceToCrenellate (talk) 11:07, 25 August 2022 (UTC)

That module invocation, which is a rare thing in articles, opens some div tags that were not closed. I have put a hack in this non-article to close them. The better resolution is to delete that page. Thanks for fixing Linter errors; you'll probably have better luck getting help with strange Linter problems at Wikipedia talk:Linter. – Jonesey95 (talk) 12:47, 25 August 2022 (UTC)

Thank you for your help. I was unsure about deleting it, probably worth pursing. I didn't know about the lint help page, thanks again! LicenceToCrenellate (talk) 15:42, 25 August 2022 (UTC)

Hi, recently I uploaded this map of the Emirate of Sharjah and I'm wondering if anyone could get it into the location map code so I can use it more efficiently in articles about suburbs and communities in the Emirate. Badass Flare (talk) 19:14, 2 November 2022 (UTC)

The documentation page suggests that Wikipedia editors should check if nothing links to a page to check if it might be broken. But clicking on a map on the list provides no such information. Is this a bug in the mobile Wikipedia formatting, or is that one sentence hint just too obtuse to be useful to first time users of the"location map" template. 77.213.220.123 (talk) 04:47, 29 January 2023 (UTC)

Moved from Special:Permalink/1149600385

Can someone please fix this module? The module is Module:Location map/data/Australia Greater Newcastle. I've been testing it on the page Swansea, New South Wales (by adding | alternative_location_map = Australia Greater Newcastle to the infobox) and I can't seem to get it on the right spot. I've tried about 50 times and it's very frustrating. Can someone please fix this ASAP? Thanks! Thiscouldbeauser (talk) 04:20, 13 April 2023 (UTC)

Seen from Washington (state) I just got an idea to place an outer title for this template, which requires an optional parameter |title=. Once this parameter is used, the title is placed at the top of <div class="thumbinner"> element, and centered in there. (see this screenshot)

Who can reproduce? -- Great Brightstar (talk) 07:33, 25 May 2023 (UTC)

On mobile the image follows the float parameter. On narrow screens such as phones, this results in the article's text flowing to the side in a very narrow and hard to read column. In contrast, ordinary images generally are centred, and don't float, unless the screen is wide enough to justify floating. Hairy Dude (talk) 22:50, 3 September 2023 (UTC)

Does anybody know how to show multiple maps that can be selected as in the Jakarta article. Looking at the WML, there is no mention of the filenames used - just some strange hashtags. I tried searching on help, but as is well known, the pathetic inadequacies of that function mean it's almost impossible to find even simple information. Any help, or a pointer to the concealed help page, would be much appreciated. Thanks. Davidelit (Talk) 04:17, 22 July 2023 (UTC)

Under the "pushpin_map" argument present in most geographical infoboxes, you can utilise multiple maps by listing the names of said maps in ascending order, separating each with a hashtag. E.G. "Indonesia Java#Indonesia#Southeast Asia". You can find the names of the specific maps you would like to use by looking at the modules of said maps; the name is shown near the top of the module documentation.

Hope this helps. — Mugtheboss (talk) 22:15, 15 September 2023 (UTC)

As an extension to this, going through Category:Location map modules by country is likely to be helpful towards your efforts in finding the modules you would like to use. — Mugtheboss (talk) 22:27, 15 September 2023 (UTC)

In Module:Location map/data/Myanmar the two maps there have different coordinates. The File:Myanmar relief location map.jpg mentioned in its description is 92-102 E. So if this file is shown, the coordinate marked is shifted left/right from the place it should be. I think the File:Myanmar adm location map.svg should be changed to File:Myanmar location map.svg and the coordinate should be adjusted accordingly. Not sure what would break if the map range is shrunk. --Lerdsuwa (talk) 02:18, 21 March 2022 (UTC)

I noticed the same thing. For instance Nat Ma Taung does not show up in the correct location. Can someone with the proper editing privileges and more technical know-how please fix this error? 69.130.10.175 (talk) 23:45, 8 February 2023 (UTC)

 Done — Mugtheboss (talk) 22:57, 15 September 2023 (UTC)

Hey, I see there's a Module:Location map/data/North Korea, but it'd be nice to have one for Pyongyang more specifically. Similar to Module:Location map/data/South Korea Seoul.

Could anyone create this? Would be much appreciated; I'd make really good mileage out of it by making a bunch of infoboxes for pages with it. toobigtokale (talk) 09:46, 26 September 2023 (UTC)

Hello, is this a bug?

In map 1, clicking on "Recanati" works fine, both on the name and on the red marker.

In map 2, it's impossible to click on "Recanati". I noticed that if I delete the "Siena" place, it kinda starts working but still a little buggy. There seems to be some kind of interaction that I fail to understand. In this map it happens with other places too, such as Milan.

I noticed it happens frequently on other different maps. Is this a general problem of Location map? Or is it specific to some maps? Can anybody help or provide some insight? Thanks in advance

Recanati

Rome

test1 places in Italy

Vatican City

Milan

Bologna

Venice

Florence

Catania

Pozzuoli

Naples

Lucca

Maiolati Spontini

Padua

Pesaro

Recanati

Bolzano

Cavarzere

Siena

Rome

Livorno

Parma

Scanzorosciate

Castelnuovo Rangone

Langhirano

Modena

Santa Maria Hoè

Turin

Tortona

Ischia

Romano di Lombardia

Bergamo

Torre del Lago

test2 places in Italy

Gor1995 (talk) 14:23, 2 October 2023 (UTC)

I used a little trick on your second map to show you what label_width of 50 means: Livorno and Siena boxes are completely covering Recanati. For most of those labels 6 would suffice, as shown of your first map. Ponor (talk) 00:31, 3 October 2023 (UTC)

Huh, I just realized I had no idea how the label_width parameter worked :/

Thanks so much for your help!! You're very kind Gor1995 (talk) 07:59, 3 October 2023 (UTC)

First I'd like to suggest including some version of {{navbar}} on each location map template (pointing to that map instead of Location map+ itself). I was experimenting with adding it on {{Oceans and seas in Southeast Asia}} and found it to be helpful and unintrusive with the right formatting parameters, but didn't save the edit because I thought it would be better to have this be standardised between all of the location maps using this template. This could have parameters to turn it off or to override whatever default formatting of navbar we picked so that the user could still format the final result as if inserting that template on the caption manually.

Secondly: We can turn off linking to the default background image with the maplink= parameter on Location map+. However, the vast majority of uses of this template on the wiki have links, and the background image link is very easy to click on by accident. Many, many of these templates are almost unusable because of their tiny links next to a clickable background. Even the example map on the template documentation suffers from a clickable background instead of maplink= despite being full of links. Proposing that the current behavior of maplink= is made the default for that template, and for some other parameter value to produce the current default. YuriNikolai (talk) 19:36, 7 October 2023 (UTC)

Whats configuration to put more than 1 marker, for example 10 markers in same map. Joaosilva2000 (talk) 08:11, 12 October 2023 (UTC)

Joaosilva2000, see Template:Location map many or Template:Location map~. Frietjes (talk) 20:03, 12 October 2023 (UTC)

The Template:Location map many its like plural version of Template:Location map right? Joaosilva2000 (talk) 03:29, 14 October 2023 (UTC)

This edit request has been answered. Set the |answered= parameter to no to reactivate your request.

Description of suggested change: see below

Diff: Special:Diff/1177292789

Ponor (talk) 12:51, 23 October 2023 (UTC)

Module:Location map/data/Zimbabwe has three maps in its definition file, but only image and image1 can be used with the help of |relief=: no value means image will be used, any value gives image1. If one wants to use image2, the full file name has to be given to |AlternativeMap=. However, |relief=2 could mean image2, and I think that's what many would expect. I'm proposing this little change Special:Diff/1177292789, which would leave everything as it is now, except when |relief=2…99. @TheDJ, Legoktm, Elli, and Frietjes: I'm pinging you as the last four contributors, not sure how much this page is watched.

no relief par

relief=

relief=yeah

relief=1

relief=2

The same thing tested at test.wiki from {{Location map}} template is here testwiki:User:Ponor/sandbox/Location map Ponor (talk) 02:43, 27 September 2023 (UTC)

This seems like a reasonable change at first glance but I don't actively maintain this module (and didn't write this) so I'll hold off on implementing for a bit to see if anyone else comments. Elli (talk | contribs) 05:03, 27 September 2023 (UTC)

Leaving a note here that Location map many, Location map+ and their modules need no changes in order for this to work (images from Module:Location map/data/Africa):

relief=1 Location map

relief=2 Location map many

relief=2 Location map+

Ponor (talk) 16:21, 30 September 2023 (UTC)

 Done * Pppery * _{it has begun...} 00:08, 27 October 2023 (UTC)

The resecently add line

       local digits = mw.ustring.match(args.relief,'^[1-9][0-9]?$') or '1' -- image1 to image99

is throwing a script error because args.relief is a boolean not a string. Phatom87 ^{(talk • contribs)} 00:16, 31 October 2023 (UTC)

Example? Frame arguments should always be strings, even if the module interprets them as booleans. I'm sure if my code were really broken it would have taken less than a month for someone to notice. * Pppery * _{it has begun...} 00:50, 31 October 2023 (UTC)

The documentation explains that |relief= takes any non-blank value and has special behavior when the value is a number like "2" or "3". Phatom87: A link to a page where something is broken is always helpful when reporting a problem. – Jonesey95 (talk) 17:47, 31 October 2023 (UTC)

Didn't realize this was sourced to multiple pages anyway Template:Russo-Ukrainian_War_detailed_relief_map is the problem page, Phatom87 ^{(talk • contribs)} 00:33, 4 November 2023 (UTC)

Yeah, that module is doing something strange. I've fixed it. * Pppery * _{it has begun...} 00:36, 4 November 2023 (UTC)

The module has different outputs depending on whether |caption= has a value, is empty, or absent from the call of {{Location map}}. It also messes up with the border. Can't say I understand why such a design decision was made, instead of using specific params that do only and exactly what they're supposed to. Anyway... I am here to ask what to do when {{Location map}} is used in a template, an infobox, which has a variable/parameter {{{pushpin_map_caption}}}. What would you use in the templates code so that {{{pushpin_map_caption}}} translates into what |caption= does: when {{{pushpin_map_caption}}} has value or is empty, use that value; but when {{{pushpin_map_caption}}} is absent from the template call in an article, make the module see it as nonexistent and provide the default caption. In other words, I need a replacement for |caption = {{{pushpin_map_caption|}}}} in the template code that will make |caption= disappear from the call of {{Location map}} in the infobox code when {{{pushpin_map_caption}}} is absent from the call to the infobox in the article. Thanks! Ponor (talk) 14:01, 23 November 2023 (UTC)

Please see this version of my sandbox for an illustration of a problem with locating Tehran on the map of Eurasia. The dot is located somewhere west of Egypt but should be considerably northeast of there, at the south end of the Caspian Sea. This problem is happening in the infobox at Tehran as well. The coordinates appear to be correct. The other three maps in that infobox display the dot correctly. – Jonesey95 (talk) 15:35, 6 December 2023 (UTC)

This map appears to be broken at Kuwait International Airport as well. I suspect a problem with the relatively new, undocumented Module:Location map/data/Eurasia, created by पाटलिपुत्र. – Jonesey95 (talk) 15:38, 6 December 2023 (UTC)

@Jonesey95:Yes, it wasn't calibrated. Should be better now. Please advise if there are issues. पाटलिपुत्र (Pataliputra) (talk) 15:53, 6 December 2023 (UTC)

That looks much better. Thanks for the quick fix. – Jonesey95 (talk) 16:48, 6 December 2023 (UTC)

This edit request has been answered. Set the |answered= parameter to no to reactivate your request.

Currently, an unsightly black box appears behind the red dot of the location map on the Android app whenever the map is inside of an infobox (such as in Plymouth Rock). This is because of styles specific to the mw:Page Content Service (PCS), which serves our content on the apps. Specifically, the <div> tags which wrap the dot inherit the background color from elements up in the tree, which happens to have their backgrounds set to dark/black when the reader requests it and when an infobox wraps the location map. There's a very obscurely-placed way to disable this (phab:T236137) that's officially supported, which is adding the "notheme" class to any element that shouldn't be styled by PCS. By adding the class to the outer div (div with class od), it suppresses the background color from being set to it and its children divs (which explicitly inherits the infobox's cell background color by default).

This change is visible only for the app view on dark/black mode. You will have to open Special:PermanentLink/1192790784 on the Wikipedia apps with dark/black mode enabled or view the Mobile HTML directly in your browser (preview) to see the difference.

Diff: (active in the sandbox, diff)

		:addClass('od')
		:cssText('top:' .. round(y, 3) .. '%;left:' .. round(x, 3) .. '%')

		:addClass('od')
		:addClass('notheme')  -- T236137
		:cssText('top:' .. round(y, 3) .. '%;left:' .. round(x, 3) .. '%')

Chlod (say hi!) 10:50, 31 December 2023 (UTC)

@Chlod:  Done, good job! Est. 2021 (talk · contribs) 15:37, 31 December 2023 (UTC)

Thank you! Hope you have a happy 2024, Est. 2021! :D Chlod (say hi!) 15:47, 31 December 2023 (UTC)

Can the caption parameter be aligned center? See example. Qwerty284651 (talk) 13:19, 10 February 2024 (UTC)

Yes. – Jonesey95 (talk) 17:30, 11 February 2024 (UTC)

That simple, huh? I went to <div style="text-align:center"> map code </div> lengths and all it took was a little {{center}}. Funny how the simplest solutions are the hardest to find. Qwerty284651 (talk) 18:59, 11 February 2024 (UTC)

I think it would be a nice detail and more grammatically correct when there's two maps that can be flipped between, instead of an option that says "Show all" it should say "Show both". Akeosnhaoe (talk) 08:50, 24 January 2024 (UTC)

@User:Akeosnhaoe I have been termed "Grammar police" (a label I do NOT disdain), as well as "Grammar ... (something beginning with N)." My thought on this is, why unnecessarily complicate things for a nicety of usage? Uporządnicki (talk) 22:24, 18 February 2024 (UTC)

By the way, "... when there's two maps." That is to say, "... when there IS two maps." Last time I checked, there ISN'T two of anything in the world or out of it. Uporządnicki (talk) 22:29, 18 February 2024 (UTC)

I will not engage with you. Akeosnhaoe (talk) 23:36, 18 February 2024 (UTC)

I'm probably doing something stupid here, but I don't see it. Can someone please rub my nose in it? See this v. the map below.

Wtmitchell (talk) (earlier Boracay Bill) 04:29, 30 March 2024 (UTC)

@Wtmitchell: Google shows you the right location because you're searching by name, but the coords are more like 18.62 and -88.15 (pin dropped near the location in Google maps). Ponor (talk) 09:58, 30 March 2024 (UTC)

Thanks. Some fiddling there got me this; I couldn't find its lat/lon location in any google search results. Cheers. Wtmitchell (talk) (earlier Boracay Bill) 22:26, 30 March 2024 (UTC)

This edit request has been answered. Set the |answered= parameter to no to reactivate your request.

Can someone please make a change so the text displayed is "Location map", not "Location Map"?

Thanks. HandsomeFella (talk) 21:24, 8 April 2024 (UTC)

To editor HandsomeFella: please show an example of where you see "Map" with "M" in uppercase styling. P.I. Ellsworth , ed. ^{put'er there} 15:37, 10 April 2024 (UTC)

I am deactivating this request until there is a clear change request. The phrase "Location Map" does not appear in the module's code. – Jonesey95 (talk) 21:30, 10 April 2024 (UTC)

Found the place: 2024 Masters Tournament. HandsomeFella (talk) 11:22, 15 April 2024 (UTC)

Fixed here. Ponor (talk) 11:36, 15 April 2024 (UTC)

Thanks. HandsomeFella (talk) 12:59, 15 April 2024 (UTC)

Hi, I've searched the talk page archives for this, but I couldn't find a solution. Is it possible to place a label exactly over the point where the mark would be? I'm trying to make a label map of Afghan provinces here on my sandbox, but it seems that the label will always be off-center, even if you move the "positon" parameter to "top" or "bottom". It would be useful if "center" were an option for this parameter. I'm trying to see if location maps could be used to make something like image-label maps such as at Template:Bulgaria Provinces, which would be much easier considering it uses coordinates instead of pixels of the image. — RAGentry (talk) (contributions) 22:17, 18 February 2024 (UTC)

@RAGentry: Sadly there doesn't seem to be a convenient way to do this currently. I guess until that "center" option is implemented, the best workaround would be to add/subtract a standard latitude from the position. If you were working with modules, such action could be automated as in Module:Russo-Ukrainian War detailed map (oblasts). Alexis Coutinho (talk) ^[ping me] 17:56, 27 April 2024 (UTC)

If one recycles markers from a larger map into a more localized map, some markers may appear all over the caption, i.e. Template:Russo-Ukrainian War detailed map (oblasts). Alexis Coutinho (talk) ^[ping me] 18:04, 27 April 2024 (UTC)

This edit request has been answered. Set the |answered= parameter to no to reactivate your request.

I found a subtle bug in the way the markers/labels are created. If a marker has a link, the anchor tag seems to inherit the font size from the user skin, not from the label_size. This is problematic for small markers, especially clustered ones. The anchor tag bounding box may be taller than the marker and label themselves, thus it may obstruct other marker/label links behind it. You can compare the difference between these 2 map versions: without fix vs fixed. Look for the Orlivka red marker which is vertically sandwiched by two villages. They are NW of Avdiivka which is NW of Donetsk. In the old version, the Orlivka marker link is barely clickable as Tonenke and Semenivka obstruct it. In the new version, the anchor follows the marker shape.

The proposed fix is written in the sandbox. It simply moves the css font-size definition from the label div to the outer div which also includes the marker div. Perhaps the only downside would be if the label_size was much bigger than the marksize, causing even more obstruction. Maybe forcing the font-size of the marker to be very small could help? What do you think? Alexis Coutinho (talk) ^[ping me] 06:43, 27 April 2024 (UTC)

 Done * Pppery * _{it has begun...} 00:15, 30 April 2024 (UTC)

This edit request to Module:Location map/multi has been answered. Set the |answered= parameter to no to reactivate your request.

I've made another bugfix, but this time for Module:Location map/multi. The problem was pretty simple: when using the load function for multi map templates, the radio buttons wouldn't show up despite the individual maps being correctly wrapped in <div class="switcher-container">. This was because the autoSwitcherLabel option was being set on args, which isn't passed to locmap.bottom (dataModule.containerArgs is instead). Effectively, it wasn't being read. If containerArgs wasn't read-only, then the new flag could be set directly. Therefore, I believe the neatest way to pass this flag to locmap.bottom is to make a shallow copy of containerArgs, modify it, and then pass it instead. Alexis Coutinho (talk) ^[ping me] 23:27, 27 April 2024 (UTC)

 Done * Pppery * _{it has begun...} 00:15, 30 April 2024 (UTC)

@Pppery: The change you made [1] includes the base Location map sandbox suffix require 😅. Alexis Coutinho (talk) ^[ping me] 01:21, 30 April 2024 (UTC)

Fixed. Sorry, I really should know better given I'm the guy systematically removing inappropriate sandbox uses. * Pppery * _{it has begun...} 01:23, 30 April 2024 (UTC)

@Jonesey95: In your recent revert in the sandbox, do you mean if a user passes a label like this: label=<div style="color:green">New York</div> (when using module syntax)? Alexis Coutinho (talk) 16:23, 20 May 2024 (UTC)

Yes. A span tag cannot wrap a div tag. Many real-world examples appear in these search results. – Jonesey95 (talk) 20:23, 20 May 2024 (UTC)

👍 Alexis Coutinho (talk) 20:44, 20 May 2024 (UTC)

The map labels in dark mode have a black background and black text. The background should either be transparent on maps where the label text colour has sufficient contrast with the background or white so the black text has sufficient contrast. Here are three examples from Moulins, Allier, and Con Mine.

JScherer-WMF (talk) 21:18, 29 May 2024 (UTC)

In case this helps debugging: I noticed that the maps in Grand Canyon use the same template but do not have the bug. JScherer-WMF (talk) 16:55, 30 May 2024 (UTC)

Hey @JScherer-WMF this should be fixed now with the recent additions to Module:Location_map/styles.css. 🐸 Jdlrobson (talk) 04:35, 31 May 2024 (UTC)

I think these changes got broken again. See Caen Kabelsalat22 (talk) 19:23, 13 June 2024 (UTC)

Hi! I tried using a map with like 27 locations on it, I followed it and it's still not showing up! help me! 45BearsFan (talk) 03:43, 28 June 2024 (UTC)

@45BearsFan there was a }} missing at the end of your call to {{Location map+}}. Ponor (talk) 13:00, 28 June 2024 (UTC)

Now that I got the easy part out of the way. The dots aren't showing up in their places. 45BearsFan (talk) 14:13, 28 June 2024 (UTC)

Special:Permalink/1231480913 Ponor (talk) 14:31, 28 June 2024 (UTC)

Thank you so much!! 45BearsFan (talk) 14:36, 28 June 2024 (UTC)

Example here in which the label background color is ignored for one element:

{{Location map~|France Paris and inner ring|lat=48.8737|long=2.2950|background = #ffcc7777|label=<div style="font-size:70%;">'''[[Arc de Triomphe]]'''<br />'''[[Place Charles de Gaulle]]'''</div>|position=top}}

In the above example, the color has partial alpha but that's irrelevant to the issue: I previewed |background=#ffcc77 and/or |position=bottom with same problem; changing |position=left or |position=right work OK. likewise changing other elements' |position= broke them.

jnestorius^(talk) 20:26, 28 July 2024 (UTC)

• It's the <div style="font-size:70%;">. My workaround was to use {{resize}} instead, which is better practice anyway. The underlying issue may still be worth fixing, whenever. jnestorius^(talk) 21:00, 28 July 2024 (UTC)

The |float= is causing infobox problems at 2024_Wayanad_landslides, see MediaWiki_talk:Gadget-switcher.js#Interface-protected_edit_request_on_1_August_2024_fix_floating_radio_buttons.

According to the monthly parameter usage report, the |float= had only 1 use, which I removed. Furthermore, do we even need the CSS float:right when it's mostly in infoboxes, which are narrow? 142.113.140.146 (talk) 08:04, 1 August 2024 (UTC)

So I tested on mobile and saw the display. It is unclear why the controls are to the left of the image. I haven't heard of any UI pattern like this layout. On mobile, we should be spacing things out on the page with plenty of padding, not trying to cram everything on one row. 142.113.140.146 (talk) 19:56, 1 August 2024 (UTC)

Done. Izno (talk) 22:09, 3 August 2024 (UTC)

Hi, so is it possible with this template to like display for example the map of germany and cut the part that isn't of interest ? For context I'm creating french pages for German Regionalligen and from 2012 til now it's fine since all 5 groups have location maps i can use, but for the period when it was divided into 3 groups there is no location map file for now and instead of creating new files (cuz i don't really know how to) i wondered if i can just used location map with the full germany map file, and then ask it to for example cut the south when showing regionalliga nord, then cut the north when showing regionalliga süd and then cut the east when showing regionalliga west. If it's not possible then I'll go ask around on how to edit svg maps and create location maps ig TheÆtherPlayer (talk) 13:40, 7 October 2024 (UTC)

From the documentation, it appears that the |width= of the location map image is specified in pixels, but per MOS:IMGSIZE, Except with very good reason, a fixed width in pixels (e.g. 17px) should not be specified, because it ignores the user's base width setting. Thus upright=scaling factor is preferred when it is desired to present an image at other than the default width. How do I set the location map size to match the reader's thumb size preference, as recommended by MOS? – Jonesey95 (talk) 04:44, 12 March 2025 (UTC)

The context of MOS:IMGSIZE is clearly about stand-alone images, not ones in infoboxes. To have uniformly formatted infoboxes should be the standard. -- P 1 9 9  ✉ 18:03, 14 March 2025 (UTC)

I agree that a uniform image width should be the standard, which is why I am asking how to set a location map to match the reader's standard thumb size preference. MOS:IMGSIZE refers to the size of a "lead image". MOS:LEADIMAGE, on the same page, explains the lead image like this: It is common for an article's lead or infobox to carry a representative image. Module:InfoboxImage, which is commonly used to display lead images in infoboxes, has frameless and upright options, which allow lead images in infoboxes to comply with both MOS:IMGSIZE and with readers' preferences. So how do we follow this standard for location maps so that they match the infobox's lead image size? – Jonesey95 (talk) 19:26, 14 March 2025 (UTC)

What's the best way to export the resulting map, please? Motivation: Template_talk:Location_map-line#Use_in_Wikidata. fgnievinski (talk) 14:06, 15 March 2025 (UTC)

I'm seeing a bug with text background color for annotations on location maps in articles, but not in the docs. Both logged-in and -out. E.g. screenshot at phab:F59386868 of the random article Fechenheim (and same elsewhere). But the examples in Template:Location_map all work properly(!?). I'm not sure where the bug is coming from, whether it's in Module:Location map/styles.css or elsewhere. I hope those clues help! Quiddity (talk) 02:12, 25 April 2025 (UTC)

Hi, just like Template:OSM Location map, I think it is better to mention the type of Location map, which is in this case is pushpin. So I propose to move this article to Template:Pushpin Location map. Thanks, Hooman Mallahzadeh (talk) 03:02, 1 May 2025 (UTC)

The pushpin (pog) is just the default marker. Templates like {{Infobox airport}} use a different image file to show locations. There is a whole family of location maps, not just this module and template; I might support a name change if their name was something like "LM", but "Location map" is reasonably descriptive. – Jonesey95 (talk) 15:16, 1 May 2025 (UTC)

This edit request to Module:Location map/styles.css has been answered. Set the |answered= parameter to no to reactivate your request.

Description of suggested change: the whole map section, including the caption, gets affected by the grayscaling effect on lines 66 and 79 in styles.css, which causes some weird coloring (see [2])

Diff:

əkrəm. 18:06, 13 May 2025 (UTC)

 Done Izno (talk) 23:48, 23 May 2025 (UTC)

I would like to propose an enhancement to Module:Location map that would allow for more precise label positioning. Currently, the module supports basic label positions (top, bottom, left, right), but does not include options for diagonal placements like northeast, northwest, southeast, or southwest.

• Expand the |position= argument to recognize and support:
  • northeast (ne)
  • northwest (nw)
  • southeast (se)
  • southwest (sw)

• Greater Precision: Labels can be positioned more naturally relative to markers, reducing overlap and improving clarity.
• Consistency: Many mapping tools and templates already support compass-based positioning, making this a logical extension.
• Improved Readability: This would allow editors to optimize label placement in cases where the default positions (top, bottom, left, right) do not work well.

• Modify the |position= handling in Module:Location map to recognize the additional options and adjust label offsets accordingly.
• Use a simple logic-based adjustment to move the label diagonally when a compass-based position is selected.

This enhancement would improve the flexibility and usability of location maps across Wikipedia. I welcome feedback and discussion on this proposal. Abhiramakella (talk) 23:42, 2 April 2025 (UTC)

I would find this very helpful, particularly for locations that are very close to each other that the editor wishes to label. I would suggest alternatively that every label could have a certain "offset" parameter, in pixels, on top of the existing position parameter. This would specify the offset from a default position so editors could adjust the label to be anywhere they wish on the map. LivinAWestLife (talk) 18:41, 8 August 2025 (UTC)

@LivinAWestLife: Adding some vertical offset to left- and right-positioned labels isn't too hard (Special:Diff/1305013356/1305042106). I don't think we need it for top- and bottom-positioned ones, and I'd advise against adding any left-right offset to those, as people tend to fine tune the absolute positions to what looks good on their screens, disregarding many other different devices and font sizes. The new parameter is top_offset, available in {{Location map/sandbox |top_offset=}}

current	top_offset=0	SW: top_ofset=−1	NW: top_offset=+1
Vela Luka	Vela Luka	Vela Luka	Vela Luka
current	top_offset=0	NE: top_ofset=−0.8	SE: top_offset=+0.6
Vela Luka	Vela Luka	Vela Luka	Vela Luka

Let me know what you think! Ponor (talk) 18:51, 9 August 2025 (UTC)

Hi, this looks like it would be very useful, thank you! I hope implementing it wasn't very hard. I can understand why you wouldn't want to be able to fine tuning the absolute positions if it makes the display worse on certain screens. I will try it out now. LivinAWestLife (talk) 19:37, 9 August 2025 (UTC)