Martijn van Exel mvexel

US Local Working Group

Call on 1/25/2016 8pm ET

Clifford, Martijn

Previously...

Notes

US Local Working Group

Call on 1/11/2016 5pm ET

Clifford, Eleanor, Martijn

Notes

Have a periodic hangout with (aspring) local organizers
Collect events from meetup and other sources and compile a calendar to post on talk-us / osm.us

Keybase proof

I hereby claim:

I am mvexel on github.
I am mvexel (https://keybase.io/mvexel) on keybase.
I have a public key whose fingerprint is 06C7 DE3C 62C6 E54B 556C 1D28 7D44 F842 EE1B D064

To claim this, I am signing this object:

ScoutSigns User Manual

Introduction

ScoutSigns is a JOSM plugin to help you quickly map speed limits and other information from actual road signs automatically captured by Scout and Mapillary users.

The sign information is collected by people like you! The latest version of Scout has a ScoutSigns mobile component built right into the app. (Right now, the ScoutSigns component is only available for iOS for iPhone 5 or better.) If you mount the phone on the windshield while driving with Scout (and you opt in) you will automagically contribute to this fast growing sign database that is free for the OSM community to use. Could not be easier!

NEW On top of that, ScoutSigns will also pull in the highest quality signs from Mapillary! As a mapper, it is likely that you already know the fantastic Mapillary project - an open source Street View is the best way to describe it. Recently, [Mapillary starte

	<?xml version="1.0" encoding="UTF-8"?>
	<osm version="0.6" generator="Overpass API">
	<note>The data included in this document is from www.openstreetmap.org. The data is made available under ODbL.</note>
	<meta osm_base="2015-08-17T22:04:02Z" areas="2015-08-17T00:07:02Z"/>

	<node id="288227199" lat="37.8693913" lon="127.7240516" version="14" timestamp="2015-05-08T18:45:38Z" changeset="30917787" uid="64557" user="qpeso">
	<tag k="bridge" v="yes"/>
	<tag k="bridge:name" v="공지교 (Gongjigyo)"/>
	<tag k="bridge:name:en" v="Gongjigyo"/>
	<tag k="bridge:name:ko" v="공지교"/>

	<?xml version="1.0" encoding="UTF-8"?>
	<osm version="0.6" generator="Overpass API">
	<note>The data included in this document is from www.openstreetmap.org. The data is made available under ODbL.</note>
	<meta osm_base="2015-08-17T22:00:02Z" areas="2015-08-17T00:07:02Z"/>

	<node id="414666297" lat="37.1126700" lon="127.6954400" version="3" timestamp="2012-10-18T23:15:32Z" changeset="13551099" uid="371753" user="sanha">
	<tag k="junction" v="yes"/>
	<tag k="name" v="문촌교차로 (Munchongyocharo)"/>
	<tag k="name:en" v="Munchongyocharo"/>
	<tag k="name:ko" v="문촌교차로"/>

	<?xml version='1.0' encoding='UTF-8'?>
	<osm version='0.6' upload='true' generator='JOSM'>
	<bounds minlat='33.2636778' minlon='-96.6810435' maxlat='33.2672447' maxlon='-96.6762466' origin='CGImap 0.3.3 (13325 thorn-01.openstreetmap.org)' />
	<node id='-23588' action='modify' visible='true' lat='33.26664934083' lon='-96.67688718508' />
	<node id='-23586' action='modify' visible='true' lat='33.2666227622' lon='-96.67722413568' />
	<node id='150068374' timestamp='2009-10-12T00:46:35Z' uid='147510' user='woodpeck_fixbot' visible='true' version='2' changeset='2821225' lat='33.275131' lon='-96.679617' />
	<node id='150072677' action='modify' timestamp='2009-10-12T00:47:24Z' uid='147510' user='woodpeck_fixbot' visible='true' version='2' changeset='2821225' lat='33.2661167354' lon='-96.67932841575' />
	<node id='150072679' action='modify' timestamp='2009-11-14T06:51:43Z' uid='147510' user='woodpeck_fixbot' visible='true' version='2' changeset='3110812' lat='33.26608715663' lon='-96.67976971512' />
	<node id='1

	<?xml version='1.0' encoding='UTF-8'?>
	<osm version='0.6' upload='true' generator='JOSM'>
	<bounds minlat='33.2636778' minlon='-96.6810435' maxlat='33.2672447' maxlon='-96.6762466' origin='CGImap 0.3.3 (13325 thorn-01.openstreetmap.org)' />
	<node id='150068374' timestamp='2009-10-12T00:46:35Z' uid='147510' user='woodpeck_fixbot' visible='true' version='2' changeset='2821225' lat='33.275131' lon='-96.679617' />
	<node id='150072677' timestamp='2009-10-12T00:47:24Z' uid='147510' user='woodpeck_fixbot' visible='true' version='2' changeset='2821225' lat='33.265431' lon='-96.678432' />
	<node id='150072679' timestamp='2009-11-14T06:51:43Z' uid='147510' user='woodpeck_fixbot' visible='true' version='2' changeset='3110812' lat='33.265428' lon='-96.679757' />
	<node id='150072704' timestamp='2009-12-22T11:13:45Z' uid='147510' user='woodpeck_fixbot' visible='true' version='2' changeset='3426186' lat='33.264678' lon='-96.678432' />
	<node id='150072706' timestamp='2009-10-12T00:47:25Z' uid='147510' user='woodpec

	09:49 < mvexel> If I had a file with proposed changes to OSM, and I wanted to send that to someone to load in JOSM and process, what would be the preferred format?
	09:50 < mvexel> OSC or JOSM XML?
	--- Log closed Wed Feb 25 09:54:54 2015
	--- Log opened Wed Feb 25 09:55:08 2015
	09:55 -!- Irssi: #osm-dev: Total of 103 nicks [0 ops, 0 halfops, 0 voices, 103 normal]
	09:55 -!- Irssi: Join to #osm-dev was synced in 20 secs
	09:59 < simonpoole> JOSM format
	10:04 < mvexel> simonpoole, any particular reason why JOSM over OSC?
	10:05 < simonpoole> osc only has changes, JOSM would typically have the complete objects
	10:05 < mvexel> I'm afraid I am not too familiar with the change file formats...

	# -- coding: latin-1 --
	'''
	A translator for Mexican INEGI data
	VECTORIAL DE LOCALIDADES AMANZANADAS Y NÚMEROS EXTERIORES
	'''

	def parseName(roadName, roadType):
	import string
	return string.capwords(roadType + ' ' + roadName)