Latest Contributions by JenniferMcCall4

I think the code may be failing on this section:     # Create in-memory feature class for holding the shadow polygons     tempshadows = r"in_memory\tempshadows"     arcpy.CreateFeatureclass_management(         "in_memory",         "tempshadows",         "POLYGON", "", "", "",         outputSR)     arcpy.AddField_management(tempshadows, origfidfield, "LONG") The syntax for the Create Feature Class tool is: CreateFeatureclass_management (out_path, out_name, {geometry_type}, {template}, {has_m}, {has_z}, {spatial_reference}, {config_keyword}, {spatial_grid_1}, {spatial_grid_2}, {spatial_grid_3}) It looks like you are creating a feature class called in_memory\in_memory\tempshadows - and I think one of the in_memory's needs to be removed. ... View more

I agree with Neil.  The "Any Value" option would work well. In addition to this, if your heightfield parameter should have a field as the input, you can use "Field" for the data type.  You can then loop through the values in the field within the script. If you want to validate that the input values for heightfield, azumuth, and altitude are in the correct data type (ex; degrees) you can add some code to validate the values.  Ex; loop through all azimuth values to ensure they are of the float data type and all between 0 and 360 - this would be done within the script after the parameters have been set, but before the rest of the script executes.  Then just spit out a message to the user if the data is not in the correct format. ... View more

I was looking at the cache scales you set: If these are the scales you are going with, I would recommend that you set you visible ranges for the layers in ArcMap so that the caching scale is in the middle of the layer visibility range in ArcMap.  Example: 1:15,000,000 - 1:6,500,001 1:6.500,000 - 1:2,000,001 1:2,000,000 - 900,001 1:900,000 - 1:650,001 1:650,000 - 1:400,001 1:400,000 - 1:175,001 1:175,000 - none ... View more

Since the data is cached, it acts like an image or graphic.  Let's say your cache levels are 1:1000, 1:2000, 1:4000 - if you view the cache at 1:2000 the symbols should look fine (as expected).  If you were to view the cache at 1:2500 or 1:3000 for example - scales that are not cached - the symbols will distort from the original cache scale. Saying this, how do your symbols look at one of your exact cache scales?  Do they appear as expected? For the issue regarding the cut-off symbols, are you setting a caching Area of Interest?  When you zoomed to the layer before publishing the service, did you also set this extent as the data frame extent in the Data Frame properties? ... View more

Can you provide some more information?  As Avinash suggested - are these symbols in one layer or two?  Is there a reference scale set on the data frame?  Are the symbol sizes the same in the map document before the cache? ... View more

Hi Jacob, The publisher connection is fine to use. You shouldn't need to stop the service when overwriting.  You don't need to when doing it manually, so I would assume the same applies through a script.  Overwriting the service should automatically stop and start the service on its own ... View more

Hi Glenn, You mentioned that ArcGIS Server is on another machine than postgres.  Could it be that you are trying to connect to postgres using localhost instead of the IP of the postgres machine?  What are your database connection properties?  Are you able to connect to the database in ArcCatalog on the ArcGIS Server machine (not through the ArcGIS Server properties)? ... View more

Opening MXD by double clicking crashing ArcMap. Opening in ArcMap itself fine. Why?  Is this the sort of issue you were referring to, Dan?  Double-clicking the mxd file to open it causes ArcMap to crash, but opening ArcMap as a blank template and then opening the mxd from there allows the mxd to open fine. ... View more

This would be my recommendation as well.  Although this link says to re-set your Normal.mxt file.  I would recommend closing at arcgis applications, re-naming the entire ESRI folder encompassing the Normal.mxt file, and then open ArcMap again. When opening ArcMap for the first time, open it as a blank template and then open the saved mxds from there. Does ArcMap crash right now when opened as a blank template?  Are you having any issues with the other arcgis applications (ex; ArcCatalog) as well? ... View more

Stopping the ArcGIS Server service should kill the job, not leave it cancelling.  How long did you wait between stopping it and starting it up again.  It's beneficial to wait at least 30 seconds. ... View more

Is this percentage where you expect the CPU to sit while caching, or while there is no caching and active users? ... View more

Hi Justin, I was referring to the ArcGIS Server service within Windows Services.  Stopping and then starting it should remove any potential locks from other services or even from processes previously run on this image service.  After starting the windows service again, wait a minute or two until ArcGIS Server and all arcgis services (ex; the image service) are back up and running.  Then try to cache just level 17 again and see if it makes a difference. When you publish the service, are you checking the box to manually create the cache after the service is published? Another source of information you could check is the Status.gdb within the cache folder.  It will only be visible through Windows Explorer, so copy this gdb to another location (ex; your Desktop) and then you can open the GDB and feature classes within ArcMap.  This may provide more information on what might be happening with your service.  I would recommend copying the GDB after you have tried to re-cache level 17 so any information about the job will be populated in the feature classes. ... View more

Could it be that another process is holding on to the instances need to cache this?  Have you tried re-starting the ArcGIS Server service in windows? What does your CPU sit at over the 3 hours? ... View more

If you open the service properties and go to Caching -> Advanced Settings, can you take a screen capture of the scales listed. Ex; I would also consider setting the min and max scales to values around the scales you want the data to show at.  If you set it for the exact scale value, it can cause problems. For example, if your layer for the 1:564 ArcGIS Online scale has a minimum scale of 564 in the map document, it will not show when cached.  I believe the actual scale value is something like 1:564.249 - which is beyond 564. ... View more