Click on expandable/collapsible bar below to learn more about the Printmaps Editor GUI.

How to start:
- Download the map template archive und unzip it.
- You have now a working example for building a map.
- Build the map in order to get familiar with the process.
- Run the actions 'Build Map' and 'Download Map'.
- Unzip the file and view it with an appropriate application.
- Modify the definition file 'map.yaml' according to your needs.

Workflow: build map from scratch
- load map definition file (map.yaml)
- upload user supplied file (optional)
- build map
- download map

Workflow: improve and build map
- edit map definition file
- upload user supplied file (optional)
- build map
- download map

Workflow: save your work
- save map definition file (YAML)
- save map identifier (ID)

Workflow: continue working (in new Browser page)
- load map identifier (ID)
- load map definition file (YAML)
- same as 'improve and build map'

1) Load/Save map definition file (YAML).

2) Upload user supplied file (optional, repeat for further files).

It is often desired to display additional user objects on the map. Examples include own
tracks, a scale bar or a coordinate grid. These user objects are in corresponding files.
The user files can be uploaded to the Printmaps server using the 'Upload' function.
Note: The 'Data' function can be used to check which user files are stored on the server.

3) Build map (fetches status until build is done).

The 'Build' function does the following:
- creates map project with unique ID (if necessary)
- updates map meta data with current map definition
- places map build order
- fetches status until build is done

4) Download map (after build is done).

The 'Download' function loads the map generated by the printmaps server into the local
download directory of the browser. The 'Download' function can only be carried out if
the status 'map build successful' was previously shown via the 'Build' function.

A) Load/Save map ID (optional).

To build a map is an iterative, incremental process and takes some time.
All neccessary files to create the map are stored on your local system.
The map project is stored under an unique ID on the Printmaps server.
If you load this ID, you are able to continue working on your project.

An unchanged project is stored for seven days on the Printmaps server.

B) Fetch map data (optional).

The 'Data' function shows the current map definition data. This can be used, for
example, to determine which files have been uploaded to the Printmaps server.

C) Delete map project from server (optional).

If a map project contains sensitive data, the map project should be deleted from the
Printmaps server after processing. This can be done via the 'Delete' function. Note:
After a week the map project will be automatic deleted from the Printmaps server.