Osmosis applying changeset to apiDB sets visible field to false

I am following the blog post here to maintain an up to date region of OSM data. I had trouble filtering my API db in Postgres by a bounding polygon after applying changesets. I eventually discovered that this was because the visible field of all entities I imported with:

osmosis --rri --simc --wdc host=localhost database=test user=xx password=yy validateSchemaVersion=no

was set to false. If I manually set the visible field to true I can filter out the new points successfully, otherwise the new points are not filtered out with a bounding polygon query.

Is there a reason that osmosis sets visible to false or that visible=f nodes are not included in polygon queries? I had a look through the source code and did some searches but couldn't see anything obvious there.

visible apidb osmosis

asked 07 Dec '14, 19:54

stev
36●3●3●6
accept rate: 0%

edited 02 Jan '15, 14:54

SomeoneElse ♦
33.2k●65●347●791

Be the first one to answer this question!

toggle preview

community wiki:

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

learn more about Markdown

Question tags:

osmosis ×231
visible ×12
apidb ×11

question asked: 07 Dec '14, 19:54

question was seen: 2,465 times

last updated: 02 Jan '15, 14:54

Osmosis applying changeset to apiDB sets visible field to false

Follow this question

Related questions