Latest Contributions by BrentEdwards

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

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

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

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

This would be provide users with the ability to generate standardized PDFs directly from ArcMap. ... View more