|
POST
|
Would still be nice to have a way to code defensively against the api not loading , regardless of where it is being served from. Might be nice to even have it try a backup locale if the initial is not working.
... View more
10-31-2012
09:59 AM
|
0
|
0
|
1019
|
|
POST
|
I seem to recall around the 2.0 days when we wanted to host it locally you had to contact esri and they would send you a dvd and it was an installation process on your server. That seems like overkill when you consider it is really just a text file is it not?
... View more
10-29-2012
12:13 PM
|
0
|
0
|
1019
|
|
POST
|
Anyone know of a good way to defensively code against Esri's host being down for the js api (like today)? I would rather have my site fail gracefully but don't really know how to handle that. right now it just hangs and i get firebug errors eventually about dojo is not defined.
... View more
10-29-2012
11:40 AM
|
0
|
5
|
1836
|
|
POST
|
yeah, its json that the js api creates when a user digitizes within my app. now that the rest endpoint has the schema (via the value in python) it fills in all of that for me when i go to the execute method. it leaves the features as a [] so that i can drop my geometry representation in there. I don't put in any attributes because this is just a sketch the user makes and the script is to validate that the geometry is acceptable before dumping it in. I suppose i could trim my schema down to have the bare attributes rather than those of the target feature class that the feature is destined for. I'll give that a try and see how it shakes out. I'm not interested in attributes for this gp tool, just want the geometry.
... View more
10-26-2012
05:57 AM
|
0
|
0
|
682
|
|
POST
|
I just noticed that in the docs after i posted. I used a lyr file and now in arcmap i do see the new feature template so i am able to digitize in arcmap, so that's cool. but when i publish the tool and send it a feature via the rest interface i get an error: Unable to complete operation. The workspace is not connected. I really don't need any of the schema i'm simply sending in coordinate sets for a polygon. I'm using that in the tool to do an intersection and then return a specific string out of the tool. Is the feature set overkill for what i need? I'm publishing from my ags web manager machine over to my ArcServer machine by creating a disconnected sd file. Maybe something isn't being copied during the publish process properly?
... View more
10-25-2012
03:10 PM
|
0
|
0
|
682
|
|
POST
|
I'm converting some 10.0 python code into a 10.1 python toolbox. One of my parameters is a Feature Set. in my 10.0 code if i run this in arcmap i get the interactive buttons to digitize a shape in 10.1 i don't get this option. i just get the layers in the map or a folder icon to load other layers. I think this has something to do with the schema. this is an input parameter. in 10.0 world i would have used catalog to point this tool at a dummy schema just to get it stubbed out. At 10.1 i think it is supposed to work differently but i can't figure it out and i don't see enough in the docs to help me. there is alot of stuff in the docs about schema for output fs params, mine is input. i want to serve this script as a gp tool in ags. the app would upload features in a format that the fs param can understand. i saw something in the doc about needing geometryType and fieldRule params but i could use a working code sample. here is what i have thus far (this is in a python toolbox): class TestTool(object):
def __init__(self):
self.label = "TestTool"
self.description = "TestTool"
self.canRunInBackground = False
def getParameterInfo(self):
#Feature Set you pick a layer or load a layer
param0 = arcpy.Parameter(
displayName="aFeatureSet",
name="aFeatureSet",
datatype="Feature Set",
parameterType="Required",
direction="Input")
#param0.value = ""
param1 = arcpy.Parameter(
displayName="aString",
name="aString",
datatype="String",
parameterType="Required",
direction="Input")
param1.value = ""
params = [param0, param1]
return params
def isLicensed(self):
return True
def updateParameters(self, parameters):
return
def updateMessages(self, parameters):
return
def execute(self, parameters, messages):
#do stuff
... View more
10-25-2012
01:36 PM
|
0
|
4
|
2966
|
|
POST
|
I typically do not check the "include data in" box under the no available connection. But then you need to make sure that the data sources in your mxd are registered with ags.
... View more
10-23-2012
05:43 AM
|
0
|
0
|
362
|
|
POST
|
Ugh. Not good news. I wonder if they stuck the fix in the next sp. which is supposed to be released in October although we only have one week left.
... View more
10-23-2012
05:40 AM
|
0
|
0
|
755
|
|
POST
|
I have a custom projection so i'm trying to use wkt instead of wkid. I see in the js api docs that they provide an example template for wkt. Problem is that when i use that format i get a json serialization error and the Post is never even handled. I'm trying to post to a 10.1 REST api endpoint to AddFeatures. If i drop the spatial reference i get errors from Oracle about sr issues. So i think i need it but i'm packaging the sketched feature from the api into my own payload going to the server and i think that is where the serialization is getting disrupted. json is picky about double and single quotes. Anyone experience this issue and know some kind of workaround? Like maybe tacking the spat ref on just before the request is sent or something like that? Or maybe another way to create the wkt in js? Also is it possible to create my own custom spat ref on the server so that i do have a wkid (albeit a custom one that i create)?
... View more
10-22-2012
12:35 PM
|
0
|
1
|
1131
|
|
POST
|
in my experience you can keep upgrading your client side api without upgrading your ags. But you need to be careful not to try to use functionality that is not supported by your ags. the docs do a good job of pointing out these areas.
... View more
10-11-2012
06:00 AM
|
0
|
0
|
361
|
|
POST
|
Yes, but you have to use caution when you try to implement the api. The docs do a good job of explaining when certain functionality was added and what level it is supported at. For example, you cannot use features in the api that are for ags 10.1 if you have ags 10.0.
... View more
10-11-2012
05:58 AM
|
0
|
0
|
514
|
|
POST
|
Did you try to tweak the page compatibility settings in IE? Hit F12 to bring up the dev toolbar and try to change the compat mode. If you find a mode that works you can use a tag like <meta http-equiv="X-UA-Compatible" content="IE=8" /> in your browser page to force IE down.
... View more
10-11-2012
05:57 AM
|
0
|
0
|
964
|
|
POST
|
I would say yes. In my experience all of the older apis support newer ags frameworks. I think esri has done a good job of adding functionality first at the ags level and then supporting it at the api level, all while maintaining backward compatibility. So a new feature in ags will be supported in a new version of the js api but will not break in an older version of the api.
... View more
10-11-2012
05:55 AM
|
0
|
0
|
514
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-03-2012 10:21 AM | |
| 4 | 01-02-2018 12:11 PM | |
| 1 | 01-04-2011 07:47 AM | |
| 2 | 09-05-2012 05:48 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-11-2020
02:23 AM
|