Today Leaflet Maps Marker was featured as one example app which uses open data from the City of Vienna on the Austria news site orf.at. To celebrate this report, I decided to release v1.5 earlier than planned
Actually I planned to integrate Vector Layers from Jason Sanford into v1.5 – but this turned out to be much more time consuming than I thought, so I postponed this feature to v1.6.
So whats new in v1.5? The most important new feature is, that you can now choose to display a list of markers below layer maps, which not only show a list of markers but also the marker name, popuptext, direction-, fullscreen- and kml-link for each marker:
This marker list can be enabled on each layer map. For new layer maps it is enabled by default, for already existing layer maps, it has to be enabled manually on layer edit screen:
Within settings / Layer defaults you can also choose how to sort the marker list:
Another new feature – which is enabled by default – is that a GeoRSS feeds for all markers is automatically added to the <head>-section of your website. This allows users to subscribe to your marker maps easily like subscribing to your blog posts. If you don´t want to use this feature, you can disable it in Settings / Misc:
Another feature requested by users was the addition of mass actions for layer maps. With v1.6 you now find those actions under tools:
Additonally to those new features I also optimized the database for boolean values and fixed on bug which caused overlay maps for layer maps not to show up correctly in backend preview maps.
- NEW: added option to display a list of markers below layer maps (enabled for new layer maps, disabled for existing layer maps)
- NEW: included option to add GeoRSS feed for all markers to <head> to allow users subscribing to your markers easily
- NEW: add mass actions for layer maps
- CHANGED: database structure for boolean values from tinyint(4) to tinyint(1)
- BUGFIX: overlay status for layer maps wasnt displayed in backend preview
Please let me what you think of this new release. If you have any issues, please see this page on how to get support. If an important feature is missing, please add your feature requests on Github. I am also looking for more translations – if you would like to contribute a new one, please visit this page for more information.