POST
|
Thanks for the work around. The work around is functional, but it is not ideal for mass reprojecting rasters. Cheers, Brent
... View more
07-31-2014
12:26 PM
|
0
|
0
|
1057
|
POST
|
I am experiencing the same problem using ArcGIS 10 on Windows 7. The "Project" (vector) tool works as it should, the providing option to select a desired transformation from a drop down list. The "Project Raster" tool does not. The "Geographic Transformation (optional)" parameter is unusable (no drop down list).
... View more
07-31-2014
10:12 AM
|
0
|
2
|
1057
|
POST
|
I expect that every element is tracked by a lower left and an upper right. When you rotate this rectangle, it changes the min / max values associated with the element. Regards, Jim Yeah, it seems like the pre-rotation bounding rectangle is rotated and then used to create the new bounding rectangle once the rotation is applied. A separate graphic object must be used if a frame and/or background are needed for the north arrow in order to ensure that the frame/background remain unchanged as the north arrow is rotated. Thanks again for your tip! We no longer have the to deal with re-positioning wandering north arrows in our map templates when rotations are applied.
... View more
01-08-2014
04:00 AM
|
0
|
0
|
856
|
POST
|
Select the North arrow >> Properties >> Size and Position. Under the Anchor Point Graphic, choose the center point, and rotation should behave as you need. Best Regards, Jim Excellent! That works perfectly. I was unaware that the anchor point of graphics could be modified via the "Size and Position" dialogue. The only strange thing is that the frame size also changes when as the object is rotated - even with round north arrows.
... View more
01-06-2014
09:16 AM
|
0
|
0
|
856
|
POST
|
Even when using seemingly symmetrical north arrow symbols like ESRI North 74, the symbol will not stay centered as the data frame rotation changes. It seems as though the anchor point of the symbol is not centered and I am not aware of any way to change the position of the anchor point. This behavior can be observed by following the steps below: 1) Insert a north arrow into a data frame (ex. ESRI North 74) and apply a frame with a visible outline to the north arrow 2) Rotate the data frame and observe the frame size changes as the data frame is rotated This is very annoying when many maps are generated based on a common template/north arrow and varying map rotations are used to optimize space in the page layout. For example, say that you want to generate a map series of hundreds of maps with varying rotation based on the index layer using data driven pages. The north arrow shifts as the rotation angle changes. Does anyone have a solution to this problem? Would a custom north arrow solve this problem? I am hesitant to create my own custom north arrows as this compromises the compatibility/portability of template MXDs. Cheers!
... View more
01-06-2014
05:43 AM
|
0
|
7
|
4179
|
POST
|
Hi Brent, Try replacing: arcpy.ImportCADAnnotation(';'.join(lst_anno_lyrs), tmp_an, 1000, "ONE_CLASS_ONLY", "NO_MATCH", "NO_SYMBOL_REQUIRED", "STANDARD", "", "NO_AUTO_CREATE", "NO_AUTO_UPDATE") with: arcpy.ImportCADAnnotation_conversion(';'.join(lst_anno_lyrs), tmp_an, 1000, "ONE_CLASS_ONLY", "NO_MATCH", "NO_SYMBOL_REQUIRED", "STANDARD", "", "NO_AUTO_CREATE", "NO_AUTO_UPDATE") Good eye. The "_conversion" is present in the actual script and it still does not work. I have corrected the post according.
... View more
02-21-2013
11:14 AM
|
0
|
0
|
314
|
POST
|
Here is a snippet from the functioning ArcGIS 9.2 script : for item in lst_dxf_o_files:
gp.MakeFeatureLayer_management(item + os.sep + 'Annotation', 'tmp_3rayon_lyr', "UPPER(layer) LIKE 'OFF_LO_RAY' AND UPPER(txtmemo) LIKE 'R: %,%'")
print unicode(gp.GetMessages()).encode("iso-8859-2", "replace") + "\n"
lst_anno_lyrs.append('tmp_3rayon_lyr')
gp.MakeFeatureLayer_management(item + os.sep + 'Annotation', 'tmp_4pc_lyr', "UPPER(layer) = 'GRA_NM_PLA_COM' AND UPPER(txtmemo) LIKE 'PC%'")
print unicode(gp.GetMessages()).encode("iso-8859-2", "replace") + "\n"
lst_anno_lyrs.append('tmp_4pc_lyr')
# Process: ImportCADAnnotation
gp.ImportCADAnnotation(';'.join(lst_anno_lyrs), tmp_an, 1000, "ONE_CLASS_ONLY", "NO_MATCH", "NO_SYMBOL_REQUIRED", "STANDARD", "", "NO_AUTO_CREATE", "NO_AUTO_UPDATE")
print unicode(gp.GetMessages()).encode("iso-8859-2", "replace") + "\n" And here is the non-functioning ArcGIS 10 version: for item in lst_dxf_o_files:
arcpy.MakeFeatureLayer_management(item + os.sep + 'Annotation', 'tmp_3rayon_lyr', "UPPER(layer) LIKE 'OFF_LO_RAY' AND UPPER(txtmemo) LIKE 'R: %,%'")
print unicode(arcpy.GetMessages()).encode("iso-8859-2", "replace") + "\n"
lst_anno_lyrs.append('tmp_3rayon_lyr')
arcpy.MakeFeatureLayer_management(item + os.sep + 'Annotation', 'tmp_4pc_lyr', "UPPER(layer) = 'GRA_NM_PLA_COM' AND UPPER(txtmemo) LIKE 'PC%'")
print unicode(arcpy.GetMessages()).encode("iso-8859-2", "replace") + "\n"
lst_anno_lyrs.append('tmp_4pc_lyr')
# Process: ImportCADAnnotation
arcpy.ImportCADAnnotation_conversion(';'.join(lst_anno_lyrs), tmp_an, 1000, "ONE_CLASS_ONLY", "NO_MATCH", "NO_SYMBOL_REQUIRED", "STANDARD", "", "NO_AUTO_CREATE", "NO_AUTO_UPDATE")
print unicode(arcpy.GetMessages()).encode("iso-8859-2", "replace") + "\n"
And here are the errror messages: GP ERRORS: ERROR 000021: Failed to create the output annotation feature class Failed to execute (ImportCADAnnotation). PYTHON ERRORS: Traceback Info: File "D:\workspace\Scripts\cadastre\_pour_v_\_Outils_\Scripts\Copie de 01_urb_cad_projete_chargement.py", line 78, in <module> arcpy.ImportCADAnnotation_conversion(';'.join(lst_anno_lyrs), tmp_an, 1000, "ONE_CLASS_ONLY", "NO_MATCH", "NO_SYMBOL_REQUIRED", "STANDARD", "", "NO_AUTO_CREATE", "NO_AUTO_UPDATE") Error Info: <class 'arcgisscripting.ExecuteError'>: ERROR 000021: Failed to create the output annotation feature class Failed to execute (ImportCADAnnotation). I noticed that the Make Feature Layer (Data Management) documentation at both versions mentions the following limitation regarding the <in_features> parameter: "Complex feature classes, such as annotation and dimensions, are not valid inputs to this tool." I have also experimented with using the python list directly for the input_features parameter, but I still get the same error. The output workspace is a PGDB for the relavant version (9.2 vs. 10). Cheers for any insight!
... View more
02-21-2013
10:49 AM
|
0
|
2
|
948
|
POST
|
The problem stems from a bug in the Append Annotation Tool. The error occurs when appending to ArcSDE annotation FCs with user defined numeric (ex. Short Integer, Long Integer, Double) fields. The error seems to be resolved in ArcGIS 10 as I am able to execute the tool without issues given the exact same data. As a work around with ArcGIS 9.2, I am forced to define my field as a text field and deal with the conversion through code for my use case.
... View more
12-17-2012
05:00 AM
|
0
|
0
|
177
|
POST
|
ArcGIS 9.2/ArcSDE 9.2/Oracle 10g I am trying to append an anno fc from a pgdb to an existing, versionned ArcSDE anno fc and I keep getting the following error : DBMS table not found[DBMS table not found[ORA-00942: table or view does not exist ][GEO.urb_cadproj_an.DOSSIER_MRN_1]] The pgdb and ArcSDE anno fc's have the exact same schema and neither of them are feature-linked. I am able to successfully execute the operation with the exact same data writing to a pgdb and fgdb but not ArcSDE. The only thing special about my anno fc is the fact that it has an extra field "DOSSIER_MRN" in addition to the default system annoation fields. If I copy paste the ArcSDE anno fc and remove the "DOSSIER_MRN" field, the command executes successfully. It seems as though the append operation hangs if there are extra, user defined fields when appending to an ArcSDE anno fc? Has anyone had success appending into an ArcSDE anno fc with user defined fields via the Append Annotation Feature Classes Tool? Any ideas?
... View more
12-10-2012
07:30 AM
|
0
|
1
|
402
|
POST
|
Same issue here. The results seem fine, but I get the same "To ensure a correct reclassification, edit ranges or use a different precision settings in the Reclassification dialog box." message.
... View more
08-09-2012
12:24 PM
|
0
|
0
|
200
|
POST
|
Another straightforward workaround to try is the Clip_management tool. Since it's outside the Spatial Analyst toolbox, it's going to probably work better with a wider collection of raster input types. Clip_management has a nice feature: it is set up to snap by default to avoid resampling. This is definitely the simplest, most straight forward solution. Hopefully some day ESRI will consolidate redundant tools. Unfortunately, in my case, the Clip_management tool at version 9.2 doesn't have the clipping_geometry parameter.
... View more
08-08-2012
04:15 AM
|
0
|
0
|
1580
|
POST
|
I am having the same problem with the Extract By Mask tool: http://gis.stackexchange.com/questions/30963/output-raster-extents-when-using-the-spatial-analyst-extract-by-mask-tool-to-cli As a work around for my use case, I ended up exporting each record in my polygon mask fc to a separate fc to use as the in_mask_data parameter in the Extract By Mask call. This works, but it is frustrating to have to add an intermediate process to workaround the shortcomings (bug?) of the Extract By Mask tool.
... View more
08-07-2012
08:01 AM
|
0
|
0
|
1580
|
POST
|
I just discovered the following tool: http://cyri.systemrequirementslab.com/cyri_if/1186/10913 on the following ESRI page: http://resources.arcgis.com/content/3dgis/10.0/optimize
... View more
03-22-2011
04:35 AM
|
0
|
0
|
174
|
POST
|
We are in the process of researching new hardware for GIS use and I love to hear about your personal experiences with various hardware configurations. What hardware elements are the most important to consider for 3D GIS use - RAM, Processor, Graphics Card, Setup/Configuration etc. I have read the following link: http://resources.arcgis.com/content/arcgisdesktop/10.0/arcgis-desktop-system-requirements However, I haven't found much recent information for 3D specific requirements/recommendations. Cheers
... View more
03-22-2011
04:09 AM
|
0
|
1
|
2167
|