Opened 15 years ago

Closed 15 years ago

#861 closed defect (fixed)

Maestro XML MapDefinition Editor Kills BaseMapDefinition

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

Description

Hi,

We add BaseMapDefinition to our MapDefinition without actual base layers - this allows for the zoom-bar to jump between the min/max scales we need but without the need to manage base-layers or tile cache. It's good.

BUT if I view the XML in Maestro and edit the display scale (e.g. 500 to 600 in the sample below) and hit save it deletes the whole <BaseMapDefinition> :-(

Many thanks for your attention, Crispin

<BaseMapDefinition>

<FiniteDisplayScale>500</FiniteDisplayScale> <FiniteDisplayScale>1000</FiniteDisplayScale> <FiniteDisplayScale>5000</FiniteDisplayScale> <FiniteDisplayScale>10000</FiniteDisplayScale>

</BaseMapDefinition>

Attachments (1)

ServerConnectionBase.diff​ (857 bytes ) - added by crispinatime 15 years ago.
ServerConnectionBase Diff

Download all attachments as: .zip

Change History (3)

comment:1 by crispinatime, 15 years ago

Please find .diff attached.

Maestro expected BaseMapLayerGroup with FiniteDisplayScale but the two are independant. Added an additional check before nulling BaseMapLayerGroup.

Crispin :-)

by crispinatime, 15 years ago

Attachment: ServerConnectionBase.diff​ added

ServerConnectionBase Diff

comment:2 by ksgeograf, 15 years ago

Resolution: → fixed
Status: new → closed
Version: 2.0.2

Fixed in r3665.

Thansk for the patch. I had not thought of using finite display scales without a map.

Note: See TracTickets for help on using tickets.