Multiple samples per field point in MX Deposit

NimbusInsights
NimbusInsights Posts: 3 Calcite Rank Badge
in MX Deposit

Is there any way to configure MX Deposit to allow more than one sample associated with the same field point?

If this is not supported natively, how is this situation commonly handled in practice?
What are the recommended workflows or best practices to manage multiple samples collected at a single field location?

Any guidance or examples from real projects would be greatly appreciated.

Best Answer

  • DavidKerr1
    DavidKerr1 Posts: 3 Diamond Rank Badge
    Answer ✓

    Yes, you can configure MX Deposit to allow multiple samples for the same point/header. In fact, if you are currently limited to just one sample row in the sample table - then somebody has explicitly configured it that way. In the activity configuration, you can expand the sample table (or any table) and there is an option called "limit entry to single row". If this option is enabled, then you will only be allowed to enter a single row (or sample) in that table. If you disable this option, it will let you add multiple rows (or samples) in that table.

    The trick with point data is the coordinates. The coordinates are captured in the header, which then enables all the coordinate validation and transformation options. So in your case, are you looking to capture different XYZ values for each sample in the same table? Or will the XYZ live in the header, and the sample table has just sample IDs? We have seen customers add their own XYZ columns in sample tables, which works fine - but you won't be able to transform those coordinates on export. You would just need to make sure that what you capture in the table is in the coordinate system that you are always working in.

    Would be good to understand if these ideas/solutions work for you, or if there's anything you think would work better here. We have tossed around the idea of having a sort of special "coordinate" table that has built-in northing/easting/elevation/CRS columns that would also make use of the coordinate transformation features on export. That would let you capture different XYZ values for different samples in the same table, then the point header could just be some logical grouping of samples.

    Thoughts?

Answers

  • NimbusInsights
    NimbusInsights Posts: 3 Calcite Rank Badge

    Thanks David, this is very helpful and clarifies the configuration and underlying logic very well.

    In our case, the objective is to associate multiple samples with a single logical field point, with all samples sharing the same XYZ captured at the point/header level. Based on your explanation, disabling the “limit entry to single row” option in the sample table is exactly what we were looking for.

    Thanks again for the detailed explanation and for sharing best-practice considerations.

  • DavidKerr1
    DavidKerr1 Posts: 3 Diamond Rank Badge

    Great, that should work just fine. Now when you export these point samples, you can also include the header fields for each sample row in the export file. Then these shared XYZ values will repeat for each row, and any other header field you might want to include. To achieve this - on the general export dialog there's a "Include header fields with table data" option that will union the header fields with the sample rows. Otherwise the export template lets you set this up as well.

Categories