Latest Contributions by BenWilder

‎12-06-2021

Hi Luke, No, I have never been able to get saved .cal files to work. I have to copy and paste out of Notepad like Dan suggested. Thanks for asking.

‎09-11-2021

Thank you, Dan! I typically, have these files saved with the .cal extension so I can load them in Field Calculator. I tried saving the file out of Notepad++ to a .cal file. That doesn't work. I can copy the code block from either Notepad++ or Notepad and the script runs normally. Thank you for pointing me in the right direction.

‎09-11-2021

Using ArcMap 10.8.1 The following Python script ran successfully about 3 weeks ago. I wrote the script in Notepad. Then saved it from the Field Calculator. Load it today and I get: Error 000539: Runtime error Syntax Error: encoding declaration in Unicode string (<string>, line 0) Notepad shows the file is encoded UTF-16 LE. I have read that Python uses UTF-8 by default. I have tried (based on suggestions on other forums) using a coding syntax like: # _*_ coding: UTF-16 LE _*_ in first line of the Pre-Logic Script Code but that doesn't work and I don't really know what I am doing with that. Seems like something basic is fouling the script up. Thanks for your suggestions. Attached: screen shot of the Field Calculator window. Script: def Blockname(Species): if Species = "Olneya tesota": return "PINV-OT" elif Species = "Parkinsonia florida": return "PINV-PF elif Species = "Parkinsonia microphylla": return "PINV-PM else: return "NA" __esri_field_calculator_splitter__ Blockname(!Species!)

‎03-10-2020

Five months later and I have this exact same question. Did you ever figure out how to use an edited basemap in ArcMap?

‎08-24-2018

Hi Everyone, I contacted ESRI support on this issue. It is a known bug in ArcGIS Desktop 10.6/10.6.1. Below is the response from ESRI tech support. I uninstalled 10.6 and reinstalled 10.5.1 and the export files work perfectly with the right block objects and attributes visible in AutoCAD. ESRI says that they support up to AutoCAD version 2017 with format (dwg) version 2013. I created the seed file in AutoCAD 2018 and saved to .dwg format 2013. The ArcGIS output file opens fine in 2018 and 2019. I haven't created any seed files in AutoCAD 2019, but it seems like it would work as long as you save to .dwg 2013 format. Ben =========================== Response from ESRI Tech Support =========================== As I mentioned in my voicemail message, I have taken ownership of this case and I am very sorry that you are running into BUG-000112999 that was logged to report that Export to CAD does not create BLOCK entities properly, along with attributes in the output CAD file at version 10.6 of ArcGIS Desktop. This process did work correctly in ArcGIS Desktop 10.5/10.5.1, and allows exporting to AutoCAD DWG format through 2017. That is the latest version of AutoCAD DWG or DXF format files that is supported in ArcGIS Desktop. AutoCAD files through 2017 are supported in ArcGIS Desktop 10.5 and 10.6. In order to run this Export to CAD process, using a seed file, the seed file must be the same version as that selected for the output DWG or DXF file, or the process will not produce correct results. Here is a link to the supported CAD formats from ArcGIS Desktop 10.6/10.6.1: http://desktop.arcgis.com/en/arcmap/latest/manage-data/cad/supported-cad-formats-in-arcgis.htm The supported formats for 10.5/10.5.1 are slightly less extensive: http://desktop.arcgis.com/en/arcmap/10.5/manage-data/cad/supported-cad-formats-in-arcgis.htm AutoDesk Corp. does not share their libraries with Esri. Esri purchases libraries to read and write AutoCAD files from a 3rd party vendor, then incorprorates those files into our software. This is of course a time consuming process, and explains why Esri does not yet support AutoCAD r2018 DWG or DXF file formats.

‎07-16-2018

I have AutoCAD 2018 on my computer. I haven’t updated it since my previous successful Export to CAD operations. On the other hand, I did reinstall ArcGIS 10.5 (I incorrectly indicated I had upgraded from 10.4 in the original post) and I still cannot get it to work. Perhaps of interest, it fails differently. 10.6 substitutes a generic circle in place of my custom block drawing. 10.5 doesn’t place any shape or point in the Insert process. 10.5 does create the layer the points / blocks should be on. Like you, I am stuck.

‎07-11-2018

Exporting a point feature class to .dwg using a seed file that contains 9 different block definitions. Block definitions have attributes that correspond to field names in the feature class. Same procedure I successfully used 6 months ago in ArcMap 10.4. Upgraded to 10.6 yesterday. I have not tried reinstalling the older ArcMap version, not sure if that is relevant at all. The issue: In CAD, the exported feature class appears with generic circle blocks, not the custom Block shapes I have created in the seed file. The properties of the newly created (exported from ArcMap) blocks indicate the right name of the various blocks--the same name that is assigned in the RefName column of the feature class, but, none of the attribute information appears in the properties window in CAD. Also, the Block Unit has changed from 'feet' to 'Unitless' (If I load the ArcGIS for AutoCAD app, I can view the attribute table using those tools, but that add-on has not been required in the past.) Clearly something in the Export to CAD is not working. Hoping someone else has encountered similar issues and can suggest where I should look.

‎08-14-2017

Hi Scott, How do I PM you? I tried to Send Message on GeoNet, but I can’t because you aren’t a connection. Can’t find an e-mail for you either. By the way, I am following you, so you could Message me back, if you like. Thanks, Ben

‎08-14-2017

Thanks for the reply, Scott. And thanks for the detailed explanation. I hadn’t heard about Survey123. Does that come with ArcGIS Desktop? Or is that a product I need to purchase? I will take a look. Sincerely, Ben

‎08-13-2017

This seems like an obvious feature request that wouldn't need a usage case defense, but here it is anyway. When we are out surveying plants on parcels slated for the dozer, the municipalities request information about which significant trees can be transplanted or not. In the case of not, there are several reasons why, and more than one can apply. Currently we have to use a field for each reason, i.e. reason1, reason2, reason3 and so on. So, our collection form for each plant would read: Disposition (This is a single-choice domain field) -------------- Transplant Remove Reason for Transplant (This is a multi-select) Poor health Low-branching Sandy (uncohesive soil) Multi-trunked Form not suitable Adjacent plants The comment above that includes a graphic showing a "Select All" is a great idea.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by BenWilder

Re: Using code block with Field Calculator error 000539

Re: Using code block with Field Calculator error 000539

Using code block with Field Calculator error 000539

Re: How do I open edited basemap in ArcMap??

Re: Export to CAD with Seed File - Block Shape and attributes

Re: Export to CAD with Seed File - Block Shape and attributes

Export to CAD with Seed File - Block Shape and attributes

Re: Add multi-select to Collector for ArcGIS dropdowns

Re: Add multi-select to Collector for ArcGIS dropdowns

Re: Add multi-select to Collector for ArcGIS dropdowns

Re: Using code block with Field Calculator error 0...

Export to CAD with Seed File - Block Shape and att...

Re: Add multi-select to Collector for ArcGIS dropd...

Re: Add multi-select to Collector for ArcGIS dropd...