I have a missing polygon

[Yvecai]

Hello,

Does anybody have the forest multipolygon Relation 1622434 missing from the database? I found nothing unusual with this one, I have it in my cache, but not in the DB.

I'm trying to track down what happened.

So, am I the only one missing this forest ?

Yves

[Jordan Mitchell]

Same - not this particular relation, but a different one in my area, 7270564. It does wind up in my cache. If I map the "name" tag and include its exact name value, it will get imported into postgres - which is a nice workaround (for now) for this one park, but I'm worried others are missing too!

[Yves]

I suspect a diffential update gone wrong, but I fail to see how to monitor updates properly.
Yves

[Jordan Mitchell]

In my case, I'm doing an import of a small area - no diffs. I'm also using -overwritecache each time since it's a small area, so it only takes a minute or two to run. I could supply import pbf file (96Mb) and mapping if that's helpful to reproduce.

[Yves]

Your mapping include boundary=protected_area?
What does Postgres log says after import?

[Jordan Mitchell]

Yes, that's in my mapping, as is boundary="national_park". I've managed to get one missing polygon (#7270564)  to be imported by adding Name: ["Multipolygon's Name Here"] to my mapping, but I've found two more that won't import even if I use that workaround:

2131838, boundary="national_park", name="Great Smoky Mountains National Park"

166587, boundary="national_park", name="Blue Ridge Parkway"

Both are in the cache. Weird!

[Jordan Mitchell]

Oh and to answer #2: there's nothing added to the default postgres logs during import.

[Mateus Santos]

I'm experiencing it too. I wonder if you have found the root cause. In my case, it's happening during diff imports too.