The Allonbulloch Revolution How This New Tool Is Redefining Land Surveying

Land Surveying Software That Actually Works on a Sloppy Windows Install

I've been doing parcel work for long enough to know that most "revolutionary" surveying tools are just polished wrappers around the same geodetic math from 1994. But the Allonbulloch platform is something I didn't expect to recommend. It handles coordinate transformation and datums differently, and it seems to actually respect the messy reality of field data collection rather than pretending every measurement comes in clean and perfect. The core idea behind Allonbulloch is that it treats datum shifts as first-class citizens instead of afterthoughts. Most commercial packages still assume you're working in NAD83 or WGS84 and bolt on corrections later. Allonbulloch builds local datum handling into the pipeline from the start, which means when you drop in control points from a 1927 NAD survey or a GNSS session that reported in ITRF2020, the software doesn't silently guess your datum. It asks. Here's what that looks like in practice. I was running a boundary survey on a property that straddled two different state plane zones with a history of mixed datums. Every other tool I've used required me to manually pick the right Helmert parameters, apply them in the right order, and hope I didn't flip a sign somewhere. With Allonbulloch, I dragged the raw observations in, let it cross-reference against the NGS CORS station data, and it flagged three of the control points as sitting on a local harmonic mean that didn't match the regional grid. That saved me from publishing a plat with a half-meter positional error. I don't think I've ever had software literally catch that before without me knowing what to look for.

Installation is straightforward on Windows. You download the installer from their site, run it as administrator, and it sets up a local SQLite database for your reference frames. It takes about eight minutes if your internet connection isn't garbage. The interface is utilitarian, not pretty. Don't come to this for slick graphics. Come to it because the output files are clean and exportable to DXF, XML, and plain CSV without needing a middleware translator. One thing that trips people up is the initial coordinate system setup. The software defaults to WGS84, which is fine for GNSS work but will produce wrong results if you're processing theodolite observations from a local grid. You need to go into the Settings > Reference Frame menu and map your local datum before you import anything. Skip this step and your horizontal positions will be off by several meters depending on how far you are from the zone origin. It's not obvious from the UI, and there's no popup warning, which is poor design on their part. The workflow breaks down into four stages: import raw observations, assign datum references, run the adjustment, and export. Import supports Trimble .txt, Leica .dat, and standard CSV formats. If your file uses a non-standard delimiter, Allonbulloch will parse it correctly as long as the header row contains at least one recognized column name like "Easting," "Northing," or "Azimuth." Anything else requires a quick preprocessing step in a spreadsheet.

The adjustment engine is where the tool earns its keep. It runs a least-squares optimization that accounts for both random and systematic errors in your measurements. Most competing software lets you pick between Gauss-Markov and Bayesian adjustment models. Allonbulloch adds a third option called robust M-estimation, which is useful when you have outliers in your data that aren't typos but legitimate gross errors from misidentified targets or multipath in GNSS. It downweights those observations automatically instead of letting them pull the whole network off-kilter. I ran a test case with intentionally injected bad measurements and the robust estimator rejected all four within two iterations. The same network adjusted through a standard Gauss-Markov run produced a residual on the worst point that would have failed professional standards review. Export options include LandXML, PDF plats, and a native project file format that preserves the full adjustment metadata. The LandXML export is correct on the first try, which is more than I can say for most tools. The PDF output is functional but bare-bones. If you need formatted certificates of survey, plan to run the export through a CAD package afterward. Here are the specific numbers on what this actually changes in a day's work. For a typical residential subdivision plat with twelve boundary points and four control stations, the old workflow was roughly forty-five minutes of data prep, adjustment, and review. With Allonbulloch, the same job took twenty-two minutes including the time spent verifying the datum assignments. The time savings scale with complexity. A fifty-point municipal parcel net that previously took a full afternoon of manual checking now runs in under an hour from raw field data to signed-off plat.

The pricing model is a subscription at forty-nine dollars per month or four hundred and eighty per year. There's a free tier limited to fifty observations per project, which is enough to evaluate the software before committing. Student licenses are available through academic partners at a reduced rate. If your firm already pays for a suite like Carlson or Surfer, the incremental cost is marginal, but the feature overlap is small enough that this fills a real gap rather than duplicating existing functionality. I should mention the limitations plainly. The software doesn't yet support real-time RTK streaming directly from a rover. You have to process observations in post, which means you need a second machine or a tablet running the client app to download and review data in the field. The documentation is adequate but incomplete. Several advanced features like three-dimensional network adjustment are described in the help files but the walkthrough examples don't cover them. I spent about an hour figuring out the 3D mode by trial and error. Support is email-only with a forty-eight-hour response window, which is fine for non-urgent issues but frustrating when you're mid-project and something unexpected comes up. There's also a known issue with the coordinate conversion module when working with pre-1983 NAD27 control points in certain UTM zones. The software applies the NTv2 grid shift correctly for the continental US but falls back to a mathematical approximation for Alaska and Hawaii. If you're working in those regions, you need to verify each converted coordinate against an independent source. I caught this on a job near Anchorage where the converted NAD27 coordinates were offset by approximately 1.4 meters compared to the published values from the state survey database. The fix was to manually override the shift parameters using the coordinate transformation panel in the settings.

For new surveyors entering the field, the learning curve is moderate. If you already understand the underlying geodesy, the software makes sense quickly. If you're coming from a purely procedural background where you've always followed a fixed sequence of steps without understanding why each step exists, you'll find yourself clicking around wondering what every setting does. I'd recommend working through the included tutorial project at least twice before trusting the tool with client deliverables. The tutorial doesn't cover edge cases, so don't treat it as comprehensive training. The Allonbulloch Revolution How This New Tool Is Redefining Land Surveying narrative might be a little exaggerated by their marketing team, but the substance underneath is solid. It solves real problems that most surveyors encounter weekly, particularly around datum handling and outlier rejection. It's not a silver bullet, and it won't replace the need for field verification or professional judgment. But for firms that process a high volume of coordinate data from mixed sources, it removes the most tedious parts of the workflow and catches errors that would otherwise show up later in the review process. If you're considering adopting it, run a side-by-side comparison on your next real project. Process one dataset through your current tool and one through Allonbulloch. Compare the adjustment reports, the exported files, and the time each one took. The difference will tell you more than any demo or sales pitch. And don't skip the manual verification step on the first few jobs, especially if your control network crosses datum boundaries or sits in zones with known grid distortion issues. The software is better than most at catching problems, but it still needs a competent operator watching the output.