Latest Contributions by JamalNUMAN

Not necessarily..., it may get a bit complicated now, but versions reference so called "database states". Each time you make any type of edit to a Feature Class, you create a new "database state", and the version starts referencing that state from that moment onwards until the next edit completes. The database state references a certain combination of records in the base table and A/D delta tables. Your single version may actually go through a whole set of "states" during its life-time until you delete the version once you no longer need it. Even during a single edit session (the time in between clicking Start Editing and Stop Editing in ArcMap), your version may go through multiple states, as you can perform multiple edits in a single edit session. It is the time you complete your edits (transaction closing time?) to specific records / geometries, which ultimately determines which records / geometries might be considered the "valid" or last "state" of the object they represent. It is this time and database state information that is used in the (batch) reconciliation and post process to determine if there are any conflicts due to other users having edited, saved and posted the same object to the same target version before you post it. You can than use the reconciliation tools to review the conflicting states and determine whether you favor the current target, or your own edit version. So don't confuse the creation time of the version with the save / completion times of specific edits to specific records / geometries. Jamal, I also strongly encourage you to read Derek Law's basic introduction to versioning to better understand what is going on "under the hood": Versioning 101 And for a really comprehensive overview (older 2004 document, but the mechanism of versioning described there is still highly relevant): Versioning - ESRI Technical paper Hi Marco, I have tried to figure out the way the updates are done (in case of conflict) when received from multiple versions. Scenario: 1. I got sde.default from which two users got their versions (u1.u1 and u2.u2) 2. The u1.u1 and u2.u2 are updated as show in the screenshot below: [ATTACH=CONFIG]27915[/ATTACH], [ATTACH=CONFIG]27916[/ATTACH] a. Feature #11 stays the same in the sde.default b. Feature #11 is moved to left in version u1.u1 and saved c. Feature #11 is moved to right in version u2.u2 and saved d. Feature #9 stays the same in the sde.default e. Feature #9 is moved to left in version u1.u1 and saved f. Feature #9 is moved to left in version u1.u1 and saved 3. The result is as shown below [ATTACH=CONFIG]27917[/ATTACH] Very confusing! I expect that the updates of feature #11 will follow the u2.u.2 version (since the most recent edits occurred there) while the updates of feature #9 will follow the version u1.u1 (since the last edits occurred there) What is confusing that the both conflicts are updated based on the u1.u1 version! How come the u1.u1 is the determinant? I tried to do other conflict changes and found out that the updates of the u1.u1 are considered! What might be the issue here? Thank you Best Jamal ... View more

Just to make sure you don't misunderstand this: in the end, it is always you as a user who needs to determine which state of an object is the right one, and needs to be maintained. Even if you set an (automated) option, like "in favour of target", you are making an important decision, namely to always favour the target! You really need to consider if you want automated reconcilation or not, and this determines your workflow setup. You may need to have manual intervention by someone with authority to determine which state is right. Another thing you really need to understand fully is, that by definition, any reconcilation will always lead to fully identical features on both the parent and child. This means that BOTH the geometry AND all its attributes will be exactly the same. The reason for this is that, after reconcilation and post, the two features will point to the same database state. This means that it is absolute impossible to have two features not being fully identical, because both features from the parent and child version are pointing to exactly the same database record! If you set "BY_ATTRIBUTE", you are just telling ArcGIS to automatically and silently merge attributes updates to two or more different fields, and to not flag them as a conflict. E.g., if you initially have feature A in the parent with a value of "Oak" for the field "Tree_species" and "30 years" for field "Tree_age", and the tree species in the parent is updated to read "Birch", while the tree age is updated in the child to be "40 years", than the resultant feature will have "Birch" and "40 years" after reconciliation in both parent and child. See below. BEFORE EDITS Parent "Tree_species":"Oak" "Tree_age":"30 years" Child "Tree_species":"Oak" "Tree_age":"30 years" AFTER EDITS Parent "Tree_species":"Birch" (EDIT!) "Tree_age":"30 years" Child "Tree_species":"Oak" "Tree_age":"40 years" (EDIT!) AFTER RECONCILIATION (no conflict detected with option "BY_ATTRIBUTE"~~!) Parent "Tree_species":"Birch" "Tree_age":"40 years" Child "Tree_species":"Birch" "Tree_age":"40 years" As you can see, both edits are silently merged without a conflict being raised, because the attribute changes in parent and child are on different fields and can be merged without causing an inconsistency. Thank you very much Marco for the help, Based on valuable elaboration you have already provided, is it correct to say: 1. If the conflict definition is set to be �??by object�?� then only spatial changes applied to the same FEATURE (in the parent and child) will be considered as conflict and will be flagged for further work. In this case, attribute changes applied to the same record FEATURE (in the parent and child) will never be considered as conflict. 2. If the conflict definition is set to be �??by attribute�?� then only tabular data changes applied to the same RECORD (in the parent and child) is considered as conflict and will be flagged for further work. In this case, spatial changes applied to the same FEATURE (in the parent and child) will never be considered as conflict I got a question in my mind: when then there is no option to set �??by object�?� and/or �??by attribute�?� at the same time so that the system will flag spatial or tabular changes as conflicts instead of considering one of them ata a time as conflict? ... View more

Have to ask: do you have a Network Analyst License for ArcGIS Server?  If yes, I'm sure one of the Silverlight fans can provide the info.  If no, you are out of luck with Silverlight or any other web bsed app. Many thanks Joe for the help, In the screenshot I attached in my previous post, the �??NAServer�?� Service is already there. The issue here is not the license but how to integrate the already published �??NAServer�?� Service in the Silverlight. Best Jamal ... View more

with firebug what do you see in net tab (request rest) when you click 'go to'? so you can understand what can be the problem. Hi Domenico, I got the help below: Images contained in mosaic data are disappeared at particular scale. To get them appeared at all scales the �??build review�?� tool must be used. [ATTACH=CONFIG]27831[/ATTACH], [ATTACH=CONFIG]27832[/ATTACH], [ATTACH=CONFIG]27832[/ATTACH] That solves my issue as well. It can be viewed from the web mapping application with no problem [ATTACH=CONFIG]27833[/ATTACH] Best Jamal ... View more

Option #2 only works in ArcGIS Server 10.0 (publishing mxd files). I would choose to publish it as an image service (option #1), if you have that extension licensed in your ArcGIS Server.  If you can put the mosaic on the web server (if there is room), it will be faster than referencing it from a shared directory. On the other hand, caching the mosaic is much faster in terms of performance. Many thanks leo for the help, I sure I do have the image server extensions that enables me to publish images (except ones of ecw format) I�??ll go for the valuable advice to gain some additional performance (speed): 1. To save the mosaic (that contains images) in the server machine 2. To publish the mosaic as �??image service�?� (but not as map service) and then to cache it Best Jamal ... View more

Shapefiles do not accept null values. See here for more information... Hannah 🙂 Many thanks Hannah. Good to know this fact Best Jamal ... View more

There is an extension. I have not made the extension work with ArcPad 10.2 / Windows 8. http://arcpadteam.blogspot.com.au/2012/10/using-arcpad-ecw-extension-on-windows-7.html Many thanks Paul for the help. I note the following: 1. Then ArcPad can�??t read ecw images as the ArcMap does. [ATTACH=CONFIG]27822[/ATTACH] 2. ArcGIS server is not able to publish ecw images! [ATTACH=CONFIG]27823[/ATTACH] I�??ll be checking if we can manage to purchase the extension for the ArcPad to read ecw images. Best Jamal ... View more

Open your python window in ArcMap and you can copy/paste the code in there.  The code will iterate through your 'D:\Practical1_Adding\Data directory and reproject each JPG.  It will write the new projected raster to the same directory with the same name plus "_project" added to it. For example, the image 'yosh_09-06-12_77.jpg' will be reprojected and named 'yosh_09-06-12_77_project.jpg'. Thank you Jake very much for the prompt help. It works fantastically. While the code you have already sent is great in its current form, I still couldn�??t figure out why the behavior of the �??project raster�?� can�??t be developed to be the same as �??raster to other format�?� such that multiple projected raster can be populated automatically in the specified folder. [ATTACH=CONFIG]27818[/ATTACH] Meanwhile, how the coded you have already sent can be further developed to allow the user to specify the input and output of raster (on the hard drive)? Is it also possible to be developed in form of script tool? [ATTACH=CONFIG]27819[/ATTACH] ... View more

Hi Jamal, I don't believe there is a way to auto populate this parameter.  You can easily accomplish this in python, though.  Here is an example: import arcpy from arcpy import env env.workspace = r"D:\Practical1_AddingData\Data" for raster in arcpy.ListRasters("*.jpg"):     arcpy.ProjectRaster_management(raster, raster + "_project.jpg", "GEOGCS['GCS_Palestine_1923',DATUM['D_Palestine_1923',SPHEROID['Clarke_1880_Benoit',6378300.789,293.4663155389802]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]]","NEAREST","0.0000025","Palestine_1923_To_Israel_1","#","GEOGCS['GCS_Israel',DATUM['D_Israel',SPHEROID['GRS_1980',6378137.0,298.257222101]],PRIMEM['Greenwich',0.0],UNIT['Degree',0.0174532925199433]]") The above code will iterate through the 'D:\Practical1_AddingData\Data' directory and reproject each JPG to a new JPG with the same name, just with "_project" added to it. Many thanks Jake for the help, Sorry but I couldn�??t know how to integrate the code you have provided with the �??project raster�?� tool. Could you please elaborate a bit more. [ATTACH=CONFIG]27804[/ATTACH] By the way, I like the behavior of the �??raster to other format�?� tool where the output is populated automatically in the specified folder. Why the design of the �??project raster�?� is not developed to be the same as �??raster to other format�?�? [ATTACH=CONFIG]27805[/ATTACH] Best Jamal ... View more

Hi! - To change permission public to protect, do steps below: Open ArcCatalog, connect to database (use sde or sa user account) --> click right on database --> choose version. After that, select default version and click right on selected version --> choose properties: click option protect. [ATTACH=CONFIG]27776[/ATTACH] - Only sa or sde user can grant privileges for other user. - User who create a version will own that version. - Only sa, sde user or owner version can delete that version. That's what I know, 🙂 --TT Many thanks Nguyen. Very useful. It works fine Best Jamal ... View more

Sounds like you unchecked "Allow NULL value" for those fields in the form.  Open the form in ArcPad Studio and look at the Control Properties for each field you want to have nulls. If they were checked out from a geodatabase, "Allow NULL Values" was set to "no" on the fields.  You will have to redo your database feature classes so that option is set to "yes" and redo your checkout.  If you just make ArcPad allow NULL values, you face not being able to check in your edits if there are NULL values. Many thanks Robert The �??allow null values�?� option is available for feature classes but not for shape files. [ATTACH=CONFIG]27688[/ATTACH], [ATTACH=CONFIG]27689[/ATTACH] Then how to allow accepting �??null values�?� in the case of shape files. I couldn�??t manage to do it in the studio [ATTACH=CONFIG]27690[/ATTACH] Best Jamal ... View more