Click on the expandable/collapsible bar below to learn more about the Printmaps Basic 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 'create', 'order', 'status' and 'download'. - Unzip the file and view it with an appropriate application. - Modify the definition file 'map.yaml' according to your needs. Primary functions: - create: creates the meta data and ID for a new map - update: updates the meta data of an existing map - upload: uploads a list of user supplied files - order: places a map build order - status: fetches the current state of the map - download: downloads a successful build map Workflow: build map from scratch - create: creates the meta data and ID for a new map - upload: uploads a list of user supplied files - order: places a map build order - status: fetches the current state of the map Workflow: improve current map - update: updates the meta data of an existing map - upload: uploads a list of user supplied files - order: places a map build order - status: fetches the current state of the map - download: downloads a successful build map Workflow: continue work on map project - load: loads map ID - same as 'improve current map' Secondary functions: - data: fetches the current meta data of the map - delete: deletes all server artifacts (files) of the map - capabilities: fetches the capabilities of the map service
1a) Create meta data and ID for new map (required only once).
The initial step in creating a large format map is to execute the 'Create' function. A new map project with a unique ID will be created on the Printmaps server. This process is unique to execute. 'Create' expects a map definition file (typical name 'map.yaml') in YAML format as input. This can be the Printmaps template, a Printmaps example or a self-created YAML file. It is advisable to create a separate folder for each map project. There should be the map definition file and all other files required for map generation (e.g. tracks, scale bars, etc.) are stored. So the map can be easily reproduced at any time.
1b) Update meta data of an existing map (improve your map).
Generating a map is typically an iterative incremental process using several improvement steps. As a rule, adjustments are made in the map definition file (typical name 'map.yaml'). In order for these changes to take effect, the map definition file must be read in again to be sent to the Printmaps server via the 'Update' function.
2) Upload user supplied file (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) Place map build order (start map generation process).
In order to request the creation of a map from the Printmaps server, the 'Order' function must be carried out. The Printmaps server then starts the map generation process. This process takes some time depending on map size and server utilization.
4) Fetch current map build state (poll until build is done).
The processing status of the map can be determined at any time using the 'Status' function. Map creation typically takes some time. The 'Status' query must be repeated several times. If the map is successfully generated, the status 'map build successful' is displayed. The map can then be loaded from the Printmaps server.
5) Download successful build 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 'Status' function.
A) Load/Save map ID to continue map project (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. Limitation: An unchanged project is stored for seven days on the Printmaps server.
B) Fetch current map meta 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.
D) Fetch capabilities of map service (optional).
Printmaps allow map generation within certain conditions. These conditions can be called up via the 'Capabilities' function.