Latest Contributions by TedCronin

One limitation with the pass thru exception is that the data is not getting shared successfully.  Its there, just not shared by default, so that has to be handled manually which is a huge bummer, but then I guess its at least there, mostly.  Can't wait for a fix, that will be sweet. ... View more

One thing that did occur to me is that Esri has made it pretty easy to load data, but there needs to be a simple way to download data in bulk for lpk files.  It seems now I need to do this task one lpk at a time, so perhaps there could be a tool in the Package toolset that allows the ability to download multiple files to a local machine.  Perhaps a list for ListPackages in a web location, then a subsequent ability to download the lpks that are needed.  Maybe this is a GP function but it interfaces with AGO. ... View more

Isn't that what we should all be doing?  Seriously, though, I am just trying to be more efficient and update your site with the latest and greatest, and make my life easier as well. ... View more

So, there is an open api just no endpoint? ... View more

Sharing BookandPage.lpk 2011-01-13 17:57:50.598000 Sharing Condos.lpk 2011-01-13 18:01:15.692000 Sharing MineralRights.lpk 2011-01-13 18:02:56.535000 Sharing ParcelFabric.lpk 2011-01-13 18:04:00.395000 ERROR 999999: Error executing function. Failed to execute (SharePackage). Sharing ParcelLines.lpk 2011-01-13 18:32:11.520000 ERROR 999999: Error executing function. Failed to execute (SharePackage). Sharing ParcelReference.lpk 2011-01-13 19:05:33.051000 Sharing StateTRA.lpk 2011-01-13 19:09:53.082000 So, its not pretty, but so far its looking as a good to go for a workaround, in that I just downloaded Parcel Lines, and they look ok as far as I can tell (2.3 million features), currently downloading Parcels to have a look see as well.  As you see above I am passing the errors and moving on, so thats pretty cool, only problem was having to write 3 Xtra lines of code, which is just extra, but someday, perhaps I can remove them, at least I can finish this script up.  I should have thought about the try... except on my end before coming to the forums, so sorry about wasting anyones time on this issue.  At least we know there may be other issues with other large loads. Thanks Mike for your help and guidance. So, looking at the Parcels (775,000 features), they look like they are ok as well, so cool. ... View more

Can you just ignore the error in your script? In our experience, a time out can occur, but the file does upload successfully. Let me know if you find otherwise as you have quite large files. We are currently investigating various ways to fix the time out problem, but it's not resolved yet. Thanks, Mike I could if I end with this script and no processes need to be completed after through a subprocess, then after the script runs, the next day, I can manually close out of python, that may need to be the workaround, I will play with this a bit more, maybe just put in a try, except and see if that passes me through. Thank you for staying on this Mike. ... View more

My new 169 MB file just failed, so I am somewhere between 20 MB and 169MB that is the threshold that works for loading data into ArcGIS.com ... View more

What is the timeline on the endpoint? ... View more

I do see a file in My Contents, so what you are saying is it is a valid file lpk.  My issue then is, if I have a few lpks, and one happens to be large, I need to make sure that the largest is processed last, so that when I get a general 9999999999999999999 error, my script will stop but the data will be there, hardly a solution for automation.  What happens when your next releases come out that support even larger sizes for lpks, surely this is an issue that can be fixed on your end to support larger loads.  Currently, I have divided my large lpk up into 6 additional lpks to see if they will load successfully, so will be starting that shortly, I do however, have a 200 MB lpk still and a 173 MB, so there still may be issues.  There has to be a workable workaround without me having to divide my parcel and parcel line layers into chunks, clearly that is crazy. ... View more

Dude.  Thanks Mike for getting back to me. 400 MB.  I can easily load 2 11MB files.  I am using the arcpy.SharePackage method, so this may be an issue with GP, or Mapping, I may post to all three since I am not sure where this will fall.  I am also seeing some other strange limitations.  I have scripts running right now, that hopefully will allow me better insight to the issues, at least a starting point for you guys to consider which ever team I intend to go after or post issues into on these forums.  Some really peculiar behavior that may or may not be expected. This issue of a large file, when done manually used to work at 10 final (NO SP), since SP and any Online maintenance on the AGO side, not sure, so maybe there is an issue there as well.  These questions will be looked into a bit further tomorrow, most definitely. ... View more

Sounds like it has been a success, and it was really good that Esri implemented the new forum category. ... View more

 You may want to have support remote into your machine to see what is going on with your errors.  Are you referring to ArcGIS Server?  I would not agree that setting up ArcGIS is very difficult, now if you made this comment 15 years ago when it was problematic to setup Workstation then perhaps you would be onto something here.  Setting up GIS software from Esri is Very easy.  Another solution could be to use the Amazon EC2 server option.   ... View more

Weird. So, it seems like 3.2.12 fixed the issue. Another issue encountered with 3.2.9 after the SP1 install was that setting the path to a workspace, ie ENV.workspace = r"Database Connections\TestServer.sde" then running fcs = arcpy.ListFeatureClasses() try:      for fc in fcs:      print fc except:      print arcpy.GetMessages(2) was not printing the full path of the fc. It was printing aspect_c16, when it should have been printing datebase.Owner.aspect_c16. This was fixed at 3.2.12 as well. So, it appears that SP1 DID NOT fix the bug with Rasters where they are showing up when print feature classes is called, since aspect_c16 is a Raster. ... View more