How to validate ArcSite topographic drawings for landscaping

How we work: This guide uses current public documentation and does not claim hands-on testing unless stated. Some links may later become affiliate links, at no added cost to you. Rankings are independent of commissions.

Treat an ArcSite topographic drawing as a visualization of entered elevations until its inputs, reference, point coverage, checks, and export have been verified. ArcSite can turn elevation points into contour lines and a color heatmap. That makes grade easier to discuss, but a polished surface does not establish where the numbers came from or whether they are accurate enough for design, permitting, drainage, or construction.

The practical test is to preserve every raw reading, tie it to a named benchmark, repeat independent points, check slopes manually, inspect grade breaks in the field, and verify the exported drawing. If the work depends on a boundary, certified accuracy, drainage design, a retaining structure, or a permit, use the licensed professional and standards required where the project is located.

This is a desk-researched acceptance protocol, not a report of hands-on ArcSite testing or professional surveying advice. The ArcSite documentation and independent surveying guidance were opened and checked on September 19, 2026. The field checks below are proposed tests; this site did not perform them.

What does ArcSite’s topographic tool actually do?

ArcSite launched Topographic Drawings on August 3, 2026. Its current help guide describes a direct-entry workflow:

1. Place an elevation data point on the drawing.
2. Enter a positive or negative height.
3. Repeat across a closed area.
4. Optionally set one point as the zero reference.
5. Generate contour lines and a color-filled heatmap.

ArcSite supports decimal feet, decimal inches, millimeters, and meters for elevation points. It says at least five points are needed for usable output. Elevation points require Draw Pro or above; generated contours and the heatmap require a Takeoff or Estimate tier. Those plan gates were checked on September 19, 2026.

The documentation explains how to enter and style the data. It does not say that the app measures ground elevation by itself. It also does not publish, on the pages reviewed, a contour interpolation method, a vertical accuracy statement, a field-closure test, or a raw elevation-point export. Record the measurement source and checks separately rather than assuming the drawing contains them.

ArcSite’s five-point threshold is therefore a software minimum, not an acceptance tolerance. The Association of Ontario Land Surveyors’ guide makes the distinction clear: many closely spaced observations can still be unsuitable if their accuracy is poor, while precise observations can still miss terrain when their spacing is inadequate.

Which evidence is strong enough for each landscaping use?

Rank the drawing by the evidence behind it, not by how smooth the contours look.

Virginia’s current topographic-survey rule illustrates what formal evidence can include: visible improvements, elevations, a benchmark tied to a stated vertical datum, scale, contour interval, units, coordinate system, collection method, date, accuracy, and professional responsibility. Other jurisdictions have their own rules. The point is not to apply Virginia’s numbers everywhere; it is to see how much information a colored surface alone leaves unresolved.

What should be decided before anyone enters a point?

Write a one-sentence purpose and acceptance rule before the site visit. For example: “Use measured relative elevations to estimate the extent of lawn regrading; no boundary, drainage outlet, retaining-wall, or permit decision will be made from this drawing.”

Then record these controls:

The aerial-measurement field protocol uses the same principle for plan dimensions: decide which measurements are risky before comparing tools. Elevation work adds a second reference system and consequences that an area-only takeoff does not have.

How do you control the base drawing, units, and benchmark?

How should the canvas be calibrated?

ArcSite separates canvas calibration from export scale. Calibration tells the drawing that a line represents a known real-world distance. Export scale controls how large the drawing appears on paper or in a file; ArcSite states that changing export scale does not improve drawing accuracy.

Use this check:

1. Calibrate against a dimension whose source and endpoints are known.
2. Measure a second, independent dimension that was not used for calibration.
3. Compare the displayed result with the field value under the project’s approved tolerance.
4. Confirm orientation and the measured area against recognizable site features.
5. Save the base-plan source, calibration line, actual distance, check line, field distance, difference, and reviewer.

ArcSite remembers the last calibration and can apply it to a later drawing. That convenience is also a failure mode: verify each project’s calibration instead of accepting the inherited canvas scale.

How should the elevation reference be controlled?

ArcSite’s Set as Reference command makes the selected point zero and recalculates the others relative to it. That is useful for communicating relative change. It does not, by itself, create a survey benchmark or identify a vertical datum.

Choose a stable, recoverable physical point. Record:

• benchmark ID and plain-language location;
• a close photo and a context photo;
• entered elevation and unit;
• whether the basis is assumed or tied to a required datum;
• instrument setup and operator;
• first reading, closing reading, and difference; and
• conditions that could disturb or obscure the mark.

Do not use movable objects, loose pavers, temporary stakes without control, or an unlabeled screen location as the only benchmark. The AOLS guide recommends redundancy rather than relying on one elevation point because a moved reference or wrong coordinate must be detectable.

Where should elevation points be placed?

Do not spread five points evenly and call the surface complete. Point placement should describe changes in terrain and the features that control the decision.

Collect or verify points at:

• the benchmark and at least one independent check point;
• tops and bottoms of slopes;
• abrupt grade breaks;
• local highs and lows;
• both sides of swales, ditches, berms, and crowns;
• thresholds and finished-floor interfaces relevant to the scope;
• tops and bottoms of curbs and walls;
• drain rims, inlets, visible outlets, and accessible flow lines;
• hardscape corners and surface transitions;
• areas hidden by vegetation or interrupted by obstacles; and
• every place where the proposed work or quantity changes.

The National Park Service’s landscape documentation guidance calls for field-run spot elevations and significant vegetation, structures, hardscape, curbs, high and low points, utilities, and drainage features when those elements are in scope. It also recommends field-checking a draft topographic survey. That review principle transfers well to an estimating drawing: a surface model cannot restore a feature nobody recorded.

For every ArcSite point, keep a companion log with point_id, drawing revision, time, operator, instrument, raw reading, unit, benchmark, relative elevation, surface or feature, photo ID, and review status. Use the same point IDs as labels on the drawing. If a point is rejected, retain it with an exclusion reason rather than silently editing the number into agreement.

How should you test the points before trusting the contours?

Run checks on the readings before interpreting the heatmap.

Decimal precision is not accuracy. A point displayed to several decimal places is still limited by the instrument, setup, surface, point placement, and reference. The acceptance record should compare measured differences with a tolerance chosen before testing, not with the number of digits on screen.

How do you validate contours and the heatmap?

ArcSite lets the user choose contour interval, fill gradient, line weight, line type, color, and height labels. These are presentation controls. A narrow interval can create more lines without creating more field information.

Use this sequence:

1. Save a revision with the verified points visible.
2. Generate contours only inside the closed measured area.
3. Set and record the interval; do not choose it merely because the heatmap looks smoother.
4. Trace every visible high, low, ridge, swale, wall, curb, and grade break against the point log and field photos.
5. Add measured points where the generated pattern crosses a hard break, bridges an unmeasured obstruction, or implies a feature not observed.
6. Regenerate or refresh the drawing, then save a new revision.
7. Have someone other than the collector review the point labels and critical flow path.

ArcSite says the map updates the area around a newly added point rather than rebuilding the entire contour map, and recommends zooming in or out if a change does not appear. Include that refresh check in the test. Never edit an input elevation only to make the contours match an expected story; resolve the field evidence.

Treat color as a legend, not a conclusion. ArcSite’s default gradient places red at low values, green around zero, and yellow at high values. A customer could easily interpret red as danger or yellow as dry even though the colors encode only relative elevation. Include values, units, reference, interval, revision, and exclusions on the reviewed output.

How can you check slope and drainage claims?

Select pairs of verified points and calculate:

grade percent = 100 × vertical change ÷ horizontal run

Use horizontal run from the calibrated drawing or a separately controlled measurement. Preserve the two point IDs, signed vertical change, run, unit conversion, result, and reviewer. Compare the manual result with the direction and spacing implied by the contours.

Do not turn that arithmetic into a universal drainage rule. Surface material, soil, compaction, obstructions, subsurface conditions, inlets, outlets, adjacent property, rainfall criteria, and local design requirements also matter. A heatmap can support reconnaissance and communication; it does not prove that a proposed grading or drainage system is safe or approvable.

Escalate when water could be directed toward a building, public way, utility, neighboring property, unstable slope, or regulated drainage feature. The licensed designer must choose the design criteria and confirm the outlet, not the estimator’s color interpretation.

How should quantities and estimates use the drawing?

Separate measured facts, generated geometry, and estimating assumptions.

Do not calculate cut, fill, soil, or drainage quantities from the heatmap alone. First confirm that the workflow produces the surface or dimensions the quantity method requires, that voids and breaklines are handled, and that a known test case reconciles. ArcSite’s reviewed topographic guide documents contours and a heatmap; it does not document a topographic cut-and-fill calculation.

The landscaping estimate template keeps measured quantity, production assumption, unit cost, and markup separate. The AI photo-estimate QA guide makes the same distinction between extracted evidence and an approved estimate: a plausible output is not a verified quantity.

What should be checked after export?

ArcSite currently documents PDF, DWG, DXF, and PNG exports. PDF offers controls for orientation, paper size, margins, output scale, export area, photos, grid, and line-weight scale. Export settings can make a correct canvas misleading, so inspect the actual deliverable rather than only the app view.

For each required format:

1. Export the entire approved drawing revision.
2. Confirm project, date, revision, north or orientation, units, benchmark basis, contour interval, legend, and exclusions are visible.
3. Measure a known horizontal check distance in the receiving workflow.
4. Compare several labeled elevation points with the field log.
5. Verify contour labels, color legend, line weights, and photos remain readable at the intended page size.
6. Open DWG or DXF in the downstream CAD tool when that format is part of the handoff; confirm geometry, units, and required layers.
7. Record file name, checksum or controlled version, exporter, reviewer, and acceptance result.

Give the crew a frozen, approved PDF for field reference and retain the editable source separately. Do not let an unlabeled screenshot become the construction drawing. The commercial landscape site-audit workflow explains why photos, observations, corrective issues, and export acceptance need distinct records even when they appear on one plan.

When must the ArcSite workflow stop?

Stop treating the drawing as a contractor-only field aid when any of these conditions applies:

• a legal boundary, easement, setback, or ownership conclusion is required;
• a permit or authority requires a sealed or certified plan;
• a retaining wall, slope stability, structural interface, or life-safety issue depends on elevation;
• drainage design or discharge affects buildings, roads, utilities, regulated systems, or another property;
• the required horizontal or vertical accuracy has not been defined and demonstrated;
• the benchmark, datum, coordinate basis, instrument performance, or field closure cannot be established;
• inaccessible terrain, vegetation, water, snow, underground features, or obstructions conceal critical conditions;
• the drawing would be used for construction layout or as-built acceptance without the responsible professional’s approval; or
• the exported file loses the control, units, features, or metadata required by the downstream user.

The next step may be a licensed land surveyor, landscape architect, civil engineer, utility locator, geotechnical professional, or local authority, depending on the question and jurisdiction. ArcSite can remain part of the communication and takeoff workflow, but it should not be used to imply a professional certification that was never provided.

What is the final acceptance checklist?

An ArcSite topographic drawing is ready for its stated landscaping use only when:

• its purpose and limits are written;
• the canvas passes an independent dimension check;
• horizontal and vertical units are explicit;
• the reference is physically recoverable and its basis is stated;
• every critical point has provenance;
• opening, repeat, independent, and closing checks meet a predeclared tolerance;
• highs, lows, grade breaks, drainage features, obstacles, and exclusions were reviewed in the field;
• manual grade checks agree with the accepted points;
• contours and heatmap were reviewed as generated output, not raw evidence;
• estimate quantities preserve their formulas and assumptions;
• exported PDF and CAD files pass dimension, unit, label, layer, and revision checks; and
• a named reviewer confirms that no survey-grade stop rule was crossed.

The value of ArcSite’s topographic feature is speed and clarity: entered elevations become an understandable surface while the estimator is working on the site. The control has to come from the workflow around it. Keep the raw readings, prove the reference, test the surface, and stop where the project’s risk demands professional survey or design evidence.