Appboard/2.4/builder/widgets/tile map/registering tilesets: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls No edit summary |
||
Line 11: | Line 11: | ||
{{Warning|The default files should not be modified as they are replaced on upgrade.}} | {{Warning|The default files should not be modified as they are replaced on upgrade.}} | ||
The process of registering tilesets is to create a new registry <tt>csv</tt> file with the correct fields and values, place this into the tile registry directory, and as a best practice ensure this file is included in backup archives (see [[appboard/2.4/admin/backup_and_recovery|Backup & Recovery]]). |
Revision as of 06:25, 3 October 2013
The Tile Map widget supports the use of multiple base-layer tilesets and overlay tilesets, but in order to make use of these they must be registered for AppBoard to know about them.
The focus of this page is to document the tile registry for cases where an existing tileset is available remotely. For cases where the intention is to generate your own tileset and/or have AppBoard serve this up locally then refer back to the main Tile Map page for more information.
AppBoard maintains the tile registry in the following directory: [INSTALL_HOME]]/server/webapps/enportal/WEB-INF/xmlroot/appboard/config/tileregistry. All csv files in this directory are loaded and by default the following files are included with the install:
- default.csv: contains the set of default base-layer tilesets
- overlays.csv: contains the set of default overlay tilesets
The process of registering tilesets is to create a new registry csv file with the correct fields and values, place this into the tile registry directory, and as a best practice ensure this file is included in backup archives (see Backup & Recovery).