Custom Symbols are not displayed correctly

[bberdel]

Custom symbols are all located in the lower left hand corner of the map.

[tomfukushima]

Thanks for this report. Could you provide more details about this such as the steps to recreate the problem? Thanks, Tom.

[bberdel]

Using 2.0beta2 IIS .net config

All of my layers that have custom symbols on them do not display correctly. They worked in 1.2. All of the symbols for that layer do not appear in the correct location. Instead, they are just placed in the lower left hand corner on top of each other.

[tomfukushima]

Would you be able to attach a small package to this ticket that will allow us to replicate the problem? I'm not exactly sure what you mean by custom symbols: are they symbols from a SymbolLibrary resource, are they SymbolDefinition resources, are they bitmap, DWF based, etc...

Also, things such as coordinate system inconsistencies may cause problems like this, so the package should contain: data, layers, symbols, and map.

[bberdel]

Symbol Library and they are PNG Format. I attached a sample.

[tomfukushima]

I can get the symbols to show up for the individual layers. The data is in different projections and when these are put on a single map only one of the layers will show up. It seems to be some projection problem, potentially a data setup error. Until it can be shown that this is a bug in MGOS I'm going to stop investigating this.

The package data also needs to be adjusted because the layers are pointing to a Solebury directory (replace with SymbolSample).

Will leave this ticket open for the time being.

[bberdel]

I just added a package with one layer, and one data source. The projection is set correctly. When Previewing just that layer in studio, the symbols are not loaded correctly.

[luala]

I have also encountered this problem. I create a symbol library and load one png file as symbol, then setup it as the symbol of a POINT feature layer, the features' label are displayed correctly but the symbol is always at the lower left hand coner.

[tomfukushima]

Hi, Does this problem still occur in MGOS 2.0.0? Thanks, Tom

[bberdel]

No, it is resolved. thanks!