Changes to UKBMS location grid refs not reflected in iRecord outputs

[IanMiddlebrook]

Hi,

Documenting a recent email exchange concerning a problem with grid references in iRecord.

A UKBMS section (Grangelands, section 7) was found to have the wrong grid reference (a historical error). The section was adjusted on the route map website, so that the grid ref was then correctly calculated. This change appeared immediately in any fresh data download from the UKBMS website. However, on iRecord, the records still appear to the county verifier with the previous, erroneous, grid reference.

@DavidRoy has said: "I suspect that the ‘raw’ data is correct in the database but the summary tables (ElasticSearch) we use for the website reports (e.g. verification page) has not updated after the location was updated."

Thanks, Ian

[Gary-van-Breda]

We have to be a bit careful here. When the grid reference was changed on the location, it was not automatically changed on all the walk section samples associated with it (the philosophy behind this may be that if there is a genuine change to the section route and hence the section gridref, you don't want to change the old correct sample gridref - but that may not be how we manage sites, so may be irrelevant). there is no code to do this automatic change. The downloads are taking the grid ref from the location, whilst I suspect the iRecord data is coming from the samples themselves, which have the old grid reference.

As an aside, there also seem to be a whole set of data upload walks which have no grid reference on the sample record.

@DavidRoy @IanMiddlebrook : two questions:

• do you want me to change all the samples for Grangelands, section 7 to use the new grid reference? We can then see if this feeds through to iRecord.
• do we need the section level samples to be automatically updated if the section grid ref changes?

[IanMiddlebrook]

Hi @Gary-van-Breda @DavidRoy

• as far as Grangelands is concerned, we know that the new grid ref is a correction, so we should change all relevant samples if we can.
• in the vast majority of cases, any change to a section grid reference will be the result of a correction - either one that the recorder has spotted, or the result of drawing in the section route, which generates an accurate grid ref different to the original estimate. We don't really allow changes to a section route which would be drastic enough to make the grid ref misleading. So I'd prefer to see samples automatically updated, on the basis that any grid ref changes make them more accurate.

Thanks, Ian

[Gary-van-Breda]

@DavidRoy : are you OK with me adding this functionality? (whenever the grid reference on a section is changed, all the subsamples that reference it will be updated to use the same grid reference).