Chaos Computer Club - archive feed

Löten gehört zum Grundhandwerk des gemeinen Hackers. Wie oft muss man mal eben zwei Kabel verbinden, ein Bauteil aus einer Platine austauschen oder eine Schaltung zusammenlöten. In diesem Petit Foo wird erklärt was löten ist, was man dazu benötigt und wie man richtig Elektronik lötet. Am Ende habt ihr das nötige Wissen um am verteilten Lötworkshop teilzunehmen.

about this event: https://www.chaospott.de

about this event: https://c3voc.de

Man kommt oft nicht umher und muss sein Projekt oder seine Idee anderen Leuten vorstellen. Ich werde heute im Petit Foo erklären, worauf man beim Präsentieren achten sollte und wie man typische Fehler vermeidet.

about this event: https://www.chaospott.de

about this event: https://c3voc.de

"Computer, schalte das Licht aus!" ist dank smarter Lautsprecher keine besondere Funktion mehr, sondern Alltag in vielen Haushalten. Eine umfangreiche Smarthome-Ausstattung haben jedoch nur wenige. In diesem Petit Foo wird erläutert welche Techniken es für das Smart Home gibt und worauf man achten sollte. Besonders wird darauf eingegegangen wie die Clubautomatisierung in der Foobar umgesetzt haben und am Beispiel der Heizungssteuerung erklären wie man weitere Automatismen und Geräte dort einbindet.

about this event: https://www.chaospott.de

SotM Working group say thank you to all volunteers and attendees and good bye until next year.

SotM Working group say thank you to all volunteers and attendees and good bye until next year.

about this event: https://2021.stateofthemap.org/sessions/PRZUTW/

A/B Street is an open source traffic simulator built on OSM and public census data, easy for the general public to use. This talk will cover some case studies of A/B Street being used to advocate for cycling infrastructure in Seattle, and describe how to use it anywhere.

A/B Street (abstreet.org) is an open source traffic simulator built on OSM and public census data. It simulates car, bicycle, foot, and public transit traffic, and runs on Mac, Windows, Linux, and directly in the web browser. A/B Street allows the user to reallocate existing road space between cars, protected cycle lanes, transit-only lanes, and street parking. Users can also modify traffic signal timing and create access-restricted neighborhoods. Individual and aggregate results from the simulation can be compared before and after the changes, creating a simple way to evaluate potential changes.

A/B Street has been designed for the general public to easily explore proposals for reducing dependency on cars. This talk will cover some specific cases in Seattle where the software has been used to propose real changes, like opening a shortcut through a gated community for cycle and foot traffic to avoid dangerous roads. We'll discuss how to start using A/B Street in your area, the challenges in finding other open data-sets required, and some options for how to publish results.

Finally, the talk will briefly demonstrate how A/B Street's rendering can be used for validating some tags, and how to get involved with the project.

about this event: https://2021.stateofthemap.org/sessions/JNVWZS/

Global dataset and a map style for hiking and biking developed from OpenStreetMap - that's MapTiler Outdoor. During development, we have to solve multiple challenges originating from a lack of international standardization in trail marking.

MapTiler Outdoor is a global dataset and a map style for hiking and biking available as a zoomable and web-compatible vector tiles, which are ready for use in OpenLayers, MapLibre, Leaflet, QGIS as well as mobile applications.

After first excitement, challenges starts to appear one after another: most of them originating from a need to create a rigid set of rules for the entire world, which is full of diversity due to the variety of nature. We also faced the challenge of lacking international standardization for hiking trails, which is unique for each country (and even on this level with many exceptions and specialities - like oneways, via ferrata routes or even climbing trails). And last, but not least, we have to dig all this information from the OpenStreetMap and turn it into a map understandable for everyone.

We managed to create a layer with trails and corresponding points of interest, which can be filtered on hiking or biking in the customize tool. This layer can be overlaid on top of any map. However, we created a specialized map style which combines OpenStreetMap with contour lines and hillshade and highlights things you need for moving around in the nature.

The schema of MapTiler Outdoor is based on the open-source OpenMapTiles (OTM) schema and data are processed using OMT stack.

MapTiler Outdoor is available via MapTiler Cloud as a service or in a form of a data package for download.

about this event: https://2021.stateofthemap.org/sessions/EBQEZJ/

Describes current situation of people using and appreciating OpenStreetMap data without being aware at all about its source.

Describes how it violates OpenStreetMap license and proposes to start enforcing it.

OpenStreetMap is not really known among people.

But it does not mean that they are not using it.

I was talking with a pair of tourists using maps.me to navigate. They commented that OpenStreetMap sounds like an interesting project. But it seemed to them to be an unnecessary duplicate of maps.me with its great maps.

They were completely unaware that all useful data displayed by maps.me is from the OpenStreetMap.

OSM data can be used by anyone, with few requirements. One of them is requirement to clearly and prominently state source of data.

Despite this, many companies somehow fail to include a proper attribution. Including ones that are incredibly wealthy and ones that put massive effort into designing their applications.

How can we change that situation?

Many people who would contribute are unaware that OpenStreetMap exists. We are losing potential contributors. Especially among people not interested already in open data and maps.

It is one of reasons why demographics of OpenStreetMap are so diverged from overall population. One needs to be quite unusual to be even aware that it exists and that this data is widely used.

Due to obvious conflict of interest between OpenStreetMap community and corporations using this data fixing this problem will not be easy. But we should try.

about this event: https://2021.stateofthemap.org/sessions/PHJ83R/

Since now 10 years, the Overpass API allows to query the OpenStreetMap data. This is reason enough to show how OpenStreetMap and the Overpass API have changed over that timespan. I will present and overview over user statistics, technical challenges and all kinds of requests to me as the developer.

Since now 10 years, the Overpass API allows to query the OpenStreetMap data.

This is reason enough to compare the OpenStreetMap of then to the OpenStreetMap of now

and to show how OpenStreetMap and the Overpass API have changed or not changed over that timespan.

For this purpose I will present an overview:

With which requests are the public instances of the Overpass API actually used?

The Overpass API has been intended for compound queries for the public transit data model of OpenStreetMap,

but actually got popular for the simpler tag queries on bounding boxes.

The provisions for an area data type have never materialized.

How has it protected itself and how does it now protect itself against excessive load?

I have always been proud that the service runs on ordinary server hardware and nothing huge,

but still can give every user a meaningful amount of computation time.

The necessary measures to curb the greedy and the stupid have evolved over time.

Which requests for features and questions have been addressed to me as the developer?

Basically everything we use now has been requested by users of the service.

Probably the best idea has been to change from the longish XML based query language to the now much shorter QL based language.

about this event: https://2021.stateofthemap.org/sessions/FV8QGF/