These tools are used to identify areas that meet a number of different criteria you specify.
find_similar_locations finds locations most similar to one or more reference locations based on criteria you specify.
detect_incidents(track_fields, start_condition_expression, end_condition_expression=None, output_mode='AllFeatures', output_name=None, gis=None)¶
The Detect Incidents task works with a time-enabled layer of points, lines, areas, or tables that represents an instant in time. Using sequentially ordered features, called tracks, this tool determines which features are incidents of interest. Incidents are determined by conditions that you specify. First, the tool determines which features belong to a track using one or more fields. Using the time at each feature, the tracks are ordered sequentially and the incident condition is applied. Features that meet the starting incident condition are marked as an incident. You can optionally apply an ending incident condition; when the end condition is true, the feature is no longer an incident. The results will be returned with the original features with new columns representing the incident name and indicate which feature meets the incident condition. You can return all original features, only the features that are incidents, or all of the features within tracks where at least one incident occurred.
For example, suppose you have GPS measurements of hurricanes every 10 minutes. Each GPS measurement records the hurricane’s name, location, time of recording, and wind speed. Using these fields, you could create an incident where any measurement with a wind speed greater than 208 km/h is an incident titled Catastrophic. By not setting an end condition, the incident would end if the feature no longer meets the start condition (wind speed slows down to less than 208).
Using another example, suppose you were monitoring concentrations of a chemical in your local water supply using a field called contanimateLevel. You know that the recommended levels are less than 0.01 mg/L, and dangerous levels are above 0.03 mg/L. To detect incidents, where a value above 0.03mg/L is an incident, and remains an incident until contamination levels are back to normal, you create an incident using a start condition of contanimateLevel > 0.03 and an end condition of contanimateLevel < 0.01. This will mark any sequence where values exceed 0.03mg/L until they return to a value less than 0.01.
Argument Description input_layer required FeatureSet, The table, point, line or polygon features containing potential incidents. track_fields required string, The fields used to identify distinct tracks. There can be multiple track_fields. start_condition_expression The condition used to identify incidents. If there is no endConditionExpression specified, any feature that meets this condition is an incident. If there is an end condition, any feature that meets the start_condition_expression and does not meet the end_condition_expression is an incident. The expressions are Arcade expressions. end_condition_expression The condition used to identify incidents. If there is no endConditionExpression specified, any feature that meets this condition is an incident. If there is an end condition, any feature that meets the start_condition_expression and does not meet the end_condition_expression is an incident. This is an Arcade expression. output_mode
optional string, default value is AllFeatures. Determines which features are returned. Two modes are available:
- AllFeatures - All of the input features are returned.
- Incidents - Only features that were found to be incidents are returned.
output_name optional string, The task will create a feature service of the results. You define the name of the service. gis optional GIS, the GIS on which this tool runs. If not specified, the active GIS is used. Returns: Output feature layer item
find_similar_locations(search_layer, analysis_fields, most_or_least_similar: str = 'MostSimilar', match_method: str = 'AttributeValues', number_of_results: int = 10, append_fields: str = None, output_name: str = None, gis=None)¶
Based on criteria you specify, find similar locations by measuring the similarity of locations in your candidate search layer to one or more reference locations.
- Find the ten most similar stores by examining the number of employees and the annual sales.
- Find the 100 most similar cities by examining the relationship between population, annual growth, and tax revenue.
input_layer: Input Layer (feature layer). Required parameter.
search_layer: Search Layer (feature layer). Required parameter.
analysis_fields: Analysis Fields (str). Required parameter.
- most_or_least_similar: Most Or Least Similar (str). Required parameter.
- Choice list:[‘MostSimilar’, ‘LeastSimilar’, ‘Both’]
- match_method: Match Method (str). Required parameter.
- Choice list:[‘AttributeValues’, ‘AttributeProfiles’]
number_of_results: Number Of Results (int). Required parameter.
append_fields: Fields To Append To Output (str). Optional parameter.
output_name: Output Features Name (str). Required parameter.
gis: Optional, the GIS on which this tool runs. If not specified, the active GIS is used.
- output - Output feature layer Item
geocode_locations(country=None, category=None, include_attributes=True, locator_parameters=None, output_name=None, geocode_service=None, geocode_parameters=None, gis=None)¶
The Geocode Locations task geocodes a table from a big data file share. The task uses a geocode utility service configured with your portal.
For more information on setting up a geocoding service see: http://server.arcgis.com/en/portal/latest/administer/windows/configure-portal-to-geocode-addresses.htm
Argument Description input_layer required Layer, URL, Item of address locations to geocode. country optional string. If all your data is in one country, this helps improve performance for locators that accept that variable. category optional string. Enter a category for more precise geocoding results, if applicable. Some geocoding services do not support category, and the available options depend on your geocode service. include_attributes optional boolean. A boolean value to return the output fields from the geocoding service in the results. locator_parameters optional dictionary. Additional parameters specific to your locator. output_name optional string, The task will create a feature service of the results. You define the name of the service. geocode_service optional string or Geocoder. URL endpoint of the Geocoding Service of GeoCoder object. If none is provided, the service will use the first geocoder registered with portal that has batch enabled. geocode_parameters
optional dictionary. This includes parameters that help parse the input data, as well the field lengths and a field mapping. This value is the output from the AnalyzeGeocodeInput tool available on your server designated to geocode. It is important to inspect the field mapping closely and adjust them accordingly before submitting your job, otherwise your geocoding results may not be accurate. It is recommended to use the output from AnalyzeGeocodeInput and modify the field mapping instead of constructing this JSON by hand.
field_info - A list of triples with the field names of your input data, the field type (usually TEXT), and the allowed length (usually 255). Example: [[‘ObjectID’, ‘TEXT’, 255], [‘Address’, ‘TEXT’, 255],[‘Region’, ‘TEXT’, 255], [‘Postal’, ‘TEXT’, 255]]
header_row_exists - Enter true or false.
column_names - Submit the column names of your data if your data does not have a header row.
field_mapping - Field mapping between each input field and candidate fields on the geocoding service. Example: [[‘ObjectID’, ‘OBJECTID’], [‘Address’, ‘Address’],[‘Region’, ‘Region’], [‘Postal’, ‘Postal’]]
gis optional GIS, the GIS on which this tool runs. If not specified, the active GIS is used. Returns: Feature Layer