Skip to content

Commit 1ffbeb2

Browse files
slafayIGNslafayIGN
committed
feat: add previous codesprint blog posts
1 parent 4f5f73f commit 1ffbeb2

16 files changed

+476
-1
lines changed

‎blog/2022/codesprint.md‎

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
---
2+
date: 2022-06-14
3+
title: GeoStyler Code Sprint 2022
4+
---
5+
6+
From Tuesday, 07.06 until Friday, 10.06.2022 the first GeoStyler Code Sprint took place. 12 motivated coders from all over the world participated and provided great contributions to the GeoStyler project.
7+
8+
{/* truncate */}
9+
10+
We want to thank everyone who contributed to the GeoStyler project. Thank you for your motivation and engagement, for all your great contributions, for all the ideas that came up during the Code Sprint and for all the fun we had during this week! You are awesome!
11+
12+
Thank you
13+
14+
[@krishnaglodha](https://github.com/krishnaglodha),
15+
[@slafayIGN](https://github.com/slafayIGN),
16+
[@geographika](https://github.com/geographika),
17+
[@ocruze](https://github.com/ocruze),
18+
[@pprev94](https://github.com/pprev94),
19+
[@annarieger](https://github.com/annarieger),
20+
[@dnlkoch](https://github.com/dnlkoch),
21+
[@kaivolland](https://github.com/kaivolland),
22+
[@hwbllmnn](https://github.com/hwbllmnn),
23+
[@chrismayer](https://github.com/chrismayer),
24+
[@jansule](https://github.com/jansule),
25+
[@vincjo](https://github.com/vincjo)
26+
and Navid.
27+
28+
![Code Sprint Members](./geostyler-codesprint-2022-members.png)
29+
30+
During the Code Sprint, we achieved the following:
31+
32+
![GeoStyler Code Sprint Stats](./geostyler-codesprint-2022-stats.png)
33+
34+
### GeoStyler User Manual
35+
36+
We now have a GeoStyler user manual, which provides a user centric description on how to style geodata with GeoStyler.
37+
38+
The manual is still a work in progress, but the basic functionality is already documented. Check out https://geostyler.github.io/geostyler-cookbook/ for the current state.
39+
40+
Kudos to [@krishnaglodha](https://github.com/krishnaglodha) and [@jansule](https://github.com/jansule).
41+
42+
### GeoStyler CardLayout
43+
44+
In October 2021, a concept for an additional layout for the [GeoStyler UI](https://github.com/geostyler/geostyler) was created and main features were implemented. This layout omits the use of windows and thereby provides a clean and mobile-friendly look. During the Code Sprint, the implementation could be finalized, and the new layout can be used via the `<CardStyle />` component.
45+
46+
![GeoStyler Card Layout Example](./geostyler-card-layout-hp.gif)
47+
48+
Kudos to [@annarieger](https://github.com/annarieger) and [@jansule](https://github.com/jansule).
49+
50+
### GeoStyler GeoServer Plugin
51+
52+
Multiple fixes and improvements were applied to the [GeoStyler community extension for GeoServer](https://docs.geoserver.org/main/en/user/community/geostyler/index.html). Tests were added, deploy pipelines created, the overall integration into GeoServer was improved and a docker based Dev-Setup was created. Also, the extension will now be served under the dedicated repository [geostyler-geoserver-plugin](https://github.com/geostyler/geostyler-geoserver-plugin).
53+
54+
![GeoStyler GeoServer Plugin](./geostyler-geoserver-plugin.png)
55+
56+
Kudos to [@dnlkoch](https://github.com/dnlkoch).
57+
58+
### Dev-Experience / Dev-Setup
59+
60+
Dev-Experience and Dev-Setup were improved in many different ways. We now have a better support for developing on windows.
61+
Also, the performance for building and working with our interactive documentation was improved drastically.
62+
63+
Kudos to [@slafayIGN](https://github.com/slafayIGN), [@geographika](https://github.com/geographika), [@ocruze](https://github.com/ocruze), [@pprev94](https://github.com/pprev94), [@dnlkoch](https://github.com/dnlkoch) and [@kaivolland](https://github.com/kaivolland).
64+
65+
### Support for Expressions
66+
67+
For quite a while, we were working on the support of expressions in GeoStyler. Through these, it is possible to set styling properties attributively and feature-based, which allows for more compact and dynamic styles. For example, color values can be calculated based on a function that uses attributes of the dataset as function arguments. So instead of providing a single rule for each possible color value respectively, users can now provide a single rule that describes the color value for all features based on a single expression.
68+
69+
Expressions are now supported in the [geostyler-style](https://github.com/geostyler/geostyler-style/) format and was already implemented for the [geostyler-cql-parser](https://github.com/geostyler/geostyler-cql-parser/) and the [geostyler-sld-parser](https://github.com/geostyler/geostyler-sld-parser/). We will work on supporting other parsers in the future.
70+
71+
Kudos to [@hwbllmnn](https://github.com/hwbllmnn).
72+
73+
### French translations
74+
75+
GeoStyler now also supports French.
76+
77+
Kudos to [@slafayIGN](https://github.com/slafayIGN).
78+
79+
### GeoStyler REST API
80+
81+
The [GeoStyler REST API](https://github.com/geostyler/geostyler-rest) was enhanced by providing a new API endpoint `GET /geostyler-rest/api/versions` that gives information about the versions of the used parsers. Besides that, multiple bugfixes and minor improvements were done.
82+
83+
Kudos to [@chrismayer](https://github.com/chrismayer).
84+
85+
### Unsupported properties
86+
87+
The [GeoStyler UI](https://github.com/geostyler/geostyler) as well as the [geostyler-openlayers-parser](https://github.com/geostyler/geostyler-openlayers-parser) and [geostyler-sld-parser](https://github.com/geostyler/geostyler-sld-parser) make now use of the `unsupportedProperties` interface. Due to these changes, the UI now gives hints about properties that were used in the UI but are not supported by a specific parser.
88+
89+
Kudos to [@kaivolland](https://github.com/kaivolland).
90+
91+
### Mapfile validation
92+
93+
The [geostyler-mapfile-parser](https://github.com/geostyler/geostyler-mapfile-parser) will soon be able to validate mapfiles.
94+
95+
Kudos to [@geographika](https://github.com/geographika).
96+
97+
### GeoStyler Demo
98+
99+
The [demo application](https://geostyler.github.io/geostyler-demo/) was improved in multiple ways. The `<PreviewMap />` component now enables zooming and panning in order to verify proper scaleDenominator configuration. The demo now also provides feedback when loading style and/or data. Furthermore, we got rid of using create-react-app and provided our own webpack configuration which facilitates working with linked dependencies.
100+
101+
Kudos to [@ocruze](https://github.com/ocruze), [@pprev94](https://github.com/pprev94), [@hwbllmnn](https://github.com/hwbllmnn) and [@jansule](https://github.com/jansule).
102+
103+
### GeoStyler Mapbox Parser
104+
105+
The [geostyler-mapbox-parser](https://github.com/geostyler/geostyler-mapbox-parser) was improved by fixing the opacity handling for MarkSymbolizer and harmonizing its behaviour with the other parsers.
106+
107+
Kudos to [@ocruze](https://github.com/ocruze) and [@pprev94](https://github.com/pprev94).
108+
109+
### Refactorings
110+
111+
All class based React components were refactored into the more compact and better maintainable function based components.
112+
113+
Kudos to [@kaivolland](https://github.com/kaivolland).
114+
115+
### Bugfixes
116+
117+
The [geostyler-cli](https://github.com/geostyler/geostyler-cli) now also works properly on windows.
118+
119+
Kudos to [@geographika](https://github.com/geographika).
120+
121+
### Conference talks and other media
122+
123+
GeoStyler will be featured on multiple talks on FOSS4G 2022. Also, there will be videos published on how to work with GeoStyler.
124+
125+
Kudos to everyone!
126+
127+
Again, we want to thank everyone who participated in this Code Sprint. It was great fun and an absolute pleasure working with you!
128+

‎blog/2022/geostyler-card-layout-hp.gif‎

1.81 MB
Loading

‎blog/2022/geostyler-codesprint-2022-members.png‎

1.3 MB
Loading

‎blog/2022/geostyler-codesprint-2022-stats.png‎

16.7 KB
Loading

‎blog/2022/geostyler-geoserver-plugin.png‎

134 KB
Loading

‎blog/2023/codesprint.md‎

Lines changed: 102 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,12 @@
11
---
22
date: 2023-06-01
3+
title: GeoStyler Code Sprint 2023
34
---
45

56
From Monday, 08.05 until Friday, 12.05.2023 the second GeoStyler Code Sprint took place. 12 motivated coders from all over the world participated and provided great contributions to the GeoStyler project.
67

8+
{/* truncate */}
9+
710
We want to thank everyone who contributed to the GeoStyler project. Thank you for your motivation and engagement, for all your great contributions, for all the ideas that came up during the code sprint and for all the fun we had during this week! You are awesome!
811

912
Thank you
@@ -48,4 +51,102 @@ We also want to thank [terrestris GmbH & Co. KG](https://www.terrestris.de) for
4851
Additional thanks to all companies that supported this event by allowing their employees to participate!
4952

5053
All of this helped us strengthening the bonds between all participants and thereby, you play an important
51-
role in growing the GeoStyler community.
54+
role in growing the GeoStyler community.
55+
56+
## Contributions
57+
58+
During the Code Sprint, we achieved the following:
59+
60+
![GeoStyler Code Sprint Stats](./geostyler-codesprint-2023-stats.png)
61+
62+
<br />
63+
64+
### GeoStyler CLI
65+
66+
The [GeoStyler CLI](https://github.com/geostyler/geostyler-cli) can now additionally be used as standalone executable! There is no need to install Node.js anymore, if you just want to convert between different styling formats without using the UI. The executables can be downloaded for each version from the [repository](https://github.com/geostyler/geostyler-cli/releases). We support Linux, MacOS and Windows.
67+
68+
Besides that, some maintenance work was done on the repository and semantic-release was enabled.
69+
70+
Kudos to [@geographika](https://github.com/geographika) and [@jansule](https://github.com/jansule).
71+
72+
### GeoStyler Converter
73+
74+
We now have a new demo application that solely focusses on the conversion between different styling formats: [GeoStyler Converter Demo](https://geostyler.github.io/geostyler-converter-demo/). Paste a style into one of the editors, edit the style and convert it into any other format. Some final polishing is still in the making, but the GeoStyler Converter Demo can already be used. See also the [geostyler-converter-demo repository](https://github.com/geostyler/geostyler-converter-demo/).
75+
76+
![GeoStyler Converter Demo](./geostyler-codesprint-2023-converter.png)
77+
78+
Kudos to [@slafayIGN](https://github.com/slafayIGN), [@ocruze](https://github.com/ocruze) and [@pprev94](https://github.com/pprev94).
79+
80+
### Support for Expressions in the UI
81+
82+
After setting the basement for the usage of expressions in the last code sprint in 2022, the GeoStyler UI now also supports expressions. Users are now enabled to create styling rules based on attributes of their dataset. Colors, sizes, strokes, etc. can now all be computed with values derived from the geodata itself. So if you want the size of a point representing a city being proportional to the number of its inhabitants, this can now be easily achieved. Many real-world styling challenges can now be adressed in an appropriate, compact and flexible way. And the best part of it: There is no need to write the expressions by hand. The UI provides a graphical editor just for that. Now, the parsers need to be updated to fully support this feature.
83+
84+
![Expressions UI example](./geostyler-codesprint-2023-expressions.gif)
85+
86+
Kudos to [@kaivolland](https://github.com/kaivolland).
87+
88+
### GeoStyler UI
89+
90+
Besides the support for expressions, the GeoStyler UI was improved in various ways. We are currently adding icons to options in dropdowns, so users can directly see what an option stands for. What was the difference again between `butt`, `round`, and `square` line caps? The answer will be directly graspable from the editor.
91+
92+
We also cleaned up some dependencies, make use of [Vite](https://vitejs.dev/) for creating our browser builds, improved the test performance, and upgraded to antd 5. As part of this, we replaced the windows with antd modals and did some polishing here and there.
93+
94+
The previously introduced `GeoStylerContext` was also implemented in various components, which will simplify adjusting the GeoStyler UI to your needs.
95+
96+
![GeoStyler UI Modal Example](./geostyler-codesprint-2023-modals.gif)
97+
98+
Kudos to [@dnlkoch](https://github.com/dnlkoch), [@SchulA](https://github.com/SchulA), [@jansule](https://github.com/jansule) and [@hwbllmnn](https://github.com/hwbllmnn).
99+
100+
### GeoStyler Mapbox Parser
101+
102+
We spent quite some time discussing the [geostyler-mapbox-parser](https://github.com/geostyler/geostyler-mapbox-parser) and how we can integrate the concept of map-based styles (which mapbox is using) in addition to layer-based styles (which SLD is using) in GeoStyler. We came to the conclusion that layers in mapbox fit quite well to the idea of rules in layer-based styles. Both are entities consisting of filters, scale denominators and styling instructions. With the support for expressions in GeoStyler in particular, we should now be able to advance the development of the geostyler-mapbox-parser and make it a first class citizen in the GeoStyler ecosystem.
103+
104+
Besides that, the geostyler-mapbox-parser was enhanced by splitting or merging styling rules where needed. A consistent style structure after parsing is still being maintained by enriching the mapbox-style with metadata.
105+
106+
Kudos to [@ocruze](https://github.com/ocruze), [@pprev94](https://github.com/pprev94), [@slafayIGN](https://github.com/slafayIGN), [@kaivolland](https://github.com/kaivolland), [@jansule](https://github.com/jansule) and [@ahocevar](https://github.com/ahocevar).
107+
108+
### GeoStyler Homepage
109+
110+
The [GeoStyler homepage](https://geostyler.org/) was updated to provide better information about the idea of GeoStyler and the different tools that it provides. GeoStyler is more than just a UI library!
111+
112+
![GeoStyler Homepage Example](./geostyler-codesprint-2023-homepage.png)
113+
114+
<br />
115+
116+
Kudos to [@OSHistory](https://github.com/OSHistory), [@geographika](https://github.com/geographika) and [@jansule](https://github.com/jansule).
117+
118+
### GeoStyler SymCore Parser
119+
120+
We added a new parser to the GeoStyler ecosystem: the [geostyler-symcore-parser](https://github.com/geostyler/geostyler-symcore-parser). This parser will allow the conversion between geostyler-style and the new [OGC Styles & Symbology Models and Encodings - Part 1: Core](https://github.com/opengeospatial/styles-and-symbology) standard. For now, the parser only contains the typings of the standard, but will be implemented in the future. This parser should facilitate the switch to the new standard and will hopefully increase the adoption of it.
121+
122+
Kudos to [@kaivolland](https://github.com/kaivolland) and [@jansule](https://github.com/jansule).
123+
124+
### GeoStyler GeoServer Plugin
125+
126+
The [geostyler-geoserver-plugin](https://github.com/geostyler/geostyler-geoserver-plugin) was updated to use the latest version of GeoStyler. Additionally, multiple bugs were fixed and the build artifacts are now being published on [nexus.terrestris.de](https://nexus.terrestris.de/#browse/browse:geoserver-extras:org%2Fgeoserver%2Fcommunity%2Fgs-geostyler). Instructions on how to download and use the build artifacts were added to the README.
127+
128+
![GeoStyler GeoServer Plugin](./geostyler-codesprint-2023-geoserver.png)
129+
130+
Kudos to [@dnlkoch](https://github.com/dnlkoch), [@hwbllmnn](https://github.com/hwbllmnn) and [@marcjansen](https://github.com/marcjansen).
131+
132+
### Miscellaneous
133+
134+
Users will now be redirected to the [GeoStyler homepage](https://geostyler.org/) when going to [geostyler.github.io](geostyler.github.io/).
135+
136+
The [geostyler-cql-parser](https://github.com/geostyler/geostyler-cql-parser/) was fixed, so that it can be directly used without the need to add configurations to webpack.
137+
138+
The GeoStyler repositories are now transitioning to using issue forms instead of templates. This should lower the barrier for non-technical users to create issues and thereby helping GeoStyler becoming a more welcoming community. See for example the issue form for a [feature request](https://github.com/geostyler/geostyler/issues/new?assignees=jansule%2CKaiVolland&labels=enhancement&projects=&template=feature_request.yaml).
139+
140+
The [GeoStyler Beginner Workshop](https://geostyler.github.io/geostyler-beginner-workshop/) is currently being updated and will use Docusaurus instead of Jekyll as static site generator. The content of the workshop will also be updated in the future, to reflect the latest state of GeoStyler.
141+
142+
The robustness of [geostyler-rest](https://github.com/geostyler/geostyler-rest) was improved by better handling unknown input and output formats, or inconsistent styles.
143+
144+
Kudos to [@slafayIGN](https://github.com/slafayIGN), [@OSHistory](https://github.com/OSHistory) and [@jansule](https://github.com/jansule).
145+
146+
### Conference talks and other media
147+
148+
GeoStyler will be featured on multiple talks on FOSS4G 2023.
149+
150+
Kudos to everyone!
151+
152+
Again, we want to thank everyone who participated in this Code Sprint. It was great fun and an absolute pleasure working with you! We are already looking forward to the next GeoStyler Code Sprint.

0 commit comments

Comments
 (0)