{"_id":"geofilter","_rev":"26-66119bffd1cb07fe202169e53c121867","name":"geofilter","description":"Simple Geospatial filter language designed for readable urls","dist-tags":{"latest":"0.1.3"},"versions":{"0.1.1":{"name":"geofilter","description":"Simple Geospatial filter language designed for readable urls","author":{"name":"Damon Oehlman","email":"damon.oehlman@sidelab.com"},"tags":["query","match","filter"],"version":"0.1.1","engines":{"node":">= 0.6.x < 0.9.0"},"dependencies":{"formatter":"0.1.x","underscore":"1.3.x"},"devDependencies":{"rigger-collate":"0.3.x","mocha":"1.2.x","expect.js":"0.1.x"},"repository":{"type":"git","url":"git://github.com/DamonOehlman/geofilter.git"},"bugs":{"url":"http://github.com/DamonOehlman/geofilter/issues"},"scripts":{"test":"node_modules/mocha/bin/mocha --reporter spec"},"contributors":[],"optionalDependencies":{},"readme":"# GeoFilter\n\nGeofilter is a simple geospatial filter language that is designed to work well with web applications.  It's primary purpose is to help with creating readable, cacheable urls for geospatial searches but also uses an [internal JSON representation](/DamonOehlman/geofilter/wiki/Internal-Representation) that can be easily translated to other spatial filter types (e.g. [OGC Filter Format](http://www.opengeospatial.org/standards/filter)).\n\n<a href=\"http://travis-ci.org/#!/DamonOehlman/geofilter\"><img src=\"https://secure.travis-ci.org/DamonOehlman/geofilter.png\" alt=\"Build Status\"></a>\n\n## General Syntax\n\nThe general syntax of a geofilter is a forward-slash (`/`) delimited filter string.  The use of the forward slash means that you get readable urls for free.  \n\nFor the most part, geofilter expressions are defined across two sections, with the first section specifying the type of filter to invoke and the second being comma-delimited arguments that will be passed to the filter:\n\n```\nhttp://testgeo.org/search/FILTERTYPE/FILTERARGS\n```\n\nWhen multiple filters are provided, these filters are combined only the __intersection__ of two filters is returned with the results.  For instance, the following request would return the results of filter `TYPE1(ARGS1) AND TYPE2(ARGS2)`.\n\n```\nhttp://testgeo.org/search/TYPE1/ARGS1/TYPE2/ARGS2\n```\n\nAt this stage, no provision for an OR operator is being considered.\n\n## Filter Types\n\nThe following filter types are being investigated / implemented for the initial release of the GeoFilter library.  While some of the filter types do not include a `/P:PROPNAME` specifier (geospatial queries usually), others will usually require this syntax.\n\nThe geofilter initialization step, does include provision for configuring the default properties that will be targeted for both spatial and also a non-spatial filter operation.  The defaults used are `the_geom` for a spatial operation, and `name` for a non-spatial operation.\n\nIn all of the filter operations specified below, you can specify a leading `/P:PROPNAME` url segment to override the default targeted fields.\n\n### BBOX\n\nA bounding box filter.\n\n```\n/BBOX/MINLAT,MINLON,MAXLAT,MAXLON\n```\n\nThe four arguments are all numeric floating point values, and correspond to the latitude and longitude of the bounding box sw-corner and the latitude and longitude of the bounding box ne-corner respectively.\n\n### DWITHIN\n\nA distance within filter.  The distance within filter returns all items that fall within the specified geometry.  The `BUFFERDIST` arg is used to specify the buffer that should be applied to the geometry search.  A 0 buffer indicates the exact geometry will be used, a positive buffer indicates the geometry will be expanded, and a negative buffer indicates the buffer will be shrunk (where possible).\n\n```\n/DWITHIN/GEOMTYPE,BUFFERDIST,GEOMETRY\n```\n\n### EQ - Equals\n\n```\n/EQ/VALUE\n```\n\n### GT - Greater Than\n\n```\n/GT/VALUE\n```\n\n### GTE - Greater Than or Equal To\n\n```\n/GTE/VALUE\n```\n\n### LT - Less Than\n\n```\n/LT/VALUE\n```\n\n### LTE - Less Than or Equal To\n\n```\n/LTE/VALUE\n```\n\n## Limitations\n\nThe Geofilter format is __not__ designed to provide constructs for describing complicated filter operations, and has not provision for providing __OR__ rule (all filters are combined with an __AND__ condition).","_id":"geofilter@0.1.1","dist":{"shasum":"f7ca1743dc4ac9feb792b48c689c647eb78b8fce","tarball":"https://registry.npmjs.org/geofilter/-/geofilter-0.1.1.tgz","integrity":"sha512-eQ0NpUHZAoI02HYrAVXY9erSOQfEnHPcaDjJgjWpAz+ROwvf4z81ao/V6DzEK0TFHYTBWdvx0YAoS/uM50hlow==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCICdFP25q/4hXuWe0exEIf9yvLHnoBlMxro91hOxrVyLSAiEAh9V+ZoiXnb0P+qb9Wm5GKxp0UULdHjKFUjT9gVVyFs0="}]},"maintainers":[{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"}],"directories":{}},"0.1.2":{"name":"geofilter","description":"Simple Geospatial filter language designed for readable urls","author":{"name":"Damon Oehlman","email":"damon.oehlman@sidelab.com"},"tags":["query","match","filter"],"version":"0.1.2","engines":{"node":">= 0.6.x < 0.9.0"},"dependencies":{"formatter":"0.1.x","underscore":"1.3.x"},"devDependencies":{"rigger-collate":"0.3.x","mocha":"1.6.x","expect.js":"0.1.x"},"repository":{"type":"git","url":"git://github.com/DamonOehlman/geofilter.git"},"bugs":{"url":"http://github.com/DamonOehlman/geofilter/issues"},"scripts":{"test":"node_modules/mocha/bin/mocha --reporter spec"},"contributors":[],"optionalDependencies":{},"readme":"# GeoFilter\n\nGeofilter is a simple geospatial filter language that is designed to work well with web applications.  It's primary purpose is to help with creating readable, cacheable urls for geospatial searches but also uses an [internal JSON representation](/DamonOehlman/geofilter/wiki/Internal-Representation) that can be easily translated to other spatial filter types (e.g. [OGC Filter Format](http://www.opengeospatial.org/standards/filter)).\n\n<a href=\"http://travis-ci.org/#!/DamonOehlman/geofilter\"><img src=\"https://secure.travis-ci.org/DamonOehlman/geofilter.png\" alt=\"Build Status\"></a>\n\n## General Syntax\n\nThe general syntax of a geofilter is a forward-slash (`/`) delimited filter string.  The use of the forward slash means that you get readable urls for free.  \n\nFor the most part, geofilter expressions are defined across two sections, with the first section specifying the type of filter to invoke and the second being comma-delimited arguments that will be passed to the filter:\n\n```\nhttp://testgeo.org/search/FILTERTYPE/FILTERARGS\n```\n\nWhen multiple filters are provided, these filters are combined only the __intersection__ of two filters is returned with the results.  For instance, the following request would return the results of filter `TYPE1(ARGS1) AND TYPE2(ARGS2)`.\n\n```\nhttp://testgeo.org/search/TYPE1/ARGS1/TYPE2/ARGS2\n```\n\nAt this stage, no provision for an OR operator is being considered.\n\n## Filter Types\n\nThe following filter types are being investigated / implemented for the initial release of the GeoFilter library.  While some of the filter types do not include a `/P:PROPNAME` specifier (geospatial queries usually), others will usually require this syntax.\n\nThe geofilter initialization step, does include provision for configuring the default properties that will be targeted for both spatial and also a non-spatial filter operation.  The defaults used are `the_geom` for a spatial operation, and `name` for a non-spatial operation.\n\nIn all of the filter operations specified below, you can specify a leading `/P:PROPNAME` url segment to override the default targeted fields.\n\n### BBOX\n\nA bounding box filter.\n\n```\n/BBOX/MINLAT,MINLON,MAXLAT,MAXLON\n```\n\nThe four arguments are all numeric floating point values, and correspond to the latitude and longitude of the bounding box sw-corner and the latitude and longitude of the bounding box ne-corner respectively.\n\n### DWITHIN\n\nA distance within filter.  The distance within filter returns all items that fall within the specified geometry.  The `BUFFERDIST` arg is used to specify the buffer that should be applied to the geometry search.  A 0 buffer indicates the exact geometry will be used, a positive buffer indicates the geometry will be expanded, and a negative buffer indicates the buffer will be shrunk (where possible).\n\n```\n/DWITHIN/GEOMTYPE,BUFFERDIST,GEOMETRY\n```\n\n### EQ - Equals\n\n```\n/EQ/VALUE\n```\n\n### GT - Greater Than\n\n```\n/GT/VALUE\n```\n\n### GTE - Greater Than or Equal To\n\n```\n/GTE/VALUE\n```\n\n### LT - Less Than\n\n```\n/LT/VALUE\n```\n\n### LTE - Less Than or Equal To\n\n```\n/LTE/VALUE\n```\n\n## Limitations\n\nThe Geofilter format is __not__ designed to provide constructs for describing complicated filter operations, and has not provision for providing __OR__ rule (all filters are combined with an __AND__ condition).","_id":"geofilter@0.1.2","dist":{"shasum":"2b9086dbe6e983cd2dd4390427c3f72d052a4db0","tarball":"https://registry.npmjs.org/geofilter/-/geofilter-0.1.2.tgz","integrity":"sha512-rt71UUIDzzOkLLunBfvJOEdJ/8I5nfn8vRHWDWGCN+vHvjfUlGlxKgIERXkdr495zq7MMfb4gQeaqpTZW7/k8A==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDwnfj3vbTGEbICpLcAJr7ccUaN/yLdfusYkLd7H0224gIhAKiLWgwLEIaP6ljni8AwPrmguzsRwEB4tans6jB8sitt"}]},"_npmVersion":"1.1.62","_npmUser":{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"},"maintainers":[{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"}]},"0.1.3":{"name":"geofilter","description":"Simple Geospatial filter language designed for readable urls","author":{"name":"Damon Oehlman","email":"damon.oehlman@sidelab.com"},"tags":["query","match","filter"],"version":"0.1.3","engines":{"node":">= 0.6.x < 0.9.0"},"dependencies":{"formatter":"0.1.x","underscore":"1.4.x"},"devDependencies":{"rigger-collate":"0.3.x","mocha":"1.9.x","expect.js":"0.1.x"},"repository":{"type":"git","url":"git://github.com/DamonOehlman/geofilter.git"},"bugs":{"url":"http://github.com/DamonOehlman/geofilter/issues"},"scripts":{"test":"node_modules/mocha/bin/mocha --reporter spec"},"contributors":[],"optionalDependencies":{},"readme":"# GeoFilter\n\nGeofilter is a simple geospatial filter language that is designed to work well with web applications.  It's primary purpose is to help with creating readable, cacheable urls for geospatial searches but also uses an [internal JSON representation](/DamonOehlman/geofilter/wiki/Internal-Representation) that can be easily translated to other spatial filter types (e.g. [OGC Filter Format](http://www.opengeospatial.org/standards/filter)).\n\n<a href=\"http://travis-ci.org/#!/DamonOehlman/geofilter\"><img src=\"https://secure.travis-ci.org/DamonOehlman/geofilter.png\" alt=\"Build Status\"></a>\n\n## General Syntax\n\nThe general syntax of a geofilter is a forward-slash (`/`) delimited filter string.  The use of the forward slash means that you get readable urls for free.  \n\nFor the most part, geofilter expressions are defined across two sections, with the first section specifying the type of filter to invoke and the second being comma-delimited arguments that will be passed to the filter:\n\n```\nhttp://testgeo.org/search/FILTERTYPE/FILTERARGS\n```\n\nWhen multiple filters are provided, these filters are combined only the __intersection__ of two filters is returned with the results.  For instance, the following request would return the results of filter `TYPE1(ARGS1) AND TYPE2(ARGS2)`.\n\n```\nhttp://testgeo.org/search/TYPE1/ARGS1/TYPE2/ARGS2\n```\n\nAt this stage, no provision for an OR operator is being considered.\n\n## Filter Types\n\nThe following filter types are being investigated / implemented for the initial release of the GeoFilter library.  While some of the filter types do not include a `/P:PROPNAME` specifier (geospatial queries usually), others will usually require this syntax.\n\nThe geofilter initialization step, does include provision for configuring the default properties that will be targeted for both spatial and also a non-spatial filter operation.  The defaults used are `the_geom` for a spatial operation, and `name` for a non-spatial operation.\n\nIn all of the filter operations specified below, you can specify a leading `/P:PROPNAME` url segment to override the default targeted fields.\n\n### BBOX\n\nA bounding box filter.\n\n```\n/BBOX/MINLAT,MINLON,MAXLAT,MAXLON\n```\n\nThe four arguments are all numeric floating point values, and correspond to the latitude and longitude of the bounding box sw-corner and the latitude and longitude of the bounding box ne-corner respectively.\n\n### DWITHIN\n\nA distance within filter.  The distance within filter returns all items that fall within the specified geometry.  The `BUFFERDIST` arg is used to specify the buffer that should be applied to the geometry search.  A 0 buffer indicates the exact geometry will be used, a positive buffer indicates the geometry will be expanded, and a negative buffer indicates the buffer will be shrunk (where possible).\n\n```\n/DWITHIN/GEOMTYPE,BUFFERDIST,GEOMETRY\n```\n\n### EQ - Equals\n\n```\n/EQ/VALUE\n```\n\n### GT - Greater Than\n\n```\n/GT/VALUE\n```\n\n### GTE - Greater Than or Equal To\n\n```\n/GTE/VALUE\n```\n\n### LT - Less Than\n\n```\n/LT/VALUE\n```\n\n### LTE - Less Than or Equal To\n\n```\n/LTE/VALUE\n```\n\n## Limitations\n\nThe Geofilter format is __not__ designed to provide constructs for describing complicated filter operations, and has not provision for providing __OR__ rule (all filters are combined with an __AND__ condition).","readmeFilename":"README.md","_id":"geofilter@0.1.3","dist":{"shasum":"6ef7ee5141183ce49170f4f5d637254e5847405d","tarball":"https://registry.npmjs.org/geofilter/-/geofilter-0.1.3.tgz","integrity":"sha512-QcBG/JdB79o6NZl+deGgX7csOcXJfp18gSxLhjpZy/nEf/7QQka61izjW1WL5tfx/ST01/9r/ylboArYKsF0Aw==","signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEQCIEgrcXe2QcQE2U1YV4KSTjifC3M6d2murv7WtIQGlh5aAiAFOjdi5r148qsbnqz9ZRbB086wLcyN49XJXPe+GSjpBw=="}]},"_from":".","_npmVersion":"1.2.18","_npmUser":{"name":"damonoehlman","email":"damon.oehlman@gmail.com"},"maintainers":[{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"}]}},"readme":"# GeoFilter\n\nGeofilter is a simple geospatial filter language that is designed to work well with web applications.  It's primary purpose is to help with creating readable, cacheable urls for geospatial searches but also uses an [internal JSON representation](/DamonOehlman/geofilter/wiki/Internal-Representation) that can be easily translated to other spatial filter types (e.g. [OGC Filter Format](http://www.opengeospatial.org/standards/filter)).\n\n## General Syntax\n\nThe general syntax of a geofilter is a forward-slash (`/`) delimited filter string.  The use of the forward slash means that you get readable urls for free.  \n\nFor the most part, geofilter expressions are defined across two sections, with the first section specifying the type of filter to invoke and the second being comma-delimited arguments that will be passed to the filter:\n\n```\nhttp://testgeo.org/search/FILTERTYPE/FILTERARGS\n```\n\nWhen multiple filters are provided, these filters are combined only the __intersection__ of two filters is returned with the results.  For instance, the following request would return the results of filter `TYPE1(ARGS1) AND TYPE2(ARGS2)`.\n\n```\nhttp://testgeo.org/search/TYPE1/ARGS1/TYPE2/ARGS2\n```\n\nAt this stage, no provision for an OR operator is being considered.\n\n## Filter Types\n\nThe following filter types are being investigated / implemented for the initial release of the GeoFilter library.  While some of the filter types do not include a `/P:PROPNAME` specifier (geospatial queries usually), others will usually require this syntax.\n\nThe geofilter initialization step, does include provision for configuring the default properties that will be targeted for both spatial and also a non-spatial filter operation.  The defaults used are `the_geom` for a spatial operation, and `name` for a non-spatial operation.\n\nIn all of the filter operations specified below, you can specify a leading `/P:PROPNAME` url segment to override the default targeted fields.\n\n### BBOX\n\nA bounding box filter.\n\n```\n/BBOX/MINLAT,MINLON,MAXLAT,MAXLON\n```\n\nThe four arguments are all numeric floating point values, and correspond to the latitude and longitude of the bounding box sw-corner and the latitude and longitude of the bounding box ne-corner respectively.\n\n### DWITHIN\n\nA distance within filter.  The distance within filter returns all items that fall within the specified geometry.  The `BUFFERDIST` arg is used to specify the buffer that should be applied to the geometry search.  A 0 buffer indicates the exact geometry will be used, a positive buffer indicates the geometry will be expanded, and a negative buffer indicates the buffer will be shrunk (where possible).\n\n```\n/DWITHIN/GEOMTYPE,BUFFERDIST,GEOMETRY\n```\n\n### EQ - Equals\n\n```\n/EQ/VALUE\n```\n\n### GT - Greater Than\n\n```\n/GT/VALUE\n```\n\n### GTE - Greater Than or Equal To\n\n```\n/GTE/VALUE\n```\n\n### LT - Less Than\n\n```\n/LT/VALUE\n```\n\n### LTE - Less Than or Equal To\n\n```\n/LTE/VALUE\n```\n\n## Limitations\n\nThe Geofilter format is __not__ designed to provide constructs for describing complicated filter operations, and has not provision for providing __OR__ rule (all filters are combined with an __AND__ condition).","maintainers":[{"name":"damonoehlman","email":"damon.oehlman@sidelab.com"}],"time":{"modified":"2022-06-18T07:35:37.433Z","created":"2012-07-02T08:16:20.830Z","0.0.0":"2012-07-02T08:16:26.655Z","0.0.1":"2012-07-03T05:16:03.272Z","0.0.2":"2012-07-05T04:00:30.679Z","0.1.0":"2012-07-25T08:55:02.292Z","0.1.1":"2012-07-25T10:02:00.775Z","0.1.2":"2012-10-30T02:20:14.575Z","0.1.3":"2013-06-19T02:49:11.778Z"},"author":{"name":"Damon Oehlman","email":"damon.oehlman@sidelab.com"},"repository":{"type":"git","url":"git://github.com/DamonOehlman/geofilter.git"},"users":{"fgribreau":true}}