Latest Contributions by MarkBaird

It's always good to hear how developers are using the API - this helps is to make the product better!  The forum requests have resulted in a few items of functionality recently, so keep the ideas coming.  We can't do everything though... Going back to the use of the graphics layer in the message group layer...  my initial thoughts here were that you should avoid doing this, but then I thought about the issue of the draw order of the graphics.  I've checked this out and the feeling is that using one of the existing graphics layers in the message group layer is okay.  However (I'm sure you were expecting this!!!), I wouldn't try manipulating the 2525C graphics (removing for example), and don't try removing graphics layers from the message group layer (the latest version of the API does a reasonable job preventing you from doing this).  Hope that helps. Mark ... View more

Out of the box there isn't a way of manipulating symbols in the message group layer in the way you have suggested, but you could try this which would work for point based graphics: - Create yourself a new graphics layer on the map - You can create a PictureMarkerSymbol which uses an image based on a buffered image from the symbol dictionary.  The buffered image can be altered as desired. - Add the picture marker symbol to the map. So you might have some code like this:             BufferedImage img = symDictionary.getSymbolImage(selectedSymbol.toString(), 150, 150);             //some code to make the image a little different in some way             PictureMarkerSymbol pms = new PictureMarkerSymbol(img);             Point pt = map.toMapPoint(eventInfo.getX(), eventInfo.getY());             Graphic gr = new Graphic(pt, pms);             GraphicsLayer gl = new GraphicsLayer();             map.getLayers().add(gl);             gl.addGraphic(gr); It's not as versatile as using the message processor (unique designation labels will not display for example), but it might be worth trying. Out if interest, are these display styles (current / stale / old) part of the 2525C standard?  (excuse the question, but I'm not a 2525C expert) Mark ... View more

The buffered image from the getSymbolImage method is created from vector data into the size of image you request. If you were to create an image 500 x 500 then it will not appear blocky because we have sized up a smaller image. The 150 x 150 I chose above was not related to any internal sizing of the data - it just looked good in my example 🙂 ... View more

I can see this too.  I'll talk to the symbol dictionary team and report back... Mark ... View more

Hi Carlos, I've checked this out in Ubuntu and I'm afraid you've got me - this is a bug! I've raised this as an issue and it will be fixed for the next release. In the mean time you might find the following code snippet useful:             //get the image             BufferedImage symbolImage = symDictionary.getSymbolImage(selectedSymbol.toString(), 150, 150);                         //bit shifting to swap around the Red and Blue to correct in Linux (not needed for Windows)             for (int x = 0; x != symbolImage.getWidth(); x++) {                 for (int y = 0; y != symbolImage.getWidth(); y++) {                   int argb = symbolImage.getRGB(x, y);                   int abgr = (argb & 0xFF000000) | (argb & 0x000000FF) << 16 | (argb & 0x0000FF00) | (argb & 0x00FF0000) >> 16;                   symbolImage.setRGB(x, y, abgr);                 }               } You will of course need to remove this code when the next release comes out otherwise your colors will be wrong again. Mark ... View more

Thanks for the update - that's good to hear Mark ... View more

Hi I'm assuming you are using 2525c symbology here. We recently identified an issue with the UniqueDesignation section of the message which is typically used for adding labels to 2525C symbols.  The problem is a case issue, so if you use "uniquedesignation" in your message instead it should work. Does this help? Mark ... View more

I've tried to replicate this and didn't see the issue you reported.  I was using version 10.1.1. of the API. Is there any chance you could pop the reproducing code on the forum? Thanks Mark ... View more

Hi Pavan, This looks similar to a question in the ArcObjects forum: http://forums.arcgis.com/threads/76392-Service-Area-Solver-Sample-Snippet-Code-for-Java If you are using the ArcGIS Runtime API (this is not ArcObjects), then take a look at the sample application which comes with the API.  Go to the Network Analyst -> Service Area (online) sample. The class you are interested in is called ServiceAreaTask. If this question is an ArcObjects question, then this isn't a good place to put your question.  This forum is for the ArcGIS Runtime SDK for Java.  This product is not ArcObjects based. Let me know if this helps Thanks Mark ... View more

Hi Kevin, You are correct, at the moment there isn't a way of symbolizing lines with arrows...  sounds like a potential product enhancement request to me! Your idea of placing a simple marker symbol (triangle maybe) at the end of the line would work.  The other alternative would be to draw your own arrow heads on the graphics layer using lines.  This way you would have more control over the size of the arrow head. Good luck Mark ... View more

I take the point about the error message, and I'll see where this comes from. However I not having much luck in reproducing the issue.  I have a test which creates a graphics layer to which I add 5000 polygons each with 10,000 verticies. It takes a while to render and isn't the most responsive map I've ever seen but it's not thowing the error you are experiencing. It's maybe that you have a lower spec machine, but either way I would encourage you to look at your data and see if it is suitable for the scales you are using it at. Consider the resolution at which your data was digitised.  If you have a coast line which was digitised every 1metre, when you zoom out to a country scale, you will be putting a big load on your database.  Consider generalizing your data for certain view scales.  This is a very common cause for any GIS or mapping application performing badly or maybe running out of memory in your case. ... View more