Straight answers on data, formats, accuracy, and what happens when something goes wrong. If yours isn't here, just ask.
Whatever you specify at order time. Washington State Plane is built in – EPSG:2926 (North), 2927 (South), and the other NAD83 realizations, in US survey feet or meters – and once you draw your site, the order page suggests the zone for its county. Elevations are always NAVD88 in US survey feet, whatever horizontal system you pick, and every package prints both datums on the summary sheet, so there's no guessing what you imported.
It depends on the source, and we tell you exactly which one. NAIP is flown over Washington every two to four years, at 60 cm since 2019 (1 m before that). LiDAR vintage varies by location: the order page lists every collection that covers your whole site, from the WA DNR portal and USGS 3DEP, before you pay. The source name and capture year are stamped on the summary sheet for every layer.
No. A clip is public source data, clipped to your boundary and reprojected. It's built for basemapping, design backdrops, feasibility, and constraints screening, not as a substitute for a field survey or a stamped boundary determination. It saves you the afternoon of gathering data; it doesn't replace your professional judgment.
Yes – that's who it's built for. You draw the site on a map and check the layers you want, and the order page suggests the State Plane zone for your county. There's nothing to install and no data to keep current. What arrives is built for CAD: DXF and DWG copies of every vector layer, plus an optional LandXML surface for Civil 3D, with shapefiles and GeoTIFFs alongside for anyone who does use GIS.
Really CAD-ready. Every vector layer ships as a shapefile with DXF and DWG copies alongside it – included with every order – and you can add a LandXML existing-ground surface that drops straight into Civil 3D. LandXML is written in US survey feet, so it's offered with the US-feet coordinate systems. Layers are named the way you'd name them by hand.
Civil 3D and AutoCAD via DXF/DWG and LandXML; QGIS and ArcGIS via shapefile and GeoTIFF. If it reads standard CAD or GIS formats, it can read our clip data.
Any interval from 1 ft up to 100 ft, and up to ten per order, generated from the LiDAR DEM in your order. Pick them when you add contours. We start at 1 ft because that's what modern lidar (about 10 cm vertical accuracy) supports; finer lines would suggest accuracy the source doesn't have.
That's the typical turnaround for a standard job once payment clears - the package is built, quality-checked, and emailed to you automatically. If a job is flagged for review, a person checks it within one business day and emails you about what happens next.
The order is held and a person checks it within one business day. A package missing a layer you paid for never goes out the door – if we can't build it, you're refunded.
A download link arrives by email when the job finishes. The link is good for seven days. The files are yours to keep once you've downloaded them.
Yes. We only ship data from public city, county, state, and federal services.
All of Washington State, every county. Parcels come from Washington's statewide parcel layer, compiled from county data. Aerial imagery is USDA NAIP, statewide. LiDAR comes from the WA DNR portal or USGS 3DEP, whichever has the newest collection covering your whole site, and the order page shows you which years exist for your boundary before you pay. Sites outside Washington aren't available yet.
Yes. Clips are a data product, so Washington retail sales tax is calculated and added at checkout based on the delivery location.
If we can't build what you ordered, you're refunded. Because a clip is delivered data, we handle anything that's wrong with a completed package case by case. Email us and we'll make it right.
For custom work, get in touch and we'll follow up with a quote.
Let us know how we can help!