You can also establish whether User defined value is supported before entering the Service Editor by determining the data type of the tool parameter using any of the following methods: To determine whether a task parameter supports the User defined value input mode you can examine it in the Service Editor and see if the input mode appears as a choice. These data types contain a mixed collection of other datasets-hence their name, containers.Ĭomplex datasets and container datasets are non-transportable and do not support the User defined value input mode.ĭetermining the data type of a tool parameter Container datasets are items such as folders, file and personal geodatabases, and map documents (.These data types are known as complex datasets because they model complex relationships between simple features. Complex datasets are datasets such as geometric networks, network datasets, topologies, TINs, and so on.There are two categories of non-transportable datasets. Non-transportable datasets are anything other than features, rasters, tables, and files.Parameters containing transportable datasets support the User defined value input mode. Transportable datasets are features, rasters, tables, and files.In the context of geoprocessing tasks, GIS datasets can be divided into two distinct categories: transportable and non-transportable. Simple data to a server, such as text, numbers, files, and geographic features and their attributes (fields).
#Arcgis 10.3 field data types how to#
Such simple clients know only how to transport (send and receive) packets of DatasetsĪ GIS service has to work with the simplest of all clients: a web browser running on a computer that does not have any GIS capabilities. The three sections that follow discuss each of these cases in order. Value Table: a special data type that is a multicolumn table of values.Scalar: anything that's not a dataset, such as numbers and strings.Dataset: data stored on disk, such as a feature class, table, folder, map document, database, and so on.There are three categories of data types: The input mode choices you have for a particular parameter depends on the tool's parameter data type. Since the value is constant, the client can't change it, so it will not become a task parameter when the service is published. Constant value: the task will use the value you supplied for the parameter when you created the result.Depending on the data type of the input, the strings in the choice list can be the names of layers or simple keyword options. Choice list: the client is given a list of strings (the choice list) and must choose one or more of the strings from the choice list.User defined value: the client provides a value for the parameter.To review, there are three input mode options, as follows: The purpose of this topic is to help you understand why some input mode options are not available for a parameter and to suggest methods for creating tasks that work with available input mode options. The mode you choose determines how clients will supply a value to the task parameter. When you are publishing your result in the Service Editor, you specify the Input mode for each task parameter. Back to Top Input modes and parameter data types In this topic
0 kommentar(er)
