地震があったね 震度6強 12月9日
Users' Diaries
Recent diary entries
قمت بتعديل جديد وقمت بإزالة بعض الأماكن التي بالفعل تم نقلها إلى مكان آخر ولا يوجد تغيير في الخريطه هل تأخذ وقت طويل في تنزيل بيانات الجديده؟ كل ما اتطلع اليه هو تقديم بيانات دقيقه فقط للمستخدمين
Not much to report today. I stopped by Play Coffee with a friend and added some POI tags while we were in line. There’s always something to map if you have a little downtime!
I also discovered that the building Cali Tacos is in has no POIs to speak of, so I’ll focus on adding those next, along with ever more fire hydrants. (I found some possibly interesting information about Van Deventer fire hydrants, but I’m not sure it’s enough to answer the question firehydrant.org posed about whether or not it was a company or just a licensed design.) In fact, the geometry on the map just shows one singular building, which is true, but there are individual units for each business. I think it makes sense to break them up, I just need to make sure I’m doing it correctly.
Using a phone running Android OS as a data collector for an RTK-enabled GNSS receiver, I ran into a fairly small but annoying inconvenience with getting data files from it on a Windows machine.
On Windows, you can’t mount a phone’s file system as an actual removable drive (don’t confuse that with seeing its file system in the File Explorer), so automating it with built-in command-line file tools isn’t an option. File paths to the data folders of Android apps are ridiculously long, so traversing them manually is another hassle.
However, it’s still possible to do that using the Android Debug Bridge tool, a part of the SDK Platform Tools.
After installing SDK Platform Tools, you should be able to use the adb command in PowerShell or classic Command Prompt batch files.
Knowing the full path to a folder where your data collector app (LocusGIS, SW Maps, etc.) stores files you need to download regularly, you can get a list of that folder’s contents by calling adb shell ls command with the full path to that folder as a parameter.
Downloading a file is as easy as calling adb pull with the full path to the file you want to download. This process can be made more or less interactive if you create a script that lists all the folder contents, then prompts you for a name, and then downloads the file by the name you entered. The target file name or path can also be specified as another parameter. It’s even easier if the data collector app uses the same filename every time, or if you save it under the same name.
For all that to work, you’d have to enable USB debugging on your mobile device and grant permission for the Windows machine to use it when you first attempt to utilize the adb. However, it would save you the hassle of switching on the File Transfer mode every time you want to access the phone’s file system.
x
Initial Situation
In the forum, a user reports that a road on Crete is not being displayed completely. It quickly becomes clear that the German style is being used for rendering.
Openstreetmap.de operates two tile servers. On both of them, the tiles are faulty. It would be quite a coincidence if this were a hardware issue or a specific data import problem. Therefore, it is very likely that the cause lies within the German style itself.
The only difference between the two road segments is that the visible part contains one additional tag, namely maxspeed:
First Attempt
In the first attempt, I added a tag, namely the surface surface, to the missing segment and forced the German server to re-render the tiles. As a result, the previously missing part of the road appeared. This brought me one step closer, but it is not a solution yet.
Second Attempt
The German style is based on the standard openstreetmap-carto style, which is used on openstreetmap.org for OpenStreetMap maps. It adopts the basic rendering but selectively modifies certain elements to make them more readable for Germans.
I was curious whether the missing road segments were also absent in the original style. Therefore, I rendered them using that style. For this, I used render_single_tile.py and retrieved the necessary information by right-clicking on the corresponding tile at https://tile.openstreetmap.de.
First, I rendered with the German style, where – as expected – the road section was missing:
render_single_tile.py --zxy 17 74577 51762 --stylefile openstreetmap-carto-de/osm-de.xml --outputfile site/rendersinglefile/1.png
Then with the original style, where the rendered tile was also incomplete:
render_single_tile.py --zxy 17 74577 51762 --stylefile openstreetmap-carto/mapnik.xml --outputfile site/rendersinglefile/3.png
From my understanding, this made it clear that the error already occurs when importing the OSM data into the database.
Hello, guys. I am trying to map a neighborhood of León, in Spain. I need a lot of help, as there are plenty of buildings not mapped or not mapped correctly, so any help would be much appreciated. This is the note where you can see the area that I am working on right now. note/5052568#map=15/42.59710/-5.56225&layers=N
Name:
2025 12 06 37,50 #SchwarzerBulle DE NW Etwas krank Rad gefahren
Fahrt:
2025 12 05 42,30 #SchwarzerBulle DE NW Schwarzer Bulle Testfahrt Nordrandweg und Terranova Speedway
Sziasztok!
Az élet sodor, gyakran mint egy hurrikán. Ugyan kevés olyan időm akad, amikor OSM-el tudok picit foglalkozni, gyakran fut át a fejemen, hogy ezt-azt megnézek a térképen a környezetemből és majd javítom, szerkesztem, ha eltér. Nyilván ettől sokkal kevesebbszer érek oda, de azért párszor már összejött.
Továbbra is érdekel és fogok is szerkeszteni.
Néha még a JOSM-ot is frissítgetem az aktuális verzióra, akkor is, ha közben mégis az ID-n egyszerűbb és gyorsabb valamit igazgatni. A kis dolgoknál ez így is marad, de ha nagyobb varázslat szükséges, a JOSM is jó, látom, ha nem is sűrűn, de még mostanában is frissítették.
Az OSM továbbra is kedvenc koncepció a szememben és örülök, hogy jó ideje stabil és fejlődik.
Üdv, V.
It was another beautiful, sunny day in Orange. I’m toying with the idea of conjuring up some sort of regular Saturday mapping activity, solely so I can use the word “Mapurday”, even though I’ve mapped at least one thing every day for the last five days. I’m sure that will slow down a bit once I re-balance the other parts of my life (although I did add a bench in Riverside last night while waiting for a friend to arrive; it doesn’t take much to contribute!). I’m not sure if it will be just for myself, or I want to try to get other local mappers involved.
It was a productive day! My goal was to add more fire hydrants along Palmyra, and to catch one I had somehow missed along Almond. I can’t say it’s representative, but so far, the manufacturers have all been one of:
- Rich Valve Co. (or Rich Manufacturing Company; I’ve seen both and other variations in newspaper clippings)
- M. Greenberg’s Sons
- Long Beach Iron Works
- Clow (Valve Company)
There’s also one Van Deventer, which firehydrants.org says could be a company, but it could also just be a fire hydrant produced under license. I plan to do a little newspaper digging to see if I can learn more.
Orange Street Barbershop
I added the Orange Street Barbershop to the map. I’ve been correcting several missing or otherwise out-of-date business POIs in addition to my quixotic hydrant mapping quest. The previous salon for 120 S Orange St was long since closed, so I updated it for the new business. I also noticed that the entire building was marked as the salon (now barbershop). I switched this to an individual node because the Orange Street Barbershop is technically suite B; there’s a suite A with doors set a bit back into a covered part of the building, but they don’t seem to be for anything useful.
YIPPIEEEEEEEEEE! I’m already at 65 edits! This is the start of something very great and beautiful. Speaking of great and beautiful, I love my girlfriend so much!
Es absolutamente maravilloso.
1
Quand on essaie de regarder Panoramax en dehors des agglomérations et des routes, dans la plupart des régions c’est le grand désert.
Pourtant, pour les randonneurs par exemple, ce serait bien de pouvoir utiliser Panoramax comme le StreetView des sentiers. Quand on veut planifier une sortie dans un endroit qu’on ne connait pas, on aimerait bien avoir un aperçu de quelques chemins pour voir ce qui parait intéressant, ce qui semble facile ou difficile… Malheureusement, à part un petit nombre de passionnés, peu de contributeurs se baladent, à pied ou à vélo avec une caméra 360° en prenant une vue tous les quelques mètres. La couverture des chemins dans une région donnée avance donc très lentement, ou la plupart du temps pas du tout.
Pour remédier à cela, l’application Baba offre une solution parallèle pour accélérer les choses. Lors d’une sortie ordinaire, pas forcément dédiée, on peut caractériser les sentiers en cours de route avec quelque dizaines de photos et envoyer les résultats sur Panoramax soit au fur et à mesure, soit le soir en rentrant.
Bien sûr, cette méthode “artisanale” n’est pas parfaite, un utilisateur aura toujours envie de savoir ce qui se passe entre deux points de prise de vue ou sur le côté comme avec une vue 360° mais ça a le mérite d’exister et de pouvoir être pratiqué par un plus grand nombre de contributeurs. Cela n’empêche pas d’autres contributeurs de repasser un jour derrière avec une technique plus complète.
J’ai commencé à mettre en pratique cette idée dans ma région.
Voir par exemple ce sentier comme point d’entrée, puis explorer la carte pour voir ce qu’il y a autour.
Quelques idées de base
Au fur et à mesure des aller-retours entre les prises de vue et les résultats sur les visionneuses, j’ai essayé de dégager quelques trucs utiles pour améliorer les résultats.
Daca doriți să îmi trimiteți imagini sau videoclipuri ca sa va ajut puteți trimite la e-mailul dariusbubu1010@gmail.com
hvorfor er s-togsnettet vist som letbane, er det en fejl eller?
Flickr is how I learned about Open Street Map. They use OSM data for their maps. Places that haven’t been worked on can only be found via coordinates. It’s frustrating.
Parma, Ohio, for example could use some love and attention.
Když přemýšlím o mapách budoucnosti, nevidím jen další technické vylepšení zobrazování terénu. Vidím především změnu v tom, jak si společnost uvědomuje prostor a jak skrze něj řídí svůj život. Mapy postupně přestanou být pouhým popisem povrchu. Stanou se další nervovou soustavou civilizace.
Dnes máme mnoho typů map, které pokrývají téměř vše co nás napadne. Infrastruktura, příroda, vlastnické vztahy, doprava, služby, počasí. Přesto stále cítím, že jsme na začátku. Reálný svět je dynamický a v pohybu. Mapy se této dynamice teprve učí stačit. Čím více bude naše civilizace žít v komplexitě a proměnlivosti, tím více budeme potřebovat mapy, které tuto živost zachytí.
Představuji si mapy s mnoha vrstvami, které proudí v reálném čase. Data o energiích v budovách. Signály o nasycení veřejného prostoru životem. Místa kde se rodí napětí i místa kde vzniká spolupráce. A také vrstvy které nebudou mít pevnou interpretaci. Emoce, nálady, očekávání. Nějaké ostrůvky takových map už tu máme. Budou mapy, které připustí nejasnost jako přiznanou informaci. Mapa už nebude jen obrazem toho co je. Bude také předpovědí toho, co při dobré definici podmínek může být.
To vyžaduje mnohem víc, než nové technologie. Vyžaduje kulturu důvěry. Transparentnost původu dat. Pravdivou informaci o tom, kdo o mapovaném prostoru rozhoduje a proč. Když se mapa stane podkladem pro rozhodování, musí být otevřená kontrole. Musí být srozumitelná těm, kteří ji potřebují číst. Musí ctít práva tvůrců i práva lidí, kteří jsou v ní zaneseni svými domovy nebo svými pohyby.
Le projet Architectes dans OSM poursuit son développement et déménage vers un site dédié :
avec toujours :
- les données extraites d’OSM (Autriche, Belgique, Suisse, Tchéquie, Estonie, France, Pays-Bas, Portugal et Slovaquie), y compris des photos Panoramax
- la carte uMap
- la recherche géolocalisée
À venir : de nouveaux pays et des articles consacrés à des architectes méconnus.
Merci à toutes les contributrices et tous les contributeurs !