Industry field guide
Land survey control points and datum metadata for AI
Two coordinate tables can share point names while using different datums, units or epochs.
- 2022 NAICS
- 541370
- Practice pack
- Example and answer key (JSON)
- Updated
What this guide tests
Which records support a same-basis comparison, and can A-to-B differences be interpreted as movement from the shared name and units?
See the specimen and fields · Work through the fictional records
Task and source context
Two coordinate tables can share point names while using different datums, units or epochs. NOAA’s National Geodetic Survey explains datum concepts. A survey practice can make a fictional comparison that tests metadata handling and prevents unsupported merges. NOAA National Geodetic Survey datums
Create two abstract control tables with similarly named points. Give one a declared coordinate basis and leave it ambiguous on the other. Ask which pair can be compared and what information is needed for the remainder. Include an independent reviewer key for identity, datum, units and coordinate precision.
Use fictitious geometry and labels. Leave boundary claims, client maps, real coordinates and critical infrastructure out. Preserve the stated source and metadata in every exported exercise.
Industry research
The U.S. Census Bureau’s industry definitions establish which activities these codes cover. The workflow sources in this guide describe the task or record type. Fiund’s pilot below uses fictional material to test a specific decision within that scope.
541370 · Surveying and Mapping (except Geophysical) Services
This industry comprises establishments primarily engaged in performing surveying and mapping services of the surface of the earth, including the sea floor. These services may include surveying and mapping of areas above or below the surface of the earth, such as the creation of view easements or segregating rights in parcels of land by creating underground utility easements.
Build a pilot sample
Set up this pilot
Use synthetic survey points with the same name and units under different datums or epochs. Grade compatible comparison only after an explicit source and transform check.
Prepare the test packets
- Start with the worked case. Use the fictional record types below as a guide to the source files you need. Give each packet a stable ID and save its source versions with it.
- Change one fact. Make one packet with enough evidence to answer the question and one where the evidence points to a different answer. Keep the other fields fixed so a reviewer can tell what changed.
- Remove the decisive evidence. Give the reviewer a third packet with a plausible near-match in its place. Have them write what can still be established and what evidence would resolve the rest.
Fields the reviewer needs
- Point identity and source link
- Defines whether two rows describe the same control.
- Datum, units and epoch
- Preserves the reference basis.
- Stated precision
- Limits interpretations of small differences.
Use Build an AI evaluation from professional work to turn the specimen into a brief with a defined task, source and review owner.
Fictional exercise
A shared point name does not establish a shared coordinate basis
Abstract invented control tables use no real coordinates or boundary information. The exercise checks identity and metadata rather than performing a survey transformation.
| Record ID | Source | What it records |
|---|---|---|
| LSC1 | Practice table A | Point P1 coordinates 10,20; basis D-A, units U, epoch E1, stated precision one unit. |
| LSC2 | Practice table B | P1 coordinates 11,21; datum and epoch unspecified, units U. No identity cross-reference beyond the short name. |
| LSC3 | Compatible check table | Point P1 explicitly linked to table A under D-A/U/E1; coordinates 10,20 at the same stated precision. |
Question for the model. Which records support a same-basis comparison, and can A-to-B differences be interpreted as movement from the shared name and units?
Show the reference answer
LSC1 and LSC3 explicitly share point identity, D-A basis, U units, E1 epoch and stated precision, supporting their documented same-basis comparison. LSC2 omits datum, epoch and a verified point link. Its one-unit coordinate differences do not establish physical movement or a valid transformation. Preserve all coordinate metadata and request the missing basis before merging or interpreting the tables.
How to check the result
Ask for the answer, the record IDs that support it and any fact the evidence leaves unresolved. Have a reviewer compare the response against the reference before deciding whether the sample is ready to expand.
Errors to flag in this case
- Joining coordinate tables on short point names alone.
- Calling a coordinate difference movement when datum, epoch or identity is unknown.
Change the inputs and run it again
Provide B's datum but a different epoch and no transformation. Require the model to resolve one metadata field without declaring full comparability.
Score the decision and the evidence separately
Save the reviewer’s expected answer, supporting record IDs and unresolved fields in a separate answer key. Score the model on the decision, its citations and its handling of the deliberate gap. A correct answer citing a different case counts as an evidence error.
Before expanding collection, have a second reviewer run the same checks on the held-out packet. Keep related versions, views and exports of the same case together so they stay on one side of the training and evaluation split.
Check permission and scope
Use fictional geometry and labels. Exclude boundaries, client maps, actual coordinates and infrastructure.
Use original or licensed practice material. Leave client work product, confidentiality obligations and regulated outcomes out of the sample.
Describe an authorized archive through Fiund’s existing-data assessment, or describe a new capture capability through the collection brief. The contributor agreement covers the terms for participation.
Sources and further reading
Resources for this workflow
Company and program reviews
Use these reviews to compare sourcing, capture or evaluation approaches. Confirm the applicable program, accepted sources and terms with the provider.
Compare the approach
Invisible Technologies review for expert-led AI training
Compare expert calibration and reviewer agreement before commissioning a professional-work evaluation.
Compare the approach
Mercor review for expert AI training work
Read how an individual expert role differs from licensing an employer or client’s work product.
Related industry examples
Industry guide · NAICS 541360
Geophysical survey line and seismic trace metadata for AI
A profile image may look complete while its export leaves out traces or records them under a different timing convention.
Industry guide · NAICS 541340
Drafting markup and drawing dimension revision data for AI
Drafting services often receive a markup, revise a source drawing and issue a new copy.
Industry guide · NAICS 541690
Energy consulting measurement baseline and comparison data for AI
Technical energy consultants compare measurements across periods with different operating conditions.