aaime wrote: > > > I don't know the exact detail about how MIL symbols do work, but I know > I want this kind of separation in order to support MapServer like > graphic symbols (again, described below). > > Cheers > Andrea > > >
HI , I just would like to give a quick overview of the MIL symbols and how they work. Basically the Mil2525B standard define the symbols with a 15 character string. eg. 'SFGPUCAAA-*****' This string wil represent Friendly Anti Armored Combat Unit. The software parse the string as follows: CH1 : 'S' = War Fighting Symbol CH2 : 'F' = Affiliation is Friendly , and their is a Blue RGB color associated with it , same for 'H' which is hostile with a red RGB associated with it , their are four main affiliations each with its own color , and it also will deter main the frame of the image , Diamond , Rectangle etc. CH3 : 'G' = Battle dimension Ground. There are seven deferent battle dimensions , also have a influence on the frame CH4 : 'P' = Is for Present , also have a influence on the frame CH5 - 10 : 'UCAAA-' = is the function of the symbol , in this case 'Anti Armored combat unit' CH11 - 12 : is the Symbol Modifier , eg. Echelon Size , Movement indicator etc. CH13 - 14: Country Code , to which country the symbol belong to CH15 : Order of battle , could be Ground , Air , Civilian etc. For the Tactical Symbols there is in the the order of plus minus 700 symbols , then there are extra symbols for Military Opreations Other Than War (MOOTW) , weather Symbols and Signal Symbols. With 9 different affiliations (but for different affiliation colors , some share the same color), so you sit with roughly 700 x 9 different symbols , and thats only tactical , not counting the extra symbols like MOOTW etc. So we use a set of 13 fonts with the different affiliation frames in the chars and the different symbol functions representations in chars , there are enough similarities in the symbols to compile a symbol through code by overlaying a few chars to get the correct symbol. Thats why we create the graphic symbols in code dynamically , not a shape , and pass the graphic back to the application that asked for the symbol. Because sometimes you would like the symbol a certain size for map display and in other occasions another size for display in a tree node. OK , i agree the size is not presented in the mil2525 standard string , but the fill color is. I also admit that is for mil symbols , in other domains it might not work the same, like Emergency response the graphic name is "ambulance" , no mention of color and size in there. I am not a guru on URL and the protocols that goes with it , but cant you pass in parameters in a URL? Like some of the URL's have query params that they do send with. Then if we can have a Geotools Comunity WellknownIcon protocol , with its handler We can maybe have something like this : <wkicon>:<domain><WellknownIconName>?<params> wkicon://mil2525/'SFGPUCAAA-*****'?size=16 or wkicon://emergency/'ambulance'?size=20&color=red or wkicon://mapsymb/'cave?size=10&color=black This way we could still use the plugin system to implement the WellknownIcon interface , for the deferent domains , each plugin get / create the icons from where ever they want. Cheers Theuns -- View this message in context: http://www.nabble.com/Well-Known-Name-Icons-tp16417499p16605715.html Sent from the geotools-devel mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
