|
The technical forum of the NBN Trust for use by the Network. It includes discussions and announcements on the NBN Atlas, Recorder 6 and Indicia |
You are not logged in. Please login or register.
Forum → Recorder Troubleshooting and Bug Reports → NBN Export Precision Errors
Hello,
I've just sent our next batch of data to the NBN Gateway and they have sent us back a list of 277 records which have an incorrect precision. I've looked at these records in our Recorder 6 database and can't see anything obviously wrong with them. Do you know why this is happening and how it could be fixed? We don't have any access to the back-end of the database unfortunately.
Thanks,
Lizzy
Lizzy
Have you tried running the records through the NBN Record Cleaner to see if the errors also appear there?
Andy
Could be spaces in the Grid Ref, but you should be able to see these. If so then the attached batch update will get rid of them.
Hi,
Is there a way of exporting the record precision (and also start and end dates), as the NBN Gateway team see them, from Recorder 6? Following our latest update we still had a load of errors of various types sent back to us, and Dario at the NBN is (understandably) getting a little frustrated that they keep cropping up. I've tried a few methods of fixing some of the errors, but I can't see any way of finding out if it's actually worked, other than waiting until our next NBN upload and seeing if the errors crop up again.
We are still fighting with our IT department to allow us to have the NBN record cleaner, as presumably that would flag up these errors. But is there a different way for now?
Thanks,
Lizzy
The attached report will do the calculations of Precision and Dates using the same code as the NBN Extract. At the moment I haven't attempted to pick out any specific problems, but If I can have some indications of what the actual problems being encountered are I will adapt the report.
The report needs to be copied into the Reports folder of R6. It will then appear under System Supplied Reports/NBN Checks
Hi Mike,
I ran the NBN Check report and it returned the attributes by Sample Key, whereas the error list returned by the NBN was by Record Key. Could the report be changed to do the same?
We had a number of difference types of errors returned:
EndDate must be the last day of the month, February 1960 specified for a date with DateType OO
EndDate must be the last day of the month, February 1964 specified for a date with DateType OO
EndDate must be the last day of the month, February 1968 specified for a date with DateType OO
EndDate must be the last day of the month, February 1972 specified for a date with DateType OO
EndDate must be the last day of the month, February 1976 specified for a date with DateType OO
EndDate must be the last day of the month, February 1976 specified for a date with DateType OO
EndDate must be the last day of the month, February 1976 specified for a date with DateType OO
EndDate must be the last day of the month, February 2000 specified for a date with DateType OO
EndDate must be the last day of the month, February 2004 specified for a date with DateType OO
EndDate must be the last day of the specified month for a date with DateType O
EndDate must be the last day of the specified year for a date with DateType Y, otherwise the DateType might be YY
EndDate must not be an earlier date than the StartDate
Precision 100 must not be higher than that of the GridReference, Some(TF9429)
Precision 2000 must not be higher than that of the GridReferenceTL99
The same date must be used for both the StartDate and EndDate for a date with DateType D
Thanks,
Lizzy
I attach a new report which will give you the Taxon_Occurrence (Record key). However, the complete report will be very large and not that useful so I have allowed you to input just select a specific key - you can still get the full report by entering a '*' in the box. You will be able to go to the records from the report output by clicking in the Taxon_Occurrence_Key column.
Two things I would point out. Firstly, that the date and precision are coming from the Sample not from the record, so in some cases NBN will be reporting multiple errors for what is just one issue in R6. Secondly, with regard to Feb and year end dates dates. I suspect these have come in from R3.3 or a manual transfer as R6 would use Feb 29 etc. where appropriate. Before the NBN came along no one worried about the last day of Feb in leap years being the being 28th, because R6 treats this correctly.
Similarly, I suspect the precision problems are down to data from the same sources and are caused by there being spaces (or other blank characters) on the end of the grid refs. Precision is simply calculated from the length of the grid ref.
When you correct errors in grid refs or dates I suggest that you delete the entry that is there, key in another slightly different grid ref or date, save this - choosing do nothing at the prompt. Then change the record to what it should be and save it again - this time bringing everything in line. This will ensure that the record is changed.
From other posts I assume you are now using the latest version of NBN Export. Early versions didn't cope properly with Feb 29th.
Thanks Mike, that's really helpful. I'll give your report and suggestions a go when I'm next in the office. And yes, we are on the latest versions of Recorder and the NBN Export.
Your suggestions and the report have worked brilliantly. We should be all OK for the next NBN update. Many thanks!
Forum → Recorder Troubleshooting and Bug Reports → NBN Export Precision Errors
Powered by PunBB 1.4.6, supported by Informer Technologies, Inc.