About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
configuration:geographic_features

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
configuration:geographic_features [2023/10/24 11:07] – Removed more historical notes from 3.x and 4.x. demiankatzconfiguration:geographic_features [2023/10/24 19:25] (current) – [General Configuration Notes] lmgonzales
Line 19: Line 19:
 ==== Coordinates ==== ==== Coordinates ====
 The coordinate data will go into field 034 of your MARC record, in subfields $d,$e,$f, and $g.  The coordinate data will go into field 034 of your MARC record, in subfields $d,$e,$f, and $g. 
-You can format your coordinates as decimal degrees (DD) or degrees minutes seconds (DMS), and you can assign hemispheres by using either letters (N,S,E,W) or symbols (+,-).+You can format your coordinates as decimal degrees (DD) or degrees minutes seconds (DMS), and you can assign hemispheres by using either letters (N,S,E,W) or symbols (+,-). If you omit the + sign, it is considered the default.
 Note that the order for coordinates in the [[http://www.loc.gov/marc/bibliographic/concise/bd034.html|MARC 034 field]], is: Note that the order for coordinates in the [[http://www.loc.gov/marc/bibliographic/concise/bd034.html|MARC 034 field]], is:
 $d: West; $e: East; $f: North; $g: South $d: West; $e: East; $f: North; $g: South
  
-* Note, [[https://github.com/vufind-org/vufind/pull/1076|PR#1076]] upgrades the code to allow for unsigned DD coordinates. With this patch, positive values do not need to be prefixed with the + sign.  +If malformed coordinates are detected during indexing, an error message containing the record ID, coordinate values, and problems with the coordinate values will be displayed. Malformed coordinates will not be included in the indexed record
- +
-If malformed coordinates are detected during indexing, an error message containing the record ID, coordinate values, and problems with the coordinate values will be displayed. Malformed coordinates will not be indexed. +
  
 ==== Labels ==== ==== Labels ====
Line 65: Line 63:
  
 ===== Displaying Geographic Data ===== ===== Displaying Geographic Data =====
 +
 +==== Underlying Technology ====
 Starting with VuFind® 5.0, geographic features are displayed with **Leaflet**. For historical information about earlier implementations using OpenLayers and GoogleMaps, click the "Old revisions" button below to find earlier versions of this page. Starting with VuFind® 5.0, geographic features are displayed with **Leaflet**. For historical information about earlier implementations using OpenLayers and GoogleMaps, click the "Old revisions" button below to find earlier versions of this page.
  
Line 70: Line 70:
 Features can be clicked on to show a popup window that will display the label and/or coordinates of that feature depending on how the [MapTab] section is configured in the **geofeatures.ini** file. Features can be clicked on to show a popup window that will display the label and/or coordinates of that feature depending on how the [MapTab] section is configured in the **geofeatures.ini** file.
  
-//Notes:// +==== General Configuration Notes ==== 
-  * The recordMap parameter in geofeatures.ini [MapTab] section has changed from a string to a boolean field in VuFind® 5.0 so that it can be used to toggle the Map Tab display on and off.+  * The recordMap parameter in geofeatures.ini [MapTab] section can be used to toggle the Map Tab display on and off.
   * The basemap is set in the [Basemap] section of geofeatures.ini   * The basemap is set in the [Basemap] section of geofeatures.ini
  
Line 89: Line 89:
 Labels can be read from the long_lat_label field if they are stored in Solr, or assigned on the fly with a look-up table. If you use a look-up table, put it in your local/config/vufind/ directory, and in the geofeatures.ini file, set mapLabels = file:filename. Labels can be read from the long_lat_label field if they are stored in Solr, or assigned on the fly with a look-up table. If you use a look-up table, put it in your local/config/vufind/ directory, and in the geofeatures.ini file, set mapLabels = file:filename.
  
 +:!: // Note:  Starting in VuFind® 7.0., the contentsecuritypolicy.ini file was implemented. You will need to modify this file to include the basemap tileserver domain. 
 +
 +The following is an example if you are using CARTO basemap server:
 +// 
 +<code>
 +img-src[] =  "http://basemaps.cartocdn.com" 
 +</code>
 +==== Notes on Map Tiles ====
 +
 +Map display depends on access to a tile set to allow zooming and scrolling around the world. The geofeatures.ini file includes some example tile URLs, but tile sets from free providers come with significant limitations on usage. If you wish to use this feature in production, you may need to subscribe to a commercial map provider or else run your own [[configuration:geographic_features:map_tile_server|local tile server]].
 +
 +One way to help reduce the amount of map tile server calls is to configure the defaultRecordTab setting in the config.ini file to something other than "Map".
 ===== Geographic Searching ===== ===== Geographic Searching =====
  
configuration/geographic_features.1698145649.txt.gz · Last modified: 2023/10/24 11:07 by demiankatz