POST
|
We ended up buying a new certificate from a different provider due to the urgency of our situation and everything works. The G2 certificate's messed up chaining seems to be the most likely culprit. If we get a chance to test this certificate later on, after installing the crossover cert, we will update this thread with our findings. Thank you for the feedback.
... View more
01-28-2015
02:29 PM
|
0
|
0
|
422
|
POST
|
We have an ArcGIS Server 10.2 on-prem that hosts a variety of services. We recently upgraded our SSL certificate to the more secure SHA-2 version. The CA is Go Daddy Root Certificate Authority - G2. After the update, when we try adding a feature service as an item to AGO, we do not get prompted to save the credentials. We then realized that the call being made to check the service URL was failing with a generic error message: "Error checking resource: ...". Below is a sample call to check a URL prior to adding an ArcGIS service as an item to AGO using one of our services: https://www.arcgis.com/sharing/checkUrl.jsp?url=https%3A//maps.xtremegis.com/arcgis/rest/services/SampleWorldCities/MapS… From our online reading, it seems that the new G2 GoDaddy certificate is not trusted by the Java Truststore. So, it is likely that the AGO services do not trust our services because of this new certificate. We need help determining if this is what is really going on or not? If so, is it possible for the AGO team to make these CA certificates trusted by their servers? Otherwise, we will purchase new certificates. This is a time sensistive client specific matterer so we appreciate any quick response.
... View more
01-26-2015
08:54 AM
|
0
|
3
|
4533
|
POST
|
Heming, Using esri.geometry.isClockwise, we validate and adjust the geometry to be a proper hollow polygon: the outer ring(s) intended to be included are clockwise and the inner rings intended to be excluded are counter clockwise. Sending a polygon with properly oriented rings to the geometry service returned the expected results. Thanks for your help!
... View more
06-11-2012
12:38 PM
|
0
|
0
|
634
|
POST
|
Thanks for the prompt response. Regarding what the geometry service (called using esri.tasks.GeometryService) should return: if passed a single geometry with the proper inner ring orientation (1st input) and an array of geometries (2nd input), the returned result is NOT expected to exclude the points that appear within the hollow area? It would be great if we can get some sample code that returns the proper intersection result instead of excessive validation and proceesing client-side to do the same.
... View more
06-11-2012
10:51 AM
|
0
|
0
|
634
|
POST
|
The idea is simple. Given a hollow polygon as geometry A and an array of point geometries, we would like to figure out the proper intersection between the two. Below is the code used: var geometryService = new esri.tasks.GeometryService("http://tasks.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer"); var relationParams = new esri.tasks.RelationParameters(); relationParams.geometries1 = [hollowPolygonGeom]; relationParams.geometries2 = [point1geom, point2geom, ..., pointXgeom]; relationParams.relation = esri.tasks.RelationParameters.SPATIAL_REL_WITHIN; geometryService.relation(relationParams, onSuccess, onErr); The results returned by the service include the intersection between the "hollow" are of the polygon and the points. We also noticed that the orientation of the inner ring (the hollow shape) affects the returned results. Either way, the results are not what we wanted. Is this behavior expected? What are we missing? Is there another way to get the results we need? Thanks in advance!
... View more
06-11-2012
08:21 AM
|
0
|
4
|
1773
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|