Why use Leaflet GeoJSON?
The BBOX strategy requests data within a bounding box. When the previously requested data bounds are invalidated (by browsing to some area not covered by those bounds), another request for data is issued
A standard use case goes like
- Create a GeoJSON feed using the Views GeoJSON module.
- Add the bounding box argument to the GeoJSON view.
- Use a leaflet map preset defined by the Leaflet module, in code or one of the integration modules.
- Put them all together using the Map pane CTools content type plug-in (since 2.x) in combination with Panels or use the Leaflet GeoJSON Bean module (since 1.x) or .
Provides API functionality as defining GeoJSON sources and adding a Leaflet bounding box strategy.
Leaflet GeoJSON Bean
Allows you to create leaflet map blocks based on GeoJSON data and will automatically extend them with the bounding box strategy if supported.
Custom blocks? Even better, we are using: Bean.
- (optional) Views GeoJSON for automatically discovered GeoJSON sources
- (optional) Bean as a dependency for Leaflet GeoJSON Bean
Implement custom GeoJSON sources using
- Leaflet GeoJSON got kickstarted while working on Geocluster.
- Maintenance status: Minimally maintained
- Development status: Maintenance fixes only
- Reported installs: 278 sites currently report using this module. View usage statistics.
- Downloads: 4,100
- Last modified: December 2, 2014
- Stable releases receive coverage from the Drupal Security Team.
Look for the shield icon below.