Feature #94

Add a basemap componant/module

Added by Mérour Xavier about 9 years ago. Updated over 4 years ago.

Status:ClosedStart date:12/07/2009
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:MAP
Target version:4.0.0
Sponsor: Ergonomic impact:
Functional impact:

Description

Currently, a list of basemap is definable under the componant SHOP and then used to "pick one of this basemap for the SHOP front-end interface in step 2.

We see that basemap can be used in many different componants and modules (CATALOG for example too).

I suggest to move this basemap list outside of the SHOP componant and make a independant componant (or module) to manage this list.
Then other componants like SHOP or CATALOG can point to the basemap item to choose the desired one.

Any comments ?

History

#1 Updated by Magoni Bruno about 9 years ago

This is a good idea to have a fully independant basemap container which can be reused inside several EasySDI components.
As basemaps could be used by other EasySDI components, I would like to propose that basemaps definition will be part of the CORE component and not be a self component.
We must be aware when reengineering source code that basemaps definition are now used by the new MAP component.

#2 Updated by Mérour Xavier over 8 years ago

  • Assignee set to Magoni Bruno

Right Bruno... do you plan to apply theses changes with EasySDI V2 ?
For the map, the logic is indeed quite similar with based layer... just that it can have several basemaps in the same MAP instance.

#3 Updated by Magoni Bruno about 8 years ago

  • Assignee deleted (Magoni Bruno)

Won't be done in V2 as we are still waiting to find a contributor to migrate SHOP from V1 to V2...

#4 Updated by Mérour Xavier about 8 years ago

Are you talking about migrating SHOP or MAP component to V2 ?

#5 Updated by Magoni Bruno almost 8 years ago

  • Assignee set to Mérour Xavier
  • Target version set to 63

Even if it should be implemented into CORE, it's a transversal need which concern SHOP and MAP.
But you're rigth as it seems better to think about this logical when refining MAP...and not SHP.

#6 Updated by Mérour Xavier almost 5 years ago

  • Assignee changed from Mérour Xavier to Magoni Bruno

Can I have some refreshing news on this feature ?
Is there any thing done in EasySDI V4.0 in that direction ?

#7 Updated by Magoni Bruno almost 5 years ago

  • Project changed from CORE to easySDI
  • Target version deleted (63)

#8 Updated by Magoni Bruno almost 5 years ago

  • Category set to MAP
  • Status changed from New to Accepted
  • Target version set to 4.0.0

#9 Updated by Magoni Bruno almost 5 years ago

  • Status changed from Accepted to Affected

#10 Updated by Magoni Bruno almost 5 years ago

  • Status changed from Affected to Resolved
  • Assignee deleted (Magoni Bruno)

Hi Xavier,

Good news about this feature :-)
In easySDI V4, administrator can create maps (previously map contexts) with MAP component.
All these maps can be used in other component (i.e. permieter's definition in SHOP component), so there is no more basemap or map context needed to be defined in other component than MAP! Each map is reusable totally in each easySDI component!

#11 Updated by Mérour Xavier almost 5 years ago

  • % Done changed from 0 to 100

It goes evenfurther than just "basemap" since it can includes others layers. Great news !

#12 Updated by Magoni Bruno almost 5 years ago

  • Status changed from Resolved to To merge

#13 Updated by Magoni Bruno over 4 years ago

  • Status changed from To merge to Closed

Also available in: Atom PDF