|
POST
|
Interesting: 1) 'C:\\Program Files (x86)\\ArcGIS\\Desktop10.1\\arcpy', to get 'arcpy' to import 2) 'C:\\Program Files (x86)\\ArcGIS\\Desktop10.1\\bin', to get pythonaddins to import 3) 'C:\\Program Files (x86)\\ArcGIS\\Desktop10.1\\ArcToolbox\\Scripts' to get some toolboxes / my custom Addin working Do you have a file "desktop10.1.pth" @ C:\Python27\ArcGIS10.1\Lib\site-packages ? This Python path file which gets put down by Desktop has those 3 references. Since you've manually created those, it sounds like you might not have it. The same exists @ C:\Python27\ArcGISx6410.1\Lib\site-packages for 64bit background, with a file called "DTBGGP64.pth"
... View more
03-12-2013
07:26 AM
|
0
|
0
|
2215
|
|
POST
|
I want to say the steps you've taken are not normal. On a brand new machine after you install Desktop, and 64-bit Background, thats it. No environment variables, no Python path settings, nothing like you've needed to do. For me to document a "fix" (like in your case), I'd need to be able to reproduce the problem so I can fully understand it. I still haven't found a way to "break" the Python window by having 64-bit Background and changing a combination of environment variables. I'm glad you figured it out. Your well documented answer is good in case someone else encounters this situation. I'll spend a little bit more time trying to reproduce, but like I said, so far I've been unsuccessful - it all just works.
... View more
03-11-2013
08:10 AM
|
0
|
0
|
4615
|
|
POST
|
I dont have detailed information on the OLEDB story but I do know we're working to support them in 64bit to some degree (I dont know if thats 100% of what we did in 32bit or just some part of that full support). In Server 10.2 we've made progress and you can use it as a datasource (Server 10.1 you cannot). I'm still working on the 64bit Background story. So: when we move to 64bit (all products), it will hopefully be a none issue (ie, we're working that out right now in the 64bit products we have)
... View more
03-08-2013
10:07 AM
|
0
|
0
|
3640
|
|
POST
|
Sounds like you might be using 64bit Background Processing. Excel as an input data type isn't supported there. If you have it installed, I'd give a quick read of http://resources.arcgis.com/en/help/main/10.1/#/Background_Geoprocessing_64_bit/002100000040000000/
... View more
03-08-2013
07:49 AM
|
0
|
0
|
1192
|
|
POST
|
Ok cool. Just to get you started, check out these Python scripts which create excel output: http://www.arcgis.com/home/item.html?id=f3d91b8f852042e289e09a7ec8342431 You just may need to tweak the inputs or take the tool as-is and combine it with another tool for getting your data into it. Once you got the tool / service, its just a matter of including it in a webapp and it sounds like you've got a good grasp on that.
... View more
03-06-2013
09:35 AM
|
0
|
0
|
1391
|
|
POST
|
John, I just came across this thread, maybe give it a read: http://forums.arcgis.com/threads/75553-SOLVED-Error-8273-geoprocessing-services-crashing-on-SOM-start-and-not-restarting In short > check your registry to see where your system "thinks" Python lives...
... View more
03-06-2013
06:33 AM
|
0
|
0
|
4615
|
|
POST
|
I can't speak from the JavaScript (other web languages) > Excel point of view (there might be solutions that do this). I can tell you from a Geoprocessing Service point of view that you can certainly send features/rows to a geoprocessing service and create either a CSV or .XlS file. The GP Service would send that file back to your web application and your user can download that. You've got a couple questions here. To answer the "getting the file back" - your GP Service (most likely a python script) would create a .XLS file. The tool (gp task) would return a file. In your say, JavaScript based web app, you'd invoke the service and the GP Service would return the file. Check out the clip and ship sample. This demonstrates executing a task that returns a file. The part of your question I'm unsure of is whats happening on the web client (which sounds like it sends data?) to the GP Service which in turn gets turned into excel? Theres multiple ways to interact with GP via the web in regards to input parameters. I dont want to suggest 1 way as ultimately it depends on how you have data and how the service will accept it. For this part of your task your web development and task (python script) development will have to work together. You'll probably need to build an app that is capable of sending data in an expected way to the gp task. OR you have to build your python script to accept data and possible massage it so you can then convert it. Hope these ideas move you forward some.
... View more
03-06-2013
06:25 AM
|
0
|
0
|
1391
|
|
POST
|
I'm not entirely certain of your setup/configuration, but I can say this: inside ArcMap, Python is 32bit. I'm not really sure how you're seeing that error from the Python window. I tried changing a few settings on my machine to my 64bit Python and my PyWindow continues to work fine. I dont know much about IronPy and the settings you've shown in regards to that - I dont imagine that its a problem though. The only thing strange about the messages you've posted are: File "C:\Python27\Lib\site-packages\numpy\lib\type_check.py", line 8, in <module>
import numpy.core.numeric as _nx
File "C:\Python27\Lib\site-packages\numpy\core\__init__.py", line 5, in <module>
import multiarray The directory is pointing at c:\Python27\lib My guess here is either you've installed your own Python27 prior to installing Desktop (as well as matplotlib and numpy) or did you just change the directory it installs to while installing Destkop? If the first (you installed it) - is it possible there isn't a complete link between Desktop and Python and (again I cant imagine how) Desktop is now falling through to the only Python it can find - the 64bit one? Just checking: everything inside Desktop/Python window works fine before installing 64bit Background Processing?
... View more
03-05-2013
01:48 PM
|
0
|
0
|
4615
|
|
POST
|
Version 3.x is highly unlikely. Its possible for a move to 2.7.3, but thats not for sure just yet.
... View more
03-05-2013
01:34 PM
|
1
|
0
|
1040
|
|
POST
|
Hey Matthew, You should be able to put together a script which does the same functionality using some of the math tools or SA math/raster functions to achieve this result. After talking with a colleague on the Spatial Analyst team, she put together a few lines of Python that might get you started on this. import arcpy from arcpy.sa import * #Checkout SA extension arcpy.CheckOutExtension("Spatial") # May want to set environments Cellsize, extent, snap, and workspaces #Cast datasets as Rasters MAR = Raster("C:/data/meanannurain") #this doesn't actually need to be cast b/c it's used in a GP tool not with operators SEFR = Raster("C:/data/soilerodfact") LS = Raster("C:/data/ls") LCR = Raster("C:/data/landcover") #Universal Soil Loss Equation Result = 0.0012* (Float("MeanAnnualRain") ** 2) * SEFR * LS * LCR #Save the temperary result Result.save("C:/output/result") For reference, heres the operators you can use in SA on once you've converted to a raster object (as shown in the script): http://resources.arcgis.com/en/help/main/10.1/index.html#/An_overview_of_the_Map_Algebra_Operators/005m000000mm000000/ Or if you'd perfer, you can continue using the tools which are supported in the Runtime. The ones you're after live in this toolset here: http://resources.arcgis.com/en/help/main/10.1/index.html#/An_overview_of_the_Math_toolset/009z0000008n000000/ Hopefully this moves you forward.
... View more
02-28-2013
09:26 AM
|
0
|
0
|
1222
|
|
POST
|
No you can't use VBScript in the Runtime packages It only supports the Python parser. Unfortunately you'll have to update your expressions or remove the layers. Just a note, I think we've enhanced the error message in a newer version. When I run the analyzer, I get this title: 00174: Expression uses VBScript, this is not supported in the ArcGIS Runtime
... View more
02-26-2013
09:04 AM
|
0
|
0
|
836
|
|
POST
|
Excellent, glad you got it. I really like modelling, but some situations, like this one, scripting proves to be more straight forward. Cheers.
... View more
02-13-2013
06:11 AM
|
0
|
0
|
2225
|
|
POST
|
Ok, I dont think I have a full understanding of your workflow. Are you trying to create a service which the user will send data and have the rows removed? Or will be they using a service where the SERVER has the data, and they're simply tell the Server what FeatureClass to act against? If its the first scenario (they send it) - then go with what I described in using copy features as the first part of the tool. However the service always creates new data and sends it back. It'd be on the consumer of the service to merge or figure out how to work with the new output data. If its the 2nd scenario where the user of the service is basically trying to remotely administer a geodatabase and the featureclasses inside: you'll have to create a sort of look up and pass just simple names to the service. In this scenario I assume you'll be working against 1 to any number of featureclasses. Here you have 2 ways to do this: 1) Accept a NAME from the user, the service then uses the name to mash up paths, find the featureclass in a geodatabase, and perform the operation. (You can do this in a model, but a script might be easier) 2) Drag all the layers that a user may want to act upon into your MXD. Run your model against a layer. Publish. Inside the Service Editor, change the parameter to choice list. Finish publishing. When the user consumes the service they pick 1 or more layers from the parameter control. Both of these methods would require registering the database as a datastore (which it sounds like you've already done) Hopefully my guess at one of your scenario's is correct. If not, please explain what it is you want your users to do against what data.
... View more
02-11-2013
11:23 AM
|
0
|
0
|
2225
|
|
POST
|
After many hours with ESRI Tech Support we figured out what the problem was. I had added the "PYTHONPATH" system environment variable at some point and this confused the ArcCatalog Publishing Task so that it could not find Python. This basically sends the Publishing Task into an endless loop and you don't know what is going on and nothing is happening. For some reason you cannot publish scripts that import the os library. Scripts without that still publish. In short, DO NOT add a "PYTHONPATH" system environment variable! Why did I do it? I think I've been adding that variable for years. It was recommended to me at some point for using Python at the command line. Doh! Thanks, Dave Can you post the incident number? I want to investigate this, but I'll try to spare you from repeating your conversation with tech support again on the forums 🙂
... View more
02-11-2013
08:40 AM
|
0
|
0
|
1806
|
|
POST
|
FeatureClass is not a supported input type for GP Services - thus why you're seeing the parameter mapping to User Defined happen. You have 3 options with FeatureClass - User Defined, which is a Feature Set, choice list (which is 1 or more feature layers to chose from) or constant (hardcoded - the featureclass is on the server, but cannot be modified as a parameter choice). Using Feature Set you can pass features through (via the layer choice in the drop down) - if this doesnt work in your Service (based on the error you reference) then it might not like how its getting the features (they'll be coming in via in_memory). Sooooo... if you did Copy Features first and persisted the output of copy features to disk, then pass that into your tool - it should serve your workflow. EDIT: Yeah, I just tested this and it works. The only thing I should have been clear on : the output of copy features has to be to a file geodatabase. You cant write to shapefile as the Truncate tool doesn't like that type either.
... View more
02-11-2013
08:29 AM
|
0
|
0
|
2225
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-25-2026 08:25 AM | |
| 1 | 09-29-2025 05:19 AM | |
| 2 | 09-20-2023 06:37 AM | |
| 1 | 09-18-2025 07:07 AM | |
| 3 | 09-18-2025 06:52 AM |
| Online Status |
Offline
|
| Date Last Visited |
03-25-2026
08:04 AM
|