Skip to content

Commit

Permalink
Merge pull request #253 from geoblacklight/2024-02-sprint-blog
Browse files Browse the repository at this point in the history
Update 2024-02-12_version-4-2.md
  • Loading branch information
karenmajewicz authored Feb 12, 2024
2 parents e79ca9e + f7f8927 commit e2a1862
Showing 1 changed file with 4 additions and 10 deletions.
14 changes: 4 additions & 10 deletions docs/blog/posts/2024-02-12_version-4-2.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ The GeoBlacklight Community conducted a two-week sprint from January 29 to Febru

Version 4.2.0 of GeoBlacklight introduces new viewers for two web-based geospatial data formats: Cloud Optimized GeoTIFFs (COGs) and PMTiles. COGs are an extension of the traditional GeoTIFF file format, optimized for cloud storage and web access, while PMTiles offer a method for storing and accessing numerous map tiles in a single, streamlined file. Both formats are designed to improve efficiency and speed across the web by utilizing HTTP range requests. This allows users to request only parts of the data, rather than entire datasets or images, distinguishing these formats from traditional geospatial web services like WFS or ArcGIS REST services. Both of the new viewers use OpenLayers instead of Leaflet, which, up until now, has been the only mapping library for GeoBlacklight.

Overall, the integration of IIIF Manifests, COGs, and PMTiles into the latest version of GeoBlacklight reflects a growing trend in data sharing, moving away from the convention of offering discrete, downloadable files and toward a more dynamic model of streaming data.

<div class="grid cards" markdown>

Expand All @@ -37,7 +38,6 @@ Version 4.2.0 of GeoBlacklight introduces new viewers for two web-based geospati
### Clover for IIIF Manifests



![](blog-images/clover.png){width=40% align=left}

In earlier versions, GeoBlacklight was limited to displaying single-part images through the IIIF Image APIs, requiring anyone interested in showcasing multipart images via IIIF Manifests to integrate a custom viewer. With the release of Version 4.2, this capability is now included by default with [Clover, a viewer developed by the Samvera community.](https://samvera-labs.github.io/clover-iiif/docs)
Expand Down Expand Up @@ -79,24 +79,18 @@ The OpenIndexMaps project has released [version 1.0](https://openindexmaps.org/s

### GeoBlacklight version 5

Our goals for the next major version of GeoBlacklight depend on upgrading our dependencies and frameworks. We made significant progress on modernizing our Javascript library into ES6 modules and removing our jQuery dependency. This progress is currently part of a development branch that we will resume work on at the next sprint.
For the next major release of GeoBlacklight, our objectives require updating our dependencies and frameworks. In the recent sprint, we achieved considerable progress in updating our JavaScript library to ES6 modules and eliminating the dependency on jQuery. These updates are now part of a development branch, which we plan to further refine in the next sprint.

We also plan to upgrade to Bootstrap v5 and Blacklight v8. [Review our Release Calendar for more details.](../../docs/releases.md)

These framework upgrades will allow us to pursue feature enhancements, such as addressing limitations of the map views or enabling more complex map searches.


### Continuing to support newer data formats

The integration of IIIF Manifests, COGs, and PMTiles into the latest version of GeoBlacklight reflects a growing trend in data sharing, moving away from the conventional of offering discrete, downloadable files and toward a more dynamic model.

### Investigating OpenLayers

We have been using Leaflet since the first version of GeoBlacklight, but begun exploring other mapping libraries, particularly OpenLayers for some features.
We have been using Leaflet since the first version of GeoBlacklight, but have begun exploring other mapping libraries, particularly OpenLayers, for some potential future features.

### Improving the default interface

After we upgrade our libraries, we will be able to address the recommendations from the [Maps UX Workgroup](https://docs.google.com/document/d/1ZXfTMGVAjzi5-KUIqshkLFmkPTFpH-G6cHbLl1oGw6k/edit).
After we upgrade our libraries, we will finally be able to address the recommendations from 2023's [Maps UX Workgroup](https://docs.google.com/document/d/1ZXfTMGVAjzi5-KUIqshkLFmkPTFpH-G6cHbLl1oGw6k/edit).

!!! tip ""

Expand Down

0 comments on commit e2a1862

Please sign in to comment.