Feature #981

Adding a leaflet map type

Added by Portier Thomas over 2 years ago. Updated almost 2 years ago.

Status:ClosedStart date:04/07/2015
Priority:UrgentDue date:
Assignee:Portier Thomas% Done:

100%

Category:MAP
Target version:4.4.0
Sponsor: Ergonomic impact:

in backoffice : add a map type radio button
in frontoffice : possibility to add a leaflet map

Functional impact:

Add the ability to configure and display map context using leaflet


Description

Add a map type parameter :
- geoext
- leaflet

According to the choice of the map type, tools that user can select will be different. Only the tools implemented for the choosen map type will be proposed to admin.

easysdi_leaflet.png (534 KB) Portier Thomas, 06/25/2015 01:56 PM


Related issues

Related to easySDI - Enhancement #879: Add ability to expose a map context configuration in json Closed 12/11/2014

History

#1 Updated by Portier Thomas over 2 years ago

  • Priority changed from Normal to High

#2 Updated by Portier Thomas over 2 years ago

  • Status changed from New to Request For Comments

#3 Updated by Villemagne Jérôme over 2 years ago

  • Status changed from Request For Comments to Request For Votes
  • Assignee changed from Technical Committee to Steering Committee

Ok for TC.
Copil has to vote.

#4 Updated by Portier Thomas over 2 years ago

A filter will be added to force admin select geoext map for shop and preview features. There will not be other impact for the actual map.

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

Hello,

I would add to this feature the following constraint : the type of MAP (OL or leaflet) should be selected at the creation of the map AND it should not be possible to change the type afterwards.
I suggest this to limit the risk of "breaking" a current configuration when type change.

#6 Updated by Magoni Bruno over 2 years ago

  • Related to Enhancement #879: Add ability to expose a map context configuration in json added

#7 Updated by Magoni Bruno over 2 years ago

I guess there is some strategic discussion about integrating other mapping APIs inside easySDI (regarding the use cases) and/or driving maps' building through json definition.

  • First of all, as json map's definition is now available (see #879) but we must care that it reflect full map's definition; in this case easySDI maps rendering should always use json service instead of database repository...
  • I guess that opening easySDI MAPS definition to be used by more than one mapping JS API is a very good thing (easySDI as got a key role in SDI definition whatever technologies you are using), but we must not forget that maintaining same functional level for all API will be very time consuming. The main point is to agree that several APIs could be integrated inside easySDI (not only OL3 and Leaflet):
    • for now easySDI is supporting only OL2/GeoExt2; OL3 is released but no clear roadmap about porting GeoExt for OL3...
    • Leaflet is still under Beta version even if it's more and more mature...
    • arcGIS API is also a very interesting candidate for creating maps and open a door to ArcGIS Online platform...

#8 Updated by Magoni Bruno over 2 years ago

SC agree about such new issue but ask for some more detailed implementation before liberating it :-)

May I ask SC members to express clearly their vote.
Thanks a lot.

#9 Updated by Magoni Bruno over 2 years ago

+1

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

+1 considering my remark here https://forge.easysdi.org/issues/981#note-5

#12 Updated by Teixeira Jérôme over 2 years ago

  • Functional impact set to -
  • Ergonomic impact set to _

+ 1

#13 Updated by Magoni Bruno over 2 years ago

  • Status changed from Request For Votes to Request For Comments
  • Assignee changed from Steering Committee to Technical Committee
  • Functional impact deleted (-)
  • Ergonomic impact deleted (_)

Thanks TC to explained a little bit more in details functional and ergonomic impacts.

#14 Updated by Van Hoecke Hélène over 2 years ago

  • Assignee changed from Technical Committee to Portier Thomas

#15 Updated by Portier Thomas about 2 years ago

  • File easysdi_leaflet.png added
  • Assignee changed from Portier Thomas to Technical Committee
  • Priority changed from High to Urgent

More informations about implementation. Sorry it's in french :

En backend Un nouveau paramètre "Type" sera ajouté à un contexte de carte EasySDI. Ce paramètre sera un radio bouton pouvant prendre la valeur "GeoExt" ou "Leaflet".
Nous préférons rendre le type modifiable car dans le cas d'une copie d'un contexte existant, ça ne bloque pas l'administrateur.

Par contre, lors d'une modification de cette valeur un contrôle vérifiera si le contexte de carte n'est pas utilisé : 
- Dans le shop pour la sélélection du périmètre de commande
- Dans le catalogue pour la saisie d'une étendue géographique
- Dans le map pour la carte de prévisualisation

Si il est utilisé dans un de ces 3 cas, la valeur "GeoExt" sera rendue obligatoire.

En fonction du choix du type de carte, l'affichage des choix des outils sera différent.

Pour GeoExt les outils suivant seront proposés : 
Google Earth
Navigation
Zoom
Historique de navigation
Etendue max
Outils de mesure
Geocoder de Google
Impression
Ajout de couche
Suppression d'une couche
Propriété de la couche
Informations sur la couche
Arbre de couches
Coordonnées de la souris
Recherche dans le catalogue
Lien vers la fiche de métadonnée
Téléchargement du produit associé
Commande du produit associé
Echelle
Localisation WFS
Navigation par étage

Pour Leaflet les outils suivant seront cachés : 
Google Earth
Historique de navigation
Etendue max
Suppression d'une couche
Propriété de la couche
Coordonnées de la souris
Recherche dans le catalogue
Echelle
Localisation WFS
Navigation par étage

You'll find attached a screenshot of the client part.

#16 Updated by Van Hoecke Hélène about 2 years ago

  • Assignee changed from Technical Committee to Mérour Xavier

Thanks to validate Thomas's proposal.
TC has already validated it.

#17 Updated by Mérour Xavier about 2 years ago

  • Assignee changed from Mérour Xavier to Portier Thomas

@Thomas,
Functional and ergonomic impacts fields should be filled before vote, thanks ;-)

#18 Updated by Portier Thomas about 2 years ago

  • Functional impact set to Add the ability to configure and display map context using leaflet
  • Ergonomic impact set to in backoffice : add a map type radio button in frontoffice : possibility to add a leaflet map

#19 Updated by Portier Thomas about 2 years ago

  • Assignee changed from Portier Thomas to Mérour Xavier

#20 Updated by Mérour Xavier about 2 years ago

  • Status changed from Request For Comments to Request For Votes
  • Assignee changed from Mérour Xavier to Portier Thomas

PSC has validated this new feature.
Thanks Thomas for your further information about this feature.

Go ahead ;-)

#21 Updated by Mérour Xavier about 2 years ago

  • Assignee changed from Portier Thomas to Van Hoecke Hélène

Sorry, need status "accepted" to be set before Thomas goes further with this ticket.

#22 Updated by Van Hoecke Hélène about 2 years ago

  • Status changed from Request For Votes to Accepted
  • Assignee changed from Van Hoecke Hélène to Portier Thomas

#23 Updated by Portier Thomas almost 2 years ago

  • Status changed from Accepted to Affected

#24 Updated by Portier Thomas almost 2 years ago

  • Status changed from Affected to Resolved

#25 Updated by Portier Thomas almost 2 years ago

  • Status changed from Resolved to To merge

#26 Updated by Van Hoecke Hélène almost 2 years ago

  • Target version set to 4.4.0
  • % Done changed from 0 to 100

#27 Updated by Van Hoecke Hélène almost 2 years ago

  • Status changed from To merge to Closed

Also available in: Atom PDF