Latest Contributions by MarkBaird

I can see the issue here.  The point you are creating is in the wrong spatial reference.  This is how you should be creating the point I believe you want which is a latitude and longitude.         graphicPoint = new Point(79.97325625691973,6.91621555958787, SpatialReferences.getWgs84());         You were centring your map based on a latitude and longitude which are angles measures from the centre of the earth in angles of degrees.  This is what we call a geographic projection and in this case is called WGS84.  Note that in navigation people say latitude then longitude, but in mathematics we say x then y, which of course causes confusion!  Note the order of coordinates changed when I specified the point. The coordinate system you were using was a projected coordinate system of which there are lots, but this is a global one called Web Mercator covering rather crudely the entire Earth and not being particularly good good for mapping the North or South Poles!  The units of measure here are in metres and measured from an origin which sits in the sea just off the West coast of Africa - very near to where you were placing your point by accident. If you are interested in more details you could read this: https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/coordinate-systems-difference/#:~:text=A%20geographic%20coordinate%20system%20(GCS,system%20(PCS)%20is%20flat.   Also you've got the same issue when setting the ViewPoint.  This code should help:     mapView.setViewpoint(new Viewpoint(new Point(79.97325625691973,6.91621555958787, SpatialReferences.getWgs84()), 7500));     Does this help?   ... View more

If you are working with a file on the local OS, you don't need a full URI format, you can just use the file on its own.   I just tried this out with the following code: GraphicsOverlay graphicsOverlay = new GraphicsOverlay(); mapView.getGraphicsOverlays().add(graphicsOverlay); // An image file on the hard drive. PictureMarkerSymbol markerSymbol = new PictureMarkerSymbol("./FireStation.png"); markerSymbol.setHeight(100); markerSymbol.setWidth(100); markerSymbol.loadAsync(); markerSymbol.addDoneLoadingListener(() -> { System.out.println("loaded status " + markerSymbol.getLoadStatus()); if (markerSymbol.getLoadStatus() == LoadStatus.LOADED) { // use the symbol Point point = new Point(0,0); Graphic graphic = new Graphic(point,markerSymbol); graphicsOverlay.getGraphics().add(graphic); } else { // error state as it didn't load System.out.println("Failed to load: " + markerSymbol.getLoadError().getCause()); } }); Does this work for you? ... View more

Yes this is possible and I can think of a couple of options depending on if you are working on a 2D map (MapView), or a 3D scene (SceneView). Both approaches will need some sort of elevation data which often comes in a raster format (DEM data) where the raster cell values are set to a value related to height instead of a color map. You can perform an identify operation on your layer which contains the elevation data to get the result. There is a sample which shows a raster identify operation on a mouse move here: https://github.com/Esri/arcgis-runtime-samples-java/tree/master/raster/identify-raster-cell The data here I don't believe is DEM data, but it shows you how it works. If you are writing a 3D scene based application, there are specific methods for getting the elevation of a surface.  This sample demonstrates this nicely: https://github.com/Esri/arcgis-runtime-samples-java/tree/master/scene/get-elevation-at-a-point If you take a look at the getElevationAsync method in the sample you will see where the elevation is obtained. Does this help? ... View more

I can see how this would not be very pleasing to the user.  I tried it myself and it feels pretty bad. You'll be glad to hear there is a better way and it's not that complicated. The laggy experience you have here is happening because you are calling an animated change of viewpoint over and over again.  The approach here is to change the viewpoint without animation. I've written a method to show how this is done: private void rotateMapView(double angle) { Viewpoint v = mapView.getCurrentViewpoint(Viewpoint.Type.CENTER_AND_SCALE); if (angle < 0) { angle += 360.0f; } v = new Viewpoint((Point) v.getTargetGeometry(), v.getTargetScale(), angle); mapView.setViewpoint(v); }   The next step is to wire this up to the custom interaction you are creating.  The best approach is to make your own InteractionListener which you can conveniently create by overriding the DefaultInteractionListener. I started to put one together here to show how it works, but it needs more work as it is not that robust yet.  It was created as a class within the application class: private class rotationInteractionListener extends MapView.DefaultInteractionListener { private double initialX; protected rotationInteractionListener(MapView mapView) { super(mapView); } @Override public void onMousePressed(MouseEvent e) { initialX = e.getX(); System.out.println("custom pressed"); super.onMousePressed(e); } @Override public void onMouseDragged(MouseEvent e) { double xDiff = initialX - e.getX(); rotateMapView(xDiff); System.out.println("custom pan " + xDiff); e.consume(); //super.onMouseDragged(e); } }   To attach the new listener to your mapview you need to add this: // create a map view and set its map mapView = new MapView(); mapView.setMap(map); //Instantiate custom interaction listener and assign it to the mapview InteractionListener interactionListener = new rotationInteractionListener(mapView); mapView.setInteractionListener(interactionListener); You should this solution much less laggy. Does this help? ... View more

Specifying a minimum spec for a SDK isn't easy.  It really depends on the data you are using and how you are using it. Theoretically if your laptop supports DirectX 11 (assuming here you are deploying to Windows platforms) it should work.  A simple map application which has a basemap and a few dots on it will work on some pretty low specification machines. If however you write an app which does intensive 3D visualisation, or even a 2D app which is displaying thousands of points or polygons all updating their location 50 times a second you are going to struggle with a low end GPU.   If resources are an issue with the device you are deploying to there are things you can do in code to make better use of the hardware.  You mention use are using graphics overlays, so a starting point could be to play around with the Rendering mode for your graphics overlays (STATIC mode may help). https://developers.arcgis.com/java/latest/api-reference/reference/com/esri/arcgisruntime/mapping/view/GraphicsOverlay.RenderingMode.html You also mention marker symbols.  If you are displaying lots of graphics then if you use a Renderer for your symbols (Unique Value Renderer for example), this will save you some texture memory on your graphics card if you are currently creating a symbol for each graphic.   Sometimes writing an app for a low end device requires careful coding to make efficient use of limited resources.   ... View more

The files on Bintray are no longer available as jFrog have deprecated this service.  You'll be glad to hear that we have already addressed the issue and details can be found here: https://community.esri.com/t5/arcgis-runtime-sdks-blog/announcement-to-developers-using-cocoapods-with-arcgis-runtime/ba-p/1009911     ... View more