Latest Contributions by DavidMartin

My apologies. I've investigated further and realised that the symptoms only arise with a very specific scenario that I only hit on accidentally and that it is easy enough to step around. My script  uses arcpy.mapping.MapDocument("CURRENT"), and  I had been outputting the feature class, rather than the feature layer. A new layer therefore got added to the ArcMap TOC based on the feature class, while in memory, a feature layer of the same name was still hanging around. When I subsequently ran the Apply Symbology to Layer tool in the foreground, I guess it applied the symbology to the in memory layer, while if I ran it in the background, it would apply it to the ArcMap TOC layer. An odd one! If you have any interest in replicating it, you can do so with this script. import arcpy # ********************************************************************************************************** # Remove this next line, and you can apply symbology afterwards, whether foreground or background processing # Leave it, on the other hand, and you can only apply symbology afterwards when in background processing mxd = arcpy.mapping.MapDocument("CURRENT") # ********************************************************************************************************** fcPath =  arcpy.env.scratchGDB + r"\testing" arcpy.MakeFeatureLayer_management(fcPath, "testing") arcpy.SetParameter(0,fcPath) Thanks for your help, David. ... View more

Your assumption seems right to me - that you need to capture touch events at the level of the map. To me, this makes good logical sense, in that you can't tap a layer as such - only the map as a whole. The current state of the app (e.g. whether a "select graphic" tool is enabled) will determine whether a particular layer should respond. If your app is relatively simple, you could drop all your logic in the MapView's OnSingleTapListener (or other listener for different touch events). Alternatively, you could extend GraphicsLayer or FeatureLayer and drop the logic for each type of layer in your app into a new method (e.g. OnSingleTap?). The MapView's OnSingleTapListener could then call each layer's OnSingleTap method, and depending on your layer's current state (which might depend, say, on which tools or options are enabled), each layer could work out what it needs to do (if anything) in respond to the tap. A GraphicsLayer can use the following methods to get the graphic(s) nearest to a tapped point: getGraphicIDs (has various overrides that allow you to specify tolerance and max number of results returned) getGraphic(int uid) - allows you to get the actual instance of a Graphic, given any of the IDs returned above. ... View more

I'm only guessing now, but... 1/ How are you instantiating your FeatureLayer? From the GeodatabaseFeatureTable? 2/ Do the FeatureLayer, GeodatabaseFeatureTable (and MapView?) objects all share the same scope? Sent from Samsung Mobile ... View more

Looking at your code, I doubt if the spatial reference is a real issue. After all, the geometry is being derived from the map. Perhaps instead you could try an alternative approach that would also allow you to inspect the query results? Use queryFeatures (with your QueryParameters) on your GeodatabaseFeatureTable and inspect the results in the callback. If you are getting results, you could then select them individually, by iterating them and using Featurelayer.selectFeature on each. (I've not tried it but it looks like a viable approach! ) David Sent from Samsung Mobile ... View more

I'd have thought you need a where clause?? To get back all records found by the spatial filter, try: q.setWhere("1=1"); You may also need to specify your output fields?? To get back all fields try: q.setOutFields("*"); And I guess it's probably worth specifying the output spatial reference: q.setOutSpatialReference(mMapView.getSpatialReference()); Also, where does the graphic, g, come from? Make sure of the obvious - that it does intersect with some of your features(!) - and that its geometry is definitely in a spatial reference equivalent to that of the MapView. You could check this with the condition: (g.getSpatialReference() == mMapView.getSpatialReference()) ... View more

Do you mean you want to project your data to WGS84? Or are you simply trying to specify that the layer's data is WGS84? You can create a WGS84 SpatialReference using the static method create() on that class as follows: SpatialReference wgs84 = SpatialReference.create(SpatialReference.WKID_WGS84) (see SpatialReference | ArcGIS Android 10.2.4 API ) And you can project geometries from one SpatialReference to another using GeometryEngine's static methods for project(...), which allow you either to specify a geotransformation explicitly (if needed) or to leave the choice up to ArcGIS. (see GeometryEngine | ArcGIS Android 10.2.4 API ) If you want to effectively have your layer (in XYZ SpatialReference) re-project on the fly to WGS84, then I'd suggest you do that as part of data / service preparation, rather than trying to code a solution in Android. If, on the other hand, you have no control over the data / service, or there are other sound reasons why you need to re-project on the fly, then your solution will depend on the type and nature of the data you're bringing in. If you are enabling your user to add their own raster data at runtime, then you could use the project method of FileRasterSource, although you'd want to have some knowledge of the SpatialReference(s) in which the user-supplied data was coming. (see FileRasterSource | ArcGIS Android 10.2.4 API ) If it's raster in the form of a TiledLayer, then you don't want to be changing the SpatialReference, or you could experience tile alignment issues. If it's a DynamicLayer, then this class has a protected field supportedSRs, which should presumably give an indication of whether the service will support re-projection to WGS84 (presumably, if it does, and the MapView's SpatialReference is WGS84, then the MapView will handle the renewed call to the service internally... someone else may be in a better position to clarify here, or you could simply test it out??). You'd need to subclass in order to access the protected field, however (or perhaps rely on the MapView giving an error if WGS84 is not supported by the layer??) (see DynamicLayer | ArcGIS Android 10.2.4 API ) If it's a FeatureLayer, then how you change the layer's spatial reference depends on its data source, as described in the doc (under Class Overview): (see FeatureLayer | ArcGIS Android 10.2.4 API ) Hope one of those covers your situation?! ... View more

Note there is now an extended version of the text adaptor that will cope with white space separators (and more) on Github: solutions-geoevent-java/solutions-geoevent/adapters/regexText-adapter at master · Esri/solutions-geoevent-java · GitHub ... View more