Лягатып OpenStreetMap OpenStreetMap

Дзёньнік smootheFiets

Апошнія запісы ў дзёньніку

Log: buildings for follow-up

Дасланы smootheFiets 8 Верасень 2020 на English. Апошняе абнаўленьне 11 Снежань 2020.

This is probably not useful to anyone but myself.

Construction

List of buildings that are listed in the BAG as “bouwvergunning verleend” and that I’ve requested to be imported as building=construction. Check in due course whether construction is finished and update!

Ruins

Buildings that I’ve marked as ruins:building=*. Check in due course if they can be deleted or if anything is rebuilt!

Areas that need attention

  • Noordhorn, Moeshorn 15a and surroundings; Langestraat 18c (new?) + 2*18d
  • Leek, North of ‘de Wiecken’

[DISCONTINUED] Project: clarify bike access on highway=secondary and highway=tertiary in Groningen

Дасланы smootheFiets 11 Люты 2020 на English. Апошняе абнаўленьне 29 Верасень 2020.

I’ve stopped this project in Sep 2020, mostly because I learned that I had misunderstood the concept of a “shared lane” on Dutch roads. There aren’t nearly as many as I had thought. Another project has spun off, though: checking primary and secondary roads in my area for bike accessibility. Primaries, in particular, are not usually open for bikes: either there’s an adjacent compulsory bike path (typically G12a) or bikes are forbidden explicitly (board NL:C9 or NL:C15). I’ve learned that the hard way when Komoot (based on OSM data) sent me on one such secondary one day. That particular problem was fixed the same day, and it got me started on surveying primaries and secondaries (in person, using Mapillary, or using public data on Dutch road signs) in my area. Here’s the corresponding Overpass query: http://overpass-turbo.eu/s/YvO

Old text below:

I see a tendency to equip more and more local secondary and tertiary highways with either an adjacent bike path or an (advisory) bike lane = fietssuggestiestrook, cycleway=shared_lane in OSM speak. This isn’t always reflected in OSM, yet. I’ve fixed some that I’ve come across, but I suspect there’s many more.

Because I find that they matter for bicycle routing, I’ll try and survey those that I can access easily, in province Groningen. Mapillary will help reduce my mileage. The idea is to tag all secondary and tertiary highways outside of town (buiten de bebouwde kom) with a cycleway tag (cycleway=no if none is present), except if they’re tagged bicycle=no or bicycle=use_sidepath. While I’m at it, I’ll also set mofa and moped tags, surface, and where surveyed locally: smoothness. Things like weight limits, updated speed limits and so on will be by-catch.

… See full entry

Photomapping with cheapo action cam

Дасланы smootheFiets 13 Студзень 2020 на English.

I got myself a cheap “action cam” straight from China, for little more than 20 EUR. GoPros run easily ten times more than that. So, what can you expect from a budget cam? Turns out, it’s surprisingly useful for photo mapping, with a few gotchas.

Can do / can’t do

  • Photo quality, of course, is mediocre at best. You get what you pay for, no more, no less. Videos look useless (I’ll have to try on a bright, sunny day), sound clearly is useless. There’s a lot of good stuff you can do with daylight pics, however.

  • The cam can be mounted on the bike’s handlebar or carried on a neck strap. Both work. Pictures can be taken with gloves on. That’s surprisingly important in January :)

  • Motion blur is an issue. Shooting sideways on the bike, as good as it sounds for shop mapping and such, won’t work. Shooting forward is OK. Night-time shots are for better cameras; this one won’t cut it.

  • Text won’t be readable unless you’re really close-by. Gotta get a feeling for that.

  • Road geometry, lane number, presence/absence of sidewalks, traffic_calming are very easy to recognize. Extremely useful.

  • Cycleway signs (NL:G11, G12a, G13): easy

(this list to be continued)

Geo-tagging

Of course, the camera itself isn’t GPS aware like its more expensive brethren. It does have a clock, though. Not the most accurate one, but still. JOSM can correlate time to GPX tracks. This works.

EXIF

JOSM relies on time information from the EXIF header. Unfortunately, my particular camera model doesn’t create EXIF headers. Time information is recorded in file time stamps, only.

… See full entry

Overpass: note to self

Дасланы smootheFiets 5 Студзень 2020 на English. Апошняе абнаўленьне 30 Сакавік 2020.

I finally figured out how to filter for thingies within, say, the province of Groningen, and to load everything into JOSM:
(this example extracts everything with operator starting in Biblionet; turns out that’s the public libraries operated by Biblionet Groningen)

[out:xml][timeout:90]; 
//{{geocodeArea:Netherlands}}->.searchArea;  // search within entity called Groningen (city) 
area[admin_level=4]["name"="Groningen"][boundary=administrative]->.searchArea; // specify: within province (admin_level=4) 
( 
  node[operator ~ '^Biblionet'](area.searchArea); 
); 
out meta;

Unclassified and residential highways within a place, say Ezinge, plus recursions up and down (partly from this link ):
(One lesson I learned the hard way: it’s dangerous to merge and/or split ways in that type of sparse editing. Do make sure to “download parent ways / relations” in JOSM, and still be careful! It’s very easy to break relations such as bus lines / routes)

[out:xml][timeout:90];
{{geocodeArea:Ezinge}}->.searchArea;  
(
  way[highway~"unclassified||residential"](area.searchArea);
  >;
);
(._;rel(bn););
(._;rel(bw););
(._;rel(br););
out meta;

Equivalently, but specifying that Ezinge is a ‘woonplaats’ rather than any random entity:

[out:xml][timeout:90];
area[admin_level=10]["name"="Ezinge"][boundary=administrative]->.searchArea; 
(
  way[highway~"unclassified||residential"](area.searchArea);
  >;
);
(._;rel(bn););
(._;rel(bw););
(._;rel(br););
out meta;

Useful (for me) admin levels within (ref):

… See full entry