Diary Entries in English

Recent diary entries

Posted by maning on 8 July 2019 in English. Last updated on 9 July 2019.

Last weekend, a couple of OSM volunteers and drone enthusiasts visited Lupang Arenda in Taytay, Rizal. The visit was part of the ongoing collaboration with Barangay Santa Ana in Taytay to use OpenStreetMap as one of their tools for managing community initiatives. The origins of this collaboration has an interesting back story but I won’t talk about it on this post. ;)

The main goal of the visit is to capture images using drones to create an updated aerial imagery of the community to identify individual building/houses. For a densely populated community like Lupang Arenda, it is difficult to get this level of detail using satellite imagery.


The crew. Photo by Erwin Olario.

See full entry

Location: Santa Ana, Taytay, Rizal, Calabarzon, Philippines
Posted by jkirk on 8 July 2019 in English.

According to Wikipedia there are four main tennis surfaces types:

  • Clay courts
  • Grass courts
  • Hard courts
  • Carpet courts

But when looking at the “sport=tennis’ tag the English and German Wiki pages are note very accurate about the tennis court surface types. The English page does not recommend any “surface” values but refers to the Wiki page (which is ok), but the German page talks about “clay”, “asphalt”, “grass” and “sand”.

But when looking at the”surface” key, only “clay”, “decoturf” and “carpet” are connected with tennis.

“DecoTurf” is a special tennis hardcourt product manufactured by an US company. I think we should avoid using “surface=decoturf”.

When checking taginfo of “sport=tennis” you can see more than 96% of them are combined with “leisure=pitch” but only less than 9% have a “surface” tag. Most of them are “clay”, followed by “paved”, “asphalt”, “concrete” and “sand”. (Next to) none of them are tagged with surface “grass” or “carpet” (or even “decoturf” (good!))!

I am not sure yet, how to tag hard courts (I tend to “hardcourt”), but we should only use the following values for “surface”:

  • clay
  • grass
  • hardcourt
  • carpet

Beginning in June of 2019, I began importing building footprints for counties inWisconsin. These were sourced from the State Cartographer’s office, and is part of a larger project of importing this data for other counties in the state.

osm.wiki/Wisconsin_Multi-County_Building_Footprint_Import

I finished Menominee county, have added all areas not already mapped for Wood county, and have now started on Winnebago county.

Posted by deptho on 4 July 2019 in English.

Just noticed wiki.openstreetmap.org/wiki/Key:source suggesting the changeset should describe the source of the change rather than every object. I’ll reduce the number/type of objects in my changesets to make it easier to relate the changes to the changeset description/sources.

Some of you will remember - and will have participated in - a demographic survey i conducted almost two years ago which aimed to establish whether there were any differences between the genders in the way contributors edit in OSM. Since then I have conducted several analyses of the data I collected and shared the results at several conferences. Each of the these papers is available on my researchgate profile which can be accessed from the following link.

https://www.researchgate.net/profile/Zoe_Gardner4

I’m delighted to announce that the following peer reviewed paper titled “Quantifying gendered participation in OpenStreetMap: Responding to theories of female (under)representation in crowdsourced mapping”, based on the data I collected from the generous OSM users that participated, has just been published and is accessible online using the link below.

http://link.springer.com/article/10.1007/s10708-019-10035-z

See full entry

If you’re organizing an OpenStreetMap-related event, consider adding it to the wiki’s global OSM event calendar, which also appears in each issue of weeklyOSM. Even if you don’t expect to attract new attendees via the event calendar, it’s a decent way to raise awareness of your local community within the broader OSM community.

To add an event to the calendar, go to the Main Page and click the little blue ✏️ link at the top of the calendar. Follow the instructions on the edit page and click “Save changes”. Note that editing the calendar requires a free wiki account with a confirmed e-mail address. Otherwise it’d be too easy for spam to get in.

(If you’re organizing a regularly recurring event for a local community, you should also advertise it in the community index that appears after uploading a changeset in iD.)

Same great taste with half the punctuation

The event calendar has been rewritten to make it easier for non-programmers to contribute new events. In the past, adding an event to the wiki’s event calendar meant editing delicate HTML microformats and idiosyncratic templates. But more realistically, it meant copy-pasting an existing event and hoping for the best. Now a single template handles the implementation details for you, so you can focus on the details that matter.

Before:

|-class="h-event"
| {{Cal|pizza}} || {{Dm|y=2019|Feb 7}} || <span class="p-name">[//www.meetup.com/Code-for-San-Jose/events/256761257/ Civic Hack Night & Map Night], [[San José, California|San José]], [[California]], [[United States]]</span> {{SmallFlag|USA}} {{SmallFlag|California}}

After:

{{Calendar/event
| type = pizza
| date = 2019-07-11
| name = Civic Hack Night & Map Night
| url = //www.meetup.com/Code-for-San-Jose/events/261576831/
| city = San José
| citylink = San José, California
| region = California
| country = United States
}}

See full entry

Location: University, Dinkytown, University, Minneapolis, Hennepin County, Minnesota, United States
Posted by ashish123 on 30 June 2019 in English.

In pt-assistant my next task is to improve the visualization. as route relations make a spider-like structure so visualization of relations becomes too tough. So the task is to break the route relations into segments where each segment serves a bunch of relations and will be a collection of ways which are serving the same bunch of common relations. for complete details, you can look TaskManager

Posted by tchaddad on 29 June 2019 in English.

The GSoC project to add Wikidata to Nominatim is now well underway. This post will focus on the first phases that have centered on updating Wikipedia extraction scripts in order to build a modern Wikipedia extract for use in Nominatim. English Language Wikipedia logo

A little background

Why is Wikipedia data important to Nominatim? What many OpenStreetMap users might not know is that Wikipedia can be used as an optional auxiliary data source to help indicate the importance of OSM features. Nominatim will work without this information but it will improve the quality of the results if this is installed. To augment the accuracy of geocoded rankings, Nominatim uses page ranking of Wikipedia pages to help indicate the relative importance of OSM features. This is done by calculating an importance score between 0 and 1 based on the number of inlinks to a Wikipedia article for a given location. If two places have the same name and one is more important than the other, the Wikipedia score often points to the correct place.

See full entry

DigitalGlobe, now Maxar [1], is transitioning the OpenStreetMap imagery endpoints (from “DigitalGlobe Standard” to “Maxar Standard”; and from “DigitalGlobe Premium” to “Maxar Premium”). OSM users should see content parity between the old and the new layers by June 30, 2019. Starting July 1, 2019, there will be only two Maxar layers available from within the OSM editors – labeled with Beta.

Our new imagery services use http/2 protocol. Please note that there are some known speed issues with the JOSM editor. A JOSM plugin for http/2 support is expected before the end of July (ticket #17861). In the meantime, increasing the concurrent connections (e.g. to 20) will help. iD editor already supports http/2.

The good news: imagery will be more recent and more frequently updated with our latest Maxar mosaic content. We hope that our improved production processes (bundle block adjustment, atmospheric compensation, continuous updates, etc.) will benefit OSM contributors.

As always, thanks to everyone within OSM for all your support and feedback. Shout out to the maintainers and contributors for iD and JOSM who have been fantastic to work with. Look for Maxar at State of the Map and State of the Map US; we will be attending and presenting more information on this new image service. And please feel free to send us feedback. Happy editing!

[1] https://www.maxar.com/