POST
|
I'm trying to find more information about this capability. I'm aware of the arcpy function WFSToFeatureClass_conversion and it looks like the equivalent in the Java SDK is WFSToFeatureClass but I haven't found specifics about the limitations or impacts to availability using these tools/API have. For example, I assume this essentially imports a WFS feature and its Feature Class from one datasource into my ArcGIS geodatabase, but if the Feature Class name already exists in my DB but the fields are different, how is that handled? Is it possible to limit which fields in a new FC are created from the WFS feature so that only a subset are created or do I have to create a subtype to do that after the FC is created? If these questions are already answered somewhere and I've missed them, I'd appreciate a pointer in the right direction. Thank you
... View more
08-13-2016
10:08 AM
|
0
|
2
|
2416
|
POST
|
Thank you! Yes, I missed it and thank you for the help.
... View more
08-05-2016
11:26 AM
|
0
|
0
|
4473
|
POST
|
I believe this is a super basic question but I'm not having any luck so far and I am just learning all of this. When I am running a custom tool scripted in python using the ArcCatalog, how do I read in the current workspace environment so I can use it in my script? This assumes before I run the script, I've clicked on the "Environments..." button and entered in the appropriate values for the current workspace and scratch workspace, etc. For parameters, I use something like arcpy.GetParameterAsText(0), but how do I get the environment values that were provided in the script launch window? Every example I find expects me to use something like arcpy.env.workspace = "c:/data/data.mdb", using a hard-coded path. I could create a parameter for the workspace too but it seems like I should be pulling the workspace from the configured environment. Am I going about this wrong? Thanks
... View more
08-05-2016
11:07 AM
|
0
|
2
|
6792
|
POST
|
These sound like good ideas. Thank you. I have a scalable workflow that uses services/capabilities that do not run on the ArcGIS server itself. I'd like to avoid having to write additional code to bridge the gap from one set of servers running in the cloud to reach back to my windows server just to access an arcpy script that creates feature classes. If there already exists a REST endpoint (for example) in ArcGIS for creating feature classes, then I have less work to do and can omit putting a service wrapper around arcpy running on Windows just to expose management type capabilities to my workflow. It doesn't have to be REST, but just some kind of API that I can access remotely. I'll take a look at your suggestions. Thanks
... View more
08-01-2016
11:49 AM
|
0
|
0
|
539
|
POST
|
Hi, I'm aware of using arcpy to programmatically create feature classes, but are there other options? I'm interested in a RESTful endpoint specifically. Thanks
... View more
08-01-2016
10:39 AM
|
0
|
4
|
1859
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|