Latest Contributions by MarkBaird

The 10.2.4 release is no longer a supported product (I think its 9 years old) and you should consider migrating to a more modern API such as out 200.0.0 release.  This isn't a Swing based product but JavaFX, so the app will need rewriting. Although I've not debugged the issue you are seeing above I suspect this is a TLS version issue.  This is certainly the case for Java 7 JDK.   It might be worth trying with Java 8 if you've not already done that, but I suspect this isn't going to be a fixable issue. ... View more

Hi @VineetMenon  When you are creating a SimpleMarkerScene symbol (which can be a cone, tetrahedron, tube etc) you create it by specifying the height, width and height.  The difference you are seeing with your geodesic buffer can be explained because you are working with a radius from a point effectively. I fixed your code by setting the size of the symbol dimensions to twice the radius of your buffer.  Note that because you are working in 3D with a SimpleMarkerSceneSymbol, the shape you end up with is a geodetic albeit slightly generalised.       // the size needs to be 2 times the radius of the buffer SimpleMarkerSceneSymbol redSphereSymbol = new SimpleMarkerSceneSymbol(SimpleMarkerSceneSymbol.Style.SPHERE, 0x77FF0000, radius * 2000, radius * 2000, radius * 2000, SceneSymbol.AnchorPosition.CENTER); Graphic rangeBalloon3D = new Graphic(centerPoint, redSphereSymbol);     This is the result with the corrected dimensions: Does this help? ... View more

I think you are missing an ApplyEdits step. If you take a look at this sample code you will see what needs to be done. Does this help? Mark ... View more

I can see the problem here.  Loxodromes are lines which happen when you follow a compass bearing.  In your example you have a heading of 0 which is North.  If you are walking to the North Pole following a compass bearing of North (0), as soon as you reach magnetic north and keep going in the same direction your compass actually starts reading South!  This explains why no matter how big a number you pop into your move method, the loxodrome stops at the top of the earth. Using your code, I switched the line type to a Geodesic (shortest distance between 2 points over the surface of the Earth) and the new point appeared having travelled over the pole. This is my code: var graphicsOverlay = new GraphicsOverlay(); mapView.getGraphicsOverlays().add(graphicsOverlay); // some markers SimpleMarkerSymbol redDot = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, Color.RED, 10); SimpleMarkerSymbol greenDot = new SimpleMarkerSymbol(SimpleMarkerSymbol.Style.CIRCLE, Color.GREEN, 10); // original point Point point = new Point(70, 0, SpatialReferences.getWgs84()); Graphic pointGraphic = new Graphic(point, redDot); graphicsOverlay.getGraphics().add(pointGraphic); //Point point2 = GeometryEngine.moveGeodetic(point, 8640000.0, new LinearUnit(LinearUnitId.METERS), 0.0, new AngularUnit(AngularUnitId.RADIANS), GeodeticCurveType.LOXODROME); //This returns Point: [0,000000, 90,000000, 0,000000, NaN] SR: 4326 // geodesic move using a geodesic line instead of a loxodrome. Point point2 = GeometryEngine.moveGeodetic(point, 12075000, new LinearUnit(LinearUnitId.METERS), 0.0, new AngularUnit(AngularUnitId.RADIANS), GeodeticCurveType.GEODESIC); System.out.println("point 2= " + point2.toString()); Graphic pointGraphic2 = new Graphic(point2, greenDot); graphicsOverlay.getGraphics().add(pointGraphic2);  You can see the green dot in my app which went over the pole.   I went a little further and increased the number to 40075000 which is roughly the circumference of the earth and the 2 dots where "fairly" close to each other.  Therefore the point went over the North Pole, the South Pole before coming back to where it started. Does this help? Mark  ... View more