OpenStreetMap (OSM) is an invaluable resource for geospatial data, providing free and open access to information about our planet. One interesting aspect of OSM is its ability to track the history of changes made to objects in its database. As someone curious about geospatial data, I’ve been exploring ways to visualize this data in a more intuitive manner. Recently, I decided to experiment with GPT-4, a state-of-the-art language model by OpenAI, to see if we could come up with a fresh approach to visualizing OSM data history. In this blog post, I’ll share my initial attempts, examples of the traditional OSM Deep History table, and the new visualization I created with GPT-4’s assistance.

Traditional OSM Deep History Table

The standard OSM Deep History page presents data history in a tabular format. While it’s a helpful tool for understanding how objects in the database have evolved, the table format can make it difficult to quickly grasp changes and trends in the data. The table includes a row for each version of the object, with columns for different attributes. As a result, finding meaningful insights can be challenging.

Figure 1: The traditional OSM Deep History table displaying object history in a linear format.

Experimenting with GPT-4

To create a more visually appealing and intuitive representation of data history, I decided to experiment with GPT-4. Together, we developed a new approach to visualizing OSM data history using an enhanced table format ಠ_ಠ in the browser. This new visualization prioritizes the most recent changes, sorts the columns based on the order in which the keys first appeared, and clearly highlights additions, deletions, and modifications to the data.

Figure 2: The experimental visualization created with GPT-4 assistance, organizing the data more effectively and emphasizing important changes.

Illustration Comparison

The traditional OSM Deep History table displays the data linearly, making it difficult to quickly identify changes and trends. In contrast, the experimental visualization enhances the presentation by organizing the data more effectively and emphasizing the most important changes. This helps users more easily understand the evolution of the object and gain deeper insights into its history.

Conclusion

My initial experiments with GPT-4 to visualize OSM data history have been an interesting learning experience. These are just my first attempts at data visualization. If you’ve come across any such examples or have ideas for other applications, please feel free to share them in the comments below.

1. Install Java Development Kit for ARM 64 processors https://www.oracle.com/java/technologies/downloads/#jdk17-mac

2. Download josm-tested.jar https://josm.openstreetmap.de/josm-tested.jar

3. Drag and drop josm-tested.jar into the Dock

4. Run JOSM!

The Ukrainian community is concerned about the possible negative impact on the project as a whole, the emergence of lawsuits from users of data and the subsequent decline of the project, and therefore restores the borders of Ukraine to the internationally recognized status. The recent decision of DWG ( https://wiki.osmfoundation.org/wiki/Working_Group_Minutes/DWG_2018-11-14_Crimea ) neglects the wide recognition of Crimea as an integral part of Ukraine expressed by numerous governments and international organizations (in particular, UN General Assembly Resolution 68/262 http://www.un.org/en/ga/68/resolutions.shtml / https://undocs.org/en/A/RES/68/262 ). DWG actions directed to cut off Crimea from the borders of Ukraine are considered to be inadequate to the interests of the project and are not recognized by law. Any blockages (bans) aimed against members who restored the border of Ukraine to the widely internationally recognized status will be seen as unjustified pressure on the entire community and usurpation of power in the OSM.

P.S.

“changing names or country information would require consensus from both the Ukrainian and Russian communities. It is unlikely that any such edit proposals will be able to achieve this.” (с) DWG //

Moreover, according to clause 4, a consensus should be reached between the Ukrainian and Russian communities on changing information about countries. There is no consensus - there is no reason to separate the Crimea from Ukraine.

CrimeaІsUkraine #DWG #CrimeaMap #КримЦеУкраїна #ИхТамНет

https://www.openstreetmap.org/relation/60199

https://www.openstreetmap.org/user/velmyshanovnyi - https://www.openstreetmap.org/user_blocks/2360 ;

https://www.openstreetmap.org/user/velmyshanovnyi - https://www.openstreetmap.org/user_blocks/2359 ;

https://www.openstreetmap.org/user/andergrin - https://www.openstreetmap.org/user_blocks/2358 ;

https://www.openstreetmap.org/user/Дівчина_з_Коломиї - https://www.openstreetmap.org/user_blocks/2357 ;

https://www.openstreetmap.org/user/паляниця - https://www.openstreetmap.org/user_blocks/2356 ;

https://www.openstreetmap.org/user/frankoivan - https://www.openstreetmap.org/user_blocks/2355 ;

https://www.openstreetmap.org/user/pumpkinpie226 - https://www.openstreetmap.org/user_blocks/2354 ;

https://www.openstreetmap.org/user/Хтосьіншийдятел - https://www.openstreetmap.org/user_blocks/2353 ;

https://www.openstreetmap.org/user/ue0 - https://www.openstreetmap.org/user_blocks/2350 ;

https://www.openstreetmap.org/user/andergrin - https://www.openstreetmap.org/user_blocks/2348 ;

https://www.openstreetmap.org/user/KKS - https://www.openstreetmap.org/user_blocks/2347 ;

…and other

Минулого року мапив територію Згурівської районної лікарні, а це знайшов серед паперів листок з нотатками від руки. Похвастаюсь в щоденничку ( ͡ᵔ ͜ʖ ͡ᵔ) Вихід в поле, як-не-як) З теґами наче все гаразд, але якщо є зауваження — буду радий щось підкоригувати.