I've also tried running on another workstation and had the same problem. So, I'm wondering if there is some configuration that I'm missing? I've never had any problems with tools before. I'm running completely local, no network processing. I sent them my data and they were able to get it to run just fine. I've got a case # in with ESRI support and I've done a repair on ArcGIS Desktop. I've tried several more datasets and it seems to not process more than around 70 features without freezing. I took that down even further to 2 datasets of 51 features each, and they ran through just fine without freezing. I broke it down to 102, and it freezes at 83% complete. My initial dataset was just 4,700 buildings.
Training sample manager freezing up series#
I'm on a new hp z640 workstation with 6 physical cores hyper-threaded to 12, 32 GB RAM with 1.2 TB Intel SSD 750 Series PCIe NVMe drive. Yes, I've been on your blog lately but have not run through your exact process, as I'm new to footprint extraction with ArcGIS. Khalid can help you, if you can share an example of your polygons with him.
You may also want to include a headline or summary statement that clearly communicates your goals and. When writing your resume, be sure to reference the job description and highlight any skills, awards and certifications that match with the requirements. I assume your data is in meters, for now my tool is set up to work on feet projection. Writing a great Training Manager resume is an important step in your job search journey.
I have a tool that's on my blog that might help with dividing features up into circles, small, medium and large features to process differently, Arthur’s Feature Extraction from LiDAR, DEMs and Imagery. For large datasets, I usually break it up under 100,000 and it still takes over an hour to run with 4 processors running at max. If your company has specific rules around locking up the office at night, using certain printers, and so on, that should be covered in compliance as well. Regularize Building Footprint tool is pretty intensive tool, I would try lowering the amount of input if you have over 100,000 features. How many buildings are you trying to process? What is the memory of your computer (mb) and how many processors do you have? I have been processing on a system with 32gb of ram and 4 cores. If I have issues, I usually run a Multipart to Singlepart, then a Repair Geometry. I have some questions on your data input, I regularly run about a hundred thousand features at a time.
0 kommentar(er)
