nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

OBIEE 11g Maps

DNK

Hi,

We are using OBIEE - map views which is utilizing oracle spatial 'mvdemo'. In US there are many counties with the same name across states such as 'Jefferson County', which is present in around 20 states.

We are unable to restrict these counties appearing on map based on the selected state.

Steps followed:

- We have added two layers for state and county -THEME_DEMO_STATES and THEME_DEMO_COUNTIES in 'Manage Map Data' tab on OBIEE.

- BI data has been added to both the layers using 'Key Layers'

- We populated state level information on map.

- As we drill down from state level to county level, we observe that all the counties with the same name across the country appear with the same data irrespective of which state they belong to.

It would be great if some one can suggest how to over come this issue.

Thanks in advance.

Find more posts tagged with

Accepted answers

All comments

Gianni Ceresa

Hi,

Did you check the logical level key to make sure it's unique and it clearly identify each counties?

It's a bit like if you think at years and months and for the months level in the hierarchy you set as key the month name (like "January"). Every year has a month named "January", so the logical level key isn't unique and the drill will return an aggregate of all the "January" months across all the years.

Your case sounds like that, mainly because you say that all the counties with the same name have the same value although they are in different states.

DNK

Thank You Gianni! for our reply.

Actually,

I did not have any dimension hierarchies setup in the rpd as of now. Do you think setting up dimension Hierarchies with right logical level keys will fix the issue?

Thanks

DNK

Gianni Ceresa

Oh, so you mean drill strictly on the map?

I thought it was a more generic drill (so also on values in tables etc.).

From a modelling point of view hierarchies for all the dimensions are needed in the RPD (it doesn't make it mandatory and allow to not have any, but you are just losing a lot of functionalities and also have issues like the one you see).

So setting hierarchies will fix drills in general, in the map you ideally need to identify keys in a way or another by something else than the name of the counties. I just don't remember exactly now how it is done and what is possible. But it's clearly possible as otherwise maps would be useless ...

DNK

Thank you !

Yes, I was talking about Maps. Sure will fix the RPD with Hierarchy set up on that dimension and will test it.

Thanks

DNK

Hello, I have created a hierarchy in rpd and created analysis with 2 fields State and amount and filtered for one state

in the results I got the result. when I clicked on the State it drills down to all the Counties in table view with Amount. But when on maps it is showing all the Counties from all states with same amount irrespective of the filtered state from the Criteria.

Thanks

DNK

Gianni Ceresa

Don't you have an issue in the keys you set in the map layers?

You can maybe concatenate the state and county if you don't have a county unique ID.

For example this layer which is part of SampleApp use a concatenation of County and the State abbreviation to make counties "unique".

DNK

Hello, thank you for your reply.

I have got to select only from the drop down(can't edit to concatenate).So, that means need to update the key from the mvdemo tables?.Not sure which tables to update.

Thanks

DNK

Gianni Ceresa

I couldn't find a 11g for the test, will need to find one of the old SampleApp to see how was the 11g world

DNK

Thank you

So in 12c you can edit that field?

Thanks

DNK

I fixed this issue by adding a new field(State_County) in the base table (COUNTIES) and updated the Theme (THEME_DEMO_COUNTIES) using the mapbuilder and purged the metadata from mapviewer console.Then I could able to see the new field under layer key.

Thanks

DNK