Imagico.de

blog

January 19, 2023
by chris
2 Comments

Names and labeling in OpenStreetMap

More than five years ago i wrote a blog post here on the problem of name tagging and multilingual names in OpenStreetMap. I want to give an update on the situation from my perspective and reflect a bit on what has changed since then and what has not. Also, this is meant to serve a bit as an introduction to a following blog post i plan about changes to the rendering of labels in my map style.

What i explained five years ago is essentially that the primary way through which mappers in OpenStreetMap record names, the name tag, has been central in establishing the idea of OpenStreetMap recording the local knowledge of its contributors because it is, by broad consensus, explicitly meant to record the locally used name of geographic features. Since every mapper anywhere on the planet does this in exactly the same way and sees this local name directly on the map as they have recorded it, this practice well represents the idea of jointly mapping the planet in all its diversity.

On the other hand – what i also mentioned already five years ago – this practice unfortunately comes with various problems:

  • it is based on the illusion that there is always a single local name.
  • recording the local name without any information on the language of that name creates serious issues in some cases (in particular in what is commonly known as the Han unification problem).
  • what mappers want to see as the label of features in the map very often is not the locally used name.

The solution from the tagging side that i proposed back then as well as various other attempts to suggest tagging ideas to address the first two of these problems did not find broader support. Both mappers and data users seemed mostly content with the status quo.

The situation today

In a nutshell: The situation today and the problems described are essentially unchanged. The problems which were already visible back in 2017 have, however, aggravated and it is visible now quite clearly that the current practice is not sustainable. Trying to categorize the use of the name tag today i get the following:

The vast majority of name tags record a single name. In most cases this is the locally used name. However, there is also a significant percentage of cases where non-local mappers record names they use or are familiar with in the name tag despite them obviously not being the locally used name (like because they are in a language not widely spoken locally). In other cases local mappers use a signed or official name (i.e. one endorsed by some sort of authority, either political authority or the owner of the feature in question) rather than the name used locally in practical communication.

All of these variants of recording a single name in the name tag that is not the locally used name are largely motivated by the fact that many data users either only interpret the name tag directly as a label tag or give it priority over other tags with names when selecting what to label. This incentivizes mappers to record the name they want to see on the map – which, depending on the individual mapper and the local cultural conventions in map design, can mean different things.

The second most common use case for the name tag after recording a single name of some kind is to record something that is not a name at all. This practice is partly fueled by the same mechanism i already discussed. The other reason why we see this is because the concept of names (or more precisely: proper names) is a highly abstract matter that quite a few mappers have difficulties with. A significant percentage of uses of the name tag for things that are not a proper name are cases where mappers record a real world label that is not showing a proper name of the feature. Often this is a brand (like in case of shops etc.), the name of a person operating a feature (that would usually be tagged with operator), address components or a classification (think of a playground where there is sign indicating use restrictions: Playground: use only allowed for children of age under 14 – and the mapper interprets the Playground as the name of the feature).

Multiple names

The third most common use case for the name tag – and we are down to a single digit percentage here, though for specific feature types and in some regions this is much larger – is the recording of multiple names in the name tag. This, likewise, is largely motivated by data users showing the name tag as is as a label and mappers in some cases seeing the display of several names in the map as the most desirable form of labeling.

There are two fundamentally different variants of this recording of multiple names in the name tag. One (and the vastly more widespread one of the two) is the recording of names in different languages. If there is not a single locally used language but several ones, a feature will usually have different names in these different languages and accordingly no single locally used name. The other (much less common) variant is when there is more than one locally used name in the single locally used language and it is not possible to verifiably determine which is the locally more widely used name.

I like to add that for both variants of this there is also the rather common case that a single locally most widely used name can be determined, but mappers – for social or political reasons – do not want to specify that and prefer to record several names as if they are equally widely used locally, even if they are not.

There has been some renewed interest more recently in the OSM community on the subject of recording multiple names in the name tag but most of the discussion dealt with the rather superficial and insignificant question how to separate the different names in that case. This is kind of like planning to pave over the cracks and discussing what shape of paving stones to use for that purpose.

In practical use the most common separators for multilingual compound names are ' / ' and ' - ' (that is slash or dash/minus with spaces around) and – for compound names where the components are distinguished through different scripts – it is also common to not have a separator at all (using just a space, which equally is used between different words of the individual names). The semicolon (;) has some use, but mostly in non-multilingual situations, in particular in cases where the different names refer to different real world features.

Despite all these inconsistencies and conflicting mapping practices there is one broad consensus about multilingual names: If there are names of multiple languages in compound name tags, each of the components should be also separately recorded in the respective name:<lang> tag. While this rule is not universally followed, there is clearly broad consensus that this is desirable.

The dilemma in map rendering

The core of the problem on the social level (and the reason why nothing of substance happened in that field for the last five years) is that the illusion of the name tag recording the single locally used name is rather convenient for data users because it allows them to label their map in a very simplistic fashion and at the same time the ability to directly control the labels in maps is something mappers have come to value and many mappers do not have the confidence

  • in data users to be able and willing to interpret more cleanly structured information in a way that results in good maps.
  • in their fellow mappers to diligently record more cleanly structured information on names (and the inconsistent use of the name tag is directly confirming that suspicion).

What i (and others) have tried in the past is presenting ideas how the problem can be addressed from the mapping side. But neither data users nor mappers turned out to be very keen of changing the status quo.

Also – both on the mapper and on the data user side – the most influential circles in the OSM community are from Western Europe and North America and primarily interested in languages using Latin script – hence have only little interest in solving the problems the lack of information on the language(s) of the name tag causes.

The dilemma for map designers, in particular in OSM-Carto, is, that it is completely clear meanwhile that the simplistic rendering of the name tags as labels for many features in OpenStreetMap is a large contributor to the bad situation as outlined above. In other words: We as map designers are part of the problem and it therefore would be prudent in a way to stop doing that. But since we want – for the reasons mentioned above and in the blog post from 2017 – to continue rendering local names in the local language everywhere on the planet and because there is no established way of record that information in OSM other than the name tag, we have no way to really do that other than displaying the name tag. And we do not want (for very good reasons i explained recently again) to actively steer mappers to change their mapping practice in a way we consider desirable.

One approach to try to overcome this stalemate between mappers and data users could be to actually present a working proof of concept showing both the benefits of actually solving the problem (instead of just paving over the cracks a bit – see above) and how a smooth transit from the status quo to such a solution could look like. And above all – to show that following such a route does not require mappers to relinquish control over mapping practice to a small elite of technical gatekeepers but would allow mappers to continue making self determined decisions and to present a solution that respects and builds on the few points described where mappers actually have consensus about how names should be mapped. This is what the next blog post is going to be about.

January 11, 2023
by chris
1 Comment

On open map design licensing

I have been working on a number of changes and new features for the Alternative Colors map style (AC-Style) during the past few months (more on that likely in future blog posts) and during that time have also contemplated quite a bit about the situation of open map design – in general and in the OpenStreetMap community specifically. One outcome of these considerations is that i have decided to change the license of the style. And in this blog post i want to explain why.

Rule based map design is something of an unusual concept – both for those who come from and who look at things from a perspective of traditional IT and software development, as well as for people with a traditional graphics design, visual art or cartography background. A map style like OSM-Carto or the AC-Style contains rules on how geodata is transformed into a visual representation – the map. These rules are implemented in the form of code that is automatically processed by computers. Hence many software developers (and sometimes also traditional designers) have a tendency to view map styles as software and to reduce them to being software. The main problem with that (apart from dismissing the core of map design work itself as insignificant) is that the way map styles work clashes with the classic paradigm of computer programming that software processes data and that the two things are technically and legally separate. Past conversations i have had about copyright and licensing of map design have often shown that many people working in IT firmly believe that when you process data with a computer program the copyright of the processed data is categorically unaffected by the copyright of the computer program. That there are such things as self replicating programs – challenging this idea quite clearly – is typically considered a practically irrelevant special case.

The map produced by an automated rule based map style, however, is a derivative of both the geodata the style is applied to and the style itself. The resulting map obviously does not contain the generic logic of the map style any more, but it contains the work of the map designers who developed the style – in the form for example of carefully balanced color combinations or line signatures – or just in the selection of what to show and what not to show at a certain map scale. And these choices are actually manifested in the resulting map. Hence the rendered map is not only based on the map style and the work of its developer in the same sense as a computer program generating data according to the intentions of its programmer, it directly and literally contains the design work itself. Or in other words: You could call it a collage of the work of the mapper generating the geodata and the work of the map designer writing the style rules.

In light of this it is rather curious that most openly licensed map styles either waive all rights of their designers (like with CC0) or are licensed under a software license (usually a fairly liberal one like BSD or MIT). This is especially remarkable in the context of OpenStreetMap, where the work of the mappers is subject to the significantly more substantial terms of the ODbL.

Superficially this makes it easier to deal with the peculiar nature of map styles as works subject to copyright. But i doubt, meanwhile, that in the long term this actually provides a net benefit. I have pointed out on this blog on several occasions now that i think in the OSM-Community (and probably also in geodata processing and digital map production in general), intellectual work, and that of course in particular means map design work, is severely undervalued compared to technical work and that this substantially limits innovation in the domain. That most open map design projects in this context are licensed in a way that allows the users of the map styles to pretend they are just software seems quite clearly not helpful in that regard.

One specific observation that made this abundantly clear was that when i pointed out to the board of the OpenStreetMap Foundation back in mid 2022 that it would be nice and morally advisable if the OSMF as the largest user of OSM-Carto would acknowledge the work of the OSM-Carto designers in their public communication, in particular on the website where the map is shown – nothing happened. And why should it you could say. If the OSM-Carto designers really would want this kind of acknowledgement they could require that in their license. And since as is this is legally not required – why should the OSMF provide it?

One important prerequisite to change the way the OSM community looks at map design work quite clearly is to provide some practically straightforward options to map designers how they can license their work in a way that

  • ensures that the style and other map design work derived from it remains open and can be used under similar terms.
  • properly acknowledges and deals with the special nature of rule based map design as something that has both software components and contains visual design work that is included in the produced maps.
  • requires users of the design work to acknowledge and credit the work of the map designers developing the style.

This is not easy because there so far seem to be no licenses specifically developed for map styles. What helps, however, is to look at other domains where the situation is similar. Economically significant here is in particular the field of computer games where – in a similar fashion as in map design – you have a combination of visual design work and software development that gets exposed to the user in the form of a collage. License models that are used in that context could therefore be suitable for map style licensing as well.

The choice i have made for the AC-Style is to license the visual design components under CC-BY-SA 4.0 and the software elements under AGPL 3.0. Both CC-BY-SA and AGPL have in the past been used in map design contexts – CC-BY-SA notably in the OpenTopoMap project, the AGPL for example for the transliteration work of Sven Geggus. Practically those licenses mean that you have share-alike provisions for both the software and the design components and that deployments of the style or derivatives need to release any modifications of the style rules under compatible terms (which would not be the case with the GPL). If this is practically a good choice of licenses will remain to be seen – like the style itself the license can be considered experimental.

Having the two different licenses for software components and visual design work does not mean that you can flatly assume that all parts written in a programming language are only subject to the AGPL. As i have tried to point out above this is not merely a technical distinction. There are plenty of cases in the style where visual design is implemented in the form of code – see the symbol designs for trees that are represented in the form of SQL code for example.

That i license the AC-Style under this license scheme does not mean that the features and ideas i develop in the style cannot also make it into OSM-Carto any more. So far i am the sole author of the specific features of this style and i am free to also license parts of this work under a different license if i choose to. On the other hand, it might of course be a good idea to discuss if to change the license of OSM-Carto as well. As i have discussed above, it is meanwhile fairly doubtful if the choice of a very liberal license for an open community map design project like OSM-Carto is of benefit for progress and innovation in the field and for attracting competent designers to contribute to the project.

I am, however, also aware that moving to a license more limiting for the style user is not necessarily going to widen the user base of the style. The whole initiative to change the license is part of a long game to raise awareness that rule based map design is not just a somewhat specific type of software development but a field of value and importance on its own that depends on qualified and talented designers being motivated to invest their time and energy in it.

I also want to make clear that this license change is not meant to diminish the work of the OSM-Carto contributors whose work the AC-Style is based on. Therefore i ask – for the attribution as required by the new license – to specifically also acknowledge their contributions.

The main result i hope for is that this initiative encourages other map designers to (a) embrace the idea of open map design and (b) to make more conscious and self determined choices about the terms under which they make their work available to others. Right now, unfortunately, too many map designers – when working on rule based map design – happen to publish their work not under terms of their choosing but under ones that others (who are often not map designers) have picked. Or they keep their work proprietary because they cannot find a good way to make available and share it and to not at the same time make it available for selfish exploitation by others without giving anything back.

December 22, 2022
by chris
2 Comments

The statement the OSMF should have made

A lot of fuzz has been made in the OSM community in the past week about a new cooperation that has been announced to start between a number of US tech companies. I am not going to comment on this in substance at this time (because there is nothing of substance to comment on so far and because i have moved away a bit from doing real time commentary on OSMF matters in general). For those who are interested in meaningful commentary i would point to Ilya’s comment, which – although i disagree with quite a few considerations of his – is the most considerate and informed comment i have seen so far.

What this blog post is about and where i could not refrain from commenting on in some form is the statement released by the OpenStreetMap Foundation today. And i don’t actually want to comment on it, instead i want to present – for your consideration as readers of this blog – the statement that in my eyes the OSMF should have made:

The OpenStreetMap Foundation is pleased to hear the announcement of a number of large users of OpenStreetMap data to cooperate more on the use of OpenStreetMap data and other Open Geodata sources. In particular the announcement that the results of this cooperation are to be largely published under open licenses is good news for the Open Geodata and the Free Open Source Software community.

OpenStreetMap data is available for anyone to use under the terms of our license and we have published guidance on how you can make sure to meet these license requirements when using our contributors’ data, in particular also in combination with other open data sources. Given the partners in this new cooperation have indicated that their contributions of data are going to be released under terms compatible to the ODbL, we do not envision difficulties with our license terms. We will of course continue to keep an eye on how OpenStreetMap data is used to ensure equal and fair conditions for all OpenStreetMap data users. By sharing data you combine with OpenStreetMap data for a more valuable combined product under compatible license terms – as it is required by our license – you support the idea of Open Data and by providing attribution for the OpenStreetMap contributors whenever you use OpenStreetMap data or data and services made with OpenStreetMap data in a form that ensures that your users become aware that OpenStreetMap data is used, you show appreciation and provide support for the work of millions of mappers in our community.

We invite the Linux Foundation as the organization hosting this new cooperation to become a corporate member of the OpenStreetMap Foundation. By doing so you support the OSMF in supporting the OpenStreetMap community with important infrastructure for their volunteer work and this way also provide material support for the OpenStreetMap community.

The strength of OpenStreetMap is its large global and globally widely distributed community of contributors and the local knowledge they provide as mappers to our project as well as the diverse skills and the expertise they bring into continuously further developing and improving the way we map our planet. We therefore do not consider the more industrial and mechanized geodata aggregation and processing ideas this new cooperation has announced to pursue to in any way compete with the work of the OpenStreetMap community. There could be chances in the future for data released by the new cooperation to be of value for our mapper community to support and help them in their work and the share-alike terms of our license help ensure that such data would be available for such use. But the core of OpenStreetMap and the key to our success is and will always be the commitment of our mappers to sharing their local knowledge and to cooperate in making this shared knowledge available to everyone.

Imagico.de StyleInfo

December 20, 2022
by chris
0 comments

Introducing StyleInfo

In the previous blog post i introduced a bit the idea of systematic testing in map design and how my work on that has led – as a byproduct if you want to say so – to the rendering illustrations you can find on TagDoc.

But there is another problem most automated rule based map rendering projects are faced with that can be solved with systematic testing. Map styles, in particular more complex ones like OSM Carto, face the problem that it is very hard to determine what the style actually renders (meaning which attribute combinations are rendered in a distinct fashion at what zoom levels) by looking at or by analyzing the code. The only reliable way to do that is by actually rendering things. The only meaningful index or map key of OSM Carto that exists so far is a hand curated wiki page produced by people based on their knowledge of the style.

The way systematic testing can be used to help with that is by feeding the style with various combinations of data and checking which of them results in a distinct rendering. As you can probably imagine this would require a prohibitive number of tests if you’d do that in a dump fashion. But by using heuristics to narrow this down, the effort required can be reduced to manageable level – even if you still end up with more than 100k tests in case of a map style like OSM Carto.

And this is what i want to introduce here – StyleInfo is a new tool that i created that allows you to view how various map styles depict OpenStreetMap data – based on an analysis of the style that uses heuristic systematic testing to determine what the style renders and in what form without requiring substantial up-front information about the style.

StyleInfo is structured a bit like Taginfo, it allows you to look at the different keys and tags of the OSM tagging system – but instead of showing how these tags are used in the database it shows how these tags are depicted by the selected style.

Key based view in StyleInfo

Tag based view in StyleInfo

In addition you can also look at how the style depicts tags only on a specific zoom level.

Zoom level based view in StyleInfo

All of this is cross referenced with links so you can move between the different views quite easily. A few examples:

The information about the map style this gives you is somewhat limited particularly in two ways:

  • For principal reasons the results cannot be guaranteed to be complete. I have already identified a few tag combinations that are missing in some styles in the analysis and will need to make adjustments to the heuristics because of that. None the less this is still the most comprehensive documentation of OSM Carto and derivative map styles available so far.
  • StyleInfo so far shows renderings of primary tags and combinations of primary tags with one secondary tag. Neither combinations of several primary or secondary tags nor tertiary tags are covered so far. What this means exactly i will explain in more detail in the following.

The underlying tagging model

In principle OpenStreetMap uses a free form tagging system – i have discussed that in more depth in context of TagDoc. Practically, all OSM based map styles interpret this tagging in a somewhat more constrained fashion and because of that, mappers also tend to use tags under this somewhat more constrained tagging model.

In this model (as documented on TagDoc) tags are roughly divided into

  • primary tags – those are tags that provide semantic meaning to a feature even if they are applied alone.
  • secondary tags – those are tags that only have a well defined meaning when applied in combination with a primary tag.

In the context of map rendering and therefore StyleInfo, primary tags are tags that alone – when applied to some geometry – influence the rendering result. That would be tags like natural=water on polygon geometries, highway=motorway on linear ways or amenity=pub on nodes. Secondary tags are tags that modify the rendering of a primary tag. Examples are name=* on any of the previously mentioned primary tags or bridge=yes on highway=motorway.

Practically, there are some cases in styles that do not follow that model. For example administrative boundaries are rendered by most map styles only if they are tagged with both the primary tag (boundary=administrative) and with an admin_level=* tag (in case of OSM Carto with admin_level between 2 and 10). That requires introducing a third type of tags into the tagging model:

  • qualifier tags – those are secondary tags without which the primary tag is not interpreted by the style.

In addition to the mentioned example of administrative boundaries, the most common qualifier tag is the name tag on features a map style renders with only a name label.

Note different map styles make different assumptions on what are primary and what are secondary tags – which poses additional difficulties on the analysis. OSM Bright and also OSM Carto in early versions interpret name=* as a primary tag and render name labels for anything with a name tag even in the absence of any other tags.

And as said – what StyleInfo so far does not cover is combinations of several different primary and secondary tags – which is interesting to look at because sometimes styles distinctly render such combinations (like a road with a bridge tag and access restrictions) while in other cases one tag shadows another (like most cases with several primary tags). What is also not covered is tertiary tags – that is cases where a three tag combination leads to a distinct rendering result – like in OSM Carto certain values of denomination=* in combination with religion=christian on amenity=place_of_worship changing the symbol used.

The principal limitations

Some might have already wondered about the selection of styles featured currently on StyleInfo. As you can see with the Map Machine style the analysis is not limited to CartoCSS/Mapnik styles. However, because of the large number of tests that needs to be run it is necessary that integration tests of the full rendering chain can be run efficiently on general purpose hardware in a headless configuration. And that is difficult for all of the postmodern client side rendered styles popular these days. If anyone can point me to a toolchain that renders Maplibre/Mapbox JSON styles into plain image files on headless general purpose hardware without depending on esoteric bloat like npm or docker i might give it a try.

For OSM Carto and other styles with a rendering database that directly reflects OSM tagging without any fancy tag reinterpretations on import, the map style analysis can be made quite a bit faster by excluding the database import step from testing. This underlines my past observation that the idea of performing tag interpretations on data import instead of during rendering – a consideration that has gained quite some popularity recently in the OSM community – is a bad idea from the perspective of map design. You gain nothing of substance (because tag interpretation is cheap) and it requires the map designer to either integrate the database import into their design work and testing (just like i need to do for the StyleInfo analysis) or to develop their style not for OSM data but for an intermediate data model out of their control (which is what most of the postmodern client side rendered style development tends to do – hence probably the popularity of that idea).

A viable map key?

What StyleInfo documents is how a map style translates OpenStreetMap data and tagging into a visual depiction. While this is evidently a key element of producing a usable map key or legend it lacks the translation between the OpenStreetMap tagging and real world semantics to qualify as such. This is – as some readers might remember – what TagDoc is aiming at. StyleInfo and TagDoc are projects complementing each other and the idea is that those two together could be key components to provide a much better understanding of the semantics of OpenStreetMap data and of OpenStreetMap based map styles to a wider audience.

Tags interpreted by OpenStreetMap Carto - visualization from StyleInfo, click to see interactive version

Tags interpreted by OpenStreetMap Carto – visualization from StyleInfo, click to see interactive version

Systematic testing in map design

December 19, 2022
by chris
0 comments

Systematic testing in map design

This post’s subject is a matter i have been working on for quite some time – the problem of systematic testing in map design. To make clear what this is about i will have to explain a bit the wider context.

Traditional testing in map design

The traditional way of designing rule based map styles, in particular in the OpenStreetMap context, is to do so based on a test database containing a sample of actual map data. Most map designers have a test database, typically containing either an extract (like from Geofabrik or created with the Overpass API) of their area of interest or a number of areas from different parts of the world. You can get an idea of the content of my test database through the ac-style sample gallery.

When you work on the design of a certain type of feature you find one or more occurrences of this in your test database and study the effects of your design work on these occurrences. Commonly used design tools – like TileMill in the early days, or Kosmtik (in case of CartoCSS styles) and other tools, like Maputnik, in case of JSON based styling languages – are specifically designed for this workflow.

Many examples of use of this approach in style development can be found in OSM-Carto – like here.

This design work strategy has several advantages:

  • It is fairly straight away and does not require significant work from the designer to get started.
  • It tests the design in exactly the context it is meant for, that is rendering of actual map data.

But it also inevitably comes with disadvantages:

  • You only test the design in those contexts you happen to have picked as sample occurrences. That usually neither covers all the relevant situations the design is going to be used in nor is it representative for the full diversity of locations that feature occurs in.
  • It is very difficult to do any sort of systematic testing. Even the comparison across different zoom levels is difficult because the geometric context changes in scale as you change zoom levels.

Synthetic tests

Because of these problems OSM-Carto developers have for a long time and in addition to the traditional testing based on real world test data started using synthetic tests. I can’t say for certain when this was done the first time but here are two examples:

OSM-Carto synthetic test example 1

OSM-Carto synthetic test example 2

Typically such tests are designed in JOSM, run through osmium renumber and then imported into a test database.

This kind of test is particularly useful for somewhat more experienced map designers who can already predict in advance in what contexts a certain change is in particular critical to be evaluated in.

I would go as far as saying that changes of the road rendering system in OSM-Carto, that often need to work in many different design contexts, are almost impossible to develop without the use of synthetic tests. The unpaved road rendering that recently finally made it to OSM-Carto is a good example for that:

OSM-Carto synthetic test example 3

As useful as this kind of testing is, it also bears the risk of map designers completely focusing on synthetic tests and neglecting testing with real world data. That is of course not a good idea. In practical map design real world data testing is always necessary and important.

The other issue is that with this kind of hand drawn synthetic tests you still have the problem of limited comparability across zoom levels.

Automated scaling of tests

This limitation has led me a few years back to develop an approach to scale synthetic test data sets in an automated fashion for better cross zoom level comparability. I have shown samples using this approach on several occasions on this blog. By scaling the test data to the zoom level you want to test at you make rendering results much better comparable across zoom levels. This is in particular useful to make sure that design parameter progressions across zoom levels (like line widths or label sizes) are working well.

Road features at z16

Road features at z16

Same at z17 with scaled geometries

Same at z17 with scaled geometries

Systematic testing

Once you have automated scaling of tests working, it is only a small additional step to systematically test rendering results across zoom levels and with different combinations of attributes. This allows two things:

  • formally testing map design in all the different variants it is supposed to work in.
  • documenting the functions of a map style in a comprehensive fashion.

The latter use case is something i already demonstrated some time ago in TagDoc:

Rendering samples from TagDoc

Lately i have further developed the whole concept of systematic map style testing into a tool i am going to introduce in the next blog post.

New Antarctic images for mapping

December 10, 2022
by chris
1 Comment

New Antarctic images for mapping

I recently prepared and uploaded some more satellite images of the Antarctic for mapping in OpenStreetMap. They mostly cover the mountain areas of Queen Maud Land, that is the section of the East Antarctic coast facing the Atlantic Ocean. This has historically been a major focus area of European exploration of the Antarctic and features some of the most spectacular landscapes of the continent. Also included are some more images of the Antarctic peninsula.

In addition to the 10m resolution Sentinel-2 images i also included a number of evening Landsat images because having two images with different illuminations available can be of high value for mapping peaks and ridges in mountainous terrain. Here an example:

Also otherwise i specifically keep the individual images in separate layers so mappers can consult several different images where available for better assessment of the local situation.

If you have read my previous discussion of the state of mapping of the Antarctic you might be wondering why i put effort into this despite the clear lack of interest in the OSM community at large in mapping the Antarctic. The reason is that in light of the poor situation in most image sources commonly used by mappers in this area i want to make sure mapping is at least not hampered by the lack of suitable imagery.

The imagery i have prepared for the Antarctic now covers more than half of those parts of the continent containing ice free areas. That means if you are interested in mapping a particular part of the continent you might still be out of luck with finding decent imagery. If you, however, are interested in mapping the continent in general you have plenty of places to do that all over the continent.

As before the new images are likely going to be available in the editors soon – if you can’t wait you can also add them manually based on the links provided on my preview map.

November 23, 2022
by chris
0 comments

The OpenStreetMap Foundation in 2022 – Trends and Outlook

In this third part of this year’s discussion of the OSMF i am going to look at the overall trends in the organization as i see them. For the first two parts see here and here.

It is hard to make reliable predictions regarding the OSMF board with four of seven board members being new next year. What is clear is that if there is a substantial change in direction or work style pursued by the new board members, that is going to be a hard uphill battle for them against the inertia and established work culture within the organization. Two of the board members who are going to continue have made it clear that they are going to want things to mostly stay as they are and the third one has shown no indications of different interests so far. Some of the candidates in their statements and answers have also made it clear that they pursue a conservative agenda.

So, based on the assumption that this conservative desire to keep things going in the present direction will prevail, i am going to describe a bit what i perceive to be the current trends in the OSMF as they are likely to continue in the future. I don’t want to be too repetitive to what i wrote in previous years so this is just a few notes on the more recent changes of direction and new tendencies. I am also – for every section – constructively going to provide a suggestion for the OSMF how to turn the development in a more positive direction. Based on the experience from past years i don’t have high hopes that these are going to be followed, but i think it is important to outline that concrete better alternatives exist and that they are, for the most part, not difficult to pursue. And i want to give the four new board members, whoever they might be, the benefit of the doubt.

Clouds and seagull

Centralization of communication and cultural homogenization

With the definitive roll-out of the behavior control framework and the new communication platform, the trends of previous years for more explicit centralized control and management of community interaction have started to substantially manifest this year. There are mainly two trends i expect to come out of this:

  • An increasing encapsulation of people on the new platform from the rest of the OSM community. In a nutshell: that new platform and how it is managed is modeled after Facebook rather than Usenet. The strongly hierarchical elements and the prominent display of participation and engagement scores in the design of the platform’s user interface and the clear distinction between the logged in user tracked in their activities at every moment and the not logged in anonymous outsider with very limited options all support this by underlining and affirming an exclusive sense of ‘we’ on it. A desire to exclude people not using the platform has already been articulated on various occasions by users there. How fast and how far this will go is not sure yet, because at the same time there is
  • a trend of fragmentation of the OSM community into closed social circles. Due to the exclusive nature of the new platform, requiring participants to significantly adjust to the social standards and expectations that are imposed centrally, quite a few local communities have decidedly not adopted the new platform as a place of exchange. Since the OSMF has expressed no commitment to continue to provide the more traditional infrastructure like the mailing lists and because of trends in communication styles, many local communities have moved to proprietary platforms like facebook, telegram or dicord instead. These have the advantage for the local communities that the commercial operators give them more freedom than the OSMF on their platform to self manage the channel in their own style. But many of these channels are semi-public (so you can only read them after having actively signed up to them – so there is no permanent public record) which often leads to significant radicalization in particular in smaller groups.

To be clear: It is perfectly expected and necessary that a diverse and multi-cultural project like OpenStreetMap socially structures into different local groups and communities with different local cultures. The key for this to work is that these groups need to interact with each other on equal levels based on tolerance and respect for each other on the foundation of the basic universal core values of the project. This can only work by accepting and tolerating that they might differ fundamentally in their cultural values, social conventions and collective and individual goals otherwise. This way different local communities form a loose but stable and inclusive sense of ‘we’ overall across culture boundaries, unconditionally including anyone who likes to participate under the basic premise of the project of cooperative mapping. What does not work and where unfortunately the current trend seems to go, is, that one part of the global community tries to impose their cultural standards and values on others and by doing that attempts to colonialize the project while others increasingly encapsulate themselves, partly in reaction to the colonial tendencies, to protect their cultural values. This is what we see happening right now. Unfortunately, the most likely reaction from the OSMF is going to be to increase the pressure and extend the radius of cultural homogenization and cultural imperialism.

What could the OSMF do to avoid this? Go back to the roots and provide communication infrastructure openly to any group within the project to manage under their own responsibility. Offer support and guidance when self managed communities struggle dealing with difficult individuals or outside interference but have trust in people to be socially responsible at large, even if they don’t abide by and subscribe to your cultural values.

Clouds

Decreasing diversity within the OSMF

In addition to these trends in the OSM community at large we also see an increasing commitment in the OSMF to the currently dominant culture in the organization. I mentioned in the first part that the first board committee with non-board members involved has been staffed exclusively with Americans. It is likely that fundraising in the future will therefore perpetuate the dominance of US corporations and organizations among the financiers of the foundation. And since corporate OSM data users and organizations like HOT are meanwhile the main source of new volunteers in the OSMF working groups, this will also have an influence on diversity among volunteers in the working groups that are not selected by decision from the top. And this is – as pointed out in previous years – a self emphasizing problem as the increasing presence of people with a professional interest in OpenStreetMap in the structures of the OSMF makes these less attractive for hobbyists.

As discussed in the first part, the Engineering Working Group this year took on the fairly remarkable initiative to draft a framework for open calls for tender of projects to be financed by the OSMF. While this is of course specifically designed for software development projects, it could be used as a blueprint for similar procedures being made mandatory everywhere in the OSMF where outside paid services are contracted. While this in principle would be a very positive perspective i see two problems with that:

  • It is uncertain if this framework will actually be followed for any larger projects at all. The OSMF board in particular has a long history of creating policy but then flat out ignoring it.
  • Even if procedures like this are made mandatory everywhere, there are well known techniques to work around the open competition these are meant to ensure. If those drafting the call for tender know in advance who they want to win the bid, they can design the call in a way that makes this outcome likely – even without outright cheating in the assessments.

Same applies for selection of volunteers. Many of the committees that were created by the board during the past years (specifically here, here, here, here and here) were staffed based on an open call for volunteers. But it was clear from the beginning that the main criterion for selection was the people whose work we know and enjoy paradigm. Plus occasionally some ensemble optimization for on-paper diversity. To put it very bluntly – if you were not part of this small inner circle of people whose work we know and enjoy of the OSMF board (which probably contains no more than about 30 to 40 people) and do not happen to have any desirable formal traits that look good for diversity on paper, you did not need to bother volunteering in such calls. And as a result people likely stopped volunteering – so despite the formally open call the selection becomes highly non-diverse. The end result is: The staffing of committees with volunteers by the board in an intransparent process became one of the most significant factors working towards less diversity in volunteer contributions in the OSMF.

My recommendations:

  • Put everything into the open. Transparency is the best cure against favoritism or the appearance of favoritism.
  • Stop trying to control who does volunteer work. Simply publish tasks that you think need doing and call for people to work on them in their own initiative and responsibility (and cooperating as a self organized group if necessary for the task in question). Offer support for that work but don’t try to steer it. Believe it or not – there are many people in the OSM community willing to volunteer for the project who are better managers than you are.
  • Let the local chapters do selection of political appointees. There are meanwhile sufficiently many local chapters for such a process being much more inclusive and representative than the usual self referential people whose work we know and enjoy approach of the board.
  • Introduce a meaningful subsidiarity principle to the OSMF. I have said so in the past – i repeat it here.

Clouds

Management structures

There seems to be a general sentiment among the board members proactively communicated in the past months that they largely suffer from work overload and burnout.

While there is certainly some truth to the workload of the board having in total increased over the past years, it is important to recognize that much of the workload of the board is self-imposed. Self-imposed either because

  • The board has taken on tasks and is getting involved in matters that are not in its domain as defined by the OSMF mission. As Simon also has recently pointed out the board has in the past few years gotten much more involved in operational work (with an often highly questionable outcome i might add).
  • The board has in the past made many decisions to substantially grow the operational scope of the OSMF without making sure a self sustaining infrastructure to support this scope exists. On the contrary – almost all of the structures newly created by the board in the past years – like various special committees etc. – were appointed by the board and were designed to be under direct control of the board and require regular board activity to continue working. This not only massively increases the board workload in total (both for actually doing these tasks and for keeping track of them), it also leads to awkwardness when the board does not live up to these self imposed obligations, like in case of the software dispute resolution panel, as described in the first part of this blog post series.

The solution is obvious – to (a) be more diligent in limiting the board to its core tasks and to (b) trust the community to pursue tasks in the interest of the project in an independent and self determined fashion, either in the OSMF working groups, in the local chapters or in self organized groups independent of formal organizations. Again – the OSMF mission outlines this principle quite clearly, the board would just need to follow this.

Unfortunately, the measure the current board seems to increasingly favor instead to mitigate the work overload problem as perceived seems to be to hire paid management. It is even possible that the proactive communication of the workload issues is partly a measure to pave the way for such a change among the OSMF members. Of course, such a step would break with existing conventions and policy and it would also massively change the inner dynamics of the OSMF and its relationship with the OSM community. It would most likely lead to a further exodus of volunteers who do not like to be supervised in their volunteer activity by paid management, from the working groups and the OSMF in general.

In total it is likely that this would not work (in the sense that it would add more work to the board than it would take off them). But if it does, it would mean an OSMF run by paid management and labor leasing from corporate OSM data users as a new professional–managerial class of the organization with support from a number of unpaid interns running the working groups (who are motivated to volunteer – just like unpaid interns elsewhere – by career interests). The volunteer board would still formally sit above this. But since the main interest of the board in the process is to offload work, it would lack the ability to substantially exercise oversight over the management because they don’t understand the internal processes enough any more to develop meaningful policy. And the paid management will of course in that scenario have and pursue interests that are distinct and possibly substantially differ from those of the OSM community and the project.

If and when the board in the future might make a move towards hiring paid management the claim will likely be that they believe that they will be able to avoid the negative consequences sketched while still getting a net benefit. They would, however, likely be mistaken in that belief. It would therefore be a very good idea for the OSMF membership to ask the board, if and when they make a move in that direction, what their plan B is in case their belief about how this should work out turns out to be mistaken. Because the risks in that are immense.

And of course with the current work culture of the board, paid management positions would most likely be filled with people whose work we know and enjoy of the board – further emphasizing and perpetuating existing cultural bias in the organization. It is also not unlikely that a revolving door principle will develop where paid managers are predominantly recruited from former board members.

Interestingly, the upcoming board election of the OSMF can also be considered a poll of the OSMF membership if they want the board to continue the current line of direct involvement in operational work or if they should focus more on oversight and policy development. Many of the candidates in the election have positioned themselves quite clearly in that regard.

My recommendations:

  • Subsidiarity principle, subsidiarity principle, subsidiarity principle (if i could make every board member write that a hundred times i would do so).
  • Maintain the taboo against paid management. Someone paid for their work in OSM telling a hobby volunteer what to do or how to do it is an affront against every single one of the millions of volunteers in OSM. That includes by the way people paid by a third party. Don’t take this lightly and don’t be so arrogant to assume you can manage these problems.
  • Don’t try to control everything, concentrate on setting meaningful policy and exercise meaningful oversight where necessary but don’t interfere with operational decisions – as it is mandated by the OSMF mission.
  • Move the OSMF out of the UK, and while doing that, create organizational structures that separate policy making and oversight over operational work from its management, while disallowing direct interference of oversight with the operational work. Clear separation of functions like this would massively reduce workload and stress while giving operational work the competence and freedom to organize their work independently without continuous interference by the higher-ups while maintaining a clearly defined and independently codified oversight over the operational work.

Clouds

The OSMF as HOT 2.0

In the predictions from last year i indicated that the OSMF might in the future pursue a business model similar to that of HOT – selling OpenStreetMap as a solution for the needs of others, without substantially controlling the project. I also indicated that such a scenario would most likely be fairly unstable.

With the developments of the past year, in particular with the negotiations with HOT on a trademark license and the stalling of the OSMF board on the pursuit of ODbL violation by large corporate financiers of the OSMF, quite a bit could be written on that, where it might go and what risks and opportunities result from that. But i will cut this short here because – as i already indicated in the first part – i am not very keen to provide free consulting services to an OSMF in pursuit of commercial interests.

Clouds and seagulls

Conclusions

In total, my outlook on the future of the OSMF has brightened a bit. Ironically this is partly because the economic climate is getting more difficult and hence the ability of people in the OSMF to use money in pursuit of ideas that are bad for OpenStreetMap is likely going to be rather limited. But more importantly, this year’s board election has the potential – if the OSMF membership shows wisdom in selecting four new board members – to substantially change the work culture and the direction of the OSMF. The possibilities how to do that are fairly clear now – i outlined a few in my recommendations above. A lot more can be found in past comments of me on OSMF matters. Yes, there is of course equally a potential for a change to the worse. But even if that is the case – it is clearly in the hands of the OSMF membership this year – and even more, thanks to the active contributor membership program, every mapper who cares about OpenStreetMap in principle had the opportunity to become a member and vote in the interest of the project they care about. In other words: This year much more than in previous years it is in the hand of the OSMF membership to decide on the future of the OSMF.

In addition, i observe that the centralization and cultural homogenization attempts from the OSMF have led to an increasingly broader push-back from the community. As discussed above, this push-back and diversification also takes some rather problematic forms with the radicalization of smaller groups on proprietary platforms. But, overall, this is a positive sign: Local communities all over the world developing a robust self-confidence in the way they unite OpenStreetMap’s core values with their local culture. If these local communities now manage to overcome their relative isolation (which i discussed a bit for the German community in the previous post) and successfully engage in a peer-to-peer exchange with each other, that would be even better. Interestingly, the local communities in Africa, Asia and Latin America here seem to be ahead of the European communities with regular supra-national conferences and more regular exchange across language barriers.

Clouds

November 18, 2022
by chris
3 Comments

The OpenStreetMap Foundation in 2022 – The upcoming elections

This is the second part of a series of blog posts on this year in the OSMF – you might also want to read the first part.

Before i get to my look at current trends and the outlook on where things are likely to go in the next years in the OSMF, i want to have a few words on this year’s board elections. Last year, the elections were boring, three of the four board members whose seats were up for election ran again and were re-elected as expected and the fourth seat was filled with a German. The only two other candidates were two Americans working for large corporate OSM data users and were known for their fairly radical political ideas.

This year, the situation is fundamentally different. No current board member whose seat is up for election is re-running and we have again four seats open because Amanda announced her plans to resign at the end of the first year of her second term. That means it will be the first time in the history of the OSMF since the initial election in 2007 that there will be four new board members and that – also for the first time – there will be more new board members than old-timers. This is remarkable and could indicate that we might be at a turning point in the development of the organization (or it could, of course, be just a singular outlier).

I want to express my appreciation for the decision of all four board members leaving to make room for new people to have the opportunity to positively influence the direction of the OSMF. This not clinging to your seat and being willing to put trust and confidence into others for the future reflects a substantially positive attitude.

I also want to point out that with Eugene, the first OSMF board member from outside Europe and North America is leaving the board. Like Ilya in 2017, who was the first board member from outside Western Europe and North America, he only served one term and does not re-run this year. For comparison: About half of the board members who have in the past served on the OSMF have re-run for their seat at least once. While two cases is not really a statistically significant pattern, it is noticeable. I see two likely explanations for this: (a) that the board – while in principle being open to people from other cultures – is still massively culturally biased, making it unattractive for people with other cultural backgrounds to work there or very difficult to contribute in a meaningful way and (b) that the clinging to your seat, that we characteristically observe and have observed in some board members, is a character trait more prevalent in Western Europe and North America.

clouds over water with sailboats

Board member statements

I recommend everyone to read Amanda’s departing statement on resigning from her position and i hope that at least some of the other three board members leaving will publish some reflection on their work and the reasons for leaving.

Possibly even more interesting are two statements of two of the three board members who will continue their terms after the election. One of them essentially declares the end of history in the sense that all political struggle regarding the strategic direction of the OSMF has allegedly concluded and there is no fundamental disagreement on the overall direction any more so all that remains is boring technical management work to pursue the strategic goals everyone supposedly agrees on. For those unfamiliar with the end of history metaphor – see here.

The other statement by a current and future board member is in German. On the one hand it tries to resurrect the old topos of an impeding hostile takeover of the OSMF in the board election, trying to motivate German mappers to put themselves up for election in light of this threat. I have explained in the past years why i think this kind of hostile takeover through the front door is not a likely scenario and the economic and soft power influence of large corporate interests is actually much more worrisome. On the other hand, that statement also essentially declares defeat of the German OSM community on the political level. It calls for three or four people who are willing to let themselves be elected and does so explicitly with no expectation to do anything once they are elected, just to prevent others from being elected and possibly do anything undesirable then. That is nothing less than a confession of political failure and expendability.

clouds over water with sailboat

This is a remarkable and at the same time highly problematic statement, because it claims that the German OSM community as a whole has no ideals to pursue beyond the conservation of the status quo and no positive vision for a progressive development of the project on the political level. On the other hand, it also implies that no other local communities do so either and that all progressive change pursued and fought for elsewhere in the global OSM community is inherently destructive and undesirable. In this way it ironically perfectly aligns with the end-of-history idea of the other statement. The vision of Mikel of the end of history is, of course, most likely that the economically-pragmatic idea of OSM as a collection of useful geodata – that so conveniently aligns with the big corporate interests – has triumphed over the backwards idealists envisioning OSM as a social project of egalitarian cooperation of local craft mappers. This kind of reflects Fukuyama’s thought in 1989 that western liberalism has triumphed and no substantial ideological competition remains – hence my use of the end-of-history metaphor. Roland, on the other hand, just seems to try to conserve the status quo out of a glass-half-empty attitude.

Roland’s statement can be considered to retroactively confirm Allan Mustard’s criticism of the Traditionalists in OSM (for which the stereotypical German mapper is probably often considered to be representative) as regressive conservatives clinging to the status quo and averse to any change out of principle. Therefore i want to clearly state: This is not a view and attitude representative for the German mapper community. There are, of course, the apolitical mappers who just want to continue engaging in the project the way they are used to and therefore want it to change as little as possible. But there are also a lot who are there to contribute to a progressive project, who are open to change and who are eager to contribute to making it better and who are willing to engage in the political discussions and the struggles of arguments that are necessary to determine the best way to do so but who stay far away from the OSMF at the moment. Reasons for doing that are in particular that many are deterred by either the dominance of the English language, the need to adopt an anglo-american work culture they dislike, the need to cooperate as hobby volunteers with people who are active in the OSMF out of career interests or simply because of the lack of perspective to affect meaningful change in a positive direction. Most of the latter you will not find active on the new community platform, you will, however, find them editing the map and possibly at the pub meets all over the country. And most importantly: Most of them will probably feel embarrassed by Roland’s call for people to put themselves up to be elected just to fill a seat on the board so no one else can.

On the other hand, while the German OSM community cannot be blamed to collectively have the glass-half-empty attitude Roland presents, they are to blame quite a bit for failing to communicate a different, positive vision and attitude in public. Staying away from, and not volunteering for, the OSMF is one thing, not engaging in public exchange with others, also internationally, about your ideas and thoughts on the project is another. This does not have to happen on OSMF managed communication platforms with their behavior control and community management, but it should happen somewhere. And while there are admirable exceptions, collectively the German OSM community has huge deficits in that.

But i am getting a bit side tracked here.

clouds over water with sailboats

Candidates

There are eleven candidates for the four seats open on the board this year – which is a respectable number, considering the general difficulties of the OSMF to recruit volunteers, though it would have been good to be a few more for a broader choice.

I have not formed a clear opinion on any of the candidates yet and i will be reluctant to give a recommendation even after reading their self-presentations (which are probably published by the time you read this). Various collective failures of the board i have pointed out in the past in my blog posts here (including the previous one) have left me astonished how that could have happened, considering the people on the board are largely smart people who have shown good judgement before they were elected to the board. Note i am not talking about decisions that i politically disagree with and criticize because of that here, i am talking about objectively bad actions and decisions. And i have seen in talks with other people that i am not the only one who is irritated by that. The most likely explanation i have for this is that the board in their practical work and in their decision making processes in the past few years increasingly encapsulated itself in an echo chamber where group dynamics seem to strongly influence the views of the board members on things. In light of this the robustness of a candidate against group-think and social pressure, the demonstrated ability to self-reflect critically and the ability and willingness to openly discuss their thoughts in public, are probably important things to look at. Reliably assessing that from candidates’ statements is of course rather difficult. A better solution would probably be to get the board to move their deliberation and decision making into a public setting again – which requires either a considerable change in work culture from within or substantial outside pressure from the OSMF membership.

That gets me to the trends and outlook on the future i am going to discuss in the third part.

clouds over water with sailboats

November 15, 2022
by chris
1 Comment

The OpenStreetMap Foundation in 2022 – looking back

We are approaching the end of the year 2022 and that means the annual general meeting of the OpenStreetMap Foundation is coming up and it is time again to look at what happened in the last year and to update my outlook for the future of the organization.

I am – as i indicated previously in other blog posts – increasingly reluctant to write more in depth on OSMF matters. Apart from the increasing commercialization of OSMF politics and the increasing dominance of lobbying in the political deliberation in the OSMF that i have mentioned and discussed many times before, i also feel there is a progressing decline in the extent and the standard of public discourse on OSMF politics. Outside of the commentary i provide and a few sporadic, isolated remarks of individuals on various – often volatile – channels, substantial analysis and open exchange of diverging views and of the arguments behind them has almost completely vanished from the public sphere of communication. I will get to some aspects and consequences of that development in the following discussion of the last year in more detail.

The funny thing is that i of course have my own business interests in the wider context of OpenStreetMap so i imagine i could (and maybe should?) feel at home and among like-minded people in today’s OSMF. But i don’t. I find the whole idea of political lobbying for economic interests both appalling and pointless in the context of a project like OpenStreetMap. The idea that i could use anything but arguments and reason presented in open public discussion (open in particular to be countered and refuted by anyone interested) to influence decisions made within the OSMF to my – direct or indirect – benefit is completely out of the question for me. That applies to both decisions potentially for my direct benefit (i.e. trying to get into the inner circle of people whose work we know and enjoy) and to trying to influence policy decisions in the OSMF in general in a direction that seems likely to be to my benefit.

Clouds over water with sailboat

I like to emphasize that i am not naive in that regard. Of course in the business world arguments and reason are often not the main factors in decisions that are made. My argument against this kind of lobbying is not only on the moral level but also that it is pointless. As i have outlined in my past discussion of the corporate takeover of the OSMF – if the process of making policy and money spending decisions in the OSMF is a matter of (mostly non-public) negotiations of interests rather than an open exchange of arguments and reason, it would be an illusion to believe that a small actor like me (or any SME for that matter) could successfully lobby for interests that do not align fully with those of the big corporate actors with multi-million Euro lobbying budgets at their disposal. In business, you have to pick the battles you can win. And i can hold my ground in an open struggle of arguments and reason even against a multi-billion Euro giant with a lobbying team of a hundred people, but i stand no chance if this is not about who has the best arguments for their ideas but who puts most power behind their interests.

And the question where the OSMF stands on that scale between decision making based on arguments and reason and negotiation of interests is, as usual, a significant part of what i will be looking at and discuss in the following.

Changes in the 2022 board

The past year in the OSMF (and i mean that as the political year of the organization, starting with the annual general meeting (AGM) rather than the calendar year) started with the former board chairperson, Allan Mustard, leaving the board. As i have already indicated in a previous blog post, with Allan departing the last board member with a distinctly non-technical background has left the board. And while this on its own is not such a major event (he was just one of seven board members after all), it marked the conclusion of a long term trend in the OSMF for many years.

I disagreed with Allan on a lot of questions of OSMF politics and i have articulated that disagreement on many occasions – as those of you who regularly read this blog have probably seen. But at least Allan was regularly exposing and presenting his views to the public scrutiny. As a relative outsider, he knew that while he brought in valuable perspectives that were otherwise missing on the board, he also depended on the input of people with more specific inside knowledge to make meaningful decisions, even if that meant listening to people (like for example me) who you fundamentally disagree with on many things.

That openness to actively seek and listen to diverse and diverging views and perspectives is of course only the first step in the process of making good governance decisions. The next one would be to put into question your own views and preconceptions based on the diverse arguments received and to discuss the conflicting ideas broadly and with an open mind to ultimately make good decisions based on balanced reasoning and an open struggle of arguments. This second part, in particular putting into question your own views and preconceptions and to discuss the conflicting ideas broadly, is what – according to what i observed – Allan struggled more with. But, overall and in retrospect, his public communication can be considered a shining light compared to that of the current board members.

The reason why i emphasize this here is that in the upcoming board election and in the process of four new OSMF board members starting their terms that will follow, these abilities could be something that might be good to look at.

clouds over water with sailboats

What happened in the past year

Overall quite a lot of things have happened in the OSMF during the past year and largely due to the very poor public communication of the board and due to the lack of interest from the OSMF membership, much of this has flown under the radar. The remarkable circumstances of some of the decisions (i will get to some cases in the following) led me to conclude that hardly any of the OSMF members currently feels inclined to do any substantial supervision of the work of the board these days. So a comprehensive writeup of what has happened from an independent outside perspective would be crucial probably. I, however, do not have the time or inclination to really do that so what follows is just a somewhat subjective and sparse cross section.

clouds over water

Present throughout the whole year was the never-ending story of takeover protection/membership prerequisites. In short: In the 2020 AGM the membership, on suggestion of the board, passed two resolutions: (a) One mandating the board to work on a set of proposals to require OSMF members to have contributed to the project in some meaningful way before they can be accepted as members and (b) to investigate the risk of paid voting in the OSMF membership and potential measures to safeguard against that possibility. Both resolutions mandated a completion of the tasks within a year.

The board members seemed not to be able to agree on how to proceed on these resolutions so they appointed a special committee on takeover protection to investigate the paid votes and takeover risks. Nothing came out of that committee that was publicly disclosed though. There was apparently a report prepared internally end 2021/early 2022 but no information about that was disclosed to the members.

Before the 2021 AGM, the board realized they can hardly go into the AGM without having in any way acted in substance on the resolutions of the members – which, as mentioned, ironically were originally approved by the members based on the initiative by the board. So they went into the AGM with the promise that there would be an extraordinary general meeting in April when the board wanted to provide a proposal for membership prerequisites for the members to decide on. It was already kind of foreseeable that this would be unlikely to happen and not surprisingly the plans for the April general meeting were cancelled. Now in late 2022 we are in a way in a similar situation as last year, so what the board did in the October board meeting was to rush doing a survey of the OSMF members (so not a binding vote like they had intended for April) about what the members think of the decision the board has already made in June, which however has so far apparently not been implemented. And this is also not what either of the original 2020 resolutions called for – which are proposals to be submitted to the members at an AGM.

This probably sounds to outsiders like i am making this up as a parody – but i am not.

clouds over water with sailboats

My own take on this: Adding the requirement for a voting member of the OSMF to have shown some interest in and to have gained some at least superficial familiarity with what OpenStreetMap is all about is prudent and 15 lifetime mapping days is a reasonable cutoff for that. But this could have been done a long time ago without making a fuzz and dragging it on taking everyone’s time with repeated votes and surveys for years. If the board wanted to ask the members what they think about this idea then they could have done what they were mandated to do in the 2020 resolutions and make a resolution proposal for the AGM and let them actually decide. Making a non-binding survey about a single policy question a few weeks before the AGM, where they could have presented it as a resolution proposal, is disrespectful and patronizing. By first dragging their feet for two years, then making a decision that is decidedly not what the resolutions called for but not actually implementing it and asking the members instead in a survey what they think about it the board is seriously damaging their relationship with the OSMF members i think.

And no one should for a second believe that such requirement will substantially limit corporate influence on the OSMF.

clouds

A rather significant development during the past year was the rollout of the behavior regulation system and of the centralized communication platform. I have commented on both more specifically already. As indicated in previous comments, observing the hierarchical and centralized community management ideas from the OSMF colliding with some of the more diverse and independent parts of the OSM community is rather interesting – though technically challenging because you have to either use the mailing list mode with the broken references (so without any threading as a flat stream of messages) or the inefficient, patronizing, unstructured and poorly readable web interface. While traditional communication infrastructure provided by the OSMF in the past (specifically the forum and mailing lists) have been managed strictly from the bottom in a decentralized fashion, the new platform has been rolled out with a tight centralized management and a community manager paid by HOT. Every local group of people that wants to have their space on the platform needs to undergo a formal procedure under the auspices of this central management before they get accepted and are obliged to continue to abide by the centrally imposed procedures also after that. Despite these constraints, there has been quite a bit of uptake of the new platform by some local communities (including the German one) but it is also visible that quite a lot of filtering out of people happened as a side effect, partly because of the requirement to accept the top-down imposed social norms and procedures, partly because of the lack of a truly self determined way to participate on these channels.

A lot more could be said about what can be observed there these days in terms of social dynamics, but i will leave that for another time.

clouds over water with sailboats and freight ship

The board has in May started the first board committee that includes non-board membersthe fundraising committee. The non-board members selected for that by the board are all Americans – evidently people whose work we know and enjoy of the Fundraising Committee chairperson. The Committee’s scope was later extended to also include budgeting – meaning that the OSMFs finances are now not only externally (through the main financiers of the organization), but also internally, firmly in American hands.

clouds over water

Another thing that happened in the past year was that the OSMF board has gone ahead with hiring their first employee. In doing so the board follows the pattern established with Martin Reifer (contracted as iD developer in 2021) to (a) sign the contract without a formal board decision and (b) to not publish the contract terms. This is remarkable because an employment contract creates substantial obligations for the OSMF as a whole for a longer time. Note the OSMF also has no regular financial auditing with a financial auditor appointed by the members independent of the management. So all of these contracts and long term financial obligations are done without any independent oversight. Apart from that, one of the important side effects is that this hiring decision probably has put an end to the considerations to move the OSMF outside the UK in the future, at least to do so in full (because you can hardly have an employee in a country where you have no legal presence as a business). The whole moving the OSMF idea is one of the things where nothing apparently happened during the past year – which is unfortunate, because as discussed in the past this would have been the chance to implement some really important structural changes in the OSMF that are difficult to impossible under UK corporate law.

clouds over water

Speaking of what has not happened during the last year – there is a long list of such things. And with the OSMF board being volunteers you of course have to be careful to manage expectations here. So i will only pick a few things where the board has in the past put obligations to do things on themselves to then fail to follow these or where these obligations derive from the core of the OSMF mission. The takeover protection/membership prerequisites is already discussed above in more depth.

Not much happened also on the front of implementation of the FOSS policy. The board in late 2021 had asked the FOSS special comittee to do another review of the (mostly unchanged) status quo in 2022. It is unclear if anything happened on that front but it is clear that the main uses of proprietary software and services remains unchanged, in particular the use of Google for Mail (i am kind of curious what would happen by the way if there ever was a board member elected who refuses to get a Google account…).

Nothing of substance has happened on the front of getting HOT to finally obtain a trademark license from the OSMF for use of the OpenStreetMap trademark. There seems to have been a lot of behind the scenes talks but the bottom line seems to be that HOT still refuses to acknowledge the OSMF’s exclusive right to the OpenStreetMap name and their need to license it and that the OSMF board seems to let them get away with that, maybe in exchange for a wad of money.

Equally nothing of substance has happened on the front of making the OSMF corporate members follow the Attribution Guidelines. This has been an open issue at least since the board has adopted the Guidelines in 2021 (prior the argument was: we need to finish the Guidelines first). There was quite a bit of pushing the matter back and forth between the Licensing working group and the board apparently. There have been pushes from the community for the board to finally do something – with no effect so far. This kind of confirmed my assessment from last year that the OSMF is now inherently unable/unwilling to do anything substantially against the interests of its major financiers, even if it is something at the core of the OSM community’s interests.

clouds over water

Also the whole matter of the software dispute resolution panel for the iD editor, that has been boldly introduced in 2020 and that was finalized in early 2021 came to a screeching halt soon after. None of the formal aspects of that panel as it was introduced was subsequently followed by the board and the panel:

  • The staggered two year terms of office of the panel members are not followed, the board instead has recently decided (after nearly two years) to summarily extend the terms of all the original members indefinitely.
  • No conflict of interest rules have been created for the panel so far.
  • No discussion of the panel and the decision to install it with the OSMF membership has happened so far (it was meant to happen after one year).

As a reminder: Originally, when the panel was created, the board had asked the working groups if any of them would be interested in taking over that function, the Data working group had indicated interest, but the board had rejected that and instead decided to create a dedicated panel appointed by them.

I think it is completely understandable that in light of this and of the now completely unclear governing rules of the panel, no other software project decided to opt into being supervised by it.

seagull flying

Something i have already mentioned in the past: The newly created Engineering working group has made a rather promising start developing a fairly elaborate project funding framework during the first part of the year to then start handing out money directly through single tender action without an open call for tender as mandated by the framework.

clouds over water

Final point – and i have left the most remarkable for last – the OSMF board continues to ignore the need for more meaningful anti-corruption rules and oversight. I have discussed the general problem extensively in the past and also more recently pointed out that one of the main problem seems to be the board’s inability recognize their inherent inability to reliably identify and acknowledge their conflicts of interest and appropriately act upon them. But the October non-public mid month meeting from this year moved this to a completely new level. During the meeting a board member declared a conflict of interest on a matter discussed (a funding request by a third party) because the requesting party are “good friends” of his. Then, in the circular following that discussion meant to decide to offer money, he not only participates in the vote, he also casts the deciding vote (4 to 3) in support of the funding request.

In general, anti corruption laws in European countries and the UK tend to be what we in German call toothless tigers. Even the least capable among all corrupt people will usually be able to weasel around these laws and avoid to violate them directly while doing their thing without serious constraints.

I am not claiming any board members to have any bad intention here – yet i cannot help but state that apparently the board managed to run afoul of anti-corruption rules in the most ostentatious way i can think of and none of the board members seems to have seen any problem with that. And if that is the case, how on earth can anyone seriously assume that the practical procedures followed by the board would prevent any substantial and serious corruption from happening?

clouds over water with ships

Some positive things to end with

As in past years, this first part with the analysis of past year’s events in the OSMF is going to be followed by a discussion of trends visible and likely perspectives for the next years. But i don’t want this post to end on such a drastically negative point.

Not everything in the OSMF was bad in the past year. In particular i saw some positive trends in some of the working groups. I already mentioned that the Engineering working group had a fairly good start initially and with some more diligent fiduciary responsibility and oversight the mentioned failure could have been avoided. The irony is that in the current constellation that oversight would have been the responsibility of the board – finally something where the board would have had a good reason to intervene with the work of a working group, but they did not.

I was also impressed that recently the State of the Map working group showed a remarkable amount of backbone towards the board’s attempts to intervene with their work behind the scenes. I had renewed my past criticism of the current concept of the SotM conference this year again and while i don’t know if my comments played a role, it seems that for the specific question of the location of SotM 2023, the working group members discussed in depth their options and the various arguments that should play into that choice, and made the decision that they deemed to be advised by the arguments, despite knowing that it is going to be unpopular among many loud voices – for Cameroon. This would have strongly pointed in the direction of what i had in the past suggested as a possible future concept for international SotM conferences, namely to hook onto different regional conferences in a rotating fashion all over the world with the international visitors coming in as guests visiting an event of regional design, rather than a traveling conference of ‘western’ design moving around the world to places they consider compatible with their style of conference. And when the OSMF board then intervened, they made the prudent decision to not give in and instead said: Either we do it the way we consider to be the right one – or not at all. The lesson to learn from this: You need to accept to step on peoples’ toes if you want to initiate meaningful change on a larger scale. If this bold initiative will carry fruit will of course still remain to be seen in the coming year and i am not too optimistic about that.

And finally, it was nice to observe that the Licensing working group this year has actually started to more actively reach out to OSM data users to provide proper attribution as required under the ODbL. They understandably excluded the big corporate members, some of which fail to properly attribute, from that effort and pushed the responsibility to deal with those to the board – where, as discussed above, it still sits. This is of course highly problematic because it communicates the message: If you are a small OSM data users you have to abide by the license and the OSMF might come after you if you don’t. However, if you are large enough and have paid your dues to the OSMF you get a free pass. That is not the fault of the working group of course. This activity is in particular noteworthy since with the Attribution Guidelines the board back in 2021 had not accepted the LWG draft as is but made substantial modifications to it.

This is the first part of a series of blog posts on this year in the OSMF – see also the second part with some thoughts on this year’s board election and a third part with observations on current trends and outlook.

clouds over water with sailboat

Green Marble 3 southwest China example

October 15, 2022
by chris
0 comments

Green Marble version 3

I am pleased to announce a major update to my global satellite image product Green Marble.

The Green Marble is a medium resolution whole earth image, offering an unsurpassed uniformity in quality across the whole planet surface on both water and land coloring, based on recent data, and a hundred percent cloud free.

Green Marble 3 in southwest China

Green Marble 3 in southwest China (GM 2.1 for comparison)

The newly produced version 3 provides a complete update to the land surface depiction – based now primarily on Sentinel-3 data (like the water rendering as it was already in version 2.1) – and using a completely new aggregation methodology, based on experiences derived from earlier versions of the Green Marble, as well as techniques developed for regional mosaics.

From the user perspective, version 3 is also a huge improvement in quality and i will provide some examples for that in the following.

Data sources

The first version of the Green Marble was produced exclusively from MODIS data. With both satellites carrying MODIS instruments reaching the end of their life it has however become important for a future proof update path to move to other image sources. For water surfaces i had already moved to use of Sentinel-3 data in version 2 of the image. Apart from the foreseeable end of the supply of new MODIS observations, MODIS data also comes with various issues. In addition to the various problems stemming from the age of the instrument and the fact that only one visible light spectral band (red) is available in high spatial resolution, the more recent versions of the MODIS surface reflectance data available are subject to some pretty severe systematic errors. These essentially make the data unusable for visualization applications without investing significant effort into mitigating them. This has already made production of the Green Marble from MODIS data quite difficult in version 2 and is also likely one major reason why you hardly see any newer larger area visual color mosaics made from MODIS data any more.


Cascade Range and Palouse example (large: GM 2.1/GM 3)

Sentinel-3 land surface reflectance data has its own issues (as i discussed) but most of the inaccuracies are random in nature and therefore not too troublesome when you do pixel statistics. The real problem is that Sentinel-3 Synergy data is incomplete due to the fairly silly masking of water areas. Because of that, i moved to processing Sentinel-3 images from the Level-1 data using Synergy Level-2 data for calibration of the atmosphere compensation. This requires processing a much higher volume of data of course. Overall, about 750 TB of data were downloaded and processed for the production of the Green Marble version 3 – including 120 TB of MODIS data, 320 TB of Sentinel-3 OLCI Level-1 data, 170 TB of Sentinel-3 Synergy Level-2 data and 140 TB of Sentinel-3 OLCI Level-2 water reflectance data.

MODIS data is still used primarily for the following purposes:

  • Cross calibration of colors with Sentinel-3 to improve color accuracy and reduce systematic errors in atmosphere compensation.
  • Supplementing Sentinel-3 data at high latitudes. Because Sentinel-3 records images at a lower sun position and has a stricter recording limit based on sun elevation, it provides less useful data at high latitudes.
  • Rendering of the Antarctic. Sentinel-3 data is incomplete for the Antarctic interior due to the orbit constraints, existing upstream data processing (cloud detection, atmosphere correction) is poor in this area and the ice shelves are largely not included in Synergy processing. Combined with the general high latitude constraints (see previous point) use of MODIS data was therefore much more practicable for the Antarctic.
  • Rendering of sea ice. Since sea ice is not included in either water or land data processing workflows of Sentinel-3 use of Sentinel-3 data here would have required significant additional preprocessing work.

Northern Ural Mountains example (large: GM 2.1/GM 3)

As you can see in the samples, despite the switch of the primary data source, not that much has changed about the overall appearance of the image in terms of colors at small scale compared to the previous version – which is testimony to the highly consistent and accurate color depiction. Both the differences in atmosphere compensation and the remaining systematic errors in that and the different spectral characteristics of the two sensors lead to some color shifts in the results. Ultimately, neither the MODIS nor the OLCI instruments are ideal for accurate visual color representation.


Egypt example (large: GM 2.1/GM 3)

Processing improvements

In addition to the switch in the primary data source, the land data processing methodology was completely redesigned for the version 3 mosaic. This has lead to quite significant improvements in the results, despite using a more narrow data basis in terms of number of years covered.

Apart from the improvements in quality that i will show examples of in the following, i first want to mention that the whole processing – and as a result the final product – are now available with both the illumination and shading as recorded and in a shading compensated version representing the illumination independent color of the earth surface.


Egypt example (large: original shading/shading compensated)

In the previous versions of the Green Marble i had not produced these different variants, except for the polar regions in version 2, because by combining data with a morning and afternoon observation time frame (from the Terra and Aqua satellites) most shading effects in the image data were already eliminated. With the move to using predominantly Sentinel-3 data with a constant earlier morning recording time this changed.


Scotland example (large: original shading/shading compensated)

Based on the shading compensated image variant, renderings with customized shading can be now produced in much better quality.


Kamchatka example (large: original shading/custom shading)

Substantial quality improvements are in particular visible at higher resolution because the noise levels have been substantially reduced almost everywhere.


Scotland example (large: GM 2.1/GM 3)


Chersky Range example (large: GM 2.1/GM 3)

This is the case even in desert regions where it is often not that readily visible in the standard tone mapping, but where you can see a significant difference in contrast enhanced rendering.


Ennedi Range example (contrast enhanced, large: GM 2.1/GM 3)

Conclusions

To wrap up this announcement, i want to provide some historic and market context for the Green Marble as a product.

It has now been more than eight years since i announced the first version of the Green Marble in 2014. During these years, and over the different updates and improvements i provided to the image, it has stayed unique in its market segment. Essentially all market competitors concentrate on higher spatial resolution products but with lower quality in just about every other aspect (like lack of visible clouds, color quality and consistency, completeness in coverage, noise levels). That puts me in many ways in a comfortable position but it also means that i have rather limited information about the market needs and where users and potential users of the Green Marble see deficits and room for improvements.

The improvements i developed in version 3 and before were designed based on user feedback and my own assessment of where there are deficits and where things should be improved. But i regard this to be a rather limited perspective on the product and its value for the user. So i would be highly interested in feedback of potential users of the Green Marble – either in the comments below or via mail. If the principal idea behind the Green Marble as a global satellite image mosaic is appealing to you and for your use case, especially that it does not focus on high spatial resolution but puts other aspects of quality in the foreground, what dimensions of quality are the most important for you? This would be very interesting to know, in particular if it includes aspects that i have so far not put focus on.

Mauretania in Green Marble 3

Mauritania in Green Marble 3

As usual you can find the updated specifications page for the Green Marble mosaic on services.imagico.de. Existing customers with a Green Marble license are eligible for a reduced price update to the new version. If you are interested in using the Green Marble in your application contact me through the form there or via email. An interactive map in Mercator-Projektion for further browsing can be found also on maps.imagico.de.

Patagonia in Green Marble 3

Patagonia in Green Marble 3