barefootstacheThe benefit of being a passenger with a window seat is that one can make notes regarding missing #OpenStreetMap details like buildings, residential landuse, sidewalk, or barriers.
Guess I have #ArmchairMapping cut out for me for next couple of days.
So little time but so much to do at camp Šumani regarding #OpenStreetMap.
Took some notes and potential panomarax media and there is still plenty of #MicroMapping tasks open.
Another from/to #airport #walk achieved.
Although it is feasible, the majority of the route is on track vel overgrown track.
Additionally one gets to experience the typical walking along primary Croatian road, thus one should not be afraid of vehicles zooming way above the speed limit pass one. Luckily, this is only about 30 minutes worth of the route.
blubOh nun kann auch #osmand 3D Gebäude 
https://osmand.net/blog/osmand-android-5-3-released/#3d-buildings
Zwar nur LOD1 aber immerhin!
SeverinGeoComparto primera entrada sobre limitaciones actuales aplicaciones de navegación sin conexióne #OpenStreetMap para smartphones como #OsmAnd, @CoMaps y @organicmaps
Problema nº1 desde el primer uso: el tamaño del mapa a descargar. En muchos casos, o se descarga todo el país o nada. Y eso suele suponer más de 100 MB, o incluso 500 o 600 MB. Mientras que otros países tienen derecho a una o incluso dos divisiones administrativas.
¿Por qué existe tal obstáculo para su uso?
Limitaciones actuales de las aplicaciones de OpenStreetMap para smartphones – primera entrada
Problema n.º 1 desde el primer uso de las aplicaciones de navegación offline de OpenStreetMap para Android, como OsmAnd, Comaps u Organic Maps: el tamaño del mapa que hay que descargar. En muchos casos, hay que descargar todo el país o nada. Y eso suele suponer más de 100 MB, con casos que superan los 500 o 600 MB. ¿Por qué?
Estou compartilhando um primeiro post sobre as limitações atuais aplicativos navegação offline #OpenStreetMap para smartphones, como #OsmAnd, @CoMaps, @organicmaps
Problema nº 1 logo na primeira utilização: o tamanho do mapa a ser baixado. Em muitos lugares, é o país inteiro ou nada. E isso geralmente representa mais de 100 MB, ou até 500 ou 600 MB. Enquanto outros países têm direito a uma ou até duas divisões administrativas.
Por que esse grande obstáculo ao uso?
Limitações atuais dos aplicativos OpenStreetMap para smartphones – primeiro post
Problema nº 1 logo na primeira utilização dos aplicativos Android de navegação #openstreetmap offline, como OsmAnd, Comaps e Organic Maps: o tamanho do mapa a ser baixado. Em muitos lugares, é o país inteiro ou nada. E isso frequentemente representa mais de 100 MB, com casos que ultrapassam os 500 ou 600 MB. Por que isso acontece?
I’m sharing an initial post on the current limitations of #OpenStreetMap offline navigation apps for smartphones, such as #OsmAnd, @CoMaps, and @organicmaps
Problem #1 right from the first use: the size of the map to download. In many places, it’s either the entire country or nothing. And that often amounts to over 100 MB, or even 500 or 600 MB. Meanwhile, other countries are limited to one or even two administrative divisions.
So why such a barrier to use?
Current Limitations of OpenStreetMap Smartphone Apps – First Post
Issue #1 when first using offline OpenStreetMap navigation apps for Android, such as OsmAnd, Comaps, and Organic Maps: the size of the map to be downloaded. In many places, it’s the entire country or nothing. And that often amounts to over 100 MB, with some cases exceeding 500 or 600 MB. Why is that?
Je partage un premier post sur limites actuelles applications #OpenStreetMap de navigation hors ligne pour smartphones type #OsmAnd, @CoMaps, @organicmaps
Problème #1 dès la première utilisation : la taille de la carte à télécharger. Dans beaucoup d’endroits, c’est le pays entier ou rien. Et cela représente souvent plus de 100 Mo, voire 500 ou 600 Mo. Alors que d'autres pays ont droit à un voire deux découpage administratifs.
Pourquoi donc un tel frein d'utilisation ?
Limites actuelles des applications OpenStreetMap pour smartphones – premier post
Problème #1 dès la première utilisation des applications Android de navigation #openstreetmap hors ligne, type OsmAnd, Comaps, Organic Maps : la taille de la carte à télécharger. Dans beaucoup d’endroits, c’est le pays entier ou rien. Et cela représente souvent plus de 100 Mo, avec des records au-delà des 500 ou 600 Mo. Pourquoi donc ?
tarofortuneBuilt an interactive map for Gyeonggi local currency merchants (Korea, 31 cities)
Built an interactive map for Gyeonggi local currency merchants (Korea, 31 cities) - Lemmy.World
I built an interactive map for South Korea’s Gyeonggi Province (14M residents) showing local-currency merchant locations across all 31 cities, with business-type filter and a real-time “open now” filter. Built solo with React + Vite + Leaflet, hosted on Firebase. Uses OSM tiles + public API merchant data. PWA installable, KakaoTalk share, dynamic OG cards. Live: https://gyeonggi-currency-map.web.app/ [https://gyeonggi-currency-map.web.app/] Sharing here because it’s a real-world OpenStreetMap consumer in production.
APneunzehn74Da ich gerade in der Gegend unterwegs bin hab ich mir gedacht füge doch die #stolpersteine in #rijeka in die #OSM Datenbank hinzu. Der #wikipedia Artikel liefert dazu die passenden Adressen, den Rest erledigt man mit #osmand unterwegs. Jetzt ist mir allerdings aufgefallen das im Wikipedia Artikel https://de.wikipedia.org/wiki/Liste_der_Stolpersteine_in_Rijeka ein paar Fehler in den Adress-Daten vorhanden sind.
Unterwegs am Smartphone kann ich das jetzt nicht korrigieren.
Hier die #overpass Abfrage:
https://overpass-turbo.eu/s/2q8m
