Fix #2167 Update submodule to include Isochrone and Itinerary plugins

[allyoucanmap]

The submodule has been updated to master and Itinerary and Isochrone plugins included. Both plugins needs to be configured in a map viewer to be enabled and a valid graphhopper url endpoint must be provided:

• Itinerary doc
• Isochrone doc

[gemini-code-assist]

Summary of Changes

Hello @allyoucanmap, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on updating the core MapStore2 submodule to its latest master branch, which is a significant dependency upgrade. The primary impact of this update is the introduction and enablement of new mapping functionalities, specifically the Itinerary and Isochrone plugins for route planning and area analysis, as well as a SecurityPopup plugin. These changes ensure the application can leverage the most recent features and improvements from MapStore2 and provides users with enhanced geospatial tools.

Highlights

• MapStore2 Submodule Update: The MapStore2 submodule has been updated to point to the master branch, bringing in the latest changes and features from the upstream repository. This includes an update to the specific commit hash from 8bcd0ab to 52891c7.
• New Plugin Integration: The Itinerary and Isochrone navigation plugins, along with a SecurityPopup plugin, have been integrated into the application. These plugins are now imported and registered in the client-side plugin index.
• Plugin Configuration: Configuration entries for the newly integrated Itinerary, Isochrone, and SecurityPopup plugins have been added to pluginsConfig.json, making them available for use and configuration within the application's map viewer.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the MapStore2 submodule to its master branch, introducing the Isochrone, Itinerary, and SecurityPopup plugins. The changes correctly integrate these new plugins by adding them to the plugin index and providing their configurations. My review focuses on improving long-term stability and maintainability. I've raised a high-severity concern about using a floating master branch for the submodule, which can introduce instability. I've also provided medium-severity suggestions to improve code readability by sorting the new imports and plugin declarations alphabetically.