Relux GLDF Conversion Guide

GLDF to Relux Conversion: Standard vs. Simplified

This guide explains the differences between the two available methods for converting GLDF files into the Relux database: Standard Conversion and Simplified Conversion.

Each method serves different needs depending on the complexity of your product data.

Standard Conversion

 What It Does

• Creates a separate product entry for each variant in the GLDF file.
• Generates a unique product number per variant, e.g., ABC123-Variant01, ABC123-Variant02, etc.

Supports complex product features like:

• Multiple variants
• 3D geometry parts linked to different emitters
• Model-specific light distributions

Why Choose This Option?

Provides more comprehensive compatibility with the Relux standard database.

Necessary if your product:

• Has multiple configurations
• Uses multiple light distributions
• Includes multiple emitter-object bindings

Considerations

Generates more entries in the database.
Product numbers are extended to reflect variants if the file has more than one variant.

Simplified Conversion

What It Does

• Creates only one product entry from the GLDF file.
• Uses the product number from the metadata section.
• Creates records in Bestückung for each variant

Why Choose This Option?

• Ideal for simple products with only one variant.
• Good for simple product data.
• Can better represent data in some use cases

Limitations

• May omit data if the product has multiple variants.
• Cannot support complex 3D geometry and emitter bindings.
• Compose table and EmitterObjectExternalName features are not supported.

Summary

Final Recommendation

Use Standard Conversion for complete, accurate representation of complex products.

Use Simplified Conversion** for simple, single-variant gldf files or mapping variants to Bestueckungen.

Try both options with your GLDF files to determine which better reflects your product in Relux.