|
POST
|
I see. Since we are actually running a union on the input features to create a single feature for the applyEdits, we'd actually solve the issue by simply automatically running the simplify operation. This is promising. Thanks for the input!
... View more
11-21-2019
11:17 AM
|
1
|
0
|
2959
|
|
POST
|
I'd like to know how much the simplify task of the geometry service "alters" the input geometry? We have a public-facing Web AppBuilder application with a custom widget that allows users to upload a shapefile with polygon features of large areas that may be complex (think about a municipality with neighborhoods delineated). These boundaries get added to a graphics layer when uploaded as a .shp and ultimately offers the user a save button that performs applyEdits on a FeatureService with the features in this graphics layer. It's actually pretty straight forward and works well. Problem: cases where users have uploaded shapefiles containing self-intersecting polygon features, which causes the applyEdits to fail. We could just automatically perform a simplify on the features prior to performing applyEdits. This allows the geometry to be saved but we're unsure how much the simplify has altered the input features and no way to inform the user "how much" it has changed or a way to quantify that the changes in geometry are acceptable. I suppose we could just inform the user about this, allow them to exit or continue but we still need a way to get their boundaries into our system. In these cases we'd just have to do perform the update manually in ArcGIS Desktop. Comments appreciated!
... View more
11-21-2019
10:15 AM
|
0
|
2
|
3124
|
|
POST
|
We went down this path Printing maps that contain secured services—Documentation (10.3 and 10.3.1) | ArcGIS Enterprise From what I recall, we required the application to generate the token and simply append it to any secured service references for the ConvertWebMapToMapDocument
... View more
10-28-2019
11:24 AM
|
0
|
1
|
1076
|
|
POST
|
Perhaps instead of UPDATE by iterating over the arcpy cursor you could instead just do a fast INSERT into a temp table in the SQL db, join that table to your destination table and run the UPDATE that way? You'd probably have to create a StoredProcedure to run the join/update. Seems a bit roundabout way but perhaps letting the SQL db do it's thing would be more efficient. Sorry in advance if this is a bad idea and wasted effort (I don't have SQLLite to give it a go myself)
... View more
10-24-2019
06:25 AM
|
0
|
0
|
2952
|
|
POST
|
We've determined the issue is with the hosted feature service (a new "Tracker" feature service). ESRI is aware of the issue, closing this thread.
... View more
10-22-2019
12:58 PM
|
1
|
1
|
3535
|
|
POST
|
I'm always here on GeoNet! Take a closer look at the Camera Class for pro. I wish I had more info but don't have access to Pro just yet. You may want to try to change the mode from GLOBAL to LOCAL or MAP? mycam.mode = 'LOCAL'
... View more
10-22-2019
11:33 AM
|
1
|
1
|
1456
|
|
POST
|
Hey there Jorge! Looks like you've commented out that error on line 46 (#mycam.mode = 'GLOBAL')… Are you still getting that error or is it something different since taking that out? Unfortunately, I'm still not working with Pro just yet so sort of just guessing here. Hope all is going well buddy! Take care
... View more
10-22-2019
11:19 AM
|
1
|
0
|
1456
|
|
IDEA
|
We do not have Enterprise and the hosted feature service is not shared publicly (only within our AGOL org). There's nothing special about the query against the REST service, just using the ring of a known polygon that encompasses several of the tracker point features. "features": [
{
"geometry": {
"rings": [
[
[
-80.0949081552946,
26.6740014188274
],
[
-80.0949188841306,
26.6765131908286
],
[
-80.0913032663789,
26.6765419512564
],
[
-80.0915178431001,
26.6736658725775
],
[
-80.0949081552946,
26.6740014188274
]
]
]
},
"attributes": {
"OBJECTID": 3
}
}
] The only real difference is that the tracker service is in WKID 4326 vs. the typical AGOL 102100/3857 spatial reference. But I know the ring is correct as I can select point features from a different hosted feature service with points in a similar area and the result is correct using that ring as the input geometry.
... View more
10-22-2019
10:13 AM
|
0
|
0
|
2052
|
|
IDEA
|
I'm running into issues when querying against the viewer service using an input geometry to select point features that intersect/within that input geometry. Basically it is returning the incorrect number of features. However, if I use the same exact input geometry on another hosted feature service it correctly applies the selection and returns the expected features. Both point feature services are in WKID 4326 and the input geometry the same. Is there any potential issues with using an input geometry when querying a tracker's viewer service?
... View more
10-22-2019
06:44 AM
|
0
|
1
|
2052
|
|
POST
|
I'm not sure how to proceed with this. I've run some additional tests and the only thing I can think of is that I'm running into some sort of data issue. The point feature service of interest is the source to the new ESRI "Tracker" app, but it's still just recording point features into a regular old hosted feature service. I have added another hosted point feature service (symbolized with the black stars) and running the same exact query using the polygon as an inputGeometry, it selects 7 point features (which is correct). However, it selects 12 point features from the tracker point feature service (the light green symbols), which is obviously incorrect as there are many more points inside the polygon.
... View more
10-22-2019
06:08 AM
|
0
|
0
|
3535
|
|
POST
|
What's odd is the first time I sent the output ring into the Simplify task and used that result as the input geometry in the query, it correctly returned the point features that fell inside of that ring. Now, subsequent attempts (manually at the REST interface) does not perform the same selection result (selecting all points outside of that input simplified ring/geometry). Head scratcher.
... View more
10-21-2019
09:03 AM
|
0
|
0
|
3535
|
|
POST
|
I tried both and it didn't seem to matter and get the same result with clockwise / counter-clockwise drawn features. How about if I send the ring into the Simplify task of the Geometry service? That seems to generate the desired coordinate order of the ring when I run it manually at the REST Geometry service Simplify task. I think I can try a quick test in my .py implementation.
... View more
10-21-2019
08:26 AM
|
0
|
0
|
3535
|
|
POST
|
Hi Joshua, The payload appears to be the same with each request made. Of note: that is a hosted feature service I simply drew a couple of polygons in and then querying against it. From the result ring I then use as input geometry to query/intersect with another map service (hosted fs points). It selects all of the point features outside of that input ring! Also: I can simply run the query from the REST query interface, copy the ring coordinates and then paste into the REST query interface of the point service and it gives me the same result. So, I'm questioning if it's even an issue with my python implementation? Anyway - thanks for any input!
... View more
10-21-2019
07:46 AM
|
0
|
3
|
3535
|
|
POST
|
I'm querying a map service and using the polygon ring coordinates to the use as input geometry for another map service query. It looks like I'm not able to guarantee the point order of the first result and treats this as an outside ring (applying incorrect selections on the second query). For example, I may have this as the initial ring: {
"rings": [
[
[
-80.0929469116589,
26.6756462518988
],
[
-80.0924963005446,
26.6756390617361
],
[
-80.0924828894995,
26.6753730253964
],
[
-80.092965687122,
26.675375422123
],
[
-80.0929469116589,
26.6756462518988
]
]
]
} However, this selects features "outside" of that ring and it needs it to be in this order: {
"rings": [
[
[
-80.0929469116589,
26.6756462518988
],
[
-80.092965687122,
26.675375422123
],
[
-80.0924828894995,
26.6753730253964
],
[
-80.0924963005446,
26.6756390617361
],
[
-80.0929469116589,
26.6756462518988
]
]
]
} Here's the basic code I am using to get the ring feature: ringFeat = ''
qFl = 'https://services1.arcgis.com/sDAPyc2rGRn7vf9B/ArcGIS/rest/services/polySelectionLayer/FeatureServer/0/query'
sql = "OBJECTID=2"
qFlParams = urllib.urlencode({'f': 'json',
'geometryType': 'esriGeometryPolygon',
'geometry': '',
'spatialRel': 'esriSpatialRelIntersects',
'outSR': '4326',
'outFields': 'OBJECTID',
'returnGeometry': 'true',
'where': sql,
'token': token
})
reqFl = urllib2.Request(qFl, qFlParams)
errchk1 = ''
try:
response = urllib2.urlopen(reqFl)
except urllib2.HTTPError, e:
errchk1 = str(e.code)
except urllib2.URLError, e:
errchk1 = str(e.code)
if errchk1 == '':
jsonResult = json.load(response)
appCount = len(jsonResult['features'])
#if you have features, set the ringFeat to use in another query
if appCount > 0:
for feature in jsonResult['features']:
ringFeat = feature['geometry']
#finalringFeat = json.loads(ringFeats)
print json.dumps(ringFeat)
finalRing = json.dumps(ringFeat)
... View more
10-18-2019
12:58 PM
|
0
|
8
|
3963
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-17-2020 10:47 AM | |
| 1 | 10-25-2022 11:46 AM | |
| 1 | 08-08-2022 01:40 PM | |
| 1 | 02-15-2019 08:21 AM | |
| 2 | 08-14-2023 07:14 AM |
| Online Status |
Offline
|
| Date Last Visited |
01-22-2025
02:28 PM
|