Cristina Mullin

@hillarymarler I tried running TADA_DepthProfilePlot with the surfacevalue and bottomvalue null which currently produces as error message. Recommendation: update this so that when these inputs are null, the function returns...

@hillarymarler I noticed that the new columns generated by some of the depth functions are appended to the end of the dataframe (TADA.ConsolidatedDpeth.Bottom, TADA.DepthCategory.Flag, TADA.DepthProfileAggregation.Flag & there may be more)....

@hillarymarler I like your idea for addressing the pie chart colors: "adding some additional colors to the palette in TADA_ColorPalette and then only using color ramp if a really large...

Recommendations for figure/map colors: - The orange outline for sites in the TADA_OverviewMap is a bit faint/hard to see. Should we use the same dark blue outline for the sites...

I like what you have now (consistent with the default used to the categories) but null would work too. From: hillarymarler ***@***.***> Sent: Thursday, May 23, 2024 3:23 PM To:...

Update: Default behavior: Suggest to rename the TADA_FindNearbySites column that is generated as TADA_MonitoringLocationID in preparation for Module 2. This new column should be used in mods 2 and 3....

On our 5/23/24 call we decided to use the json array to concatenate the monitoringlocationID's to be consistent with the way the WQX 3.0 profiles will be serving 1-to-manys in...

@renaemyers all other topics related to this issue are now addressed elsewhere. This issue can be closed once your edits to TADA_FindNearbySites are merged, with the concatenation format you already...

@renaemyers The current TADA.NearbySiteGroups column is being replaced by a new different column TADA_MonitoringLocationID in this issue. Whenever we change existing functions in the TADA package, we need to review...

We need to be cautious about removal of outliers in environmental datasets. This would only provide an option to review and remove data that are different than approximately 99% of...