CadShift Blog

Most municipalities and utility contractors have their underground infrastructure documented somewhere — in CAD as-built drawings, in PDFs, in someone’s head. Getting it into a proper GIS layer is the difference between calling 811 and hoping versus knowing where a 6-inch water main runs before you start excavating. QGIS handles this well. It’s free, it imports CAD files, and it exports GeoPDF files that field crews can use offline on a tablet. The setup isn’t complicated, but there are decisions you need to make before you start drawing — particularly around file format, CRS, and attribute schema — that determine whether the data is useful for the next 20 years or becomes another file nobody trusts. ...

Data scientists encounter GIS when spatial data shows up in a project: a dataset with latitude/longitude columns, a shapefile from a government portal, a GeoJSON file someone dropped in the repo. The first few operations usually work. Then something breaks silently — a spatial join returns an empty DataFrame, a buffer produces geometry the size of a continent, or exported shapefiles arrive at the lab with every field name truncated. ...

Every SolidWorks tutorial on flat pattern views shows the same thing: open a sheet metal part, drag the flat pattern from the View Palette into a drawing. That works perfectly when you have one part and one drawing. It doesn’t help when you have an assembly with twelve sheet metal components and you need all the flat patterns in a single drawing document. The assembly case has two complications that the single-part case doesn’t. First, the View Palette shows assembly-level views, not individual part views — so the flat pattern doesn’t appear there. Second, when you insert from the assembly, SolidWorks shows views relative to the assembly coordinate system, not the part’s sheet metal orientation. Knowing which insert path to use for each scenario saves the frustration of inserting views that display the wrong orientation or can’t locate the flat pattern at all. ...

GIS format conversions do not crash loudly when they fail. They produce an output file, report success, and leave you with data that is wrong in ways you may not notice until the analysis is already done. Field names get silently cut at 10 characters. Geometries disappear without warning. Coordinate systems shift without errors. Attribute types coerce to something that looks right but produces wrong numbers. These are not edge cases. They are the default behavior of the tools most GIS teams use daily — including GDAL/OGR, QGIS’s built-in export, and ArcGIS Pro’s geoprocessing toolbox. None warn you by default. ...

You add a louver, a lance, or a drawn cutout to a SolidWorks sheet metal part, flatten it, export DXF, and the cuts that should appear in the flat layout are either missing or positioned wrong. The forming tool placed correctly in the bent part. The flat pattern shows the footprint outline but not the cut geometry. The laser operator can’t nest from this file. This happens because of how SolidWorks models forming tool geometry — and the fix depends on which features are actually in play. ...

Open Task Manager during almost any SolidWorks session and you’ll find sldProcMon.exe sitting quietly next to SLDWORKS.exe. Most of the time it’s invisible — a few megabytes of RAM, no window, no icon you’d notice. Then, on some machines, it pins a full CPU core at idle, spawns a fresh copy every time you relaunch SolidWorks without cleaning up the old one, or — in scripted and remote-desktop automation — climbs to 90%+ CPU and refuses to let go. ...

The “Abnormal bolt pretension is detected during the modifying pretension cycle” warning stops your simulation run and tells you nothing useful. The docs say check material and geometry. Forums say add contact sets. None of that is wrong, but none of it explains the actual failure mechanism. This post covers how bolt connectors work internally, why the two-step pretension analysis exists, what “abnormal” actually means in this context, and the specific setup errors that trigger it. ...

You’ve spent an hour adding custom properties to each cut list item — part numbers, supplier codes, cost-per-unit. You modify a structural member, hit Rebuild, and they’re gone. Not obviously corrupted. Just attached to the wrong items, or pointing at stale folders that no longer exist in the tree. This is the cut list auto-update problem, and it’s not a bug. It’s the expected behavior of a consolidation system that doesn’t know you cared about those specific folders. ...

Some SolidWorks settings save reliably between sessions. Others reset silently every time you restart, or behave differently depending on how SolidWorks was installed, what Windows profile type is in use, and whether any admin policy overrides your preferences. This post covers the specific settings that fail most often, where they’re stored, and the fixes that work. Where SolidWorks Stores Its Settings SolidWorks stores user settings in two places: the Windows registry and document files. Knowing which is which tells you immediately whether a reset issue is a machine problem or a template problem. ...

The Wrap feature works instantly or fails with a cryptic error, with little indication of which outcome you’ll get until you click OK. Three modes — Emboss, Deboss, Scribe — fail in different ways and for different geometric reasons. Knowing which one applies to your geometry, and why the others will fail, stops the rebuild-error loop before it starts. What the Three Modes Actually Do All three Wrap modes start with a sketch on a flat plane and project that sketch geometry onto a curved or non-planar face. The divergence is what happens to the geometry after it lands. ...