The map-styles manager manages map styles (“render themes”) for vector maps.
Top toolbar menu
The top toolbar menu provides the following options:
- Extract styles: If checked then zipped styles are extracted in the “Mapsforge styles” directory. This option is useful for developing custom render themes because you can directly edit the XML file.
- Check for updates: Checks if updates are available for the styles. This works only for styles with an associated download server.
- Info: This page.
Style entry popup menu
When clicking on a style entry the following popup menu entries are available:
- Set as default Mapsforge style: Sets the style as the default Mapsforge style.
- Set as default MBTiles (vector) style: Sets the style as the default MBTiles (MVT) vector style.
- Layers: Opens a dialog where you can select Mapsforge layers provided by the selected style (city, bicycle, hiking, etc.).
- Enable Mapsforge features: If the style is a Mapsforge style then this option should be enabled.
- Rename: Renames the style.
- Delete: Deletes the style.
- Move to folder: Moves the style to another folder.
- Clone: Creates a copy of the style entry.
- Redownload/update: Re-downloads the style. This option is only available when a download url is attached to the style.
Main view “+” button
The “+” button offers the following options:
- Add folder: Adds a new folder.
- Import style: Imports a style from a file.
- Download style: Shows a dialog with sites offering styles for download.
7 thoughts on “Mapstyles manager”
I’ve been using the old Windows 10 Desktop Version Cartograph Pro 2.6.2 in the past years and recently updated/changed to new Desktop version Cartograph 3 (version 3.2.2), which has good improvements (e.g. tracks information etc.).
However, unfortunately the standard ML Mapsforge maps (e.g. OpenAndroMap Alps_East_oam.osm, etc.) with Elevate themes are not rendered/displayed anymore in a good manner: they appear with very low contrast only (e.g. contour lines hardly visible) regardless what settings I try. For that reason I’d stick to the old version or/and other software which don’t show this rendering weakness.
Or is there a way that this can be improved in Cartograph 3?
Thans and regards,
Please open the map as a “Mapsforge (raster)” map (by clicking on the map entry in the Map manager). This will show the map with the old Mapsforge render engine.
Great – thanks for your info!
BTW: I also checked the functionality for displaying Orux/Locus SQLite Maps (with different projections, sizes, etc.) which basically are displayed correctly. FYI, just the calibration of these format is somehow slightly interpreted wrongly, as those maps are always a bit stretched: GPS waypoints/coordinates are displayed ~50-200 meters away from their real position (too far north-west on the upper/northern map part and ~100-300 meters too far south at the southern map part). No big deal for me (as I rarely use these maps ), but maybe an interesting info for you (room for improvement 🙂 …).
Anyway, thanks for your great software!
Are you facing this problem only with Orux SQLite maps (which contain a XML + DB file), or also with Locus SQLite Maps (which should always be WGS84)?
Actually with Orux SQLite Maps (XML+DB; ), which all have have datum=”WGS 1984:Global Definition@WGS 1984:Global Definition”. Some have … projection=”Transverse Mercator,9,0,0.9996,0,0″ … some have … projection=”UTM,32″ …
Actually with Orux SQLite maps (XML+DB; ), which all use datum=”WGS 1984:Global Definition@WGS 1984:Global Definition”. Some have projection=”Transverse Mercator,9,0,0.9996,0,0″ some projection=”UTM,32″ …
Thanks, I have noted down the bug.