Digitizing individual building footprints down to smaller mapping units is a tiring task but it can be achieved if you have good cartographic/CAD skills. I am viewing all my 3D building models using F4map.com, which normally takes 48hours or so before the 3D visuals can be seen in the application. F4map performs well with OpenStreetMap(OSM) if you input the correct TAGS into appropriate fields. Colors to buildings can also bee seen if you use their correct tags as well. Thanks to all those Mappers who have been assisting in populating/digitizing maps around Papua New Guinea.

Thankyou all and lets keep improving our Maps for betterment.

After recently moving to the area I’ve found myself with the need to go out and do some GPS traces. A small sushi bar is what pushed me to go find out more about my local area and I found several shops that haven’t been mapped yet that I plan on adding, perhaps when it isn’t raining so hard.

I’ve learned quite a bit over the last few weeks, so I’m re-doing some of my earlier entries.

Notes for self and others: Based on local knowledge I’ve been able to determine that the PEMA ortho images are newer than the NYS Orthos, but not by much; these are both newer than Mapbox, but Mapbox is higher resolution/clearer.

both PEMA ortho and NY Ortho appear to be positioned pretty well in the Great Bend area, but Mapbox needs to be adjusted.

ESRI world seems to use the NY Ortho in this area and their positioning is shifted slightly to the north relative to the PEMA and NYS Orthos, but it seems to be registered fairly well overall. I would tend to believe ESRI in general, but the state Orthos may be better aligned for this area. Either way, it’s a negligable shift.

Bing: don’t bother; horrible for this rural area.

Can’t tell the vintage/date for the USGS 3DEP DEM model in this area. There is a much higher resolution Lidar dataset on the USGS website.

I’ve now been editing Oxford, Ohio for over a year, with more than 15,000 edits in the area and only a handful elsewhere. I figured it was finally time to set a proper goal for my editing: “complete” Oxford by the end of May 2022. For now, “complete” refers to mapping all the buildings, highways, POIs, and landuses, with perhaps some nuance. The details for each of these:

Buildings

By my count, there’s 7 neighborhoods/groups of houses left to map. That’s the most significant improvement from when I started a year or so ago, when we probably had around four or five neighborhoods mapped and only half of the downtown/uptown area. After those, there’s just a scattering of buildings on the outskirts of Oxford left. This phase of the project is nearing completion.

Highways

I have five goals for highways currently:

• Consistent, accurate tagging of paths around campus

A number of paths are vehicle-accessible but aren’t labeled as such. I’m not sure what the proper tagging for those is, so figuring that out is the first step here.

• TIGER cleanup

Easier said than done, or so I hear. tiger:reviewed=no is still on most roads in Oxford. I’ll need to do some research as to what TIGER tags should be kept or removed and such. I imagine the zip tags aren’t too useful.

• Sidewalks

There’s lots of sidewalks around Oxford. I’ll probably map these separately, with crossings. That shouldn’t be too hard, but will take a good bit of time.

• Intersections

I’m not sure about how much work there will be to do here, but I want to check up on things like the turn restrictions and traffic lights on all the intersections around Oxford. Some of this might be survey work.

• Parking lots

There aren’t tons of these, but where they exist they’re very inconsistently mapped. Some work will need to be done to bring these up to standard.

POIs

… See full entry

The other day a new user was asking questions about mapping the new development of the former Royal Engineers Barracks opposite Mill Hill East tube station. I’ll write about their problems with postcodes another time.

However, this prompted me to look at the OSM map of the area, which I knew well in the 1980s. I was a PhD student in Central London (UCL), but a close friend was doing his doctorate at (NIMR](National Institute for Medical Research), and I visited fairly frequently. Over time I got to know other scientists & staff at NIMR, not least because I became an active member of the walking group which was part of the staff club (NIMROD, which still leaves a trace on OSM), but also because of scientific collaborations.

… See full entry

uploaded a public path through Great Hollanden to avoid walking on Riding Lane on way to Hildenborough station.

Previously I wrote about checking National Parks in Britain and Ireland for breakage, by counting the number of valid polygons in a rendering database.

A similar approach can also be used to check line features as well as polygons. It’s possible to count the number of contiguous sections of a given polygon. For example, here’s the Lyke Wake Walk, which is in one piece:

psql -d gis -c "SELECT count(*) FROM planet_osm_line WHERE (osm_id = '-1996318');"
 count 
-------
     2
(1 row)

and here is the Sabrina Way, which isn’t:

psql -d gis -c "SELECT count(*) FROM planet_osm_line WHERE (osm_id = '-537430');"
 count 
-------
    12
(1 row)

If something is changed in OSM that introduces an extra piece, or fixes a gap, that number will change. This script can be used to count the change in the number, like this:

Change in relation components for Sabrina_Way 537430
3c3
<     12
---
>     13

… See full entry

The City of Fremantle has new speed limits, mostly 40km/h. I’ve been trying to get the map up to date. They provide a bit of a map (archive), and I’m checking against the new signs as they go up. I don’t know why they don’t care about what happens west or north of the railway line.

I normally don’t really care about vehicle speed limits, because I don’t drive, but this was an interesting exercise in JOSM filters and non-geometric mapping.

Another short post on street furniture (you can definitely tell I haven’t got out much in the pandemic as this is the sort of mundane detail I’m focused on at present). Once again these are, as much as anything, notes for myself.

The Ranty Highwayman wrote a great detailed post about the different types of tactile paving and how they should be used in the UK: https://therantyhighwayman.blogspot.com/2015/02/tricky-tactiles.html. It’s very helpful if confused about the various types, and may help to spot incorrect layouts (which can be tagged).

My only additional contribution is to note that in the UK the tactile paving slabs tend to come in a very restricted set of sizes:

• 40 cm square. The most usual size for both blister & corduroy (hazard warning) paving. There are 6 blisters up & across. I haven’t counted the lines.
• 45 cm square. A bit less frequent, 7 blisters across (illustrated in the blog post above).
• larger (perhaps 60cm+). Blister interval possibly bigger than in the previous two examples, 9 blisters a side. I haven’t measure these slabs precisely, but this is an example on Mapillary.

More examples of tactile paving can be found on suppliers’ sites such as this one.

So far, so unbelievably nerdish, but there’s a nifty bit of knowledge from this info which can be applied to mapping much more widely! Knowing the paving slab sizes makes it easy to estimate the width of pedestrian crossings, crossings at dropped kerbs and any pavement/sidewalk where the corduroy hazard slabs are used. This can not only provide a simple way to survey widths without using a tape measure or laser device, but can also assist in estimating widths based on experience.

This blog post is a version of my recent SOTM 2021 presentation on the OpenStreetMap Standard Layer and who’s using it.

With the switch to a commercial CDN, we’ve improved our logging significantly and now have the tools to log and analyze logs. We log information on both the incoming request and our response to it.

We log

• user-agent, the program requesting the map tile;
• referrer, the website containing a map;
• some additional headers;
• country and region;
• network information;
• HTTP protocol and TLS version;
• response type;
• duration;
• size;
• cache hit status;
• datacenter;
• and backend rendering server

We log enough information to see what sites and programs are using the map, and additional debugging information. Our logs can easily be analyzed with a hosted Presto system, which allows querying large amounts of data in logfiles.

I couldn’t do this talk without the ability to easily query this data and dive into the logs. So, let’s take a look at what the logs tell us for two weeks in May.

… See full entry

Over time I’ve noticed features appearing on highways & paths which are unusual and which I don’t know how to describe. Often these become much more prevalent. Recently I made an effort to do some reasearch on a couple of these and learnt some useful terminology (documented here so I don’t forget):

• Deterrent Paving: These is a form of paving which it is difficult to walk or drive over. It is used in a range of situations, but a common use is where a road has been blocked for cars and cycles are allowed through but there has to be some provision for access by emergency services (often labelled “FIRE PATH” in the UK).

There is quite a wide range of different types, some aimed more at stopping pedestrians. The presence of deterrent paving may represent a significant hazard for people with reduced mobility or impaired sight.

… See full entry

Well, I just wanted to see what this feature does so I’m posting some useless stuff.

As listed on my profile page I muck with mkgmap and my Garmin Nüvi for the USA. These Nüvis can only handle 4GiB map files. So I look at the diagnostic output of mkgmap and noticed we’ve got a billion live nodes that need to be parsed for just the USA. Not exactly sure when it passed this mark, but it was fairly recent.

1 billion USA nodes, and each node has a longitude and latitude that if were represented by a floating point number (single precision float - 32 bits) would mean 4 bytes per longitude, 4 bytes for latitude. Then an identifier…

This would 8GB by itself, without ways to link the nodes. Impressive that osm.pbf can “compress” all these nodes, ways, relations, and all the tags into a (currently) 8GB file.

But anyway been trying to go through a bunch of the QA issues in the map data. I think I got through one pass of the roundabout routing issues that are shown in mkgmap. I was playing with OSRM and GraphHopper with the errors and with the fixes, I’m surprised that people haven’t found some roundabouts that OSRM/GraphHopper completely refuse to enter… they’re scared of roundabouts! Hopefully OSRM, GraphHopper, and even my Garmin Nüvi will now route through them properly.

Alright that’s enough for now here. If this text is even useful…

I am driven by an intrinsic desire to make the world a better place. Together we can do that by mapping using OpenStreetMap!

Minor mapping on some forests in Ecuador

I am saving this list here as a to-do-list. Should anyone suggest a proper way to map this stuff, I will try to enter it in OSM. These are places where the owner can fine you with some hundreds euro if you drive through, if you stay more than 15 minutes at the gas station, if don’t spend enough money at the gas station, and so on.

Diese ist eine List von bekannte Besitzstörungsfälle in Wien:

• Shell-Tankstelle, Ecke Katsushikastraße/Leopoldauer Straße 49, 1210 Wien (hinter der Brücke bei McDonalds)
• Sackgasse Breitenleer Straße 50, 1220 Wien
• Liegenschaft Siemensstraße 105A, ident mit Richard-Neutra-Gasse 3, 1210 Wien
• Donaufelder Straße 135, 1210 Wien (zwischen Hofer und Einkaufszeile Schichtweg)
• Franz-Eduard-Matras-Gasse 5-7, 1220 Wien Es handelt sich hier um eine Sackgasse an deren Ende es kein Weiterkommen für mehrspurigen Verkehr gibt. Das Wenden des Fahrzeuges ist nahezu unmöglich. Deshalb nutzen viele Lenker die Möglichkeit und wenden in einem anliegendem Grundstück. Da dieses überwacht wird, kommt es in jedem Fall zu einer Besitzstörungsanzeige.
• Brünner Straße 64, 1210 Wien, FS Tankstelle. Sogar Kunden der bei selber Adresse befindliche Autowerkstatt werden angezeigt.
• Donaufelder Straße 128, Tankstelle, 1210 Wien
• Heiligenstädter Str. 60, Shell
• BP Tankstelle, Gaudenzdorfer Gürtel 77, 1050 Wien

Over 6 months ago, OpenStreetMap (OSM) and OpenStreetMap Foundation (OSMF) members, community supporters, organizations, and allies called for change in how OSM and OSMF conduct themselves.

We asked:

“The OpenStreetMap Foundation (OSMF) and OpenStreetMap (OSM) need to prioritize diversity and inclusion in positions of power and governance. We recommend a renewal and implementation of an OSM Code of Conduct and deliver on the next recommended stages for a diverse and inclusive OSM and OSMF. We want the OSMF to ask itself: who does it exist to serve? How can we be more open?”

Resource: A Call to Take Action and Confront Systemic Offensive Behaviour in the OSM Community »>The original document»>

The Result:

The OSMF board asked the Local Chapters and Community Working Group (LCCWG) to form a subcommittee on “Moderation”. This group has been meeting and coordinating since January 2021 (lead by Maggie Cawley, OSM US).

“In December 2020, the OpenStreetMap Foundation (OSMF) Board set out to “find partners to help instate a moderator team for the OSMF-talk and talk mailing lists” and in their December 2020 meeting requested that the LCCWG take the lead on this initiative. Subsequently, this group has been formed as a subcommittee of LCCWG. The Moderation Subcommittee is a temporary group of OSM community members working on this Scope of Work via this Implementation Plan. Learn more about participants and find links to any draft documents on the Subcommittee’s page. “

The Ask - Give feedback by August 18, 2021:

The LCCWG Moderation Subcommittee solicits community input on its DRAFT Process for Moderation, which would apply to the osm- and osmf-talk mailing lists. Hosted in the OSM wiki, the Discussion page is open for comments until August 18, 2021.

… See full entry

I’m a recently retired senior leader/exploration geologist after 23 years working for a major international oil and gas company. I’m familiar with GIS systems, but not an expert by any means.

I spent a large portion of my career mapping remote sensing data in order to determine what lies below the surface of the earth. In my case this was primarily seismic data and well log data, but occasionally magnetic or gravity data.

I’m looking for some fun things to do so I started contributing to OSM.

New to OSM, may make some newbie mistakes, so please comment, send me a msg. Feedback/help always welcome.

Generally using aerial imagery (ESRI World, world clarity, Mapbox, Maxar). I scan through multiple images to get a sense of offset. Also using OSM GPS traces loaded by others

This diary entry is a bit delayed, but this will contain my progress for the gsoc period so far and what I have been upto during the last 5-6 weeks A detailed description of my work can also be found at Github Wiki

My task was to create an Element History Comparison dialog for Vespucci, which can be provided as a separate library so that it can be useful for other open source projects if they need the same functionality.

What the Element History Comparison Dialog does is what the name suggests, i.e it compares what changes the have been made to a particular OSM element on the map and details them, like providing tag changes and which user has made those changes. It works as something similar to the built in history feature of JOSM.

Right now, I have completed the dialog itself and am currently testing different possible user interfaces for the application, in order to better suit a mobile screen, which has been the most challenging part so far as due to the lack of width on the mobile device certain compromises needed to be made

My Weekly progress has been the following:

Week1

• Created all the required base OSM elements and storage structures
• Created a custom implementation of the OSM parser to parse the XML response
• Added unit tests for the base OSM classes and the parser
• Created the initial library interface
• Setup for the HTTP requests

Week2

• Created the version selection screen UI
• Impl. the version selection logic with radioButtons and groups

Week3

• Created tests for the version selection screen
• Improved UI for the history screen
• Current UI for the selection screen

Week4

• Created the base UI for the comparison screen
• Created the logic for the comparison screen
• Implemented changeset fetching

Week5

• Created logic for the comparison screen
• Added changeSet Details
• Add basic UI for comparison
• Fix test cases

Week6

• Ui testing and improvements

… See full entry

I really hate litter. I have a very vague project in mind which will involve mapping litter in some way. Having information about the location of litter bins seems like it would be helpful, so I am starting with that. Hopefully as I work through this the vague project will take better form - this works in many other endeavors, so why not with this one.

Little Steps !