i was finished 1401 my edit

I was Complete 1200 My edit

1000 times edit

(Work in progress)

During the summer of 2019 Ashish Singh worked on further improvements to PT_Assistant. He improved the data model, which led to a better functioning of sorting stops in public transport routes. It could also lead to nicer visualisations of the routes, but that has not been implemented yet.

In this diary entry I want to highlight some of the new features and explain others that existed before.

Public transport

Validator

In the validator everything related to public transport is prepended with PT:

• It can detect that routes can be fixed by simply resorting the ways

• Or that stops aren’t served.

• It also reports when the highway is not suitable for the mode of transport

• Or that the vehicle goes against oneway traffic, or takes a turn where there is a turn restriction

Visualisation

The route that is currently selected or for which the relation editor has focus (it’s on top) is highlighted in purple with the stops in yellow. The stops have the ref of the route, followed by a sequence number.

Relation Editor

Routing Helper

• The routing helper was added last year and is now better on (wrongly) split roundabouts

• There is also a new option, which makes it possible to split the way that is painted in white. The way that was added last in most cases. If a user does this by selection option 8, they get the possibility to make a turn before the white way’s end node is reached. The user selects option 1, 2 or 3. Often there is only 1, or goes further back by using option 8. Once a turn is selected, it is the white way that is split and the side road becomes the new white way.

Demo

Stops sorter

… See full entry

Summer has come to an end, and so this post is to wrap up the progress made over the course of the “Add Wikidata to Nominatim” project. Overall, the main contributions are documented in the 4 preceding diary posts, and in:

• updated steps for extracting Wikipedia data and calculating importance scores
• a new script for extracting Wikidata items and place types

These new processes have made big improvements in several OSM-to-Wikipedia comparison metrics as compared to equivalent numbers from 2013 (when the previous Wikipedia snapshot was taken).

Improved Numbers

For context, the number of Wikipedia articles in the top 40 languages in 2013 was 80,007,141, and the number of Wikipedia articles for the same 40 languages in 2019 was 142,620,084 - an increase of ~78%.

Within these article records, in 2013 it was possible under the old processing steps to attach latitude and longitude numbers to 692,541 articles, while in 2019 it was possible to enrich 7,755,392 records with location information - an increase of ~1,020%. This particular statistic largely reflects an improvement in the source Wikipedia / Wikidata projects.

More exciting, with the old method of linking Wikipedia articles to osm_ids, it was possible to link 313,606 Wikipedia article importance scores to osm_ids, but with the new method that uses both Wikidata item ids, and Wikipedia pages together, the number of Wikipedia article importance scores that can be linked has risen to 4,730,972 - an increase of ~1,409%. This increase is due to both the large number of Wikipedia and WIkidata tags added by OSM contributors since 2013, as well as the inclusion of Wikidata item ids in the linking process for the first time via this project.

Future Work

Although the project technically concludes today, there are obviously always areas of future work where more gains can be made. These include:

… See full entry

Im edit in file 901 edit so in happy in this work

I have made some LGBTQ/rainbow pride versions of the OSM Logo:

What I’ve done is CC BY-SA 4.0, but the OSMF Trademark Policy probably means that doesn’t apply. view all here

I have it all in a github repository, please feel free to download, share, remix, make suggestions, print yourself, etc.

I plan to print some of the these out as 5.2cm× 5.2cm stickers and bring them to State of the Map in Heidelberg. Would you like some? Would you like a specific one? I was only going to print one or two designs. Leave a comment here, or OSM message me, or email me to request a specific set, and how many.

My Editing 858

I’m primarily working on surveying Electric Vehicle charging stations to power https://gitlab.com/showmethechargers – I have got everything in the Kirkland Lake + New Liskeard area, everything near the highway through North Bay, and I’m about 6 away from getting all of Kitchener + Waterloo, which I will hopefully get soon.

I’ve planned a trip to survey Stratford. After that Cambridge will probably come in bits and pieces over time as I’m not there much.

My other main survey focuses (usually in areas I’m surveying anyway, or sometimes just while passing through) are: bicycle parking, mailboxes, and business opening hours.

My main tool of choice for survey right now is to take photos of any useful object or detail with my phone, with compass and location tagging turned on. This gives me a close (but not exact) geopoint which I can correct using memory + satellite imagery later when inputting with iD.

I would really like to fix the transit map for Kitchener/Waterloo (since it’s out of date after the new launch) but that’s not really doable in iD and I haven’t sat down to learn JOSM yet. I’m also not sure how much of that I can claim is from “local knowledge” without being poisoned by seeing the official maps and timetables. Ideally we could just use the Region’s Open Data but not sure on license compatibility.

Today I would like to share what I have learned about using external data in OSM but not in the classic import fashion.

I have gone over what I have learned about data importing in OSM after being involved in a few of them. But today I want to talk about how we’re using data from our local government as a reference but not using the usual import method and why.

So what is the definition of an import in regards to OSM? The Wiki defines it as “the process of uploading external data to OSM.“.

But uploading is not always the most effective way to use external data to improve OSM. What we are doing is showing external data as a layer over OSM and using that to edit OSM by hand.

But Why?..Wouldn’t it be better to direct upload the data?

… See full entry

… See full entry

This post is an answer to Roland’s call for input on his planned SotM session on New processes to agree on tagging suggestions and their interaction with the editing software available on openstreetmap.org

I have no specific suggestion for an overall solution to the problem but a few observations on the matter that i would like to share on the level of problem analysis so to speak.

… See full entry

The last post introduced Wikidata, and covered how to extract basic information from wikidata dumps using a postgres database and regular SQL queries. This post explains some simple SPARQL queries and the Wikidata Query System and related API, and how they relate to the improvements desired in Nominatim. The following examples, along with a few other tools from the Wikidata ecosystem, are a good start for any OSM contributor that is Wikidata-curious.

Explaining SPARQL

For a new user, probably the most foreign aspect of using Wikidata is the need to know something about SPARQL. So what is SPARQL?, and why do you need it?

… See full entry

August 29, 2019. Just registered and looking forward to starting with OpenStreetMap! Orientation meeting at my firm next week.

I added some road names and place names today in Beitbridge

Dear all,

Today, v4.22.0 of the OpenStreetMap Carto stylesheet (the default stylesheet on the OSM website) has been released. Once changes are deployed on the openstreetmap.org it will take couple of days before all tiles show the new rendering.

Changes include

• Shop label fixes and use ST_PointOnSurface for building label placement

  This fixes some bugs and makes building label placement consistent with shop label placement.

• Use cache-feature: true to improve performance of layers with attachments

• Use retail colour fill on malls

• Drop highway=steps from zoom 13

  This makes step rendering consistent with footways

• Render place=locality from zoom 16

  This fits current usage of the tag and what it is normally tagged on.

• Render natural=bay from linear ways

• Render administrative boundary labels from relations only

• Stop rendering natural=marsh

  It is recommended marshes are tagged with natural=wetland + wetland=marsh

• Use a whitelist for barrier rendering, and render historic=citywalls like barrier=city_wall.

• Support new Tibetan font name

  Noto has renamed Noto Sans Tibetan to Noto Serif Tibetan. The old name is still supported.

• Code cleanups to increase reuse and improve consistency

Thanks to all the contributors for this release, including daveol and btwhite92, new contributors, and jeisenbe, a new maintainer.

For a full list of commits, see https://github.com/gravitystorm/openstreetmap-carto/compare/v4.21.0…v4.22.0

As always, we welcome any bug reports at https://github.com/gravitystorm/openstreetmap-carto/issues

A year I was just starting as a volunteer for the CWTS++ program, from answering a question to being accepted in the program. I did not even realize that there is something beyond this before I thought the benefit of it was just the technical of mapping. Surprisingly, I did not even expect what would be coming as I went through with it and imagine representing it to other people.

So I am one of those people that got lucky and been awarded a travel grant to “Pista ng Mapa” a national conference in Dumaguete, Negros. So everything is sponsored and I am thankful for that because I get to experience something new again, this includes air travel and no parental supervision outside of Manila.

One of the workshops that I went to is Data Storytelling with Open Contracting Data. I just had a feeling that’s why I choose this workshop and I can’t to the other workshop ‘cause I already have experience in OpenStreetMap and it was only the introduction of it. So I challenge myself by force and went to the Data Storytelling, even though I don’t have a clear idea of the whole workshop rather than creating a story with the given data. The speakers were journalists and data scientists which amused me about their topic and the talk itself, even though I can’t intake everything they’re talking about. I was grouped with other people which had a lot of experienced specially with politics, academe, and volunteering. They taught me how to filter a whole of data set which was around a thousand plus items, you have to sort it, tally it, analyze and make an interpretation out of all the gathered data to create your own story. Sadly the time was not enough to create the whole data story but it was fun learning at a different level.

… See full entry

I experimented with extracting the heights values from the drone imagery and add them to the building polygons traced in OpenStreetMap. Read along if you want to understand the process or just go here to see it in action here!

3D buildings around Foundation University, Dumaguete

Day 3 of Pista ng Mapa last Aug 3, 2019 was a series of field mapping activities. A couple of people did on the ground survey with field papers and mapillary. Our resident drone Mapher Leigh deployed her DJI Phantom 4 to survey the event venue and its surrounding community. Leigh uploaded all the drone derived data into OpenAerialMap including the elevation models! Using QGIS 3.6, I decided to explore ways to extract the heights from the derived DSM/DTM and use it for visualizing building polygons from OpenSteetMap.

For this exploration I used QGIS 3.6 with the GRASS GIS, Profile tool and QGIS2threejs plugin.

Downloading the drone derived layers from OpenAerialMap

… See full entry

Introduction

So, this is the final entry of a what has come to be a 6 entries series, regarding this year’s Google Summer of Code project and the work that has been done on the 3D Renderer OSM2World. This post will summarize the last 2 tasks that did not get their own separate entries as well as give an overview of the whole summer work, starting from the latest. The two tasks in question are those of Rendering Destination Signs and Guessing the positions of non-explicitly defined signs, as stated in the application document, which have proved to be particularly challenging to say the least; we will go through them later on this post.
So without further ado, let’s present what has been done so far in this Summer of Code, in a chronological order:

1. Font rendering for signs with custom text: https://github.com/tordanik/OSM2World/pull/147
2. Human readable traffic sign values: This particular task does not have a pull request of its own as its TODOs, mentioned in the application document, where gradually being implemented as parts of the other tasks (a good example of this can be found in this entry)
3. SVG texture support: https://github.com/tordanik/OSM2World/pull/151
4. Traffic sign catalogues: https://github.com/tordanik/OSM2World/pull/153
5. Destination signs: https://github.com/tordanik/OSM2World/pull/154
6. Guessing the positions of non-explicitly defined signs: https://github.com/tordanik/OSM2World/pull/155 (may be changed)

A summary is available for each of the first 4 tasks, in their corresponding diary entries, listed below in the same order:

1. Font rendering for signs with custom text
2. Human Readable traffic sign values
3. SVG texture support
4. Traffic sign catalogues

Let’s now see what the remaining 2 tasks are all about!

Rendering of Destination signs

… See full entry

I’m working on repairing the forest multipolygon in Hokkaido. They are deleted/modified/destroyed badly for several weeks ago.

It is very hard to repair with revert or redrawing, because the damage is too serious and complex. So I would like to reuse the polygons from old planet files if possible.

But I’m facing versioning issues. Anyone has more easy solution?

• Extract multipolygon relation using osmium: Like those command.

osmium getid -r ./hokkaido-190601.osm.pbf r1083877 -o r1083877.osm

• Merge: Merging those polygon and current osm.org data using JOSM merge selection.
• Upload: It causes numerous conflicts due to object version is smaller than https://www.openstreetmap.org’s current objects.

Should I tweak the xml file for versioning? (e.g. using sed or some other methods)

P.S. The vandal mapper is editing his edit ignoring my message/changeset comments. I already reported this with https://www.openstreetmap.org’s reporting feature.

… See full entry