From 8666c9b52e28aa5b47db13bfa3d57965df971a9d Mon Sep 17 00:00:00 2001 From: Stephen K Hess Date: Mon, 28 Sep 2015 13:50:49 -0400 Subject: [PATCH] Update 004-place.md removed unnecessary word --- getting-started/004-place.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/getting-started/004-place.md b/getting-started/004-place.md index c06fe81..e8c0dd1 100644 --- a/getting-started/004-place.md +++ b/getting-started/004-place.md @@ -28,7 +28,7 @@ The results are returned in the order requested. ***From Rhonda -- is there another example where you might do multiple requests at the same time...in other words, more related locations?*** -Keep in mind that if you enter a `source:layer:id` combination that cannot be found, then the `features` array in the response contains a different number of elements than the number of requests. This will be most noticeable in requests with multiple IDs, as your request may have three IDs requested but only two results returned. The reason for this is that the `features` section of the response is GeoJSON-compliant and there is currently no way to convey an exception condition (not even an empty JSON element, `{}`). For this reason, if your application is dependent upon the results mapping directly to the individual input requests in order, then you'll have to do your own bookkeeping to handle with exception conditions. +Keep in mind that if you enter a `source:layer:id` combination that cannot be found, then the `features` array in the response contains a different number of elements than the number of requests. This will be most noticeable in requests with multiple IDs, as your request may have three IDs requested but only two results returned. The reason for this is that the `features` section of the response is GeoJSON-compliant and there is currently no way to convey an exception condition (not even an empty JSON element, `{}`). For this reason, if your application is dependent upon the results mapping directly to the individual input requests in order, then you'll have to do your own bookkeeping to handle exception conditions. ## Valid combinations of place searches