CadShift Blog

The r/gis thread from August 2026 asked a question that comes up every few months: which Python web mapping library handles large datasets? The common answer — “use PyDeck” — is partly right but misses the key distinction that determines whether your map loads in two seconds or crashes the browser. The real question is not “which library is faster” but “where does the data go and in what format?” Each library makes a different choice. That choice determines the practical upper limit of what you can render. ...

Every sheet metal shop with more than a handful of active parts runs into the same gap. The model changes — a bend radius is revised, a hole pattern shifts, a flange length is adjusted — and the SLDDRW already has everything: dimensions, bend notes, tolerances, title block, revision table. But the DWG that goes to fabrication is still sitting at the old revision. Someone has to open the drawing, let it rebuild, and export. Every time. ...

The EU Deforestation Regulation applies from 30 December 2026. For operators placing timber, cocoa, coffee, palm oil, soy, cattle, and rubber on the EU market, compliance requires a Due Diligence Statement submitted through the TRACES NT system. That statement must include plot-level geolocation data — and the format specification is not flexible. TRACES accepts GeoJSON in WGS84 (EPSG:4326) with coordinates expressed as decimal degrees to at least six decimal places. Plots over 4 hectares require a complete boundary polygon. Plots under 4 hectares may be represented by a single point. ...

Every nesting operator knows the moment: 200 DXF files land in an import folder named Part1.dxf, Part2.dxf, FlatPattern-3.dxf. The cut program runs. Parts come off the machine. Now someone has to match each blank to an installation slot by hand—measuring, comparing, labeling. This is a manual step that costs 30–90 minutes per nest cycle, scales with order volume, and doesn’t improve no matter how much you spend on nesting software. The root cause is a mismatch between what SOLIDWORKS produces by default and what ProNest, Lantek, and JETCAM expect in order to route parts back to their jobs automatically. ...

The Move Face command in SOLIDWORKS has three modes: Offset, Translate, and Rotate. In Translate mode, the PropertyManager shows a Copy checkbox. When checked, the original face stays in place and a translated copy is created alongside it — useful for generating offset geometry, creating clearance ledges, or duplicating a surface patch to use as a reference. The API tells a different story. IFeatureManager.InsertMoveFace3 is the method that drives Move Face programmatically. Its signature accepts a move type from swMoveFaceType_e (0 = Translate, 1 = Rotate, 2 = Offset), the faces to move, and the transformation values. There is no copy parameter. IMoveFaceFeatureData, the data accessor for reading back a Move Face feature, has properties for MoveType, Distance, Rotation, TranslationX/Y/Z, and the face arrays — but no Copy or bCopy flag anywhere in the interface. ...

Autodesk Inventor has no backward compatibility. Open an .ipt or .iam file from Inventor 2020 in Inventor 2025, save it, and that file will never open in 2020 again — not with any workaround, not with a trial license, not with a downgrade export. The migration is a one-way door. This matters because version upgrades in Inventor are not transparent events. Each new release updates the internal file format. When you open and save a file, Inventor rewrites it in the current format. If your team is spread across two Inventor versions — which happens whenever a seat upgrades before the rest of the organization — that saved file is now unreachable to anyone still on the old version. ...

Construction engineering creates a document management problem that product engineering doesn’t have. In a manufacturing shop, a single team owns the CAD model from concept to production, revisions are controlled through PDM, and the end artifact is a set of drawings for a factory with controlled access to your files. In construction, the same drawing passes through a structural engineer, MEP consultants, a general contractor, multiple subcontractors, a building inspector, and eventually the owner — each with different tools, different naming conventions, and different ideas about what “current” means. The DWG file from the structural engineer needs to align with the Revit model from the architect and the IFC export from the MEP team. File management failure in this environment means someone builds from a superseded drawing. ...

You receive a STEP file from a supplier or another team. It opens in SOLIDWORKS as an assembly with hundreds of sub-components. Some of them are clearly bent sheet metal parts—brackets, enclosure panels, mounting clips. Your goal is to get flat-pattern DXF files for the laser shop. When you right-click a component and look for Flat Pattern, it’s not there. SOLIDWORKS treats every STEP-imported body as a dumb solid: geometry only, no feature tree, no bend data, no flat pattern. Even if the body was originally modeled as sheet metal, none of that intelligence survives the STEP format. ...

Dassault Systèmes announced over a dozen AI features for SolidWorks at 3DEXPERIENCE World 2026. The marketing materials show engineers describing geometry in plain English, generating drawings on demand, and having AI explain why a feature failed. Most of that is real — but the gap between what runs on your desktop today and what requires a 3DEXPERIENCE subscription is larger than the announcements suggest. This is a precise breakdown: which features ship, which platform they require, what they can and cannot do, and where API macros still outperform them. ...

A question posted on the 3DEXPERIENCE forum in August 2026 had zero replies after several days: how do you extract the version history stored in the PDM archive’s index.xml files into SQL for reporting or internal tooling? The poster wanted Document ID, archive folder path, actual archived filename (like 00000001), and the full version chain, including entries that use a ref pointer instead of storing their own copy. No answer existed. No Dassault KB article covers it. No public blog post addresses it. This is that guide. ...