1

Topic: Import error matching sites

I am just running an import, the first I've done into v6.22.2.273

When I reach the screen for matching up sites, one is already matched, but the 'Recorder Matches' column is displaying the sixteen character GUI for the site (which is correct) - overtyping with the site name to match causes the GUI to reappear but deleting the entry and rematching does display the name of the site. All new matches behave as normal

Craig

Craig Slawson
Staffordshire Ecological Record

2

Re: Import error matching sites

I suspect that  there must be something strange  in   IW Matched Locations. If you can I suggest you have a look in there.

Mike Weideli

3

Re: Import error matching sites

I've come across this issue too. I don't see anything unexpected in IW Matched Locations

4

Re: Import error matching sites

Thanks. Will dig a bit deeper.

Mike Weideli

5

Re: Import error matching sites

Have worked out why this is happening. It can be fixed in the next release, but an immediate fix is possible if you have access to SQL Tools. the attached script needs to be run as a query.

Post's attachments

SQLForLocationMatching.sql 1.62 kb, 21 downloads since 2014-04-07 

You don't have the permssions to download the attachments of this post.
Mike Weideli

6

Re: Import error matching sites

I've noticed another odd thing with the location matching. If there are 7 or 8 grid references amongst the records that apply to the matched site then on the "Location Specification" panel when they are listed in the "Grid Reference" column against the matched site the final grid reference in the list is nearly always "corrupt", or even blank.

Here's a sample of quirky final grid refs from some data that I've just imported.

TL17)
TL1843(OSG)
<Blank>
TL0826(OS)
TL0539()
TL122229(O)
TL1)
T)
TL)

I never saw the problem with 6 gridrefs for a site, and never had a site reported with more than 8 gridrefs (though I don't know if the data contains such).

I think the import is okay, so it may just be a reporting-to-the-screen issue. I hope so because as I just imported 80K records. There were no gridref issues reported during the import step.

Keith

7

Re: Import error matching sites

If it a new problem, then it is probably still in the  matching sql, which I will look at. However, if it is then then I think it is just about what is displayed and will have no effect on the final import.

Mike Weideli