|
IDEA
|
I believe OP is referring to the ability to overwrite Cached Map Image Web Layer which cannot be overwritten on Pro so long there is an existing Cache on the server. The only option right now is deleting the service reference in portal, then deleting the service itself for (in Server Manager - not stable) or more reliably in ArcCatalog which works better than Server Manager for these sort of managerial tasks. Unfortunately, here we are using "legacy" tech. It's not possible to do all this in Pro?
... View more
01-25-2018
01:59 PM
|
0
|
0
|
2309
|
|
POST
|
Does anyone know when will this be introduced into Pro? In my Migrating from ArcMap to Pro course in Sep 2017 the instructor mentioned that ESRI is expecting that Pro will match all ArcGIS Desktop (legacy) software functionality by the second quarter of 2018. Does this include all Distrubute Databases functionality including replication/synchronization, etc? Seems that the the old SDE approach is being pushed to the back burner a bit in favour the new data stores solution. It's good but still too simple. If only there was a way to replicate/ synchronize published feature services to a remote multiuser geodatabase/data stores and push changes back and forth.
... View more
11-24-2017
07:43 AM
|
3
|
2
|
1227
|
|
POST
|
Every time i select a feature or edit or split a feature the selection appears to slowly pulse which is a new visual effect in Pro. The pulse effect takes way too long bordering on annoying which is especially cumbersome when splitting a feature to many parts as every part slowly pulses after the split operation completes. The whole editing experience feels slower and non-responsive as a result. Is there a way to turn off ALL such animated effects in Pro? I attached a short video clip showing the effect.
... View more
11-16-2017
08:30 AM
|
5
|
4
|
2482
|
|
POST
|
I am running converting labels to annotations for 1m interval LiDAR contours and it's taking extremely long time. In ArcMap, this would only takes minutes but in Pro 2.01 the process is at 90% after 1.5 hours of processing. I will try your suggestion about doing this in a completely new project.
... View more
10-27-2017
09:26 AM
|
0
|
1
|
5093
|
|
POST
|
A bit late to reply to your comment, but I seem to be having the same issue. I have created a hosted feature layer (using an esri template just to be sure it's not just my data) in both AGOL and ArcGIS Portal, and I can't get the current version of the Web AppBuilder Developer edition to show the related tables. They don't appear in either the popup or the edit window. It works fine with the built-in version of WAB in AGOL, just not the developer edition which is very frustrating. Have you had any luck or filed a bug with ESRI?
... View more
04-07-2017
05:50 PM
|
0
|
0
|
1405
|
|
POST
|
Adding ampersand "&" to the end of my URL (without any parameters) worked for me. You can redirect the URL and modify the index.htm to do this automatically.
... View more
01-04-2017
12:21 PM
|
0
|
0
|
1982
|
|
POST
|
Good one Dan! Seems that any parameters tacked on the link trigger the original state of the app. I just added an ampersand "&" without any parameters and it seems to trigger the original state without executing any parameters.
... View more
01-04-2017
12:15 PM
|
0
|
0
|
1358
|
|
POST
|
Awesome! Thanks! My defulat coordinate system is NAD 83 UTM 15 (metres). The scale works great with that. Displays exactly the scale levels i've set up with my cached services. When I add a second coordinate system to this coordinate widget (WKID: 3857 TFWKKID: 1188 Units: DD) the scale works fine when the default coordinate system is shown. However when I switch to the WGS system, no coordinates are shown, only scale and the scale spans across 2 lines. Switching back to default restores the coordinates and the scale. Still, good enough for me for now. Great work!
... View more
11-15-2016
01:43 PM
|
0
|
0
|
2482
|
|
POST
|
Using rounding and comparing rounded pairs helped but didn't work 100%.
... View more
07-11-2016
06:44 AM
|
0
|
0
|
2658
|
|
POST
|
ROUND( SHAPE_Area,2) IN ( 0.21, 244163503.16 ) is in fact a valid query. I can work with that. Thanks for pointing me in the right direction.
... View more
06-25-2016
10:20 AM
|
0
|
0
|
2658
|
|
POST
|
These are great suggestions on handling it but i still need to query for the original number somehow. Is there a way to to this the other way; to "elegantly" incorporate such tolerance in a query other than using BETWEEN? Would a wildcard character work on a number for example something like Shape_Area IN (987.87676%,876.7655%,564.987675%) or if I round the numbers beforehand is there a way to query rounded number for example ROUND(Shape_Area, 6) IN (987.876765,876.76553,564.9876754)
... View more
06-25-2016
10:01 AM
|
0
|
0
|
2658
|
|
POST
|
Thanks Dan! Not a good news. Is there a solution/workaround? I need to print the values as string (and concatenate a simple but long FIELD IN (value, value, value,...) statement to make a definition query that will return the records whose values are used in this query. Is there a way to handle false precision especially when shape area and length are involved? The interesting thing is that when I use the Query builder in the attribute table and hit the unique values button - they all seem to be correct - building a similar query with these values in the Attribute Table Query Builder always works correctly. This is essentially the same values I need but when I convert them to string in VB.Net those values are slightly changed hence making my own query unusable.
... View more
06-25-2016
08:47 AM
|
0
|
2
|
2658
|
|
POST
|
I am have an issue in my addin; I need to construct a defenition query from Shape_Area, Shape_Langth and other values but when these numbers are converted to string in any way the resulting number is most often rouded to less decimal places than those in the the source feature class. Example: the actual value in pRow.Value(i) = 1234.12345678987656 but the result of pRow.Value(i).ToString = 1234.123456789877 Any ideas?
... View more
06-25-2016
07:17 AM
|
0
|
7
|
5878
|
|
POST
|
Previous problem - Attribute Transfer simply not transferring attributes. Solution to previous problem: create a new mxd and copy all layers over, start editing and create a new mapping. Works fine New problem - Attribute Transfer tool switches source and target whereas it transfer attributes from target to source not from source to target. Solution to new problem: Same as before - create new mxd, copy layers over, re-map attribute transfer. Works fine Conclusion: There is something broken in the mxd structure that causes the attribute transfer tool to malfunction. Creating a new mxd, copying layers over solves the problem until such time that it no longer works at which point a new mxd must be created yet again. Note: mxdDoctor does not correct the issue, a new mxd document must be created for this workaround.
... View more
10-26-2015
07:49 AM
|
0
|
1
|
2917
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 11-14-2024 06:48 AM | |
| 3 | 11-14-2024 06:40 AM | |
| 1 | 10-08-2024 06:12 AM | |
| 2 | 03-15-2024 10:37 AM | |
| 1 | 05-21-2014 08:25 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-14-2024
04:08 PM
|