|
POST
|
Can you share your service definition in whole? You can send it to my mail akajanus@esri.com.
... View more
02-06-2017
04:51 AM
|
0
|
2
|
7679
|
|
POST
|
Here is a doc to hosted services. Can you have a look into your service and make sure that the your service has `HasAttachements` set to true and you can see `AddAttachement` rest endpoint in the service. You can access the later by investigating existing feature in the service. Here is a example how to access the feature endpoint Are you using hosted feature services or are they published through ArcGIS Server?
... View more
02-06-2017
01:32 AM
|
0
|
1
|
7679
|
|
POST
|
You might need to load the feature to get the information loaded to it before using the feature. var feature = query.First() as ArcGISFeature;
await feature.LoadAsync(); // load feature to get the metadata
if (!feature.CanEditAttachments)
throw new Exception("Cannot edit attachment on this feature");
...more stuff
... View more
02-03-2017
08:27 AM
|
0
|
1
|
7679
|
|
POST
|
I think that your feature service doesn't support editing. Can you verify that the debug message is written and the feature and the FeatureTable has correct values indicating that the edit can be done. var featureTable = new ServiceFeatureTable(new Uri(url));
await featureTable.LoadAsync();
if (!featureTable.IsEditable || !featureTable.HasAttachments)
throw new Exception("Editing attachments not supported");
var query = await featureTable.QueryFeaturesAsync(new QueryParameters() { WhereClause = "1=1" });
var feature = query.First() as ArcGISFeature;
if (!feature.CanEditAttachments)
throw new Exception("Cannot edit attachment on this feature");
var fileBytes = File.ReadAllBytes(@"C:\Temp\P1050951.JPG");
var attachment = await feature.AddAttachmentAsync("test.jpg", @"image/", fileBytes);
... View more
02-03-2017
05:59 AM
|
0
|
3
|
7679
|
|
POST
|
Thanks for reporting this. I can verify that TryGetValue always returns false and I have created issue to fix it.
... View more
02-03-2017
02:12 AM
|
0
|
1
|
4311
|
|
POST
|
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
02-01-2017
03:55 AM
|
0
|
1
|
1379
|
|
POST
|
Here is the link to the guide that covers the topic. Make sure that you use lastest documentation when working with Xamarin.
... View more
01-30-2017
02:47 AM
|
0
|
0
|
932
|
|
POST
|
Also make sure that your feature service is enabled for sync. For example https://services6.arcgis.com/ExtdhXSbhHKK7FFW/ArcGIS/rest/services/SSMH_midvale/FeatureServer/0 doesn't have capability enabled. See documentation how to enable it.
... View more
01-13-2017
07:19 AM
|
0
|
1
|
2476
|
|
POST
|
I would think this issue is not coming from the client side. Have you checked your logs on the server what it says? Make sure that your data is set up following this guidance.
... View more
01-13-2017
07:11 AM
|
0
|
2
|
2476
|
|
POST
|
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
01-12-2017
06:00 AM
|
2
|
1
|
1632
|
|
POST
|
Hi Mark, There is mention about this in the System requirements documentation (weirdly this is not mentioned in local server package support document but I'll add in issue to fix that). ArcGIS Desktop 10.4.1 is required to create content packaged for Local Server 100.0.0. This includes map packages and geoprocessing packages (.mpk and .gpk). If you are creating geoprocessing packages then you will also need to apply this patch to ArcGIS Desktop 10.4.1 I strongly recommend to install the patch mentioned. At the moment we don't support direct read for rasters through Local server but as you mentioned, we should be able to use direct read through Raster layer for that. How are you using TPKs and which kind of custom tiling scheme you are using?
... View more
01-12-2017
05:47 AM
|
0
|
1
|
1408
|
|
POST
|
Glad that you get it working. We are going to make using GP a bit easier in next release where you can create parameters using a factory method and it takes care of using correct execution type and creates all the parameters for you.
... View more
01-11-2017
03:09 AM
|
0
|
0
|
3189
|
|
POST
|
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
01-06-2017
07:05 AM
|
1
|
0
|
3189
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 11-12-2014 03:52 AM | |
| 1 | 08-27-2015 03:47 AM | |
| 1 | 12-08-2014 09:58 AM | |
| 1 | 05-05-2015 10:19 AM | |
| 1 | 07-30-2015 08:43 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|