{"action":"created","issue":{"url":"https://api.github.com/repos/Esri/geoservices-js/issues/99","repository_url":"https://api.github.com/repos/Esri/geoservices-js","labels_url":"https://api.github.com/repos/Esri/geoservices-js/issues/99/labels{/name}","comments_url":"https://api.github.com/repos/Esri/geoservices-js/issues/99/comments","events_url":"https://api.github.com/repos/Esri/geoservices-js/issues/99/events","html_url":"https://github.com/Esri/geoservices-js/issues/99","id":149846167,"number":99,"title":"Wish: support filtering geocoding to a bounding box.","user":{"login":"markstos","id":25829,"avatar_url":"https://avatars.githubusercontent.com/u/25829?v=3","gravatar_id":"","url":"https://api.github.com/users/markstos","html_url":"https://github.com/markstos","followers_url":"https://api.github.com/users/markstos/followers","following_url":"https://api.github.com/users/markstos/following{/other_user}","gists_url":"https://api.github.com/users/markstos/gists{/gist_id}","starred_url":"https://api.github.com/users/markstos/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/markstos/subscriptions","organizations_url":"https://api.github.com/users/markstos/orgs","repos_url":"https://api.github.com/users/markstos/repos","events_url":"https://api.github.com/users/markstos/events{/privacy}","received_events_url":"https://api.github.com/users/markstos/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-04-20T18:19:40Z","updated_at":"2016-04-22T06:50:56Z","closed_at":null,"body":"It would be nice if there was an option to specify a bounding box to be used with geocoding, so that results outside the bounding box would be considered geocode failures.\r\n\r\nI read the PDF linked into the docs for the upstream REST geocode API being used. It did not have documented support bounding box restriction built in. \r\n\r\nThis library could perhaps use [coordinatesContainsPoint](http://terraformer.io/core/#comparisons) to check results as they come back. "},"comment":{"url":"https://api.github.com/repos/Esri/geoservices-js/issues/comments/213290691","html_url":"https://github.com/Esri/geoservices-js/issues/99#issuecomment-213290691","issue_url":"https://api.github.com/repos/Esri/geoservices-js/issues/99","id":213290691,"user":{"login":"StephanGeorg","id":7861660,"avatar_url":"https://avatars.githubusercontent.com/u/7861660?v=3","gravatar_id":"","url":"https://api.github.com/users/StephanGeorg","html_url":"https://github.com/StephanGeorg","followers_url":"https://api.github.com/users/StephanGeorg/followers","following_url":"https://api.github.com/users/StephanGeorg/following{/other_user}","gists_url":"https://api.github.com/users/StephanGeorg/gists{/gist_id}","starred_url":"https://api.github.com/users/StephanGeorg/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/StephanGeorg/subscriptions","organizations_url":"https://api.github.com/users/StephanGeorg/orgs","repos_url":"https://api.github.com/users/StephanGeorg/repos","events_url":"https://api.github.com/users/StephanGeorg/events{/privacy}","received_events_url":"https://api.github.com/users/StephanGeorg/received_events","type":"User","site_admin":false},"created_at":"2016-04-22T06:50:56Z","updated_at":"2016-04-22T06:50:56Z","body":"Thanks @jgravois. When I started developing the geocoder-arcgis I wanted a simple and lightweight node.js wrapper **based on promises**. And I wanted to support of all features and optional params. And I think that's the problem of geoservices-js. \r\n\r\nI agree, the documentation of the api is very confusing ;)"}}