Saving IFC to SVG results in no data

Aspose.CAD Product Family
1

I’m loading an IFC file with Aspose.Cad.Image.Load(stream)

LargeBuilding.zip (291.5 KB)

And saving it as an SVG, with these options:

                    options = new SvgOptions
                    {
                        TextAsShapes = false,
                        ColorType = Aspose.CAD.ImageOptions.SvgOptionsParameters.SvgColorMode.Rgb,
                        VectorRasterizationOptions = new CadRasterizationOptions
                        {
                            Quality = new RasterizationQuality { Text = RasterizationQualityValue.High, ObjectsPrecision = RasterizationQualityValue.High, Arc = RasterizationQualityValue.High, Hatch = RasterizationQualityValue.High },
                            PageWidth = width,
                            PageHeight = height,
                            AutomaticLayoutsScaling = true,
                        }
                    };

I get an SVG with no data:

<?xml version="1.0" standalone="no"?>
<!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.0//EN" "http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd">
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" id="body_-160474540_81" width="512" height="512">

<g transform="matrix(0.0095764466 0 0 -0.0095764466 217.47725 242.82428)" >
</g>
</svg>

I’m able to render it as PNG fine, and I can see the image.

Thanks,
Kirk

2

@kirkmarple,
Hello, I can confirm the problem, I have logged CADNET-8741 ticket in our system, pending for investigation.

3

@kirkmarple,
just as additional note: you may consider downgrade temporarily to 22.2 version until we fix this issue.

1 Like
4

No worries, and it looks like 22.2 doesn’t have SVG support, correct? I see the FileFormat.Svg isn’t there in 22.2. We can wait for Aspose to fix this, since we don’t immediately have any customers using this format yet.

5

I believe there is support, please, find the test project attached.
TestApp.zip (1.1 MB)

6

Oh thanks, I’d forgotten the enum had changed from SVG to Svg in the newer version. That’s why I was thinking it didn’t have SVG support, when it didn’t find the enum when backdating the package.

1 Like