It is an ordered list of map sources to be layered one on top of the other, where the last map source is the top-most.Įxample files for download Example custom multi-layer map source.xml Example custom multi-layer map source2.xml Custom Built-in Map Packĭeveloping a custom built-in map pack requires at least basic Java skills. The most important part of this definition is the entry. A non-transparent layer will hide all layers listed before it. Note All map source layers, except the first in the list (the background layer), must have transparent parts. Map sources which consist of two or more layers can be defined, similar to single-layer custom map sources. name = "Your map source name here" Įxample file for download Example beanshell map source.bsh Custom multi-layer map sources Note It is recommended to add a line defining the unique name of the map source to the BeanShell code. It will be loaded on next start-up of MOBAC.
Mapsource map blank code#
To do so place the saved BeanShell code file (file extension. Not supported: OruxMaps and Osmdroidĭ:\MOBAC\LocalTiles\Įxample file for download Example custom tile SQLite source.xml Custom BeanShell map sourcesīeanShell map sources as the can be developed using MapEvaluator can be used by MOBAC. Supported atlas formats are: RMaps, MBTiles, BigPlanetTracks, NaviComputer and OSMAND. SQLite based atlas formats can also be used directly by MOBAC.
Mapsource map blank zip#
Tiles can also be packed into one or more zip files and directly used by MOBAC.Įxample file for download Example custom tile zip source.xml Note Java 7 is required when working with ZIP files larger than 4 GB Local Tiles in SQLite file Įxample file for download Example custom tile files source.xml file, adapt the entry and place it in the mapsources directory. Note At the moment the formats used by OSMTracker, AndNav, BackCountry Navigator, Maverick and OSMAND are supported. Custom CloudMade maps can be added to MOBAC via a simple XML file containing a map name used by MOBAC and a styleID:Įxample file for download Example CloudMade Fine Line.xml Local Tile filesĮxisting atlases or locally rendered tiles can be directly integrated into MOBAC as custom map source without having to set-up a local web-server. Each style is accessible through it's styleID. The CloudMade map service offers a large number of OpenStreetMap based maps with different styles. Otherwise you have to use their XML encoding, such as `&`Įxample file for download Example custom WMS map source.xml Custom CloudMade map sources It is recommended to wrap any field that has special charcters, such as an ampersand, inside a `` element. Currently only EPSG:4326 is supported as the coordinate system. It is a template containing specific placeholders, which are encapsulated by curly braces, and specify the requested tile.Įxample file for download Example custom map source.xml Custom WMS map sourcesĪ WMS server can be defined as a map source. It defines an additional map source named "Custom OSM Mapnik" which shows map tiles identical to the predefined map source "OpenStreetMap Mapnik". The following section shows is an example how the xml file has to be formatted. Simply copy and paste the content of an custom map source XML file into the editor and execute it. Note: For simple testing a custom XML map source you can also use MapEvaluator.
Most of them are defined in an xml file in the mapsources directory. Custom map sources which uses a similar URL scheme as Google/OpenStreetMap can be added to MOBAC.
0 kommentar(er)
