Open slibby opened 6 years ago
@slibby @ecaldwell @rwmajor2 I'm beginning to work on this in my own fork. Can you test this and let me know if you think I'm headed in the right direction?
If so, I'll create a new PR and we can go from there.
I also added the progress as a notification, so you can continue to use ago-assistant for other stuff while the copy is in progress. In addition to that, I made the browser warn you before navigating away from the page if a copy is in progress. @slibby Should you add these to your list above?
@hogpilot looking good so far! I like the time estimate too.
One thing I thought of - I think there's an issue here where duplicating the service is going to reorder all your rows when you send simultaneous addFeatures requests - because any one of them may come back first, those rows become the first rows in the table.
I also noticed that it is not using the maxRecordCount from the source during queries to the source layer.
Also, is it possible to update the right-side view to show the new feature service with the proper info (Type, Item ID) like the other features, but still keep it Green with Copy Successful
?
It's time for some UX improvements to Deep Copying Feature Services, which works very well now but has some failure issues with large numbers of features or highly-complex geometries.
maxRecordCount
of the source service, request that many features from the source service with each/query
requestcc @hogpilot References content from #172