You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem here is about using a reject filter instead of an accept one. So, if a new content tag is added for storage tanks, for something else than oil, then my results will be false. So this solution is not ideal.
On the other hand, if I'm using an accept filter, this will force both rows with {"man_made" : "storage_tank"} and {"man_made" : "gasometer"} to have a content tag corresponding to my list, but for gasometer no such tag exists...
Expected Behavior
What I want is to be able to choose a filter accept for rows having {"man_made" : "storage_tank"} like this: {"content": ["fuel","natural_gas","hydrocarbons", "gas", "LNG", "LPG", "oil"], and no filter on content for {"man_made" : "gasometer"}.
The goal being to be able to aggregate data from both storage tanks and [gasometers](wiki page) in one single table, applying different filters according to some tag value.
Possible Fix
What I imagine is something like the following, but there might be a better way.
The goal being to be able to aggregate data from both storage tanks and [gasometers](wiki page) in one single table,
applying different filters according to some tag value.
my recommendation as a workaround:
create 2 simple tables ( in imposm3 )
AND create a wrapper SQL view ( UNION ALL ) as postprocessing. ( in SQL )
see an example: #217 (comment) just replace : "green" --> storage_tank ; "red"--> gasometer
Context
Here is an idea for improving imposm. I want to be able to apply specific filters to specific tags.
For example, I would like to map all data about oil tanks in one single table. This is how I am currently doing:
The problem here is about using a
reject
filter instead of anaccept
one. So, if a newcontent
tag is added for storage tanks, for something else than oil, then my results will be false. So this solution is not ideal.On the other hand, if I'm using an
accept
filter, this will force both rows with{"man_made" : "storage_tank"}
and{"man_made" : "gasometer"}
to have acontent
tag corresponding to my list, but forgasometer
no such tag exists...Expected Behavior
What I want is to be able to choose a filter
accept
for rows having{"man_made" : "storage_tank"}
like this:{"content": ["fuel","natural_gas","hydrocarbons", "gas", "LNG", "LPG", "oil"]
, and no filter oncontent
for{"man_made" : "gasometer"}
.The goal being to be able to aggregate data from both storage tanks and [gasometers](wiki page) in one single table, applying different filters according to some tag value.
Possible Fix
What I imagine is something like the following, but there might be a better way.
And maybe there's already a way to do this but I couldn't find one in the documentation.
The text was updated successfully, but these errors were encountered: