1 Topic by ser

  • ser
  • ser
  • Administrator
  • Offline
  • From: Staffordshire Ecological Recor
  • Registered: 24-09-2008
  • Posts: 603

Topic: Import error message

I am currently trying to run an import of records from a TXT file and at the final report I received the following error:

ESpatialRefSystemConversionError: The spatial reference system cannot be recognised.

The offending grid reference is SJ9046, which is not only valid, but also correct for the site - I cannot find any hidden characters or leading/trailing spaces.

What is the explanation for this error and how can I circumvent it

Craig

Craig Slawson
Staffordshire Ecological Record

ser's Website

2 Reply by MikeWeideli

  • MikeWeideli
  • Administrator
  • Offline
  • From: Littlefield Consultancy
  • Registered: 05-07-2006
  • Posts: 2,645

Re: Import error message

You should be abke to edit the field when it is dispayed in the import wizard. Try deleting the grid ref and replacing  it. Also check other fields as the message maybe spurious.

Mike Weideli

MikeWeideli's Website

3 Reply by ser

  • ser
  • ser
  • Administrator
  • Offline
  • From: Staffordshire Ecological Recor
  • Registered: 24-09-2008
  • Posts: 603

Re: Import error message

Mike,

I have just tried the import again and retyped the offending grid references in the Import window, but Recorder still threw them out with the same error - I cannot see any data in other fields which could cause problems!

I have just tried importing into our other copy of Recorder and they went straight in! Both copied of Recorder share the same executables, the only difference is the settings in the Registry of the workstations to point to different copies of NBNData, so it looks as if the problem must be in NBNData!

Craig

Craig Slawson
Staffordshire Ecological Record

ser's Website

4 Reply by ser

  • ser
  • ser
  • Administrator
  • Offline
  • From: Staffordshire Ecological Recor
  • Registered: 24-09-2008
  • Posts: 603

Re: Import error message

Mike,

I have discovered where the faulty grid reference is - it is in the Site entry in the Locations table, presumably one of the valid squares grid refs - I've checked the original copy of Recorder where the site originates from and it is wrong there as well, which doesn't explain why I was able to import the records into the other copy of Recorder! There was no obvious problem with any of these grid references, but deleting them all cured the problem of not being able to save the site record which also generated the same error which was appearing in the import

Craig

Craig Slawson
Staffordshire Ecological Record

ser's Website

5 Reply by ser

  • ser
  • ser
  • Administrator
  • Offline
  • From: Staffordshire Ecological Recor
  • Registered: 24-09-2008
  • Posts: 603

Re: Import error message

Mike,

I've discovered the problem, don't know how widespread it is in the system, but checking the GRID_SQUARE table in SQLServer, I found two of the grid refs for the problem site had no SPATIAL_REF_SYSTEM entry - adding 'OSGB' to this field cured the problem.

These two entries in GRID_SQUARE also had a much more precise ENTRY_DATE and CHANGED_DATE to 1/1000 of a second, all the other entries were precise to the second - the entries originate from the original import of data by Sally

Craig

Craig Slawson
Staffordshire Ecological Record

ser's Website

6 Reply by MikeWeideli

  • MikeWeideli
  • Administrator
  • Offline
  • From: Littlefield Consultancy
  • Registered: 05-07-2006
  • Posts: 2,645

Re: Import error message

Makes sense. The error is occurring when  R6 attempts to check that the imported  record is in the grid square. Was it a R3 to R6 data transfer ?  I suspect we would have trusted the R3 output. as far as the Spatial Ref Type field is concerned.   

Reports Sy06 and SY 07 in System Supplied Reports/Problem Identification should identify blank Spatial Ref Type in Grid squares.

Mike Weideli

MikeWeideli's Website

7 Reply by ser

  • ser
  • ser
  • Administrator
  • Offline
  • From: Staffordshire Ecological Recor
  • Registered: 24-09-2008
  • Posts: 603

Re: Import error message

I've already populated the empty field via SQL Server, there were 7 problem grid ref and all originated in the Rec3 to Rec6 transfer

Craig

Craig Slawson
Staffordshire Ecological Record

ser's Website