Latest Contributions by Tim_McGinnes

@MichaelVolz I was planning to semi automate this - on demand at the moment. From looking at the logs, you shouldn't need to manually stop the service as the overwrite process handles it all. That Updating Geocoding Services script in my original post already works in Pro & Python 3.6. Here's a great video with various options for updating locators and services where that script is discussed: https://community.esri.com/t5/devsummit-conference-videos/updating-your-locator-service/m-p/976744  ... View more

@JayantaPoddar , I have narrowed down the error to ArcGIS Server being unable to rename the service. This occurred regardless if I manually stopped the service prior to doing the overwrite, or if ArcGIS Server automatically stopped the service during the overwrite. Here are some logs of both scenarios. Creating the Locator service then overwriting it: Overwrite Locator_YYY Service VERBOSE Job 'j245c93962c164bd58f60ef87eaf56eda' for service 'System/PublishingToolsEx' completed its execution. The status of the job after completion was 'esriJobFailed'. Elapsed time '25644' ms. 2021-03-26T20:29:01 Server SEVERE Error executing tool. PublishServiceDefinition Job ID: j245c93962c164bd58f60ef87eaf56eda : ERROR 001369: Failed to create the service. (more) 2021-03-26T20:29:01 System/PublishingToolsEx.GPServer VERBOSE Execute job j245c93962c164bd58f60ef87eaf56eda 2021-03-26T20:29:01 System/PublishingToolsEx.GPServer VERBOSE End execute 2021-03-26T20:29:01 System/PublishingToolsEx.GPServer INFO Deleted the item 'i038f087b-77dd-4694-bb6a-68537ec31ae0' successfully. 2021-03-26T20:29:01 Admin SEVERE Failed to create the service.: ERROR: code:500, Failed to rename service 'Locator_YYY.GeocodeServer'., Internal server error. 2021-03-26T20:29:01 System/PublishingToolsEx.GPServer FINE End create service wrapper 2021-03-26T20:29:01 System/PublishingToolsEx.GPServer VERBOSE Released 'service-locator_yyy_202103262028.geocodeserver' workflow lock. 2021-03-26T20:29:01 Admin VERBOSE Released 'service-locator_yyy.geocodeserver' workflow lock. 2021-03-26T20:29:01 Admin SEVERE Failed to rename service 'Locator_YYY.GeocodeServer'. 2021-03-26T20:29:01 Admin FINE Shutting down an instance of service 'Locator_YYY.GeocodeServer'. 2021-03-26T20:28:36 Locator_YYY.GeocodeServer FINE Shutting down an instance of service 'Locator_YYY.GeocodeServer'. 2021-03-26T20:28:36 Locator_YYY.GeocodeServer VERBOSE Acquired 'service-locator_yyy.geocodeserver' workflow lock. 2021-03-26T20:28:36 Admin VERBOSE Stopping the service 'Locator_YYY.GeocodeServer'. 2021-03-26T20:28:36 Admin INFO Service to publish: [name: Locator_YYY; type: GeocodeServer]. 2021-03-26T20:28:36 System/PublishingToolsEx.GPServer VERBOSE Job j245c93962c164bd58f60ef87eaf56eda is successfully submitted. 2021-03-26T20:28:35 System/PublishingToolsEx.GPServer Create Locator_YYY VERBOSE Job 'j09315681d0ba4a9abff4246a7955a24e' for service 'System/PublishingTools' completed its execution. The status of the job after completion was 'esriJobSucceeded'. Elapsed time '25076' ms. 2021-03-26T20:13:20 Server INFO Service published [name: Locator_YYY; type: GeocodeServer]. 2021-03-26T20:13:17 System/PublishingToolsEx.GPServer INFO Service 'Locator_YYY.GeocodeServer' was created successfully. 2021-03-26T20:13:10 Admin INFO Service to publish: [name: Locator_YYY; type: GeocodeServer]. 2021-03-26T20:12:57 System/PublishingToolsEx.GPServer VERBOSE Job j09315681d0ba4a9abff4246a7955a24e is successfully submitted. 2021-03-26T20:12:55 System/PublishingTools.GPServer Creating the locator service, manually stopping the service, then overwriting it: Overwrite Locator_AAA Service VERBOSE Job 'jc09b7e8d949c41ef8750e7237f9d9d85' for service 'System/PublishingTools' completed its execution. The status of the job after completion was 'esriJobFailed'. Elapsed time '27614' ms. 2021-03-27T08:55:49 Server SEVERE Error executing tool. PublishServiceDefinition Job ID: jc09b7e8d949c41ef8750e7237f9d9d85 : ERROR 001369: Failed to create the service. (more) 2021-03-27T08:55:49 System/PublishingTools.GPServer SEVERE Error executing tool. PublishServiceDefinition Job ID: ja56785d59ca7429390142f914c288b7c : ERROR 001369: Failed to create the service. (more) 2021-03-27T08:55:47 System/PublishingToolsEx.GPServer VERBOSE Execute job ja56785d59ca7429390142f914c288b7c 2021-03-27T08:55:47 System/PublishingToolsEx.GPServer VERBOSE End execute 2021-03-27T08:55:47 System/PublishingToolsEx.GPServer INFO Deleted the item 'i50bc29e8-722f-4bc6-b531-3201340105b1' successfully. 2021-03-27T08:55:47 Admin SEVERE Failed to create the service.: ERROR: code:500, Failed to rename service 'Locator_AAA.GeocodeServer'., Internal server error. 2021-03-27T08:55:47 System/PublishingToolsEx.GPServer FINE End create service wrapper 2021-03-27T08:55:47 System/PublishingToolsEx.GPServer VERBOSE Released 'service-locator_aaa_202103270855.geocodeserver' workflow lock. 2021-03-27T08:55:47 Admin VERBOSE Released 'service-locator_aaa.geocodeserver' workflow lock. 2021-03-27T08:55:47 Admin SEVERE Failed to rename service 'Locator_AAA.GeocodeServer'. 2021-03-27T08:55:47 Admin WARNING Unable to process request. Error handling service request :Could not find service. Service may be stopped or it may not be configured. 2021-03-27T08:55:40 Rest INFO Service to publish: [name: Locator_AAA; type: GeocodeServer]. 2021-03-27T08:55:23 System/PublishingToolsEx.GPServer VERBOSE Job jc09b7e8d949c41ef8750e7237f9d9d85 is successfully submitted. 2021-03-27T08:55:21 System/PublishingTools.GPServer Stop Locator_AAA Service VERBOSE Released 'service-locator_aaa.geocodeserver' workflow lock. 2021-03-27T08:51:47 Admin VERBOSE Stopping the service 'Locator_AAA.GeocodeServer'. 2021-03-27T08:51:46 Admin FINE Shutting down an instance of service 'Locator_AAA.GeocodeServer'. 2021-03-27T08:51:46 Locator_AAA.GeocodeServer VERBOSE Acquired 'service-locator_aaa.geocodeserver' workflow lock. 2021-03-27T08:51:46 Admin Create Locator_AAA VERBOSE Job 'je99488525f97409f8d54f9b88cf63875' for service 'System/PublishingTools' completed its execution. The status of the job after completion was 'esriJobSucceeded'. Elapsed time '25411' ms. 2021-03-27T08:49:42 Server INFO Service published [name: Locator_AAA; type: GeocodeServer]. 2021-03-27T08:49:40 System/PublishingToolsEx.GPServer INFO Service 'Locator_AAA.GeocodeServer' was created successfully. 2021-03-27T08:49:32 Admin INFO Service to publish: [name: Locator_AAA; type: GeocodeServer]. 2021-03-27T08:49:18 System/PublishingToolsEx.GPServer VERBOSE Job je99488525f97409f8d54f9b88cf63875 is successfully submitted. 2021-03-27T08:49:16 System/PublishingTools.GPServer   ... View more

Are you trying to find if they match exactly to one of the other layers (ie vertices are the same) or are they close enough within a tolerance? Would be good to see a screenshot of the data as well. I would start with the following: Polygon To Line tool - Convert Polygon A to lines. Use the IDENTIFY_NEIGHBORS option so that you don't get multiple overlapping lines. Split Line At Vertices tool - convert the lines from above into individual segments. Add a field to hold the results from the next section (Text length 2 for example) For each polygon boundary layer: Convert it to lines with the Polygon To Line tool. Buffer the lines by your tolerance distance. Use the Select By Location tool to select all the individual Polygon A segments that are COMPLETELY_WITHIN the buffer. Use the Calculate Field tool to set the result field for all the selected records to 'OK' When you have finished, all the individual segments that were not within the buffers (and therefore did not overlap with any other polygon boundaries) should have NULL in the result field - Select by <field> IS NULL. ... View more

I am using Pro 2.7.2 with the Deep Learning Framework installed using the esri installer. I was able to complete that road surface investigation sample ok without any problems. It could be a problem with your input data. The prepare data function expects a folder with 2 subfolders called images and labels In the images folders should be all your images eg: Adachi_20170906093835.jpg In the labels folder, you should have a corresponding xml label file for each image with the same name eg: Adachi_20170906093835.xml Each XML file should have something like the following: <annotation> <folder>Adachi</folder> <filename>Adachi_20170906093835.jpg</filename> <size> <width>600</width> <height>600</height> </size> <segmented>0</segmented> <object> <name>D20</name> <bndbox> <xmin>87</xmin> <ymin>281</ymin> <xmax>226</xmax> <ymax>432</ymax> </bndbox> </object> </annotation> Are your XML files the same format as this? What format and width\height are your images? ... View more

That's interesting - some undocumented functionality? The JSON response should give you the item id of the saved excel file: { "type":<type of the exported item>, "size":<size of the exported item>, "jobId":<jobId for the export job> "exportItemId":<id of the exported item that is created>, "serviceItemId": <id of the hosted feature service item that was exported>, "exportFormat": <exportFormat> }  I think it gets saved into the same user folder? ... View more

Not that I know of - you may have to script it in your language of choice or maybe FME if you have it? I think that long running REST processes with large attachment layers are just problematic. We have had lots of issues with replication of these types of layers as well. Scripting small batch extracts with lots of error checking and retrying on failure seems like the best option to me. ... View more

This article explains how to export from the rest endpoint using smaller batches of records. That should have a much better chance of working. https://support.esri.com/en/technical-article/000014156  ... View more

I have had something strange happening that sounds sort of similar. Also editing polygons in Pro. Sometimes the feature I just edited disappears when clicking outside or clearing the selection. The row is still in the attribute table but no matter how I zoom or pan or refresh the view it will not display. If I save my edits, remove the layer and add the layer back in the feature now displays. This has happened 5 or 6 times now but I cannot force it to happen. I am using Pro 2.7.2. I have also once had the feature remain on the screen, even when I remove the layer. It does not disappear, even after zooming\panning. I had to delete the map to get it to disappear. I imagine this sort of problem would be quite hard to track down, maybe a memory or cache corruption issue?. Anyone else experiencing strange things? ... View more

Well it's a slightly different error this time. My only suggestion now would be to go back to using the default Python environment (arcgispro-py3). What did you mean when you said it was "unable to read the dlpk"? I am also on Pro 2.7.2, and used the deep learning framework from the installer and using the default environment. ... View more

By default the Landsat service will show you a 3 band combination, but the deep learning model expects 7 bands. In the properties of the Landsat service under Processing Templates, you need to set the Processing Template to None. Worked for me ok once I did that. You should probably set your required extent in the environment variables as well. ... View more

Can you provide some more information to assist with diagnosing the problem - - ArcGIS Pro version & how you installed the deep learning components - Screenshot of the Messages in the geoprocessing output (it's down the bottom) - Information on the input raster you are using - Type, Bands, Bits per Pixel, Columns, Rows, Coordinate System etc. ... View more

Just some further thoughts - you have already recognized that disaggregating data using population\building footprints has issues, because not all buildings are residential. Using land use to assist is good, but what happens when you get mixed land use areas (which are really common) such as commercial\residential? One factor you may not have considered is that each footprint may not necessarily be one family - what about high density multi-story buildings with hundreds of people in a single footprint? Your hexagons are very small relative to the overall area. The smaller you make them, the more chance of errors during the disaggregation. It wouldn't be hard to pick out some individual hexagons that are not correct and cast doubt on the entire map. It all comes down to the purpose of your mapping - if it is being used for policing, healthcare, policy making, strategic planning etc. then it might be quite important to ensure the results are accurate. ... View more