Latest Contributions by TedChapin

When the parameters of a geoprocessing service change, the only way I can get the geoprocessing widget to show the new parameters is to remove the widget altogether and re-add it, including all the other widget configuration that's needed.  Would be nice if there was a refresh button or if the widget responded to the "Set" url by repopulating the parameters. ... View more

If your web map configured for feature layer search using the search bar returns no results, even though the query works fine in a manual REST query, here's why: New at 10.3 in the ArcGIS REST API: - query now supports pagination in a query layer. This allows you to page through query results instead of getting all the service limit results at once.  New query parameters resultRecordCount allows you to ask for how many results you want at a time and resultOffset allows you to ask for a new batch of results .  http://resources.arcgis.com/en/help/arcgis-rest-api/index.html#/Query_Map_Service_Layer/02r3000000p1000000/.  These were introduced at 10.3 because SQL Server (and other RDBMS too) introduced pagination at SQL Server 2012, in which select query results can be obtained in batches using "fetch-offset" T-SQL statements.  If you try to query a layer with data from a RDBMS that does not support pagination (SQL Server 2008 does not), you will get an error that pagination is not supported.  If you are writing your own custom REST client you can find out if a layer supports pagination before you decide to use these parameters.  Go to the layer's REST page and in the "Advanced Query Capabilities" is a property called "Supports Pagination".  In the December update for ArcGIS Online, the "feature search" was updated to use pagination in its query (confirmed with Fiddler) with a default resultRecordCount = 5.  Therefore, if your data layer does not support pagination the search won't work.  Of course, the documentation to configure feature search in a web map (http://doc.arcgis.com/en/arcgis-online/create-maps/configure-feature-search.htm) does not mention pagination or the resultRecordCount. Also, the feature search annoyingly supports only text fields. ... View more

I've got some data in an enterprise geodatabase (SQL Server 2012).  I want to create a view that joins points in a feature class to the nearest line in another feature class.  The join includes the shape field and attributes from the point feature class, plus some attributes from the nearest line, plus the distance to the nearest line.  I wrote a simple but inefficient view that works for a small test dataset, but performance quickly degrades.  6 seconds for 2000 points against 20 lines.  Looking at the execution plan, the spatial index is not being used at all. I manually created the spatial index in ArcCatalog for both the points and the lines with coordinates that bound all of the data with Medium grid granularity at all levels. Here is the code, looking for tips on how to engage the spatial index or better, more scalable logic in general: --POINTS is the point feature class --LINES is the line feature class select   p.OBJECTID,   p.SHAPE,   p.PointAttribute,   closestline.LineAttribute,   p.shape.STDistance(closestline.shape) from   POINTS as p   cross apply (   select top 1 l.LineAttribute, l.Shape   from LINES as l   order by p.SHAPE.STDistance(l.SHAPE)   ) as closestline ... View more