I tried adding datasetKey and the message gone away but still no result ...

Thinking a little more about this i wonder if this has something to do with being unable to query using complex polygons on the interactive map. The same services are used? In which case we should still be able to do a bounding box...

accidentally put in the incorrect wkt and getting error below. Could this just be timeout issue some where?

org.springframework.jdbc.BadSqlGrammarException:
### Error querying database.  Cause: com.microsoft.sqlserver.jdbc.SQLServerException: A .NET Framework error occurred during execution of user-defined routine or aggregate "geometry":
System.FormatException: 24111: The well-known text (WKT) input is not valid.
System.FormatException:
   at Microsoft.SqlServer.Types.WellKnownTextReader.Read(OpenGisType type, Int32 srid)
   at Microsoft.SqlServer.Types.SqlGeometry.GeometryFromText(OpenGisType type, SqlChars text, Int32 srid)
.
### The error may exist in uk/org/nbn/nbnv/api/dao/warehouse/TaxonObservationMapper.java (best guess)
### The error may involve uk.org.nbn.nbnv.api.dao.warehouse.TaxonObservationMapper.selectObservationsByFilterOrderedByDataset-Inline
### The error occurred while setting parameters
### SQL: SELECT obs.*, obs.id AS observationID, f.label AS location, f.resolutionID, r.label AS resolution, si.providerKey AS siteKey, si.name AS siteName, pt.name AS pTaxonName, pt.authority AS pTaxonAuthority, rr.name AS recorder, rd.name AS determiner FROM (SELECT o.*, 1 AS fullVersion FROM TaxonObservationDataEnhanced o INNER JOIN UserTaxonObservationID utoa ON utoa.observationID = o.id  INNER JOIN FeatureData ftd ON ftd.id = o.featureID WHERE ((utoa.userID = ?) AND ftd.geom.STIntersects(geometry::STGeomFromText(?, 4326)) = 1 AND ftd.geom.STTouches(geometry::STGeomFromText(?, 4326)) = 0 AND sensitive = 0) UNION ALL SELECT o.*, 0 AS fullVersion FROM TaxonObservationDataPublic o INNER JOIN FeatureData ftd ON ftd.id = o.featureID WHERE (o.id NOT IN ( SELECT utoa.observationID FROM UserTaxonObservationID utoa WHERE utoa.userID = ?) AND ftd.geom.STIntersects(geometry::STGeomFromText(?, 4326)) = 1 AND ftd.geom.STTouches(geometry::STGeomFromText(?, 4326)) = 0 AND sensitive = 0)) obs INNER JOIN FeatureData f ON f.id = obs.featureID INNER JOIN Resolution r ON r.id = f.resolutionID INNER JOIN TaxonData pt ON pt.taxonVersionKey = obs.pTaxonVersionKey LEFT OUTER JOIN SiteData si ON si.id = obs.siteID LEFT OUTER JOIN RecorderData rr ON rr.id = obs.recorderID LEFT OUTER JOIN RecorderData rd ON rd.id = obs.determinerID ORDER BY obs.datasetKey
### Cause: com.microsoft.sqlserver.jdbc.SQLServerException: A .NET Framework error occurred during execution of user-defined routine or aggregate "geometry":
System.FormatException: 24111: The well-known text (WKT) input is not valid.
System.FormatException:
   at Microsoft.SqlServer.Types.WellKnownTextReader.Read(OpenGisType type, Int32 srid)
   at Microsoft.SqlServer.Types.SqlGeometry.GeometryFromText(OpenGisType type, SqlChars text, Int32 srid)
.
; bad SQL grammar []; nested exception is com.microsoft.sqlserver.jdbc.SQLServerException: A .NET Framework error occurred during execution of user-defined routine or aggregate "geometry":
System.FormatException: 24111: The well-known text (WKT) input is not valid.
System.FormatException:
   at Microsoft.SqlServer.Types.WellKnownTextReader.Read(OpenGisType type, Int32 srid)
   at Microsoft.SqlServer.Types.SqlGeometry.GeometryFromText(OpenGisType type, SqlChars text, Int32 srid)

Thanks Ben, both old and new service seem to have all gone down. More testing tomorrow I think!

Hi Matt,
Thank you for your reply.

Just to clarify, does this mean that those of us that need to query the gateway using a user defined polygon (e.g. point and buffer or site with buffer) can no longer do so under the new service?

Would it not be possible to test the polygon area before performing the query and so restrict polygons over a certain size?

Ben

Ok cheers Matt.

Sorry, from Paula's email I assumed I wouldn't be getting a reply until next year so I hadn't checked!

I hadn't realised I'd reversed the lat-long - I converted it from the Easting/Northing and hadn't thought which way around the coordinates should go.

Thanks for clarifying the issue with polygons. I'll have to think about how best to extract the data we need then - our searches (and most people's I imagine) are generally a circular buffer around a point, so don't easily fit a grid square search.

Cheers,

Tim

No, that's not a problem, except for the maximum 10,000 character length of the URL string and the number of points in a large circle - I've written a search program in .NET that uses SQL Server 2008 spatial queries, and can easily create a WKT string from there (particularly now I've got the lat/long the right way around!).

The problem is that another filter (dataset, species group etc.) has to be specified as well, and we want to download everything so I can apply our own species categories at this end.

Tim

One quick question, before I get lost somewhere else, what would be a viable maximum area size that you could work with, I may have to reduce the maximum size for performance reasons, but I would like to get some feedback of the sort of areas you are considering using so I can see if it causes any issues or not.

Thanks,
Matt

Just a note that a simple bounding box datasets query is very slow or not working at all.

https://data.nbn.org.uk/api/taxonObserv … on=POLYGON ((-2.676420445063187 53.378815657299505, -2.6192334599467686 53.379125980347332, -2.619755819813232 53.415094098408538, -2.6769910369200143 53.414783370617975, -2.676420445063187 53.378815657299505))

In case anyone needs it this javascript will produce a rough WGS84 circular polygon from OS easting, northing, radius in metres and the number of points to form the circle.

<script type="text/javascript" src="http://www.bnhs.co.uk/focuson/grabagridref/html/BNHS_coords.js"></script>

<script type="text/javascript">
function CircularPolygon(centre_x, centre_y, radius, points) 
  {
  var step  = 360 / points; // note that 360 must be exactly divisible by points!
  var angle = 0;
  var polygon = "POLYGON((";
  for (var i=0; i<=points; i++) // the first point must be calculated twice to close the polygon
    {
    var x = parseInt(centre_x) + Math.round(Math.cos(angle * (Math.PI/180)) * radius);
    var y = parseInt(centre_y) + Math.round(Math.sin(angle * (Math.PI/180)) * radius);

    var os = new OSRef(x,y);
    var latlng = os.toLatLng(os);
    latlng.OSGB36ToWGS84();

    polygon = polygon + latlng.lng + "%20" + latlng.lat;
    if (i < points)
      {
      polygon = polygon + ",";
      }
    angle = angle + step;
    }
  polygon = polygon + "))";
  return polygon;
  }
</script>

// Useage:
var polygon = CircularPolygon(512350, 245650, 1000, 12); // A 12-sided circle with radius 1km centred on TL123456

Keith