Hi there,

This post in in reply to an email from 29 Nov 2022 I received about the same issue;

Jono is still reporting double lines on graphs - in this case it is another project - 6088 Ipswich

 I have checked the data and it appears that there are 3 different matrix types being allocated to samples under the provided filter (Water, GW, Trade Waste)

 https://online.ESdat.net/DataView/Graph/Chem_Result#filter=%5B%7B%22Field%22%3A%22Location_ID%22,%22Operator%22%3A%22in%22,%22Value%22%3A%5B17765,17766,17774%5D%7D,%7B%22Field%22%3A%22ChemistryLookup.Code%22,%22Operator%22%3A%22in%22,%22Value%22%3A%5B%227429-90-5%22,%227664-41-7+(as+N)%22,%227440-38-2%22,%22BOD%22,%227440-70-2%22,%22COD%22,%2216887-00-6%22,%227440-47-3%22,%227440-50-8%22,%22EC_Field%22,%227439-89-6%22,%227439-92-1%22,%227439-95-4%22,%227439-96-5%22,%227439-97-6%22,%2214797-55-8(as+N)%22,%22pH_Field%22,%227440-09-7%22,%227440-23-5%22,%2214808-79-8_Turb%22,%22TOC%22,%227440-66-6%22%5D%7D%5D

 Trade waste is allocated to Matrix State of NA.

 Please confirm if this is causing the error or something else.

We’re still encountering this issue as per the message above received from ESdat support. It is occurring for another site on this project too - https://online.ESdat.net/DataView/Graph/Chem_Result#filter=%5B%7B%22Field%22%3A%22Location_ID%22,%22Operator%22%3A%22in%22,%22Value%22%3A%5B17709%5D%7D%5D

 We’ve been generating graphs for this project since 2020 and it only seems to be in the last 6 months we’ve encountered this issue. We have not changed anything in the setup of these sites/locations/project.

Keen for a resolution on this issue. Thanks.

Hi Claire, I was aware that it was the matrix types causing the issue. As an aside, I don't understand why the graph would show different matrix types as diffent lines when they are both for the same location name (i.e., a groundwater well location is only ever going to be the GW matrix type)

I want to reiterate that we’ve been generating graphs for this project since 2020 and it only seems to be in the last 6 months we’ve encountered this issue. We have not changed anything in the setup of these sites/locations/project.

Has there been an ESdat update in this time that may have resulted in this change occuring?

To go back and now manually change matrix types in historical data we inherited will be incredibly time consuming.

Thanks.