Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#662 closed defect (fixed)

Layers saved in Maestro cannot be edited in Studio

Reported by: andrewd Owned by: ksgeograf
Priority: high Milestone:
Component: Maestro Version:
Severity: major Keywords:
Cc: External ID:

Description

I thought I'd created this ticket already, but don't see it. If it's a duplicate, sorry!

I used Studio to make a bunch of layers (using the load procedures) quickly, and then used Maestro to make some changes to those layers. When I save the changes (or even don't change anything, but push the save button) and then open that layer in Studio, my Feature Class and Geometry data gets lost...once I reassign it, it works fine again.

After checking the XML before and after, it's easy to see the problem...The "FeatureName" is different in Maestro than in Studio. Here is the XML produced by Studio:

<?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://435966/Data/50k_airport.FeatureSource</ResourceId> <FeatureName>Default:50k_airport</FeatureName> <FeatureNameType>FeatureClass</FeatureNameType> <Geometry>Geometry</Geometry> <VectorScaleRange>

<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>

Here is the XML produced by Maestro:

<?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://435966/Data/50k_airport.FeatureSource</ResourceId> <FeatureName>Default:-x35-0k_airport</FeatureName> <FeatureNameType>FeatureClass</FeatureNameType> <Filter /> <Geometry>Geometry</Geometry> <Url /> <ToolTip /> <VectorScaleRange>

<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>

Among a few other differences, Maestro is sticking a "-x35-0" in front of my FeatureName, which is confusing Studio. Seems like a simple fix...let's hope.

Change History (5)

comment:1 by ksgeograf, 16 years ago

Status: newassigned

This is a duplicate of #635.

I am not closing this because it has a better desription of the actual problem :).

I am currently working on the issue, but has had no response from the FDO team, explaining why FDO returns those weird encoded names.

I'll give it a few days, and then manually correct the wrong encoding in Maestro if the FDO team does not give me any clues as to why it is there.

comment:2 by ksgeograf, 16 years ago

Version: 2.0.1

comment:3 by ksgeograf, 16 years ago

This should now be fixed in r3285, which can be downloaded here: http://trac.osgeo.org/mapguide/wiki/maestro/Downloads

comment:4 by andrewd, 16 years ago

Resolution: fixed
Status: assignedclosed

That fixed it! Thanks

comment:5 by ksgeograf, 16 years ago

There were some extra charaters that were not handled in r3285, but are now handled with r3289. http://trac.osgeo.org/mapguide/wiki/maestro/Downloads

Note: See TracTickets for help on using tickets.