Latest Contributions by AnttiKajanus1

I assume that you are using UWP with NetCore 5.2.2 which as a bug on the serialization code. This is mentioned in Release notes and you can solve by either using different NetCore version or following workaround. Let me know if this solves your issue. ... View more

Hi, There are multiple ways to implement MVVM design pattern into application so it party depends from that. It comes to down how you want to abstract the View (in this case MapView) from the ViewModel. Discussion on hit testing covers the same problem essentially. You can find the sample code from Xaml is here and C# is here. I will try to write a blog post about this updated to the 100.0.0 in couple of weeks. As mentioned, this is just one way of doing it such as using view services concept or event aggregator. ... View more

The parameters are actually handled through C++ (Map) and we surface that to the API as a IDictionary. It is true that it doesn't ensure that the order is preserved but is there any specific reason why we should have forced the ordering for the parameters? I give you that if you look the json which is send might be a bit confusing if you don't look the parameter names but not sure if there are other reasons that I have missed. In general you shouldn't really be looking the json for anything else than debugging purposes. When parameters are send to the service the parameter order shouldn't matter since they are accessed through the arcPy on the order they are defined in the geoprocessing task that is published to the server. You need to make sure that your geoprocessing task and script has the same order for the parameters. From my testing it doesn't matter if we send the parameters in different order as long the tool and the script is correct. For example I use following simple script and create a tool in ArcMap using the same order of parameters while creating it. import arcpy def get_param(name, index):     param = arcpy.GetParameter(index)     arcpy.AddMessage("Input: " + name + " = " + str(param))     return param def set_param(name, message, index, param):     arcpy.SetParameter(index, param)     arcpy.AddMessage("Output: " + name + " = " + str(param) + " Operation: " + message) i = 0; xMax_ = get_param("InputXMax", i) i += 1 yMax_ = get_param("InputYMax", i) i += 1 xMin_ = get_param("InputXMin", i) i += 1 yMin_ = get_param("InputYMin", i) i += 1 outputParam_ = "YMin = " + str(yMin_) +  ", XMin = " + str(xMin_) + ", YMax = " + str(yMax_) + ", XMax = " + str(xMax_) + "." set_param("OutputExtentAsText", "Extent as a string", i, outputParam_) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Then I publish it as a geoprocessing task to the ArcGIS Server (using 10.41 here). At this point I verified that the JSON definition for the task is correct and the parameters are defined in the same order. I will execute the task using following code var url = @"http://xxxxxxxx/arcgis/rest/services/OrderTest/GPServer/Script"; var task = new GeoprocessingTask(new Uri(url)); var parameters = new GeoprocessingParameters(GeoprocessingExecutionType.AsynchronousSubmit); parameters.Inputs.Add("InputXMax", new GeoprocessingDouble(1)); parameters.Inputs.Add("InputYMax", new GeoprocessingDouble(2)); parameters.Inputs.Add("InputXMin", new GeoprocessingDouble(3)); parameters.Inputs.Add("InputYMin", new GeoprocessingDouble(4)); var job = task.CreateJob(parameters); var results = await job.GetResultAsync(); foreach (var log in job.Messages) {     Debug.WriteLine(log.Message); } Debug.WriteLine("The result is following : "); var outputParameterValue = (results.Outputs.First().Value as GeoprocessingString).Value; Debug.WriteLine(outputParameterValue);‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I get following response which is expected Sending request get result. Received response for get result. Sending request get geoprocessing service info. Received response for get geoprocessing service info. Job succeeded. The result is following : YMin = 4.0, XMin = 3.0, YMax = 2.0, XMax = 1.0.‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ If I change the values in the Inputs collection to another way around parameters.Inputs.Add("InputYMin", new GeoprocessingDouble(4)); parameters.Inputs.Add("InputXMin", new GeoprocessingDouble(3)); parameters.Inputs.Add("InputYMax", new GeoprocessingDouble(2)); parameters.Inputs.Add("InputXMax", new GeoprocessingDouble(1));‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ I get same results as expected Sending request get result. Received response for get result. Sending request get geoprocessing service info. Received response for get geoprocessing service info. Job succeeded. The result is following : YMin = 4.0, XMin = 3.0, YMax = 2.0, XMax = 1.0.‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ If the parameters are not defined in the same order in the geoprocessing task (published to the server) that the script is expecting, the script output might be different that you might expect. I created a new geoprocessing tool in ArcMap from the same script but this time I created parameters in different order. Note that I have changed the order so that X values are together and Y values are together contrast to Max values being together and Min values being together. I run the test with first set of parameters and will get 'wrong' results because the parameters are taken from wrong indexes. Received response for get result. Sending request get geoprocessing service info. Received response for get geoprocessing service info. Job succeeded. The result is following : YMin = 4.0, XMin = 2.0, YMax = 3.0, XMax = 1.0.‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ To fix the script I should change the indexes to correspond the order defined in the geoprocessing task. Edit: Tried to make it more clear where I'm meaning geoprocessing task, which is published to the server, and GeoprocessingTask which is an API class. ... View more