POST
|
We have a ClickOnce WPF application and are looking to upgrade from the old ArcGIS client control to the new ArcGIS Runtime for .NET product. The application doesn't leverage much in terms of the client-side tooling has no need for the entire "local" part of the new libraries at this time. I was pretty surprised when I installed in the NuGet package and saw that my output directory contained 60MB attributed to ESRI! This would pretty much triple the ClickOnce install (for now, ignoring the option of making this package a prereq). The old ESRI.ArcGIS.Client.dll was under 1MB. The new ArcGIS Runtime pushes 60MB. Is there a way of getting back to the resonable size of the previous version?
... View more
08-13-2015
06:27 AM
|
0
|
0
|
2647
|
POST
|
If that is the case, then the GraphicsLayer definition should not include a SpatialReference property at all. I am encountering a similar problem to this where adding points - which their SR set correctly - to a GraphicLayer is hanging the application. The map is fully loaded with it's SR set and the layers initialized, yet the problem persists. The workaround for my issue is to set the GraphicsLayer.SpatialReference via reflection (since it's private), and the issue is solved.
... View more
07-16-2015
05:34 AM
|
0
|
1
|
1355
|
POST
|
Avoid "On Demand" caching! After having tiles take upwards of 3 minutes to generate with my services, ESRI eventual got back to me and said "do not use" this feature as it does not work as advertised.
... View more
01-26-2015
10:14 AM
|
0
|
0
|
472
|
POST
|
I have a map service on ArcGIS Server 10.1 that I am accessing using WMTS. The map covers a small region and the caching settings are to "Create tiles on demand". I have found that when I request a tile that is within the extent of the map, it returns in less than a tenth of a second. However, if I request a tile outside of the map's extent it takes almost 2 seconds for a 404 error to be thrown. If I turn off "Create tiles on demand" on the service, the 404 is thrown almost instantly. For testing purposes I have been making the calls directly to ArcGIS and using Fiddler to trace the calls. Is this expected behavior? I realize that I could do client-side checks to ensure the request is being made for only those tiles within the map's extent; however, that would appear to be a band-aid fix for a potential server-side issue. Cheers, Mark.
... View more
08-29-2013
05:17 AM
|
0
|
0
|
2717
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|