A fabricator sends you a DXF. It has the cut profile, the bend lines on a separate layer, and a note that says “10 ga A36, K=0.42”. You need to recreate it as a SolidWorks sheet metal part so you can validate fit, run interference checks against the assembly, and re-export a DXF that matches your shop’s layer conventions. There are two ways to get from that DXF to a working sheet metal body in SolidWorks. The discoverable path through the UI — Boss Extrude (Thin) → Convert to Sheet Metal → Sketched Bend — is what most users land on because every command is on a top-level toolbar. The cleaner path — Base Flange from sketch → Sketched Bend along bend lines — exists but it’s hidden behind a Sheet Metal toolbar that nobody opens until they’ve already started the wrong way. ...

A SolidWorks fab shop posted a sheet metal failure on Reddit last month. Their part had two L-flanges meeting at a corner with a small fold-back tab on one of them. The Sheet Metal feature kept throwing “Failed to compute flat pattern”, and after an afternoon of fighting it, they exported the DXF anyway, opened it in AutoCAD, and finished the cut profile by hand. Twenty-eight upvotes on a comment showing a five-step rebuild that worked for someone else but not them. ...

A PSA on r/gis last month pointed out that Apache Parquet now has native geospatial types and that GDAL’s GeoParquet driver is mature, ESRI ships read/write support, and QGIS treats it as a first-class format. The thread had the same energy as the old “stop using shapefiles” threads, except this time the alternative is not a marginal incremental improvement. GeoParquet is a different shape of file that solves problems shapefiles never could. ...

A user posted on r/SolidWorks asking why exporting a multi-view drawing to DXF produced a file with only one view. The replies suggested sheet templates, view scaling, and the usual draft-quality toggles. None worked. The actual cause was buried two dialogs deep: the DXF version dropdown in Tools → Options → File Locations → Export → DXF/DWG was set to R12. R12 cannot store layouts. SolidWorks wrote the model space and silently dropped everything else. ...

The r/SolidWorks thread that prompted this post had a line that anyone who has automated sheet metal exports will recognise: “I can’t for the life of me get the API to cooperate with DXF orientation on sub-bodies at arbitrary angles. Multibody DXF export wants to maintain the base part axis.” The comments offered advice that did not work, because the root problem is not in the macro — it is in how SolidWorks decides where a flat pattern lives in 3D space, and how ExportToDWG2 carries that decision through to the DXF. ...

Most GIS analysts who try to learn scripting open a blank Python console, type from qgis.core import *, and close the console within ten minutes. PyQGIS documentation dumps you into an object model of two hundred classes with no hint of which ones matter for the three workflows you actually run every week. It is the wrong entry point. The Model Designer is the right entry point. You already use it to wire up Clip, Reproject, and Extract by Location into a reusable graph. The menu option that nobody talks about is one click away: Export → Export as Python Algorithm. QGIS writes a complete QgsProcessingAlgorithm subclass that reproduces your model exactly, including every processing.run() call with the correct parameter dictionary. You now have a working script to modify instead of a blank console to fight. ...

The SolidWorks API documentation has a warning that stops add-in developers cold: “Only one instance of SQLite can run in SOLIDWORKS process space. SOLIDWORKS maintains a reference to the SQLite singleton. To ensure compatibility, your SOLIDWORKS add-in must use a version of System.Data.SQLite.dll that is the same as the version used by SOLIDWORKS.” If you’ve read that and immediately thought “but Lightning uses SQLite and it works perfectly fine alongside SolidWorks” — your instinct is correct. The documentation is not lying, but it’s describing a narrow problem in language broad enough to sound like a blanket prohibition. Most developers either over-react (abandon SQLite entirely) or under-react (ignore the warning and get lucky). ...

GeoJSON keeps showing up in places it shouldn’t. Someone drops a 2 GB .geojson into a processing pipeline, the script that used to run in 20 seconds runs for eight minutes, and the team spends a Thursday wondering whether the problem is their query planner, their RAM, or their patience. The problem is the format. GeoJSON is a perfectly good interchange format — human-readable, one-spec wonder, works everywhere a text editor opens. It’s a terrible working format as soon as your dataset has more than a few hundred thousand features. This post is about when to stop loading GeoJSON directly and what to convert to instead, based on what teams handling real-scale data actually reach for. ...

Every few weeks a mold shop posts a job for a Python or C# developer who can automate their SolidWorks mold design pipeline. The scope is usually the same: take an incoming 3D model, run shrinkage, generate parting surfaces, split the core and cavity, and hand off tooling data. The assumption is that because SolidWorks has a documented API, every mold step is scriptable. It isn’t. Some steps map cleanly to IFeatureManager calls. Others still require a human to pick faces in the graphics area. Knowing which is which is the difference between a pipeline that ships and one that spends six months bouncing between the add-in and the user. ...

A watershed analyst in Oregon runs QuickOSM’s “hospitals in the state boundary” query on a Monday morning and gets Download Failed: HTTP 406 Not Acceptable. The query worked on Friday. She re-runs it, gets the same error. Switches to QGIS’s native “Download OpenStreetMap data” tool — same error, slightly different wording. Twitter says other people are seeing it too. The r/QGIS thread has six comments and no consensus. The 406 response from overpass-api.de is not a timeout, not a rate limit, not your query, and not a QGIS bug. It’s the Overpass server telling you something specific about your request that most documentation glosses over. The fix is a one-line configuration change, but only if you know which line. ...