Request - Add min and max depth to flat

[happiah-madson]

Help us understand your request (check below):

• search or data request (help with SQL or provide the specific fields you are trying to retrieve for your collection)
• add a new Github user to the Arctos Users team
• a new barcode series
• a new term for data entry or management
• a change or new report or label
• update to an Agent (split, merge, or other type of change)
• bulkload changes (to Agents, Identifiers, etc that are not already available as a bulkloading tool)
• new feature or otherwise a good idea to make Arctos even better
• quarantine taxon name and suggested replacement (please supply links)
• other

Describe what you're trying to do

Per #8524, I am seeking to add some fields to flat. Elevation fields are part of flat, but depth fields are not. Would it be possible to add locality_min_depth and locality_max_depth and locality_depth_units? I actually don't need all 3, I just want the min and max depths and then the units can be there, too? IDK what happens magically in the background.

@dustymc @mkoo

[dustymc]

I think this needs significant additional clarification.

I actually don't need all 3

The concatenation is in flat

arctosprod@arctos>> select json_locality[0] ->'depth' from flat where guid='DMNS:Inv:26912';
     ?column?     
------------------
 "19000-19000 ft"

It's not clear to me if that's sufficient for the user (can we ask them?), or if they need to be some other structure (or what that might be - is this request implicitly for the 'best' locality only, or ?? ), or ????????

locality_min_depth and locality_max_depth and locality_depth_units

None of those exist in this context.

[mkoo]

I think what's being said here is that already exists @happiah-madson
HOWEVER it is not available in the options in the customized Results (as far as I can see-- currently JSON wrapped in Locality). So I think the request is to have depth as an option for viewing and seeing in the summarize results etc etc

[dustymc]

currently JSON wrapped in Locality

yes

depth as an option for viewing and seeing

That's technically plausible as long as the need is the depth from the (one) 'selected' locality, but I'll need details. Costs could be:

1. However many columns this involves will not be available for later expansion (we're currently using ~15% of the capacity)
2. Some processing (minimal since we're already pulling data from the relevant table)
3. Some storage (I think little impact)

[happiah-madson]

I think this needs significant additional clarification.

My apologies, I should have used many different words.

HOWEVER it is not available in the options in the customized Results (as far as I can see-- currently JSON wrapped in Locality). So I think the request is to have depth as an option for viewing and seeing in the summarize results etc etc

Yes, this is exactly what I was trying to communicate, but did so very poorly.

That's technically plausible as long as the need is the depth from the (one) 'selected' locality

Yes. I assume that's the same way that it is done for elevation? As a user, I would assume this would work the same way.

[happiah-madson]

Ha! I found a better way to ask my question, I think:

Can filtered_flat.min_depth_in_m and filtered_flat.max_depth_in_m be added to the search result via the customize profile bit?

[sharpphyl]

Yes, it would be very helpful to have the Depth option available in the customize options (especially Results) the same way Elevation can be selected.