Display Name: LSDB Query by Attribute
Description: The LSDB Query Tool allows users to query data into summary statistics based upon the developed Kansas Biological Survey’s (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’s, 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:
Help URL: https://services.kars.geoplatform.ku.edu/arcgis/rest/directories/arcgisoutput/LSDB_GP_Query_Tools/LSDBQuerybyAttribute_GPServer/LSDB_GP_Query_Tools_LSDBQuerybyAttribute/LSDBQuerybyAttribute.htm
Execution Type: esriExecutionTypeAsynchronous
Parameters:
Parameter: Geographic_Scale
Data Type: GPString
Display Name Geographic Scale
Description: The geographic scale references the KBS’s 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
Filter:
Dependency:
Default Value: ring
Parameter Type: esriGPParameterTypeRequired
Category:
Choice List: [ ring, wheel, cog, hexagon ]
Parameter: First_Selection_Statement
Data Type: GPString
Display Name 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 “Dataset: [LSDB Table] | Query: [SQL Where Clause].” 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 “OR” and “AND” 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
Filter:
Dependency:
Default Value: Dataset: Landscape and Habitat | Query: description = Percent Water AND number >1 AND number < 10
Parameter Type: esriGPParameterTypeRequired
Category:
Parameter: invert_First_Selection
Data Type: GPBoolean
Display Name 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: Second_Selection_Statement
Data Type: GPString
Display Name 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 “Dataset: [LSDB Table] | Query: [SQL Where Clause].” 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 “OR” and “AND” 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: invert_Second_Selection
Data Type: GPBoolean
Display Name 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: Third_Selection_Statement
Data Type: GPString
Display Name 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 “Dataset: [LSDB Table] | Query: [SQL Where Clause].” 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 “OR” and “AND” 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: invert_Third_Selection
Data Type: GPBoolean
Display Name 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: Fourth_Selection_Statement
Data Type: GPString
Display Name 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 “Dataset: [LSDB Table] | Query: [SQL Where Clause].” 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 “OR” and “AND” 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: invert_Fourth_Selection
Data Type: GPBoolean
Display Name 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: Fifth_Selection_Statement
Data Type: GPString
Display Name 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 “Dataset: [LSDB Table] | Query: [SQL Where Clause].” 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 “OR” and “AND” 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: invert_Fifth_Selection
Data Type: GPBoolean
Display Name 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
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeOptional
Category:
Parameter: Output_Geographic_Layer
Data Type: GPFeatureRecordSetLayer
Display Name Output Geographic Layer
Description: A temporary output geographic layer. The output geographic file will be saved into the output ZIP file.
Direction: esriGPParameterDirectionOutput
Filter:
Dependency:
Default Value:
Geometry Type: esriGeometryPolygon
HasZ: false
HasM: false
Spatial Reference: 102100
(3857)
Fields:
-
FID
(
type: esriFieldTypeOID, alias: FID
)
-
grid_id
(
type: esriFieldTypeString, alias: grid_id, length: 254
)
-
ring_id
(
type: esriFieldTypeString, alias: ring_id, length: 254
)
-
wheel_id
(
type: esriFieldTypeString, alias: wheel_id, length: 254
)
-
cog_id
(
type: esriFieldTypeString, alias: cog_id, length: 254
)
-
hexagon_id
(
type: esriFieldTypeString, alias: hexagon_id, length: 254
)
-
Shape_Length
(
type: esriFieldTypeDouble, alias: Shape_Length
)
-
Shape_Area
(
type: esriFieldTypeDouble, alias: Shape_Area
)
Features: None.
Parameter Type: esriGPParameterTypeRequired
Category:
Parameter: Output_ZIP_File
Data Type: GPDataFile
Display Name 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: “queried_” + [geographic scale] + [Minute_Hour_Day_Month_Year]Queried Geographic Layer Example: “queried_ring_11_33_08_03_2022.shp”The geographic layer will be formatted as: “queried_” + [Table Name] + [Minute_Hour_Day_Month_Year]Queried Table Example: “queried_landscape_and_habitat_11_33_08_03_2022.csv”
Direction: esriGPParameterDirectionOutput
Filter:
Dependency:
Default Value:
Parameter Type: esriGPParameterTypeRequired
Category:
Supported Operations:
Submit Job
Child Resources:
Metadata