Latest Contributions by JamalNUMAN

Jamal, I noticed one thing in your screenshots that concerns me. You have a lot of labels visible, and those labels seem to be dynamic. They are not a fixed size nor position. Dynamic labeling is very costly in most cases, and you probably want to avoid this in your web services. What you should consider, is converting your labels to Annotation Feature Classes in your geodatabase, probably best as a feature-linked version, that updates with updates to your parcels layer. As the Help page I linked says: "Geodatabase annotation is indexed spatially, meaning that it will draw and select much faster." You would also do good to set a fixed reference scale for the Annotation and labels, e.g. 1:5000, so as to have the labels scale. And set a visible scale range. As the Help says: "To maximize ArcMap display and query performance, always define a visible scale range for each annotation class so annotation features only draw when you're zoomed in enough to read their text." Many thanks Marco for the help, The issue here is that even in case of publishing an mxd of simple feature class with no labels, the cache is not completed Scenario: Consider an mxd file that contains only one feature class (attached) with the following properties 1. No labels 2. The surface area is 131x51 km 3. The data size is about 800 kB [ATTACH=CONFIG]25932[/ATTACH], [ATTACH=CONFIG]25933[/ATTACH] Caching this mxd is never completed with the settings below [ATTACH=CONFIG]25934[/ATTACH], [ATTACH=CONFIG]25935[/ATTACH] Challenges: 1. Publishing data introduces slow speed when the services are accessed by web applications or even with the arcgis desktop! Services are quite slow when accessed anyway 2. Caching the service is either not completed or takes long times (hours) even for very light data. Then caching is almost impossible anyway. Then what is the benefit of publishing data while the performance (speed) is slow? ... View more

There are a vast amount of variables here. 1st off, you say 'huge' I laugh, we have caches 10x that size even with small areas, mind you, we go down to 1:256 for some serious details. Even with a tiny area, you are going down to the 1000 level so depending on the project area, size would be expected and by using Exploded method (which creates many folder directories as well as jpgs (though the advantage to this is 'merging' caches quite easily) the size problem is exaggerated. Its again further exaggerated by using 128x128 tiles and again exaggerated using png without compression. Try re-running the cache by selecting EXTENT of the map (after of course, getting the area you want) - I have had strange problems with using features as the area of interest (however, I think this was due to custom projections being used) Use MIXED Tile format at 75 compression - you wont notice a difference! Use 512x512 tile Use Bundle format (compressed storage format) as for the estimates shown, Ive yet to see one that is accurate or really close - its a big 'guess' done by samples and algorithms. as for the 'caching never ends successful' what does the geodatabase results show you? which failures, if any are in the attribute table? Another thing you can do is create the service MANUALLY cache and send the GP request through Cache manager in Catalog to the map service when published. Many thanks Michael for the �??road map�?� that you have provided in order to publish my mxd successfully with cache options, I tried the settings that you have recommended but sound massive time is still required to get my mxd published with cache option. [ATTACH=CONFIG]25854[/ATTACH], [ATTACH=CONFIG]25855[/ATTACH] Till the moment I�??m writing this post, my published mxd is not completely cached. The total number of tiles at the scale of 1:1000 is 480635. Is that normal? [ATTACH=CONFIG]25856[/ATTACH] Best Jamal ... View more

Jamal, I can't comment on why things might be failing at your site, Michael is in a better position to do that, but in general, you should not consider caching as the only alternative for hosting data. If you just want to serve non-complex data, like small scale polygons of provinces like the once you showed in this thread with few vertices per polygon, and with simple outline symbology, you are probably much better off serving data straight from the feature source (or a copied file geodatabase), than to create a huge cache. It will bloat storage requirements compared to the original feature data. Caches are best used for complex large scale data that may take up (tens of) gigabytes of diskspace using complex symbology, like detailed cadastral land records, high quality topographic data etc. E.g. say you have an MXD having 20 layers with large scale topographic data symbolized using layered line symbology for roads, complex hatch symbols for polygons to represent 50 different land use types and so on, dynamic labelling etc. with a re-draw time of (a dozen) seconds per screen in ArcMap. If this MXD needs to serve as a basemap layer, e.g. a background to other more dynamic data, than that type of data is best served through cached services, as you wouldn't ever be able to serve that data dynamically to hundreds, or thousands, of users at a time. Just imagine with every hit to your website, the server needing 10 seconds to render a single image before it can send of the rendered data to the user... It really depends on the type of data, and the complexity of the symbology to be used, what type of method you chose to host the data. Many thanks Marco for the very informative answer, In my case, 14 layers are required to be published where the background is the satellite image. What might be the best scenario to do this? [ATTACH=CONFIG]25797[/ATTACH], [ATTACH=CONFIG]25799[/ATTACH], [ATTACH=CONFIG]25800[/ATTACH] For the time being, the published mxd (service) that contains these layers and satellite image is quite slow even before being accessed by web mapping application. The service itself is quite slow. [ATTACH=CONFIG]25801[/ATTACH] Therefore, all users are complaining due to the very slow speed in panning and zooming the maps accommodated in the web application. [ATTACH=CONFIG]25802[/ATTACH] By the way, how Google is providing massive maps with relatively high speed? I think that the only way is caching them. Is that true? ... View more

Define caching succeeds? "Generation not in progress" could be due to the caching is complete. This does NOT mean you will see 100% as I mentioned above, I have complete caches done showing 18%. There are a lot of variables determining the percents. Did you do what I mentioned and look at the geodatabase status? my bet is it will say SUCCESS for all records. Many thanks Michael, I never succeed in caching whatever even with a scale as low as 1:1000. The unfinished caching is not working! I check this with adding the link to the Silverlight [ATTACH=CONFIG]25767[/ATTACH] Facts: 1. Caching takes massive time even when caching small area (like the West Bank). In return, how a map like the one in the link below is cached and works fine? http://www.govmap.gov.il/ 2. Caching never ends successfully. 3. Caching takes huge space size on the hard drive [ATTACH=CONFIG]25768[/ATTACH], [ATTACH=CONFIG]25769[/ATTACH] If the cache never work then no meaning for publishing the data due to the very slow speed What might be the solution? ... View more

When you unregister a replica, be sure to do it on both ends; you need to 'cut the cord' between parent and child on the parent end and the local/ child end as well. Many thanks Joe. Good to know this point. [ATTACH=CONFIG]25513[/ATTACH], [ATTACH=CONFIG]25514[/ATTACH] Best Jamal ... View more

Jamal, This is by design. Please have a look at the below link for more details: [ NIM040283 - Using GP tool (create replica) to create replica and set ALL_ROWS for expand feature classes and tables, the attribute table only has its schema replicated.] http://support.esri.com/en/bugs/nimbus/TklNMDQwMjgz You can also have a look at the below post for a good workaround: http://forums.arcgis.com/threads/481...604#post166604 (look at the last post) Hope this helps! Regards, Thank you Asrujit for the help, My non-spatial table is intended to be versioned and wanted to have same behaviour as for the spatial data when replica is created. Is there a solution in 10.2 such that non-spatial data is replicated when �??create replica�?� is used? ... View more

By default, when replicating tables the 'Check Out' for the table is set to Schema Only rather than 'All Records'.  You will need to go into the advanced options when creating the replica (screen1.png).  Then you can set the 'Check Out' to 'All Records' (screen2.png). Hi Jake, I�??m experiencing the same problem. May you please have a look on the thread below: http://forums.arcgis.com/threads/86754-Tables-participating-in-a-replica-generated-empty?p=306636&posted=1#post306636 Best Jamal ... View more

The first shows an application of the second. (It is noteworthy that these formulas do not require that the locations be distinct: the calculation works just fine, and makes perfect sense, even when multiple values are available at some locations.) Thank you Eric and William for confirming the equation. Have you any idea how the IDW then can be expressed mathematically in ONE equation? ... View more

Hi Jamal, 1.  Unfortunately, No, I do not know of a method to change more than one at a time from Geometry to SDEBinary. 2.  No, I dont think that having the versions remain will slow it down to much.  I have only experienced lag when we have had major edit sessions and over 100,000 features were changed.  As soon as we reconciled, posted, and compressed everything sped back up.  We just have everyone delete their version at the end of the day so we know they have done the reconcile and post to our QC version.  If someone wants a version to do what-if scenarious that will not be posted to Default then we allow that one to remain. 3.  I dont see a problem with doing it daily.  We are probably smaller than most GIS departments and just find that end of week works for us.  Good Luck! Luci Many thanks Luci. This is useful Best Jamal ... View more

That's not for IDW to do. Instead, you need to compute a distance grid for each source location and use Map Algebra to calculate the w(i) from those and form the desired linear combination.  Distance grids can be computed in any way that is appropriate: using CostDistance to approximate travel times, for instance, or even just the Euclidean distances. Hi William, Mathematically, do you agree that the formula of the IDW can be expressed in screenshot 1 and 2 below: [ATTACH=CONFIG]25195[/ATTACH], [ATTACH=CONFIG]25196[/ATTACH] Are they equivalent? Best Jamal ... View more