{ "name": "LSDBQuerybyAttribute", "displayName": "LSDB Query by Attribute", "description": "The LSDB Query Tool allows users to query data into summary statistics based upon the developed Kansas Biological Survey\u2019s (KBS) nested hexagon framework (NHF) and the Landscape Summary Database (LSDB). The LSDB database contains summaries of data layers of interest to state agencies, private companies, NGO\u2019s, and the public, and is an additive compilation of data layers associated with landscapes, wildlife, energy, weather/climate, and socio-economic data. See the associated LDSB Query Tool Summary for more information.", "category": "", "helpUrl": "https://services.kars.geoplatform.ku.edu/arcgis/rest/directories/arcgisoutput/LSDB_GP_Query_Tools/TempExampleAGOLTool_GPServer/LSDB_GP_Query_Tools_TempExampleAGOLTool/LSDBQuerybyAttribute.htm", "executionType": "esriExecutionTypeAsynchronous", "parameters": [ { "name": "Geographic_Scale", "dataType": "GPString", "displayName": "Geographic Scale", "description": "The geographic scale references the KBS\u2019s NHF, which consists of hexagons nested within each other. The selected option will be the geographic output layer of this tool. The selectable options (from largest to smallest) includes:Hexagon = 1 squared kilometerCog = 7 squared kilometersWheel = 49 squared kilometersRing = 343 squared kilometers", "direction": "esriGPParameterDirectionInput", "defaultValue": "ring", "parameterType": "esriGPParameterTypeRequired", "category": "", "choiceList": [ "ring", "wheel", "cog", "hexagon" ] }, { "name": "First_Selection_Statement", "dataType": "GPString", "displayName": "First Selection Statement", "description": "The selection statement (based on the SQL where clause) will query the NHF and LDSB dataset and produce an NHF and LDSB sub-datasets. Only results that match the SQL query will be created as outputs.The selection statement should follow this format \u201cDataset: [LSDB Table] | Query: [SQL Where Clause].\u201d The dataset is the LSDB table to query from, and the SQL Where Clause is the query that will be applied to the dataset. Below is an example. Example: Dataset: Landscape and Habitat | Query: description = Percent Water AND number >1 AND number < 10The selectable tables and queryable attribute fields can be found in the associated LDSB Query Tool Summary document. The SQL Where Clause supports the \u201cOR\u201d and \u201cAND\u201d conjunctions, though both cannot be used in the same selection statement. Additionally, the SQL Where Clauses supports the following operators [=, >, <, >=, <=, !=, LIKE, NOT LIKE, IS, IS NOT].Any invalid selection statements such as referencing tables that do not exist, attribute fields not apart available in the referenced tables, or selection statements not following proper format will generate an error in the tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": "Dataset: Landscape and Habitat | Query: description = Percent Water AND number >1 AND number < 10", "parameterType": "esriGPParameterTypeRequired", "category": "" }, { "name": "invert_First_Selection", "dataType": "GPBoolean", "displayName": "invert First Selection", "description": "If turned on, this Boolean will invert the associated selection statement. In other words, the data that does not meet the query requirements will be the output of this tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": null, "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "Second_Selection_Statement", "dataType": "GPString", "displayName": "Second Selection Statement", "description": "The selection statement (based on the SQL where clause) will query the NHF and LDSB dataset and produce an NHF and LDSB sub-datasets. Only results that match the SQL query will be created as outputs.The selection statement should follow this format \u201cDataset: [LSDB Table] | Query: [SQL Where Clause].\u201d The dataset is the LSDB table to query from, and the SQL Where Clause is the query that will be applied to the dataset. Below is an example. Example: Dataset: Landscape and Habitat | Query: description = Percent Water AND number >1 AND number < 10The selectable tables and queryable attribute fields can be found in the associated LDSB Query Tool Summary document. The SQL Where Clause supports the \u201cOR\u201d and \u201cAND\u201d conjunctions, though both cannot be used in the same selection statement. Additionally, the SQL Where Clauses supports the following operators [=, >, <, >=, <=, !=, LIKE, NOT LIKE, IS, IS NOT].Any invalid selection statements such as referencing tables that do not exist, attribute fields not apart available in the referenced tables, or selection statements not following proper format will generate an error in the tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": "", "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "invert_Second_Selection", "dataType": "GPBoolean", "displayName": "invert Second Selection", "description": "If turned on, this Boolean will invert the associated selection statement. In other words, the data that does not meet the query requirements will be the output of this tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": null, "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "Third_Selection_Statement", "dataType": "GPString", "displayName": "Third Selection Statement", "description": "The selection statement (based on the SQL where clause) will query the NHF and LDSB dataset and produce an NHF and LDSB sub-datasets. Only results that match the SQL query will be created as outputs.The selection statement should follow this format \u201cDataset: [LSDB Table] | Query: [SQL Where Clause].\u201d The dataset is the LSDB table to query from, and the SQL Where Clause is the query that will be applied to the dataset. Below is an example. Example: Dataset: Landscape and Habitat | Query: description = Percent Water AND number >1 AND number < 10The selectable tables and queryable attribute fields can be found in the associated LDSB Query Tool Summary document. The SQL Where Clause supports the \u201cOR\u201d and \u201cAND\u201d conjunctions, though both cannot be used in the same selection statement. Additionally, the SQL Where Clauses supports the following operators [=, >, <, >=, <=, !=, LIKE, NOT LIKE, IS, IS NOT].Any invalid selection statements such as referencing tables that do not exist, attribute fields not apart available in the referenced tables, or selection statements not following proper format will generate an error in the tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": "", "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "invert_Third_Selection", "dataType": "GPBoolean", "displayName": "invert Third Selection", "description": "If turned on, this Boolean will invert the associated selection statement. In other words, the data that does not meet the query requirements will be the output of this tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": null, "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "Fourth_Selection_Statement", "dataType": "GPString", "displayName": "Fourth Selection Statement", "description": "The selection statement (based on the SQL where clause) will query the NHF and LDSB dataset and produce an NHF and LDSB sub-datasets. Only results that match the SQL query will be created as outputs.The selection statement should follow this format \u201cDataset: [LSDB Table] | Query: [SQL Where Clause].\u201d The dataset is the LSDB table to query from, and the SQL Where Clause is the query that will be applied to the dataset. Below is an example. Example: Dataset: Landscape and Habitat | Query: description = Percent Water AND number >1 AND number < 10The selectable tables and queryable attribute fields can be found in the associated LDSB Query Tool Summary document. The SQL Where Clause supports the \u201cOR\u201d and \u201cAND\u201d conjunctions, though both cannot be used in the same selection statement. Additionally, the SQL Where Clauses supports the following operators [=, >, <, >=, <=, !=, LIKE, NOT LIKE, IS, IS NOT].Any invalid selection statements such as referencing tables that do not exist, attribute fields not apart available in the referenced tables, or selection statements not following proper format will generate an error in the tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": "", "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "invert_Fourth_Selection", "dataType": "GPBoolean", "displayName": "invert Fourth Selection", "description": "If turned on, this Boolean will invert the associated selection statement. In other words, the data that does not meet the query requirements will be the output of this tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": null, "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "Fifth_Selection_Statement", "dataType": "GPString", "displayName": "Fifth Selection Statement", "description": "The selection statement (based on the SQL where clause) will query the NHF and LDSB dataset and produce an NHF and LDSB sub-datasets. Only results that match the SQL query will be created as outputs.The selection statement should follow this format \u201cDataset: [LSDB Table] | Query: [SQL Where Clause].\u201d The dataset is the LSDB table to query from, and the SQL Where Clause is the query that will be applied to the dataset. Below is an example. Example: Dataset: Landscape and Habitat | Query: description = Percent Water AND number >1 AND number < 10The selectable tables and queryable attribute fields can be found in the associated LDSB Query Tool Summary document. The SQL Where Clause supports the \u201cOR\u201d and \u201cAND\u201d conjunctions, though both cannot be used in the same selection statement. Additionally, the SQL Where Clauses supports the following operators [=, >, <, >=, <=, !=, LIKE, NOT LIKE, IS, IS NOT].Any invalid selection statements such as referencing tables that do not exist, attribute fields not apart available in the referenced tables, or selection statements not following proper format will generate an error in the tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": "", "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "invert_Fifth_Selection", "dataType": "GPBoolean", "displayName": "invert Fifth Selection", "description": "If turned on, this Boolean will invert the associated selection statement. In other words, the data that does not meet the query requirements will be the output of this tool.", "direction": "esriGPParameterDirectionInput", "defaultValue": null, "parameterType": "esriGPParameterTypeOptional", "category": "" }, { "name": "Output_Geographic_Layer", "dataType": "GPFeatureRecordSetLayer", "displayName": "Output Geographic Layer", "description": "A temporary output geographic layer. The output geographic file will be saved into the output ZIP file.", "direction": "esriGPParameterDirectionOutput", "defaultValue": { "displayFieldName": "", "geometryType": "esriGeometryPolygon", "spatialReference": { "wkid": 102100, "latestWkid": 3857 }, "fields": [ { "name": "FID", "type": "esriFieldTypeOID", "alias": "FID" }, { "name": "grid_id", "type": "esriFieldTypeString", "alias": "grid_id", "length": 254 }, { "name": "ring_id", "type": "esriFieldTypeString", "alias": "ring_id", "length": 254 }, { "name": "wheel_id", "type": "esriFieldTypeString", "alias": "wheel_id", "length": 254 }, { "name": "cog_id", "type": "esriFieldTypeString", "alias": "cog_id", "length": 254 }, { "name": "hexagon_id", "type": "esriFieldTypeString", "alias": "hexagon_id", "length": 254 }, { "name": "Shape_Length", "type": "esriFieldTypeDouble", "alias": "Shape_Length" }, { "name": "Shape_Area", "type": "esriFieldTypeDouble", "alias": "Shape_Area" } ], "features": [], "exceededTransferLimit": false }, "parameterType": "esriGPParameterTypeRequired", "category": "" }, { "name": "Output_ZIP_File", "dataType": "GPDataFile", "displayName": "Output ZIP File", "description": "The output ZIP File is the location where the output files will be saved. The files will be automatically formatted based on the geographic scale selected and the selected tables from the selection statements.The geographic layer will be formatted as: \u201cqueried_\u201d + [geographic scale] + [Minute_Hour_Day_Month_Year]Queried Geographic Layer Example: \u201cqueried_ring_11_33_08_03_2022.shp\u201dThe geographic layer will be formatted as: \u201cqueried_\u201d + [Table Name] + [Minute_Hour_Day_Month_Year]Queried Table Example: \u201cqueried_landscape_and_habitat_11_33_08_03_2022.csv\u201d", "direction": "esriGPParameterDirectionOutput", "defaultValue": null, "parameterType": "esriGPParameterTypeRequired", "category": "" } ] }