NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum

3
3

After collecting all the street names, it's time to collect house numbers. What is the best mobile application to automate the process ?

One possible workflow would be:

  1. Application records GPS data or it's done on a separate device.
  2. Application presents user with at least 13 buttons including: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, L, R and 'Clear'
  3. When the user passes a house, he enters the house number followed by either L for left or R for right.
  4. The application logs the keystrokes, including GPS time.
  5. At the end of the session, a post processing phase will correlate the tracklog with the keystrokes and generate an OSM-XML file
  6. The user reviews the file and uploads it to the database.

asked 31 Oct '10, 21:25

Nic%20Roets's gravatar image

Nic Roets
58391219
accept rate: 6%

closed 16 Feb '11, 14:47

Richard's gravatar image

Richard ♦
30.9k44279412

The question has been closed for the following reason "User has answered his own question and solved the problem" by Richard 16 Feb '11, 14:47


If you have an iPhone: For this purpose I put the buttons "copy all tags" and "paste all tags" into iLOE. So it is only half automatic, but fast enough when on a walk outside. Insert the tags for one house in the street, then copy all the tags. Put all the tags for the next house and just change the housenumber. Then upload. Happy mapping, Johannes

permanent link
This answer is marked "community wiki".

answered 16 Feb '11, 12:21

Johannes's gravatar image

Johannes
11
accept rate: 0%

Note that Nominatim (and possibly other geocoders) only need the addr:housenumber tag.

(16 Feb '11, 12:34) Nic Roets

On Windows Mobile I've used OSMtracker to enter custom text waypoints. If the number was on the left, I enter say "12," (or sometimes just "12") if it was on the right I'd enter ",15" and if recording numbers on both sides of the way at once I'd enter say "14,17". In your application (which I can't test) you'd need some way of entering text for houses which have addresses such as "36a" or for full text names in cases where houses are named but un-numbered (older parts of villages in this area).

permanent link

answered 18 Jan '11, 10:20

EdLoach's gravatar image

EdLoach ♦
19.5k16156280
accept rate: 22%

Do I understand correctly that entering "12," will not actually place the housenumber on the left ? Afterwards you need to inspect and place nearly every node ?

(18 Jan '11, 22:25) Nic Roets

Yes, the waypoint will only ever be where the GPS records your position at the time you save the number. Were you thinking by specifying left or right in your workflow the app could perhaps offset the nodes by an entered distance (which might need reconfiguring for each road and depending which side you are walking down)? It's an interesting idea if so, but as you need to review anyway to allow for any GPS inaccuracies I'm not sure how much time it would save.

(19 Jan '11, 08:47) EdLoach ♦

Yes. My post processor already offsets the node. After some testing I'll perhaps make the offset different for left and right.

(19 Jan '11, 09:39) Nic Roets

If you have an Android device:

  1. Make sure the time on it is accurate. NTPc is a free app for this.

  2. Start recording GPX traces (possibly on a separate device).

  3. Install and use the KeypadMapper app to enter the house numbers (screenshot). If a house is on your left, try to hit L when you are traveling perpendicular to the direction of the house. Similarly hit R if the house is on your right. If the house is straight ahead, hit F just before turning.

  4. You can start and stop KeypadMapper as many times as you like. You can also stop and start GPX logging while KeypadMapper is closed.

  5. When done, mount the device(s) on your computer and run

    python KeypadMapper.py /media/.../*.gpx </media/.../keypadmapper >km.osm

  6. Open km.osm with josm to review and upload the data

During the first large test 214 housenumbers were collected in 42 minutes (One 3 digit number every 12 seconds). A subsequent review showed that 89% was correct. The remaing 11% had to be edited as to not confuse the geocoder / reverse geocoder. (Arranging the nodes in neat rows is beyond the scope of this exercise).

I subsequently improved my productivity further by using addr:interpolation.

Source

APK file

KeypadMapper.py

permanent link

answered 17 Jan '11, 23:03

Nic%20Roets's gravatar image

Nic Roets
58391219
accept rate: 6%

edited 15 Feb '11, 13:46

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×352
×42

question asked: 31 Oct '10, 21:25

question was seen: 8,945 times

last updated: 16 Feb '11, 14:47

NOTICE: help.openstreetmap.org is no longer in use from 1st March 2024. Please use the OpenStreetMap Community Forum