1 Reply by Ian M Spence

  • Ian M Spence
  • Veteran
  • Offline
  • From: North east Wales
  • Registered: 30-06-2006
  • Posts: 193

Re: Import wizard not recognising location names

Hi

I have experienced a problem that I cannot find a way round. I have set up a new R6 database (v 6.13.2.176) and entered location names and centroid grid refs for 1826 tetrads for a North Wales Breeding Bird Atlas project. The names follow the pattern:

Location = SJ12A, Grid ref = SJ1121

I have entered no further information, eg about county as tetrads are rather large to assign, always, to just one county. I can find no advice in Recorder Help about the issue.

When I have an import file in Excel with the locations and grid refs as above, I come to the screen for the matching of locations and no locations are matched at all. In the past I have laboured through the file and selected the correct location and selected it with f9, but am not prepared to do that with a test file with all 1826 tetrads in it! On one test, I ticked the box labelled 'Place any remaining unmatched locations into the location name' and the file has been imported successfully. When I check the Observations after import, the location is as expected (eg SJ12A) and the grid ref is correct. However, on using the Report Wizard the Event Location field comes out blank (which is not helpful).

I have checked the format of the field in Excel (general or text), the format of the location name in the Location field in the import file and can find no way to get the Import Wizard location screen to come up with matches. Why? What do I need to do to ensure that they do show on import?

If a location is shown in the Observations, why is not reported under Event Location by the Report Wizard?

I don't know what else to try but am frustrated that the answer is probably very simple.

The same problem has occurred once with a data file for importing for my other bird recorder database. Again, I was unable to find out why the problem arose with this one file, but used the select with f9 to fill all the gaps on that occasion. There has to be an issue I need to check and deal with but cannot think what it may be.

Does anyone recognise this problem? Can you direct me to a solution?

I look forward to hearing from you!

Cheers, Ian

2 Reply by Syrphus

  • Syrphus
  • Veteran
  • Offline
  • From: Strathpeffer, Highland
  • Registered: 16-12-2008
  • Posts: 535

Re: Import wizard not recognising location names

Ian -

I  think if you export the Event Location Name (not Event Location) you should see what you want.

Murdo

Syrphus's Website

3 Reply by Ian M Spence

  • Ian M Spence
  • Veteran
  • Offline
  • From: North east Wales
  • Registered: 30-06-2006
  • Posts: 193

Re: Import wizard not recognising location names

Hi Murdo

Thanks for your suggestion. I have tried it and found that Event Location Name produces nil entries in a report, whereas Event Location provides what I need, now, the tetrad reference (eg SH54G).

On importing data today I have had several files where the import has worked properly and at the Location screen, the grid refs and tetrad names being matched. However, I had two files where most of the 'matched' locations were blank. I have found that ticking the little box at the top of the screen does not then put the location names in the correct field and after import I had to alter them manually. Consequently, it is better to do the drill down to the location page to do the match manually on import. The two files that caused the difficulty were put together in exactly the same way as the others and all the location data were added in the same way.

I don't understand this vagary of R6...

Cheers, Ian

4 Reply by SimonWood

  • SimonWood
  • Veteran
  • Offline
  • Registered: 09-09-2008
  • Posts: 63

Re: Import wizard not recognising location names

Hi Ian,

The Location matching screen is a bit more complex than some of the other matching screens. Basically locations in your import file are not automatically matched to Recorder locations based purely on name, instead they also ensure that the imported grid reference is within 2 km of the Recorder location’s spatial reference. 

Cheers,

Simon Wood
[url=http://www.dorsetsoftware.com/]Dorset Software Services[/url]

SimonWood's Website