About 99% of supplements have garbage in them like seed oils, starch, citric acid or other fillers because most people are too ignorant to read the ingredients labels, let alone realize that ultra-processed pseudo-food is harmful for them in the first place.

I wonder if there is some tag for a nutrition supplements store to state that they offer clean supplements with just one ingredient, just like vegetarian tags, except focused on health rather than ethics.

Maybe diet:raw=* could somewhat apply?

县道、乡道、村道的编号规则是什么？ 答：1.县道命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“线”组成，如起于高淳县东坝镇终于高淳县固城镇，则命名“东固线”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“线”组成。

（2）编号规则：本轮县道网编号以现有编号体系为基础，现有县道编号基本保持不变，新增县道编号按照方向和类型，在现有县道编号后依次排列，即“老路老编号、新路新编号”。具体编号原则如下：

①编号由字母和数字共10位构成，如“X105320125”，其中，“X”反映县道的性质；“105”反映线路的类型、方向和顺序；“320125”为线路所在县（市、区）的行政代码（以国家统计局发布的2013年江苏省行政区划代码为准）。

②例：“105”：第一位“1”表示线路方向和类型，“05”表示为顺序码。

“1”开头表示由县城（市、区）向外辐射的树状县道网，顺序码从正北方向顺时针依次增大；

“2”开头表示南北纵向县道编号，顺序码从东向西依次增大；

“3”开头表示东西横向县道编号，顺序码从北向南依次增大；

其中，“101~150”、“201~250”、“301~350”编号，适用于保留、局部延伸或调整的现有县道线路，原有县道线路编号不做调整；“151~199”、“251~299”、“351~399”编号，适用于本轮新增县道和上轮县道规划后陆续增编的临时县道编号线路（即X+字母+两位数字+行政区划代码的线路）。

2.乡道命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“线”组成，如起于溧水区晶桥镇止于溧水区晶桥镇新山里村，则命名“晶新线”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“线”组成。以上两种命名规则，必须保证在同一县域范围内名字不重复。

（2）编号规则：路线编码由行政等级代码+三位编号+县级行政区划代码共十位组成，具体表示方法如下所示：

“Y”：代表乡道的行政等级代码；“101”：代表乡道的排列顺序编码，采用“老路老编码，新路新编码”原则，老线路以及延伸段采用原有编码，新线路编码从“AA0”开始至“ZZ9”；“320111”：代表该县（市、区）的行政代码。

县（市、区）交通运输局根据各乡镇的实际情况拆分乡道编码，确保县（市、区）域范围内乡道编码的唯一性。

3.村道公路命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“路”组成，如：起于溧阳市上兴镇建盟村，终于溧阳市上兴镇红旗村，则命名“建红路”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“路”组成。以上两种命名规则，必须保证在同一县（市、区）域范围内名字不重复。

（2）编号规则：路线编码由行政等级代码+三位编号+县级行政区划代码共十位组成，具体表示方法如下所示：

“C”：代表村道的行政等级代码；“101”：代表村道的排列顺序，采用“老路老编码，新路新编码”原则，老线路以及延伸段采用原有编码，新线路编码从“AA0”开始至“ZZ9”；“320125”：代表该县（市、区）的行政区划代码。

县（市、区）交通运输局根据各乡镇的实际情况拆分村道编码，确保县（市、区）域范围内村道编码的唯一性。

Вітаю, спадарства!

Неўзабаве скончыў перакладаць openstreetmap на клясычную (тарашкевіцу).

Спроба сыстэматызаваць тое што было, пасьлядоўна ды ґрунтоўна прайшоўся водле працы якую пачалі ўжо даўно. Пэўныя тэрміны, магчыма, будуць незразумелымі ці нязвыклымі, мэтай была ўжываць нашыя спрадвечныя адменьнікі, унікаючы калькаваньня.

Цяпер патрэбная вычытка, прыбраць хібу, якую я мог дапусьціць.

Пераклад ужо бачны на сайце, каб пабачыць трэба выбраць мову, яна ніжэй, пад “беларуская”. Перакладзены толькі сайт, не id-рэдактар, там нашмат болей працы, і іншы пляц для перакладу, не такі зручны як translatewiki.

OPORTUNIDADE PARA PARTICIPAR DE PUBLICAÇÃO CIENTÍFICA ABERTA

---

Portuguese only

A Editora IVIDES está com inscrições abertas para processo seletivo que visa à composição do comitê científico dos volumes 2 e 3 da série Estudos de caso em mapeamentos colaborativo e participativo. O primeiro volume da série, lançado em 2025, já conta com mais de mil downloads! Os documentos informativos desta seleção estão disponíveis:

 

🡇 Chamada pública para o comitê científico - Critérios

🡇 Convite para o comitê científico

 

✻ O prazo para envio das candidaturas é:

20 de fevereiro de 2026, 17h (UTC-3, hora de Brasília)

 

✍ Formulário de inscrição

 

✻ Os resultados serão comunicados até 23 de fevereiro de 2026, 23h59 (UTC-3, hora de Brasília), via e-mail informado pelo candidato;

 

✻ Chamada para residentes em países lusófonos;

 

✻ Parte dos capítulos inclui OpenStreetMap, aproveite para contribuir e enriqueça o seu currículo como parecerista.

 

---

… See full entry

For a while, I was interested in understanding what makes one pedestrian OSM way better than another. I wanted to know if there is some generic way to identify good walking routes from OSM data. I looked at Garmin and Strava heatmaps at first. Then I checked Strava segments and their proximity to points of interest such as rivers, ponds, and parks. Then I thought to look at my running pace along OSM ways to separate good and not-so-good walking routes. My idea was simple — a good walking route means a smooth running pace. There are fewer stops, less waiting at intersections, etc. Of course, my pace depends on many factors, such as how far I have to run to get to a certain place. So it cannot be a simple cutoff, but rather the distribution of paces along a given segment. This turned out to be a reasonably good approximation of how good or bad I perceive each route to be. I created this Kaggle dataset as an illustration. This relies on my personal GPX data, so it does not scale, but it captures the kind of local knowledge that I find hard to share in any other way.

Banjar

• SD Negeri - ALL DONE
• SD Swasta - ALL DONE

Pataruman

• Pataruman
  • Negeri 1-5 - ALL DONE
  • Swasta
• Binangun
  • Negeri 1-2 - ALL DONE
  • Swasta

Purwaharja

• SD Negeri - ALL DONE
• SD Swasta - Empty

Langensari

I mainly edit OSM based on GPX files from my runs. I use JOSM. I created a simple script to extract a buffered area around my GPX files to make sure I don’t accidentally edit parts of OSM I don’t intend to. See this Github Gist for the source.

Hello! I’m Quincy Morgan. Thank you for considering my candidacy for the board of directors of OpenStreetMap US.

If we haven’t met before, or if you just want to chat about OSM, I encourage you to reach out via OSM, Slack, email, or social media. You can check out my website for detailed information about me, my work, and more ways to contact me.

About

I have been an avid member of the OpenStreetMap community since 2018 in both volunteer and professional capacities. I am the only person to have been employed by both OpenStreetMap US and the OpenStreetMap Foundation. Recently I have organized my activities under Wayside Mapping.

Mapping

As a volunteer mapper, I’ve contributed more than 13,000 changesets over the span of 1,400 mapping days, including more than 3,000 changesets in the past year. My mapping interests are varied but include trails, waterways, peninsulas, scenic routes, monitoring stations, and undermapped places.

Development

As a paid and volunteer open source developer, I have made major contributions to OpenStreetMap tools such as iD, Field Papers, OpenTrailMap, and the openstreetmap.us website. Most recently, I have built and launched themap.is and OSM 411 on my own time.

Life

I’m currently based in New York City but have previously lived in Pennsylvania, California, and Idaho. I’ve spent time in all 48 contiguous United States and all 10 provinces of Canada. When I’m not at my desk, you can find me hiking, biking, paddling, train hopping, or road tripping to the next spot on the map.

Positions

I believe the core roles of a nonprofit board member are threefold:

1. Represent membership

A board member is a democratic representative of the members of the organization. If elected, it would be my job to actively listen to the community and be responsive to their interests.

… See full entry

Eu odeio relações de ônibus

About me

I started mapping in 2021 as I tried to ride every street in Brooklyn, NY on wandrer.earth. I kept finding private streets and other issues on OSM and began fixing them.

At the moment I split my time between the Seattle area and Tucson, Arizona. My professional work is in non-profit accounting. I have worked with a number of organizations covering a full range of financial responsibilities. Handling everything from hands on bookkeeping to grant management to financial strategy.

My mapping

My most cohesive, complete project is detailed mapping of Train Mountain Railroad, the worlds longest miniature railroad. If you’re curious I gave a talk at State of the Map US in 2024 about it.

Most of my mapping is more miscellaneous in nature. I’m a big StreetComplete user, and I’ll always pull over on a bike ride to map a public bookcase! I also enjoy contributing detail to pedestrian and bicycle networks.

Board service and goals

Through the last two years serving as the Board Treasurer I have help usher OpenStreetMap US through a number of shifts in financial situation. Guiding the staff through financial challenges and changes in financial structure.

Through the next two years I want to continue this work, and assist the staff in streamlining bookkeeping and reporting. In addition, as a best practice I would like to see the organization through a financial audit or review. Ultimately leaving the organization on an even stronger financial foundation than it is today.

En mi entrada anterior “Procesamiento en tiempo real de notas de OSM con Bash” expliqué cómo mantener una base de datos local sincronizada con las notas de OpenStreetMap en menos de 10 segundos, usando herramientas comunes de Linux y PostgreSQL. Ese trabajo permitió tener un repositorio actualizado y confiable de notas, comentarios y cambios de estado.

Hoy quiero mostrar el siguiente paso: cómo esa base de datos se convierte en un servicio WMS que permite visualizar las notas directamente en aplicaciones como JOSM, Vespucci o QGIS. De esta manera, pasamos del procesamiento en segundo plano a la representación gráfica en el mapa, abriendo nuevas posibilidades para mapeadores e investigadores.

---

Las Capas del Servicio

El servicio ofrece cuatro capas principales:

• Notas abiertas (rojo): todas las notas activas, con intensidad de color según antigüedad.
• Notas cerradas (verde): reflejan el trabajo ya realizado, con intensidad según el tiempo desde el cierre.
• Países y zonas marítimas: fronteras, aguas territoriales y ZEE, para dar contexto geográfico y político.
• Zonas en disputa y no reclamadas: áreas donde la asignación de país es ambigua, clave para entender por qué algunas notas no encajan en un análisis nacional.

---

Casos de Uso

• Priorización de trabajo: un mapeador abre JOSM, carga la capa de notas abiertas y ve un cúmulo de puntos rojos en su ciudad. Decide enfocarse allí.
• Verificación de progreso: un grupo comunitario carga la capa de notas cerradas y observa un mar de puntos verdes, evidencia del esfuerzo colectivo.
• Contexto geopolítico: cerca de una frontera, las notas aparecen en una zona marcada como disputada. El mapeador entiende la ambigüedad en la asignación.
• Análisis espacial: un investigador usa QGIS para estudiar patrones: más notas en áreas urbanas, menos en rurales. El servicio facilita estadísticas y visualizaciones.

---

Cómo Usarlo

… See full entry

Kilka słów o postępie w nauce, 8 lutego 2026 roku

1. Dodawanie zakresów mieszkań tagiem addr:flats jest tylko informacyjne. Nie pomaga to niestety w nawigacji i możliwości wpisywania adresów z numerem mieszkań do prowadzenia przez nawigację. Stanowi jednak dobry wstęp by w przyszłości “rzeźbić” samemu każde mieszkanie lub by ktoś inny się tego podjął.
2. To dziwne, że nie było automatu Pocztex zaznaczonego na osiedlu Zygmunta starego. InPost, DPD czy one box są dobrze oznaczone w całym mieście, jednak tutaj niezweryfikowane podejrzenia iż to się zaczytuje automatycznie.
3. Podejrzewam, że OSM jest traktowane po macoszemu przez wszystkich. Szczególnie tych, którzy korzystają z tego nieświadomie. Ma to swoje zalety - udało mi się jako pierwszemu dodać dwa urządzenia będące recyklomatami na mapie OSM dla Poznania.

Podsumowując, całkiem przyjemnie jest edytować wiedząc, że nikt mnie nie ubiegnie. Szkoda jednak, że tak wiele jest jeszcze przez to do zrobienia.

The seriousness with which the OpenStreetMap community approaches discussions is a true strength of the project. Over years of debate, the community has formed a highly cohesive tagging system for names. These guidelines are simple for beginners, yet they allow for the precise classification and mapping of real-world names. A name is perhaps the most vital piece of data for most users—it is what they want to see on screens and paper, hear via voice navigation, and even touch.

However, this post isn’t about which tag to choose, but rather the format in which the name should be entered. I want to discuss the phenomenon of ellipsis—or, to put it simply, the shortening of names—and what we as mappers should watch out for when collecting and adding toponyms to the map.

What are elliptical toponyms?

Elliptical toponyms are geographical proper names that have been historically truncated or shortened in oral or written use. These are often names that originally included a generic term (a word indicating the type of object), which over time partially or completely disappeared. The table below shows several examples of such “shortened” Scandinavian and Baltic toponyms:

Historical Full Form	Truncated Form	Explanation
Sed-ezeris	Sedzeris	The hydronym “Lake Seda” lost the generic term ezeris (lake).
Spanggroben	Spanget	A neighborhood near a stream; the second element -groben (ditch/trench) was dropped.
Stampedam	Stampen	A farmstead near a pond; the second element -dam (pond) was dropped, leaving only the specific element.
Sankt Peters Kirche	Sankt Peter	St. Peter’s Church; the second element Kirche (church) was dropped.

… See full entry

Те, як серйозно в OpenStreetMap ставляться до обговорень, — справді сильна сторона проєкту. Протягом років таких обговорень спільнота сформувала дуже цілісну систему теґування назв. Ці настанови прості для тих, хто тільки починає, але при цьому дозволяють точно класифікувати та наносити на мапу реальні назви. Саме назва, мабуть, є найважливішим елементом даних для більшості користувачів — адже саме її вони хочуть бачити на екрані й на папері, чути та навіть торкатися.

Але цей допис не про те, який теґ обрати для назви, а про те, у якому вигляді цю назву заповнювати. Я хотів би розповісти про явище еліпсису або, якщо перефразувати, — усічення назв, і про те, на що ми, картографи, повинні звертати увагу під час збору та нанесення на мапу топонімів.

Що таке еліпсовані топоніми?

Еліпсовані топоніми — це власні географічні назви, які історично під час усного чи письмового вжитку були усічені або скорочені. Наприклад, ті, у яких спочатку було родове поняття, що позначало тип обʼєкта, але з часом воно частково або повністю зникло. Нижче у таблиці наведено кілька прикладів таких «усічених» скандинавських топонімів:

Повна форма	Усічена форма	Пояснення
Sed-ezeris	Sedzeris	Гідронім «озеро Седа» втратив родове поняття ezeris (‘озеро’).
Spanggroben	Spanget	Назва кутка поряд зі струмком, другий елемент -groben (канавка, рів) опущено.
Stampedam	Stampen	Назва хутора поруч зі ставком, другий елемент -dam (ставок) опущено, залишився лише специфічний елемент.
Sankt Peters Kirche	Sankt Peter	Церква святого Петра; другий елемент Kirche (церква) опущено.

… See full entry

https://en.wikipedia.org/wiki/Akkadian_Empire https://en.wikipedia.org/wiki/Ebla#/media/File:Ancient_Near_East_2400BC.svg https://en.wikipedia.org/wiki/Bell_Beaker_culture https://en.wikipedia.org/wiki/Ebla https://www.historicnewburgh.org/_files/ugd/e582e3_718ec184562a4a38b356d24b99a57131.pdf https://www.usi.edu/media/cprjxhjf/campus-maps-floor-plans_01-21-2022.pdf

Trijn Rembrands (Alkmaar, ca. 1557 – aldaar, 10 juni 1638[1]) was een vrouw uit Alkmaar die bekendheid verwierf door haar vermeende rol tijdens het beleg van Alkmaar in 1573. Ze wordt in historische bronnen en literatuur afgeschilderd als een heldin die dapper meevocht tegen de Spanjaarden. Zij wordt soms de Kenau van Alkmaar genoemd; een duidelijke verwijzing naar Kenau Simonsdochter Hasselaer.) Wikipedia

Op 10 oktober 2025 is in het Victorypark in Alkmaar een standbeeld onthuld ter ere van Trijn. Het locatie met alle tags.

Today, I continued my journey as an OpenStreetMap contributor by actively participating in humanitarian mapping through the HOT Tasking Manager. During this session, I focused on mapping basic features such as buildings and road segments using satellite imagery.

This experience helped me better understand the importance of accurate data in supporting humanitarian efforts, including disaster response and community planning. I paid close attention to data quality, proper tagging, and alignment with OpenStreetMap mapping guidelines.

Through this contribution, I strengthened my familiarity with the OSM editing tools and improved my confidence as a mapper. I also gained valuable insight into how collaborative mapping enables volunteers from around the world to support vulnerable communities with reliable geospatial data.

I look forward to continuing my contributions, improving my skills, and participating in more humanitarian mapping projects in the future.

Jede*r hier hat (ständig wechselnd) andere Prioritäten und alle halten ihren Schwerpunkt immer für den Wichtigsten ;)

So schlimm ist es natürlich nicht. Ich mache mich mal auf im Landkreis Waldeck-Frankenberg einen Ort nach dem Anderen (nach Gemeinde) abzuarbeiten um die uralten Geometrien aus den Anfangsjahren mal ein wenig abzuarbeiten.

Jovita Fuentes Javellana, age 82, of Acworth, GA, passed away on Thursday, February 7, 2019. She was born on June 24, 1936 in Iloilo, Barotac Nuevo in the Philippines to Angelina Agudo and Nicolas Fuentes. We call her by her name, Betty. Our lola (Grandma) Betty.

Jovita was a dedicated and loving wife, mother and grandmother. She had a talent for sewing, crocheting and gardening. In addition to being a wonderful mother, Jovita was also a great cook.

… See full entry

Bilang paggunita sa aking yumaong lola ngayong buwan ng Pebrero: sa ika-7 anibersaryo ng kanyang pagpanaw; napagpasyahan kong i-pin sa OpenStreetMap ang libingan ng aking lola na si Jovita J. Isa siya sa mga pinakamahalagang tao sa aking buhay, kasunod ng aking mga magulang, at patuloy na nabubuhay ang kanyang alaala sa aking puso.

Si Jovita Fuentes Javellana ay pumanaw noong ika-7 ng Pebrero, 2019 sa Acworth, Geogia sa Estados Unidos sa edad na 82. Ipinanganak siya noong ika-24 ng Hunyo, 1936 sa Iloilo, Barotac Nuevo sa Pilipinas. Mga magulang niya ay sina Angelina Agudo and Nicolas Fuentes.

Si Jovita ay isang mapagmahal na asawa, ina, at lola. Siya ay may natatanging talento sa pananahi, crocheting, at paghahalaman. Bilang isang masigasig na ina, palagi kong hinahanap ang mga masasarap at masustansyang pagkaing hindi malilimutan. Tulad ng Pasta Valenciana, at mga pagkaing tatak Ilonggo.

Si Jovita Javellana ay nag-iwan ng mga minamahal na alaala sa kanyang mga anak na lalaki:

… See full entry