Mapdown is a drop-in library that renders GPX or a list of coordinates to a #map, using #Leaflet and #OpenStreetMap. You just drop-in stylesheets + script and it renders. Primarily targeting #markdown generated #HTML, but can be used for any HTML doc.

https://cfe84.github.io/mapdown/

#webdev #JavaScript

Mapdown is a drop-in library that renders GPX or a list of coordinates to a #map, using #Leaflet and #OpenStreetMap. You just drop-in stylesheets + script and it renders. Primarily targeting #markdown generated #HTML, but can be used for any HTML doc.

https://cfe84.github.io/mapdown/

#webdev #JavaScript

StreetComplete is a really fun and accessible way to contribute to OpenStreetMap from an Android device - walk around in your local neighbourhood (or anywhere really) and solve 'quests' by answering questions about the things around you!

You don't need to learn anything about mapping conventions, or infrastructure, or about the more complex mapping tools that exist for OpenStreetMap. The app will explain everything to you that you need to know, when you need to know it, and ask easily understandable questions with reference pictures for the answers.

The only setup needed is to make an OSM account and log into it from the app, so that it can upload your answers - and you can also do that at any later time, after trying out the app without an account for a while first. You can just install it and go outside right away!

The app doesn't need any cellular internet connection; it can work offline and synchronize your answers once you reach a place with eg. WiFi. It's also quite performant, and should run well even on lower-end phones. There is also a 'multiplayer' option that lets you split up in teams and each tackle different quests in the area.

https://streetcomplete.app/

#StreetComplete #OpenStreetMap

@veilroy Am besten Hashtags folgen - dann findest Du automatisch viele Kontakte: https://fedi.tips/how-do-i-follow-hashtags-on-mastodon-and-the-fediverse/

#qgis #gis #osm #openstreetmap #geoinformatik

For all people interested in #vegan or #vegetarian restaurants (and other venues). Have a look at #VeggieKarte.

The website got a nice upgrade.

https://www.veggiekarte.de

Based on #OpenStreetMap, #OSM.

With integrated reviews from https://lib.reviews/

#opensource #FOSS

I made GNOME Maps stop doing search queries faster than most people can type, with this One Weird Trick™: https://gitlab.gnome.org/GNOME/gnome-maps/-/merge_requests/584

Medium-to-fast typists will no longer see flickering search results and won't be doing "Hokuto no ken" network requests anymore. I presume #GNOME users will have less chances of collectively DDoSing servers when the Year of the Linux Desktop™ happens.

#GNOMEMaps #OpenStreetMap #GraphHopper #EnergyEfficiency #EnvironmentThisWeek

StreetComplete is a really fun and accessible way to contribute to OpenStreetMap from an Android device - walk around in your local neighbourhood (or anywhere really) and solve 'quests' by answering questions about the things around you!

You don't need to learn anything about mapping conventions, or infrastructure, or about the more complex mapping tools that exist for OpenStreetMap. The app will explain everything to you that you need to know, when you need to know it, and ask easily understandable questions with reference pictures for the answers.

The only setup needed is to make an OSM account and log into it from the app, so that it can upload your answers - and you can also do that at any later time, after trying out the app without an account for a while first. You can just install it and go outside right away!

The app doesn't need any cellular internet connection; it can work offline and synchronize your answers once you reach a place with eg. WiFi. It's also quite performant, and should run well even on lower-end phones. There is also a 'multiplayer' option that lets you split up in teams and each tackle different quests in the area.

https://streetcomplete.app/

#StreetComplete #OpenStreetMap

#OSM / #OpenStreetMap question:

There's a public car park here that's already mapped.
It's an area with amenity=parking and parking=surface. Its capacity is noted to be 24 spaces.

So far, so good.

However, about nine lots on this car park are reserved for carsharing. The others are public parking spaces.

Right now, the car park in its entirety is part of a big relation that encompasses all stations of this operator. The lot itself doesn't mention carsharing.

I'd like to change this by mapping the specific carsharing areas on the lot. It's further complicated by the fact that the carsharing station consists of two separate areas on the lot and isn't continuous.

How would I do this? As I see it, I have a couple of options:

• Split the public car park and the carsharing lots into separate areas altogether with amenity=parking and amenity=car_sharing respectively. Add the two split carsharing lots to a complex multipolygon relation. Add the new carsharing areas (or the multipolygon relation…?) to the existing regional operator relation.
• Map new amenity=carsharing areas on top of the whole parking lot area, and add them to a multipolygon relation. How do I handle lot capacity and the operator relation?
• Add the carsharing tag to the entire parking lot even if it's inaccurate.
• Just keep it as is.

#OSM / #OpenStreetMap question:

There's a public car park here that's already mapped.
It's an area with amenity=parking and parking=surface. Its capacity is noted to be 24 spaces.

So far, so good.

However, about nine lots on this car park are reserved for carsharing. The others are public parking spaces.

Right now, the car park in its entirety is part of a big relation that encompasses all stations of this operator. The lot itself doesn't mention carsharing.

I'd like to change this by mapping the specific carsharing areas on the lot. It's further complicated by the fact that the carsharing station consists of two separate areas on the lot and isn't continuous.

How would I do this? As I see it, I have a couple of options:

• Split the public car park and the carsharing lots into separate areas altogether with amenity=parking and amenity=car_sharing respectively. Add the two split carsharing lots to a complex multipolygon relation. Add the new carsharing areas (or the multipolygon relation…?) to the existing regional operator relation.
• Map new amenity=carsharing areas on top of the whole parking lot area, and add them to a multipolygon relation. How do I handle lot capacity and the operator relation?
• Add the carsharing tag to the entire parking lot even if it's inaccurate.
• Just keep it as is.

For all people interested in #vegan or #vegetarian restaurants (and other venues). Have a look at #VeggieKarte.

The website got a nice upgrade.

https://www.veggiekarte.de

Based on #OpenStreetMap, #OSM.

With integrated reviews from https://lib.reviews/

#opensource #FOSS

Great write-up with beautiful photos on why building communities around opensource software is the better long-term path, anchored around the #Komoot debacle.

Don't flock to closed solutions and eco-systems. Don't ignore, that your data and contributions further enrich some very few and how this is against your own interest. And obviously this issue is not limited to the bike community. Take action now!

https://bikepacking.com/plog/when-we-get-komooted/

#OpenStreetmap #OpenSource https://wanderer.to/ @CoMaps@floss.social @fedibikes@soc.schuerz.at #Fediverse #decentralization #enshittification #ProfitOverPeople
... and thanks for sharing @ilumium@eupolicy.social

Great write-up with beautiful photos on why building communities around opensource software is the better long-term path, anchored around the #Komoot debacle.

Don't flock to closed solutions and eco-systems. Don't ignore, that your data and contributions further enrich some very few and how this is against your own interest. And obviously this issue is not limited to the bike community. Take action now!

https://bikepacking.com/plog/when-we-get-komooted/

#OpenStreetmap #OpenSource https://wanderer.to/ @CoMaps@floss.social @fedibikes@soc.schuerz.at #Fediverse #decentralization #enshittification #ProfitOverPeople
... and thanks for sharing @ilumium@eupolicy.social

#OpenStreetMap
Bon à savoir : il existe une page spéciale sur GitHub dédiée au suivi des manquements d'attribution constatés sur certains sites qui utilisent des cartes OpenStreetMap en « oubliant » les mentions obligatoires : conditions de licence et crédit à « © les contributeurs d’OpenStreetMap ».
Ces manquements constituent une mauvaise pratique, contraire aux conditions de la licence libre #ODbL utilisée par #OSM.
N'hésitez pas à créer un ticket de signalement.
https://github.com/osm-fr/attributions

En parallèle du ticket de signalement, vous pouvez également essayer de contacter le responsable du site sur lequel vous avez constaté l'absence d'attribution ou une attribution incorrecte, pour demander (gentiment ! 😀) à ce que le problème soit corrigé.
Vous trouverez sur cette même page Github une proposition de modèle de courriel.
#OpenStreetMap

#OpenStreetMap
Bon à savoir : il existe une page spéciale sur GitHub dédiée au suivi des manquements d'attribution constatés sur certains sites qui utilisent des cartes OpenStreetMap en « oubliant » les mentions obligatoires : conditions de licence et crédit à « © les contributeurs d’OpenStreetMap ».
Ces manquements constituent une mauvaise pratique, contraire aux conditions de la licence libre #ODbL utilisée par #OSM.
N'hésitez pas à créer un ticket de signalement.
https://github.com/osm-fr/attributions

@uneabeille That's something I'd love to do too!

I just struggle with the following specifically:

First of all, POIs are simple enough to work with for me. A POI is a single point on a map with a type and properties defined by their type. I can easily add or edit them using #CoMaps, #StreetComplete or, if I'm feeling particularly brave, even #Vespucci.

But buildings, paths and such I don't get yet. I don't really understand boundaries, relations, nodes, polygons, vectors, whatever. That's why I'm not confident enough to make non-trivial contributions.

For example, how do we canonically actually handle businesses? Is a business a POI placed on top of its building polygon on the map? Is the POI supposed to be placed in the middle of the building, or where the entrance is?

Where should information about the business go, as in, name, contact info, opening hours and such? Is the building polygon itself supposed to be tagged as, say, a restaurant? Is a POI on top of the building supposed to hold all the business information? How do we connect the POI to the building it is inside of, data-wise?

I mean, I can always look into the wiki to read the documentation. But usually, the actual implentation of my area's mapping is completely different from the documented way to do it. We have buildings tagged as restaurants, POIs slapped on top of buildings.

Therefore, there's a lot of wrong or missing data basically everywhere here.

Deprecated properties and tags, misused property values, missing or partial data, wrong data, imprecise data. Standards naturally evolve way faster than map data does.

It's so much that it sometimes feels a little pointless to clean up my local area.

Does it really matter to anyone at all if I spend weeks making sure that my neighbourhood's buildings are all correctly tagged with type, height and roof colour? That every single garden appears on OSM, even when no other garden is actually mapped in my entire city, and even some major public parks are mistagged, no bicycle lanes are mapped, and nearly no road has a surface property?

Do I really tangibly help out a single cyclist when I spend a whole day tagging cycle paths and cycle path types, surfaces and widths, when no navigation app actually makes use of any of that data, and the rest of my city is untagged?

In the end, I always arrive at the same somewhat depressing conclusion: all the data in the world is only useful if someone's making use of it.

No matter how meticulously we micro-map every detail of pedestrian infrastructure, there is no navigation app that lets us navigate to the closest bench with a backrest.

Or that navigates me only through wide, well-lit bicycle paths. Or that actually does anything with the type or location of trees in our local park.

That's the demotivating part of #OpenStreetMap for me. All that detailed data, but no practical application to make it useful. I don't feel like I'm making a difference.

It's kind of like rewriting your website to consist solely of perfect, semantic HTML. Tagging every date with <time>, every <address>, every <abbr>eviation. It's machine readable in theory, but since no browser does anything with all that data, it's completely useless.

@steffo I do contribute to #OSM occasionally :)

Since I don't have an education in #GIS though, my contribution to #OpenStreetMap is sadly limited to #StreetComplete and fixing metadata of local businesses and such. I doubt I can be very helpful in the high-level design of its standards, protocols and tagging systems.

Although it's always been super interesting to me! I'd love to contribute somehow.
I wish someone knowledgeable would take me under their wing and teach me the ways. :P

A question for #OpenStreetMap mappers. There is a mall in my city, which I'm using a lot and it was not mapped properly, since 2019 I think — there are a lot of non-existent amenities, a lot of new amenities don't exist on the map, and a lot of POI placed semi-randomly.

I tried to fix it "on foot" by editing and moving amenities, but it is not very easy for me with Every Door application and without JOSM (and without the big screen with a big keyboard) .

So, I think about to take the official website of the mall, which has the actual information about all the stores inside and about their position inside the building — and fix the #OSM map for this mall.

But I unable to find — is it legal (in terms of OSM) to use this external source of information (floor plans for mall visitors) in OSM mapping?

#AskFedi