I am also now having a similar problem with this at a smaller scale.

I have now received a similar error message for a site with only 4 grid squares. It allowed me to enter ST 9800 and ST9801, but gives an error message if I try to add ST9700 or ST9701. I had previously added all 4 squares (among others) to the parent site successfully.

Exception occurred in application Recorder 6 at 21/02/2008 11:52:16.
Version : 6.10.4.120

Exception path:
ESpatialRefSystemConversionError : The spatial reference system cannot be recognised.

Last event\actions: 
  actObservations invoked
  TfrmObservations created
  TfrmLocations deactivated
  TfrmObservations activated
  TfrmSurveyDetails created
  TfrmSurveyDetails destroyed
  TfrmSurveyDetails created
  TfrmObservations deactivated
  TfrmLocations activated

Operating System : Windows XP  5.01.2600  Service Pack 2
Physical Memory available : 1,039,724 KB

DLLs loaded:
  advapi32.dll (5.1.2600.2180)
  comctl32.dll (5.82.2900.2180)
  comdlg32.dll (6.0.2900.2180)
  gdi32.dll (5.1.2600.2180)
  HHCtrl.ocx (5.2.3790.1194)
  kernel32.dll (5.1.2600.2180)
  mpr.dll (5.1.2600.2180)
  MS5.Dll (5.0.0.12)
  MS5User.Dll (5.0.0.4)
  odbc32.dll (3.525.1117.0)
  ole32.dll (5.1.2600.2180)
  oleaut32.dll (5.1.2600.2180)
  shell32.dll (6.0.2900.2180)
  user32.dll (5.1.2600.2180)
  version.dll (5.1.2600.2180)
  winmm.dll (5.1.2600.2180)
  winspool.drv (5.1.2600.2180)

Information has been saved to the file Q:\LastError.txt

Hi Gordon

Just a very quick response to say that I haven't missed this post and I will look into this further when I can.

Best wishes,

Thanks Sarah

Looking at this again, it appears that now I cannot make any changes to some of these large locations, if I click Edit and then Save without making any changes then I get the same spatial reference error, but it does not stop me from adding grid squares to locations that only have 2 squares to start with. Would it help to send you an export of the database?

(Currently running on MSDE across a network, operating as System Manager)

Gordon

Hi Gordon,

Sorry, but Sarah did not get round to reporting this issue. However I've just tried this in version 6.13 and I can't reproduce either of the problems. There were lots of fixes and general improvements in version 6.13 so it is possible that it was fixed anyway. When you get round to the update, would it be possible for you to double check if the problem still exists please?

Kind Regards

John,

just to expand on yesterday's quick reply, I now think that the problem is slightly different from how I initially reported it, and I have possibly found other problems since in trying workarounds.

1) The original problem was to do with adding 1k grid squares to large locations under the Geo Info - Grid Squares tab, and apparently hitting a maximum limit to the number that could be added 'manually'. As large numbers of squares can now be added by associating a polygon and extracting squares, I haven't checked this again in 6.13 so it may no longer be a problem.

2) Another problem appears to be that a sub-site cannot be saved if any of its grid squares do not appear within the first 10 squares listed for the parent site. This also appears to be true if there are no grid squares associated, but the grid reference for the location is not in the first ten squares. (It may also be the case that a site can not be edited if its own grid reference is not within the first ten, but I have only noticed this today and will need to check the circumstances for this further.) Still happening in 6.13. Extracting grid squares via the map screen avoids this problem initially, but renders the location uneditable.

3) There may also be some problems with the function for associating polygons and extracting grid squares. Again I probably need to do some further investigation to pin it down. Extracting grid squares from within the Location - Geo Info - Grid Squares tab seems to work where the associated polygon is simple, e.g. where the polygon is already a series of contiguous grid squares joined into a single block, but when the polygon is complex, directly imported from GIS, it only adds a handful of squares.  Running the extract squares from the map screen seems to work for any polygon, but causes problems if you have two polygons you want to associate. The second extraction appears to cause a failure if there is an overlap between the grid squares of the two polygons. I will find a suitable candidate site to check this on again as I managed to fix it on the first site I had this problem but cant remember how.

Apart from this 6.13 seems to be going pretty well, and the fixes for previous problems seem to have worked, but that only seems to give me more time to find new ones :)

Gordon

I am also getting the same problems for data entry and editing. Either for editing an existing record to its correct location or adding a new record I am getting the Spatial Conversion Error if the grid reference is not within the first few grid squares in the list. Hopefully there will not be many records that will need to be associated with a location of over 10 sq km rather than within sub-sites, but it appears to be related.

Gordon

Hi Lynn,

Do you know if this was fixed in the current update?

Gordon

No worries. Thanks for letting us know

G

Just for the pot.

We had a recurring problem where we had more than one entry for the same grid square in a location.
This came about either through miskeying or merges of locations (where grid squares are just added together - and not rationalised).
Whenever any editing of the location occurred, the error would jump up and not allow any saving, until the duplicate square had been removed.

I think this is still a problem - but only when we try and edit one of these rogue locations.

M

Matt/Lynn

I have been able to create duplicates but only as a result of a merge between 2 locations that have the same gridsquare. This was certainly the case in  R2002, and I think it still happens in 6. It is also possible to get duplicates of other Geo Info items in the same way - I remember a similar topic on the forum but am not sure if it was in relation to land parcel or boundary.

It appears that the merge tool simply adds these items to the list of those associated with a location without doing any checking for duplicates, so the error is only noticed when you attempt to edit and save the location. Can't say it was often a major problem to locate the duplicated squares, although this is another case where it would be useful to be able to sort the list of grid squares alphabetically if you needed to check a location with large numbers of squares. I haven't found any other problems that follow from the duplication of squares.

Gordon

These problems don't go away however long we keep them out of mind.

I was doing a bit of innocent tidying up of locations - merging duplicates etc, etc.

I start to receive the 'Unknown spatialRef system error' and the focus jumps to the grid squares tab.
Hummmm?

Looking at the Grid_Squares table I find a load of spatial_ref_system values empty on the locations I have been editing.
More hummmm?

I dig further, and summarise:

I have this location which has 13 grid squares associated, and two names. All GRID_SQUARE.SPATIAL_REF_SYSTEM values are set at OSGB.

I edit the location - make a change to one of the names and save. FINE.
I edit again and try to save - get the spatialrefsystem error.

I check the GRID_SQUARE table - three values have had the spatial_ref_system values removed - the last three values of the location I have been editing.
I reset them, and I can edit again - once, before the error starts again.

i.e. the act of editing resets the grid square values - but only sets the first ten as OSGB, any more than that get theirs removed. Without the OSGB value - the Spatialrefsystem error appears.

So the ten value grid square thing as identified by Gordon is very much there. I cant confirm the sub site thing.

M