I am experimenting with setting up an OSM tile server.

So far, I have downloaded a recent version of the data, loaded it into PostGIS using osm2pgsql, and set up renderd and mod_tile on my server instance.

I have a test harness that shows some missing polygons along the River Thames:

http://174.129.244.158/jlmap.html

Is there a straightforward approach to debugging this? How do I determine if the polygons are missing, or if it is a missing tag or rendering error.

Thanks in advance.

asked 27 Nov '13, 22:55

john_willyn's gravatar image

john_willyn
26224
accept rate: 0%

edited 28 Nov '13, 20:01

aseerel4c26's gravatar image

aseerel4c26 ♦
31.9k16237548

1

Haven't looked into this in detail, but the fact that the default osm.org map (and, in fact, the various other renders available on osm.org) all show the correct riverbank there suggests to me that it's not a data issue.

(27 Nov '13, 23:27) Richard ♦
2

You're missing dozens of polygons - residential areas around south london, Wimbledon Common etc. It looks like your import has failed somehow.

(28 Nov '13, 09:21) Andy Allan

The general way to approach such a problem would be (note that with the web site design constantly changing, the process might differ slightly if you read this at a later time)

  • go to www.openstreetmap org
  • zoom very far into an area that has at least one line of the polygon you're interested in
  • activate the data layer (click the layer button on the right then activate the "map data" checkbox)
  • click on the blue line in the map and select "details" on the left hand side
  • make a note of the way ID, and also look at the bottom of the node list where it should say "part of..." and point to a riverbank relation
  • use pgsql (or pgadmin or similar) to connect to your database
  • in the planet_osm_polygons table you should have an object with an osm_id of the negative (!) id of the relation
  • if that isn't there, check if your planet_osm_rels has an entry with the positive (!) id of the relation and if planet_osm_ways has all the constituent ways; likely something is missing and therefore the polygon could not be constructed. Check your source data in that case. If however the building blocks are all there but the polygon is not, then for some reason osm2pgsql decided not to create the polygon - either due to a bug or due to tag filtering via the style file or LUA code.
  • if however the polygon is there in your database but not on the tiles then there must be some kind of problem down the line, in your rendering rules.
permanent link

answered 28 Nov '13, 07:53

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
69.9k806321095
accept rate: 24%

Thanks for the very detailed instructions. Unfortunately, I only see the node numbers listed in the node list, and not any relations, or at least anything I can identify as a relation. I scouted around in the tables and tried to figure out the structure, but none of the id's look they were listed in the node list.

The way ID is 204068876 in case anyone wants to help guide me further. At least this seems to be one of the missing polygons.

I do suspect my import was partially bad, and I noticed a couple of errors reported in 'pending ways', but thought the relations and polygons completed without errors.

Thanks again.

(28 Nov '13, 17:04) john_willyn
Your answer
toggle preview

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:

×385
×156
×74
×69

question asked: 27 Nov '13, 22:55

question was seen: 2,970 times

last updated: 28 Nov '13, 20:01

powered by OSQA