Opened 16 years ago
Closed 16 years ago
#684 closed defect (fixed)
Character encoding issues
Reported by: | billc | Owned by: | ksgeograf |
---|---|---|---|
Priority: | medium | Milestone: | |
Component: | Maestro | Version: | |
Severity: | major | Keywords: | |
Cc: | External ID: |
Description
Hi
This is a follow on from the resolved issues #635 and #662. There's another character encoding incompatibility between Studio and Maestro that hasn't been fixed yet.
When using the KingOra FDO connector Studio adds a tilda (~) as a separator in the FeatureName, and Maestro adds the character string -x7e-
Can Maestro be fixed so that -x7e- becomes a ~ character?
Thanks.
Change History (3)
comment:1 by , 16 years ago
Status: | new → assigned |
---|---|
Version: | 2.0.1 |
comment:2 by , 16 years ago
Hi
Thanks for the reply.
As far as I can tell the offending character encoding is in the <FeatureName> tag:
From Studio:
<FeatureName>KingOra:OSMM_MG~TOPOGRAPHICAREA_HP~GEOM</FeatureName>
From Maestro:
<FeatureName>KingOra:OSMM_MG-x7e-TOPOGRAPHICAREA_HP-x7e-GEOM</FeatureName>
Here's the full Studio layer:
<?xml version="1.0" encoding="UTF-8"?> <LayerDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:noNamespaceSchemaLocation="LayerDefinition-1.2.0.xsd" version="1.2.0"> <VectorLayerDefinition> <ResourceId>Library://OSMM/Connections/osmm_mg_KingFDO.FeatureSource</ResourceId> <FeatureName>KingOra:OSMM_MG~TOPOGRAPHICAREA_HP~GEOM</FeatureName> <FeatureNameType>FeatureClass</FeatureNameType> <Geometry>GEOM</Geometry> <VectorScaleRange> <PointTypeStyle> <DisplayAsText>false</DisplayAsText> <AllowOverpost>false</AllowOverpost> <PointRule> <LegendLabel> </LegendLabel> </PointRule> </PointTypeStyle> <LineTypeStyle> <LineRule> <LegendLabel> </LegendLabel> </LineRule> </LineTypeStyle> <AreaTypeStyle> <AreaRule> <LegendLabel> </LegendLabel> <AreaSymbolization2D> <Fill> <FillPattern>Solid</FillPattern> <ForegroundColor>ffffffff</ForegroundColor> <BackgroundColor>ff000000</BackgroundColor> </Fill> <Stroke> <LineStyle>Solid</LineStyle> <Thickness>0.0</Thickness> <Color>ff000000</Color> <Unit>Centimeters</Unit> <SizeContext>DeviceUnits</SizeContext> </Stroke> </AreaSymbolization2D> </AreaRule> </AreaTypeStyle> </VectorScaleRange> </VectorLayerDefinition> </LayerDefinition>
And here's the full Maestro layer:
<?xml version="1.0" encoding="utf-8"?> <LayerDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xsi:noNamespaceSchemaLocation="LayerDefinition-1.2.0.xsd" version="1.2.0"> <VectorLayerDefinition> <ResourceId>Library://OSMM/Connections/osmm_mg_KingFDO.FeatureSource</ResourceId> <FeatureName>KingOra:OSMM_MG-x7e-TOPOGRAPHICAREA_HP-x7e-GEOM</FeatureName> <FeatureNameType>FeatureClass</FeatureNameType> <Geometry>GEOM</Geometry> <VectorScaleRange> <PointTypeStyle> <DisplayAsText>false</DisplayAsText> <AllowOverpost>false</AllowOverpost> <PointRule> <LegendLabel /> </PointRule> </PointTypeStyle> <LineTypeStyle> <LineRule> <LegendLabel /> </LineRule> </LineTypeStyle> <AreaTypeStyle> <AreaRule> <LegendLabel /> <AreaSymbolization2D> <Fill> <FillPattern>Solid</FillPattern> <ForegroundColor>ffffffff</ForegroundColor> <BackgroundColor>ff000000</BackgroundColor> </Fill> <Stroke> <LineStyle>Solid</LineStyle> <Thickness>0.0</Thickness> <Color>ff000000</Color> <Unit>Centimeters</Unit> <SizeContext>DeviceUnits</SizeContext> </Stroke> </AreaSymbolization2D> </AreaRule> </AreaTypeStyle> </VectorScaleRange> </VectorLayerDefinition> </LayerDefinition>
comment:3 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Thank you for that report. I belive it is fixed in r3289 which I have just uploaded: http://trac.osgeo.org/mapguide/wiki/maestro/Downloads
I don't have a working Oracle data source to test on. Can you submit the Xml for a layer that works in Studio but not in Maestro? If you can attach files like the ones in #662, I should be able to figure out what goes wrong.