This is documentation of an archived release.
For documentation on the current version, please check Knowledge Base.

Printing conditions

In Orbit a print job implies some limiting conditions that are inherent to the Java runtime.
Take the following in consideration:

Hardware vs software rasterization

By default Orbit software uses hardware rasterization.
In a client/server environment however, the client can not access the GIS data so Orbit falls back to software rasterization.

Software Rasterization (java 1.1 PrintJob) Hardware Rasterization (java 1.2 PrinterJob)
Orbit rasterizes GIS data and subsequently sends strips of images to the printer driver Orbit sends GIS data (eg vectors) directly to the printer driver which in itself performs the rasterization

Use buffer page

Sometimes a problem occurs while sending a print job to the printer driver (eg problems regarding use of transparency, truncated or mirrored labels, hatches, etc). Usually these problems occur due to the java runtime (jre).

As a solution Orbit can perform the print job in an image buffer memory that uses the display driver. This buffer can then be sent as an image to the printer. In this way, complex print jobs can be avoided. However, this workaround comes at the cost of RAM memory on the user's PC.

By default Orbit uses buffer paging but following validation rules apply:

No buffer page buffer page
1. Parameter (default: true)
false see 2
2. Page Size 1) see 3 ≤ A2
3. Maximum Memory 2) < 2000 megabytes > 2000 megabyte

Print Resolution is fixed at 300 dpi even though the print engine allows other resolutions.

Known Issues

Problem Solution
The resulting print is empty (white) ⇒ out of memory issue address more memory3)
Labels are truncated (cut in strips). use buffer paging
Labels are mirrored.
Print result contains hatching
the size of the page buffer is proportional to the size of the printed page
Last modified:: 2019/03/25 11:36