Appboard/2.4/builder/widgets/tile map/offline data: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls |
||
| Line 22: | Line 22: | ||
== Building Offline Tileset Packs == | == Building Offline Tileset Packs == | ||
Tileset packages are simply a zip file with a particular directory structure containing a set of tile images and a tile registry file which contains meta data for AppBoard to understand how to use the tiles. | Tileset packages are simply a zip file with a particular directory structure containing a set of tile images arranged in XYZ directories and a tile registry file which contains meta data for AppBoard to understand how to use the tiles. | ||
General process: | General process: | ||
| Line 28: | Line 28: | ||
# create a working directory, and change into that directory | # create a working directory, and change into that directory | ||
# create a subdirectory for the tile images, this '''must''' be in the following hierarchy: <tt>webapps/enportal/custom/tiles/''your_tileset''</tt> and replace ''your_tileset'' with an appropriate name. | # create a subdirectory for the tile images, this '''must''' be in the following hierarchy: <tt>webapps/enportal/custom/tiles/''your_tileset''</tt> and replace ''your_tileset'' with an appropriate name. | ||
# place the set of XYZ directories and images files into the directory above. So for example you may end up with something like <tt>webapps/enportal/custom/tiles/''your_tileset''/''z''/''x''/''y.png''</tt> where ''z'', ''x'', and ''y'' would be numbers representing the zoom level and coordinates. | |||
# create the subdirectory for the tile registry file and place it there. This '''must''' be in the following hierarchy: <tt>webapps/enportal/WEB-INF/xmlroot/appboard/config/tileregistry/''your_tileset.csv''</tt> where ''your_tileset.csv'' is the registry file and the rest of the path is the subdirectory. | # create the subdirectory for the tile registry file and place it there. This '''must''' be in the following hierarchy: <tt>webapps/enportal/WEB-INF/xmlroot/appboard/config/tileregistry/''your_tileset.csv''</tt> where ''your_tileset.csv'' is the registry file and the rest of the path is the subdirectory. | ||
Revision as of 12:55, 2 October 2013
The Tile Map Widget can be configured to use multiple base layer tilesets and multiple overlay tilesets, including tilesets served up by the AppBoard server removing the need for external Internet access.
Viewer clients connected to AppBoard will fetch the tilesets from the AppBoard server, to which they must already have network access.
It's important to understand that the size of the offline tileset grows exponentially for each additional zoom level. Levels 0 through 7 of the default OpenStreetMap (OSM) tiles is roughly 100MB, but online you can zoom through to level 20. Attempting to have an offline tileset with this deep level of zoom would be ... big.
Importing Offline Tilesets
Edge can provide some packaged OSM tiles for offline use, please contact support. Otherwise it is possible to build your own offline tilesets using a variety of sources and tools (see the Building section below).
- Shutdown AppBoard
- In a terminal change into [INSTALL_HOME]/server/bin
- Run the following command: portal FilesImport -jar <OfflineTilePackage>
- Restart AppBoard, the new tileset should be available when configuring Tile Map widgets.
Building Offline Tileset Packs
Tileset packages are simply a zip file with a particular directory structure containing a set of tile images arranged in XYZ directories and a tile registry file which contains meta data for AppBoard to understand how to use the tiles.
General process:
- create a working directory, and change into that directory
- create a subdirectory for the tile images, this must be in the following hierarchy: webapps/enportal/custom/tiles/your_tileset and replace your_tileset with an appropriate name.
- place the set of XYZ directories and images files into the directory above. So for example you may end up with something like webapps/enportal/custom/tiles/your_tileset/z/x/y.png where z, x, and y would be numbers representing the zoom level and coordinates.
- create the subdirectory for the tile registry file and place it there. This must be in the following hierarchy: webapps/enportal/WEB-INF/xmlroot/appboard/config/tileregistry/your_tileset.csv where your_tileset.csv is the registry file and the rest of the path is the subdirectory.
