# வார்ப்புரு:OSM Location map/doc



This template provides a map in a , for any location and scale. At its simplest it can simply show the OpenStreetMap image and a scale indicator for a given area of land. Optionally a range of marker, label and annotation tools are available to include location markers, labels, numbered dots, a heading, caption, mini-locator map and overlays. The map also provides a link to a full-screen interactive 'maplink' version.  

## Purpose
**OSM Location map** allows an editor to include a map in a for anywhere in the world, at any scale from the whole world down to one or two streets. It makes use of the OpenStreetMap mapping data, and enables a place-based page or topic to simply show the area being described, without the need for pre-determined map templates. The underlying map will be updated and improved automatically as the OSM data develops.  

The template can also show multiple marks, images and labels (currently limited to ten). The template makes use of , which allows unlimited numbers of marks and labels, utilises a different coding mark-up, and is particularly suited to using data directly from a Wikidata source.  

The resulting framed map also has a link to a full-screen version, which opens at the same location, above the current page. This has a richer map interface, can be re-scaled and panned by the user, has optional images and captions for the marker points, and can also access a wide range of maps, satellite images etc. (The fullscreen option uses the mapping provision.)  

A rough guide to the scale of the map is provided in the bottom corner. This is only a guide, as the projection means the scale changes depending on the latitude. Some allowance has been made for this, but only in large 20 degree chunks.  

## Comparison with
From May 2018 it has also been possible to create a map in a via , which in some respects does a similar job to OSM Location map. In both cases a static map image can be added to an article, for anywhere in the world, pulling in the map from OpenStreetMap data. The differences are in what they can and can't add to the base map. Maplink, in both its framed and fullscreen versions, can only add either points (numbered or icon-style pointy dots), or various lines and areas can be imported from OpenStreetMap via wikidata Q values (such as boundaries, roads, rivers etc). Thus the framed map and fullscreen version will show identical information. The OSM Location map on the other hand, cannot add the Q value lines and areas except to the fullscreen click-through, but can use the framed map to show a much richer selection of dots, shapes, overlays, images and especially text to convey specific details relevant to a particular article.  

## Usage
;Minimal version: an unadorned map centred on a latitude and longitiude coordinates, via a value. Set the zoom to give a scale that fits the subject (0=whole world, 18=a street). With just these options set, all other parameters use the defaults, or are unused. It gives a link to the full screen version.  

| <source lang="html"></source> | } |
| --- | --- |

;Single marker: Using mostly default settings, with a Red pog marker and label, and some additional info for use on the full screen version.  

| <source lang="html"></source> | } |
| --- | --- |

;Code blank  
| Blank code for a single marker map | Blank code with comments |  |
| --- | --- | --- |
| <source lang="html"></source> | <source lang="html"></source> | } |

## Multiple markers, labels and images

In addition to the un-numbered mark parameter set, there are 30 numbered ones. These are otherwise identical to the one above, but the name terminates in a number (1-30). Each mark and label has its own set of parameters (, , , etc..., , , etc.) Values can be inherited either from the 'mark1 master parameter set', or from a special 'markD' Default set that provides override defaults. When set, these values are inherited by the other numbered sets to avoid having to repeat for each, whilst they can still be set individually where required.  

### Multiple markers

| Example code for the two-marker map one the : |  |
| --- | --- |
| <source lang="html"></source> | } |

#### Inherited values
To minimise repetition of code, there is a sliding scale of inheritance that applies to each value in each parameter set. For example, if <code>label-size4=16</code> is set, that will always take precedence. If label-size4 has not been set, it will inherit the value from the special Default setting (defined using <code>label-sizeD= </code>). If no Default has been set, it will inherit the value set by the 'master parameter set', <code>label-size1=</code>. If that is also undefined it will fall back to the underlying default, which in the case of label-size is 12. The same is true of all the variables relating to marks and labels, (although not to the coordinates, labels themselves, or mark-titles, which are always unique to the particular mark they relate to.)  

### Adding a Minimap in the corner
Many pages with info-boxes already include a locator map to give readers a proper sense of where the topic or place is located within a broader area. The underling 'Graph' module that OSM Location map uses offers a built-in map of the world option, which will act as a mini locator map and automatically adds a red locator dot (<code>minimap = on</code>). Unfortunately it is too general for most purposes, so an alternative is to make use of an existing 'Location map' file. This can be seen in the Llanfechell map example, however it is not very automated. The width and height of the Location map both have to be decided upon, specified (and calculated so as to not distort the map dimensions). Some location maps may already highlight the feature, but if not, an optional locator 'pog' can be placed by specifying the minipog-x and -y values, using the same scale values as mini-width and -height. With an origin in the top of the minimap, the minipog can be placed over the relevant point on the minimap.  
If the area of the actual map is a large portion of the mini-map, an open red box can be included instead of a dot, so as to show the bounds of the main map. To use this feature, simply specify the width of the required box: <code>minimap-boxwidth=xx</code> where xx = the pixel width of the box. In general anything much below xx=15 will be better served by a dot. The required width will require some trial and error to pin down. The box height is then matched in proportion to the actual map.  

### Text on an arc
Text for broader geographic features can be placed around an arc, to convey a sense of a broader area, or to follow the curve of a river, mountain range, coastline, etc. This works entirely separately from the other labels. It does not attach itself to any mark or dot, and does not create any fullscreen markers. It requires coordinates for the first letter, parameters for the starting angle, radius of arc and gap between letters. Text size and color can also be specified, or inherited from Default settings.  

| Blank starter-code for text on an arcs, with starter-examples for different arc-patterns. |  |  |  |  |  |  |  |
| --- | --- | --- | --- | --- | --- | --- | --- |
| arc-coordA= | arc-textA= | arc-angleA= | arc-gapA= | arc-radiusA= | arc-text-sizeA = | arc-text-colorA= | ellipse-factorA=1.0
</source> |
| The nature of the earth's coordinate system means that there will be some variation in an arc at different latitudes and at different zoom levels. The program makes corrections for this, but there will still be residual variation. Similarly, changes in radius will also have some effect on the gap size, with a larger radius opening out the gap somewhat. There will therefore need to be considerable trial and correction to get the shape and effect desired. As a general rule, identify the coordinates of the required start-point, then choose a starter-pattern from the selection below, and then adjust parameters to fit the requirement of the map. |  |  |  |  |  |  |  |
| Shallow smile:
arc-angleA=-170
arc-gapA=-1.2
arc-radiusA=1.6 |  |  |  |  |  |  |  |
| Deeper smile:
arc-angleA=-150
arc-gapA=-3
arc-radiusA=0.7 |  |  |  |  |  |  |  |
| wide eyebrow:
arc-angleA=-20
arc-gapA=3
arc-radiusA=0.8 |  |  |  |  |  |  |  |
| opening bracket (reading up):
arc-angleA=-110
arc-gapA=1.5
arc-radiusA=0.6 |  |  |  |  |  |  |  |
| opening bracket (reading down):
arc-angleA=-60
arc-gapA=-2
arc-radiusA=0.5 |  |  |  |  |  |  |  |
| closing bracket (reading up):
arc-angleA=120
arc-gapA=-1.5
arc-radiusA=0.8 |  |  |  |  |  |  |  |
| closing bracket (reading down):
arc-angleA=60
arc-gapA=2.5
arc-radiusA=0.4 | } |  |  |  |  |  |  |

### Multi marker example

| Worked example of a map with multiple markers and text: Pentre Ifan |  |
| --- | --- |
| <source lang="html">
</source> | } |

## Alternative marks
Instead of using the standard 'Red pog' for mark points on the map, other images can be used. Any image from Wikimedia Commons can be specified. The Pentre Ifan example above uses 'Archaeological site icon (red).svg'. If a particular image file is specified in <code>mark1=</code>, all subsequent marks will use it as well unless they name their own image file. If the image is not square, a dimension value also needs to be set (width ratio for a height of 1)  

### Transparent overlay

A marker image does not have to be small and opaque. A larger overlay image (with a transparent background) can be used to show particular features not included in the base map, such as a town's former walls (see the adjacent map). Such images can be created in several ways (such as tracing over a copy of the base map); they are invoked like any other marker image file. (For a detailed guide to creating and deploying an overlay for these maps see User:J. Johnson/OSM overlay how-to).  

### Text color

Color of label text can be specified using <code>label-color = </code>. Standard html colors can be specified by name, and any color can be specified using the hex triplets coding #xxyyzz (see Web colors). However, to create a consistent look and feel across the wikipedia maps, there are some OSM Location map specific colors, with a more muted tone range that fit well with the color scheme of the base maps. In general it is best to make use of this range, unless there are good reasons for using other particular shades for specific features.  
Under normal usage, the following label color scheme should be followed:-  
**Parkland, national/regional parks, gardens, forests etc = soft green works well on top of OSM green areas. (hard green may be desirable in forests or for the subject of the map)**

| Individual sites = hard red - especially if no other labels are applied and the site is indicated by a red pog | } |
| --- | --- |

### Full table of color options

| Colors recommended for OSM Maps.
These have a more pastel shade than the standard colors, so blend well the map backgrounds |
| --- |
| } |

### Text effects
;multi-line label: Where label text is too long to fit on a single line, using <code>label = </code>, two further label lines can be used: <code>labela = </code> and <code>labelb = </code>.  

;Label with no mark: If <code>mark-size=0</code> this has the effect of a free-floating label with no marker  

;Angled label: It is possible to specify a <code>label-angle = </code>, which will pivot the label text around the centre of the marker point by the specified angle. Using an angled label which also has no marker is particularly good for labelling various geographic and linear features. A more characterful alternative is to set the text on an arc, using the ArcText options, illustrated by the 'Preseli Hills' text on the Pentre Ifan map. For stylistic consistency settlement and building names should not normally be given an angle.  

### Numbered dots

If numbered dots are needed, instead of (or as well as) text labels, this can be achieved using the built in shapes. For example, <code>shape1=n-circle</code> will place a numbered dot at that coord position (or <code>l-circle</code> for letters). Generally it is much better to use the dots in sequence, so each numbered mark gives a numbered dot, and they will match the full screen ones. If <code>auto-caption=1</code> then the caption will generate a numbered list using the <code>mark-title</code> entries. For example:-  

<source lang="text">  

</source>  
The other built-in shapes can be used in the same way (<code>n-square</code>, <code>n-diamond</code> etc.). The <code>shape-outline1=</code> value sets the colour for the number (unlike normal, when it sets the shape-outline), and as with the others, only the <code>mark1</code> parameter values need to be set, to establish the default for this map, which can be overridden as required. The <code>numbered1..2..3 etc</code> parameters can override the automatic numbers or letters to use your own values for each mark. is a useful real life example in template form.  
### Use in infoboxes
can be imbedded in infoboxes which allow the <code>module</code> parameter, for instance by using the instruction <code>|module=</code>. :St John Fisher Catholic School is a real life school with two sites and marked on the infobox map.  

## Full list of parameters
| Demonstration of multi-mark example, Heathrow Airport |  |  |
| --- | --- | --- |
| - | <source lang="html">
</source> | } |

| Code blank - OSM Location map template, listing all the parameters |  |  |
| --- | --- | --- |
| - | <source lang="html"></source> | } |

## Parameters
| Parameter | Description |
| --- | --- |
| <code>coord</code> | *Latitude* and *longitude* coordinates of the centre point of the map. Use <code>coord=</code>. can deal with a wide range of formats. e.g.: <code>coord=, coord=, coord=.</code> This may not be the 'coord' points of the page, as an appropriate framing area for the map may place the subject off-centre. (Marker point(s) are set separately, see below). gridreferencefinder.com, is a helpful place to find coordinates, or you can =click on the 'Full screen linked' map. |
| <code>zoom</code> | Sets the **scale** of the map, from 0 to 19, to the levels defined by OpenStreetMap. (details here). The actual distances represented will vary depending on the latitude, as the scale defines different fractions of a degree. The apparent scale will also vary hugely depending on the monitor being used, the browser magnification level, etc. For most Wikipedia situations, maps with a zoom of 10 (notionally 1:500,000) up to 16 (1:8,000) are likely to be of most use. |
| <code>float</code> | Positions the to the , centre (or ) or . (default is ). If centered, the text will be forced above and below, otherwise text will wrap to the side. |
| <code>width</code> <code>height</code> | Sets the width and height of the map in pixels. Only the number is required (i.e. no px). Default is 350 by 250 pixels. |
| <code>fullscreen-option</code> | By default a link is supplied in the bottom of the . By setting this to 0 or no, the link will not appear, should that be preferred |
| <code>nolabels</code> | By default the base map uses a map label model called 'osm-int'l', in which progressively higher zoom levels bring more place names onto the map. For some contexts it may be preferred to 'turn off' the place name labels, and use the mark/label options to provide such names as are wanted. By setting <code>nolabels = 1</code> an alternative 'osm' base map is used, with no place name labels. (At higher zooms the road names still occur). |
| <code>caption</code>
<code>auto-caption</code> | Optionally, a text caption can be included, below the map. Unless overridden by tags etc., this is -justified plain text. It can include any wiki-item that can be inserted into a table cell, including images, formatting, citation references, etc.
If <code>auto-caption=1</code>, a numbered list will be automatically generated to follow any caption. This will generally only make sense when using numbered dots. |
| <code>title</code> | Optionally a title or other text can be placed in a cell above the map. By default this is centred and bold, but as with the caption, any wiki-markup etc. can be included. |
| <code>map-data-heavy</code>

<code>map-data-light</code>

<code>map-data</code>

<code>map-data-text</code>

<code>map-data-color</code>

<code>map-data-width</code> | Allows OSM ExternalData elements to be added to the map. This can be an administrative boundary, highway or other map element that has been assigned a wikidata Q value. (e.g.: <code>map-data=Q83065</code> will add the city boundary of Leicester.) The map item needs to be on the same place as the map itself. It currently only allows line features (not areas etc.), which appear as various styles of line. Multiple elements can be added, separating each Q value by a comma. A major limitation, as of May 2017, is that it only appears on the 'fullscreen' map, not on the framed map on the page. Adding map-data items now should mean they appear on the page if and when this limitation is overcome. nominatim.openstreetmap.org/ has a search engine to identify data elements for which Q values have been assigned, or to add wikidata Q values to map elements.

For <code>map-data-heavy</code> and <code>map-data-light</code>, this will draw orange lines of thickness 9 and 3 pixels respectively. <code>map-data</code> is more flexible, so can default to an orange line of 6 pixels, but color (using format #XXXXXX) and width in pixels can be set, as can a text element which appears when the line is clicked on. This can include wikilinks. |
| <code>minimap</code> | Used to add an optional locator minimap in the bottom corner. If set to <code>on</code> it adds a 'built in' small(ish) world map with a locator dot showing the position of the main map. (This is a feature supplied by the underlying 'Graph:' template, so the only control over it is to be set as on or off.) If set too <code>off</code> it is not used. If set to <code>file</code> it requires the next section details to be added, which will include a custom map. Default is <code>off</code>. |
| <code>mini-file</code>

<code>mini-width</code>

<code>mini-height</code> | Takes the file name of a standard location map from commons, and displays it as a minimap in the bottom corner, provided <code>minimap=file</code>. This can be used to show a larger entity from which the main map is drawn. |
| <code>minipog-x</code>

<code>minipog-y</code>

<code>minimap-boxwidth</code> | Within the custom minimap this can place an optional small Red pog. Nb. The x and y are not lat and lon values. They relate to the mini-width and mini-height. The origin is top, of the mini map, so if mini-width=80 and minipog-x=20, it will be a quarter of the way across. (Some location maps have a highlighted location already, so leaving these two parameters undefined gives the map without a dot.)

minimap-boxwidth=xx can optionally use an open red box instead of a Red pog. xx = the pixel width of the box, and the height is then matched in proportion to the actual map. In general anything much below xx=15 will be better served by a dot. The required width will require some trial and error to pin down. If xx=0 or minimap-boxwidth is undefined, a Red pog is used. |
| <code>scalemark</code> | By default or with scalemark=1, a scale line with guide to the scale of the map is supplied in the bottom corner of the map. If this is not required - e.g. if it interfers with a map element at that point - it can be turned off by setting this to '0'. To shift it further , e.g. to avoid a minimap, or to avoid a 'busy' bit of the map, enter the number of pixels. e.g. scalemark=180 will move it to the of the built-in minimap. If there is no minimap it does not need to be mentioned. |
| Thirty-one marks can be set on the map, being an un-numbered version, and the rest numbered 1 to 30. The first numbered one, (mark1, label1, etc.) is a 'master marker' and its values (or defaults) are inherited by the other numbered markers unless set individually. All label, mark and full-screen parameters are available for each numbered marker.

If the un-numbered mark is used as the subject of the map, it will be point 1 on the Full Screen map (unless <code>mark-title=</code>) and can use specific mark and label values of its own. The first numbered mark has values that will be inherited by subsequent marks. For added flexibility a parameter set with a 'D' value instead of a number will override the master values with a more general Default. |  |
| <code>shape</code> | OSM Location map can use either an external image as a location marker, or one of various built-in shapes. Shape should either be set as <code>=image</code> or can be a circle, square, cross, diamond, triangle-up or triangle-down. If blank or absent it will default to 'image', and use either a Red pog.svg or specified <code>mark = </code> image. If numbered dots are required, use <code>shape1=n-circle</code> Subsequent markers will use the same setting, and automatically number up to 30. <code>shape1=l-circle</code> will do the same but with letters, and any of the built in shapes can be used. |
| <code>shape-color</code>
<code>shape-outline</code>
<code>numbered</code> | Set the shape infill and outline to any color, using either the color names shown under 'label-color' blow, or hex triplets (e.g. #FF0000), as described at Web colors. Only used for built in shapes. Setting them to the same value gives an appearance of no outline. Default = #B80000 (a dark red). The <code>numbered = </code> parameter is used with numbered shapes, to override the automatically allocated number. |
| <code>mark</code> | The name of a Wikimedia commons file, which is used as the marker. Default is Red pog.svg. Other pog colours are available, and a large range of map markers can be found at Commons:Location markers and Commons:Category:Map icons |
| <code>mark-size</code>
<code>mark-dim</code> | Size and dimensions of a marker. <code>mark-size</code> is used by both <code>shape</code> and <code>mark</code> to define the size of the marker symbol. It sets the height of the mark or shape in pixels (no 'px' required, default is 10). If only a text label is wanted with no marker, set <code>mark-size=0</code>.
<code>mark-dim</code> is used to give a non-square mark. (It has no effect with the built in shapes.) default is 1, i.e. equal width and height. A value of 1.4 will give a typical landscape rectangle. 0.7 will give a typical portrait rectangle. If the original mark-file is non square, a value here is needed to correct the proportions. |
| <code>mark-coord</code> | Latitude and longitude coordinates of the marker point. Use the format <code></code>. Used by either <code>shape</code> and <code>mark</code> as well as the related <code>label</code>. If the location is outside the area of the map, it will not appear. (for backwards compatibility mark-lat and mark-lon still work, but are not the preferred method.) |
| <code>label</code>
<code>labela</code>
<code>labelb</code> | Text to appear alongside a mark or shape. No inline formatting, line wrapping, or other tags, links etc. are possible. If blank then any mark will show without a label. If only a text label is wanted with no marker, set <code>mark-size=0</code> A blank label and a mark-size=0 will result in an invisible marker, which will still feature on the Full screen option. If the label is too long for a single line, use labela and labelb for 2nd and 3rd lines. nb if labelb is set without a labela, there will still be a gap where labela would go. |
| <code>label-size</code> | Sets the text size for the label, in points. default = 10 |
| <code>label-color</code> | cellpadding=2 |
| Settlements = soft grey (Subject of the map can be hard grey and larger label-size). Map areas with darker or busier backgrounds may need to move a shade darker to hard grey and dark gray respectively. |  |
| Rivers, lakes, sea areas etc = soft blue (Works well on top of OSM blue areas) |  |
| Parkland, national/regional parks, gardens, forests etc = soft green works well on top of OSM green areas. (hard green may be desirable in forests or for the subject of the map) |  |
| Individual sites = hard red, especially if no other labels are applied and the site is indicated by a red pog | } |

| Full table of colors recommended for OSM Maps.
These have a more pastel shade than the standard colors, so blend well the map backgrounds |
| --- |
| } |

|-  
| <code>label-pos</code>  
| Sets the position of the label, relative to the marker: , , top or bottom. Default=. Top and bottom text is -justified, whereas and align against the marker. The label aims to be an appropriate distance from the edge of the marker, but irregular shapes and larger sizes may need further adjustment using the label-offsets.  
|-  
|<code>label-angle</code>  
| It is possible to specify a <code>label-angle = </code>, which will pivot the label text around the centre of the marker point by the specified number of degrees. (+ve angle rotates clockwise, -ve anticlockwise) If mark-size is set to zero, this has the effect of a free-floating label with no marker, useful for various geographic and linear features. For stylistic consistency all settlement names should not be given an angle.  
|-  
| <code>label-offset-x</code>  
<code>label-offset-y</code>  
| Allows adjustment of the label location in an x and y direction, relative to its mark coordinates, by the specified number of pixels. It can be +ve or -ve numbers. Higher -x values will move the label to the . Higher -y values move it down the map. Default is 0,0.  
|-  
! | Additional content for Full screen link  
|-  
| |The 'full screen' map uses the same OSM base map, in a different map environment, including the option for users to scale in and out, to pan across the map, and to find (via the 'More details' button) other maps and satellite imagery for the location. It also includes numbered markers, for which tooltip-style titles, and image thumbnails with captions can be brought up. This makes most sense where there are several markers on the map. The content for this facility is set with the following three parameters - which need to be numbered for each mark as for the other mark attibutes:  
|-  
! Parameter  
! Description  
|-  
| <code>mark-title</code>  
| This title appears as a tooltip and also a title, accessed via the marker. if <code>mark-title=</code> that will exclude that marker from the full screen map. (it will still show as normal on the main map).  
|-  
| <code>mark-image</code>  
| This provides a pop-up image when the marker is clicked. Include only the image name from Wikimedia commons etc. (i.e. no brackets, or 'File:').  
|-  
| <code>mark-description</code>  
| Caption text, which will either accompany a pop-up photo, or if no photo then as a text box, when the marker is clicked. This can include wikilinks etc., to link on to additional relevant articles.  
|-  
! | Arc Text: label placed on an arc  
|-  
| | The use of arc-text parameters allows a short text (up to 20 characters) to be placed along on arc, with parameters to control the tightness of the circle (radius) and the looseness of the text (gap). The nature of the earth's coordinate system means that there will be some variation in an arc at different latitudes and at different zoom levels. Some allowance is factored in, but there will still be residual variation. Similarly, changes in radius will also have some effect on the gap size, with a larger radius opening out the gap somewhat. There will therefore need to be a degree of trial and correction to get the shape and effect desired. As a general rule, identify the coordinates of the required start-point, then choose a starter-pattern from the selection at OSM Location map#Text on an arc, and then adjust parameters to fit the requirement of the map. The parameters below are for set A. Sets B and C are also available.  
|-  
! Parameter  
! Description  
|-  
| <code>arc-coordA</code>|| coordinates of first letter, using =  
|-  
| <code>arc-textA=</code>|| Add your text here  
|-  
| <code>arc-angleA</code> ||in degrees, -180 to 180. 0 will start as horizontal, -90 straight up, 90 straight down  
|-  
| <code>arc-gapA</code> ||1= a notional 'standard'. 0.2 is very tight, 10 is very wide. Applying a negative gap will invert the letters and run the other way around the circle  
|-  
| <code>arc-radiusA</code> ||1= a notional 'standard' 0.5 is quite a tight circle, 8 is so wide as to be almost flat, dependent on latitude and zoom level  

|-| <code>arc-text-sizeA</code> ||standard font sizes. If undefined, default is 12  
|-  
| <code>arc-text-colorA</code> ||sets text color. #000000 color hexes and standardised OSM Location map colors are accepted  
|-  
| <code>ellipse-factorA</code>||will squash or stretch the circle. 1= notionally circular, 0.5 to 1.0 will flattern top and bottom, above 1.0 flattens the sides.  
|}  

## Underlying technology
OSM Location map itself has no map or display ability of its own. Everything within the is produced through the template , created by User:Yurik. This in turn calls internal processes that turn all the data supplied at edit time into a rendered bitmap image, so that there is no calculation overhead by the time the page is read by a user, any more than any other commons image.  

Whilst the map is being edited and previewed, the page is supplied with a rasterised image, collating the base-map, marks, labels, etc. on the fly. It will be particularly noticeable on small fonts that when the 'Publish Changes' button is pressed, the resulting bitmap has much worse fonts than the preview. (Maybe this will be improved at some point). The process of updating the map image and providing the bitmap is all handled internally and invisibly. One of the consequences of the 'bitmap' solution, which is different from the standard method, is that there is no text or objects on the final image, so there is no possibility of adding wikilinks within the template.  

The full screen option, which can be clicked through from below the map, provides an entirely different mapping approach, using the same base-map data. This provides an interactive map that can be panned and zoomed. It also replicates (although at present only as numbered markers) the various marks from the page map. These can then be given more content, by way of a title, caption and image along with displaying the coordinate values. The caption and title can then be given all the wikilinks and other markup features that may be desired, providing a map-based page that will offer another way of engaging with the article content.  

Future development of the various mapping technologies is likely to result in further options for showing maps on Wikipedia. In particular, , which initially just created a text link to a full-screen map, can now create a framed image including dot-markers, roads, boundaries, etc., and can acquire data directly from wikidata to do this. Again, the processor overheads are reduced by initially showing a bitmap, which can be clicked to become interactive within its . Maplink is being effectively rolled out within info-boxes, where the map is automatically generated from already available data.  

This template, on the other hand, is probably better suited to a hand-editable map, in which the area displayed and the selection of items and labels included are selected, edited, and added to, to suit the specifics of the subject in hand. A further approach, which is not currently supported within this template, but is available via the inderlying template, is to draw the data from Wikidata, using a SPARKL query that provides the selection of marks requested.  

The 'Graph' technology used here is described as under development, so while it is highly likely that this or a similar solution will still be available, it may evolve over time.