A rectangle's orientation does not describe its entry openings
A floor layout describes where outside rectangles end up. A handling-access record describes how the actual units may be approached, supported and moved. Those are connected questions, but the numeric rotation in a layout is not a pallet's fork-entry specification. A 90-degree placement exchanges the footprint's length and width in the drawing. It does not report the opening width, deck construction, tine position, insertion depth or equipment movement that would be needed at that position.
Consider a fictional load with a 1200 by 800 mm finished footprint. A floor comparison permits right-angle rotation and uses the historical 5898 by 2352 mm twenty-foot preset, with no gap or wall clearance. The identical-rectangle engine returns eleven positions with an optimal geometric status for the verified case. This result says that those rectangles can occupy the modeled floor. It does not certify access to every pallet face, describe the actual entry openings or simulate placing the final pallet.
Separate model orientation from the physical face
Save the returned coordinates and rotation values first. Then map the physical faces of the actual load to that drawing in your local handling record. A face can have a label, a known entry arrangement or an obstruction that the rectangle engine does not receive. Do not invent a standard face convention from the engine's zero-degree label. It is relative to the input length and width, and the pallet or packaging may have been described differently by the person measuring it.
The EPAL product reference can support identification of an EPAL Euro pallet, but a reference drawing does not establish the condition of a particular carrier or compatibility with a particular handling device. Record actual carrier construction and condition through the responsible process. Likewise, a wrapped load may hide or obstruct access features that were visible on the empty pallet. Preserve that finished-load observation rather than copying an empty-carrier assumption.
| Record item | Value or interpretation |
|---|---|
| Geometric input | 1200 × 800 mm outside footprint; rotation permitted |
| Returned layout | Coordinates and 0°/90° placement orientation |
| Physical entry data | Carrier face, actual opening measurements and source |
| Equipment data | Relevant device dimensions, identified by the responsible operation |
| Unknown questions | Approach, insertion, lifting and final-unit placement |
| Interpretation | The rectangular search does not answer the unknown handling questions |
Use dimensions as observations rather than a clearance rule
Suppose a hypothetical measured opening is 180 mm wide and a relevant tine is 160 mm wide. Their simple width difference is 20 mm. Suppose their measured heights are 70 and 50 mm, again a difference of 20 mm. These are illustrative subtractions, not a recommendation for minimum clearance. A difference alone does not establish alignment, insertion depth, tine spacing, deflection, surface condition or compatibility under movement. Do not label the device suitable based on those two numbers.
Keep the original measured values, measurement date and object identity privately. Record whether the observation applies to an empty carrier or the completed load. If an entry dimension is unknown, mark it unknown and obtain the actual information from the responsible supplier or operation. Replacing an unknown with zero or an assumed average creates a false record. This website has no fork-geometry fields into which those observations can be entered for a supported handling simulation.
Retain the geometric comparison without adding unsupported inputs
Open the twenty-foot footprint example. Review the separate container result for the entered pallet footprint. The case stack remains its own result. Do not append invented forkWidth or approachAngle query fields: the supported parser does not make such values part of the calculation. Store the handling observations alongside the returned drawing in your own document.
A lower count with a requested gap may leave more empty space, but the gap field is separation between rectangles. It does not prove a usable aisle or route for a device. A wall-clearance field reserves geometry at the boundary; it does not prescribe the amount needed for forks or a person. Obtain the real allowance from the responsible operation and state its purpose when entering it. The methodology explains the finite search and coordinate scope.
Questions to resolve before using the drawing for movement
Which physical face corresponds to each input side? Which faces permit the intended entry on the actual carrier? Are openings unobstructed on the finished load? What device and movement procedure will be used? Are any positions inaccessible after neighboring loads are present? What measurements or requirements are still missing? Retain the answers and their sources locally, linked to the specific coordinate record.
Review changes that a count alone can conceal
Two layouts can have the same count and different orientations or sequences. A revised footprint can move a rotated unit to another location while preserving eleven positions. A carrier change can preserve the outside dimensions and change its entry construction. These changes affect the handling record even when the large count does not move. Compare the actual placements and physical information rather than treating equal counts as identical plans.
The useful handoff presents one drawing and one separate set of unresolved access questions. It does not invent a minimum aisle, declare a pallet face usable from its label, or claim the calculator has modeled fork motion. Send the actual measurements and proposed arrangement through the normal carrier or site review process. A specific unknown is easier to resolve than a general assertion that an optimal rectangle packing is ready to load.