Latest Contributions by DavidMartin

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

Thanks RJ, I'll take a look at the Javascript pre-processing option. Cheers David ... View more

Does this "auto-picking" of transformations continue to be the case in 10.2? If so, is there any way of discovering what transformation is being auto-picked? For example, what would be the auto-picking logic in use behind a request to transform between WGS84 and OSGB36? ... View more

I'm guessing you're saying that this error only occurs when you deploy your application? And that it doesn't occur in your development environment? If that's the case, then the fact that it's being thrown by a local service is probably indicative of your having opted for a basic license (which won't support local services) instead of a standard license. I'd check the choices you made in the License Viewer, and hence the license code snippet that you've compiled into your application. ... View more

Also relevant here is that you can use tools like Add Field to add attributes to the Footprint layer. The Add Field tool, and others like it (e.g. Calculate Field) will take a Mosaic Dataset as an input (as-is) and will apply their actions directly to the Footprint layer. ... View more

This appears to be a tool validation issue. If I create this same model in Model Builder, and run the "Make Mosaic Layer" portion of it, I can then validate the entire model and it will run OK - whether within Model Builder or subsequently via the tool's UI (provided default parameters exist and I don't change them). Whenever I do change the parameters, however, it errors with the message that %MosaicLayer%\Footprint does not exist. I'd say that the tool is treating %MosaicLayer%\Footprint as a necessary prerequisite to running the model. If it's there (in memory?) due to previous runs of the model in Model Builder, then all's well. Otherwise it won't validate. Looks like a bug? I am also running 10.1 (SP1). However there is a workaround - using the Calculate Value tool in Model Builder. The model shown in the attached screenshot will run OK. ... View more

I believe it is, yes, unless someone else is about to educate us otherwise. Note too that the Calculate Geometry Tool will give you the lat/lon using the datum of the selected coordinate system. You have the choice of using the coordinate system of the layer or of the data frame. In the case of your screenshot, these are one-and-the-same and so you will get your lat/lon based on the GCS_IRENET95 datum. Assuming you want your lat/lon in WGS84 (perhaps you don't though?) then even the Caculate Geometry Tool will fail to give you the answer you're seeking here. Although admittedly you could coerce it by setting the data frame to use WGS84 and supplying ArcMap with the appropriate transformation as you do so. If you did that, you could then use the coordinate system of the data frame in the Calculate Geometry Tool and get the right answer that way. But in Model Builder I believe you'll need to follow the approach I've described above. A quick search has brought up a similar question from 2011, and the response then was effectively the same as the one I've given here, so unless there's been any new tools brought out since that could address your problem, then it looks like that's the approach you'll need to take: http://forums.arcgis.com/threads/37718-Calculate-Geometry-in-Model-Builder ... View more