12-06-2017 12:38 AM
it would be beneficial if you can add additional details. Has the cache got created? Can you see the vectorset in a desktop or standard browser app? what is the CS of the vectorset? have you checked primary key is set in vector settings?
12-06-2017 06:12 PM
Has the cache got created? ---> yes created successfully and i checked the directory files to make sure its created.
Can you see the vectorset in a desktop or standard browser app? --> yes and also i can use it in BI .
what is the CS of the vectorset? ---> 3857(its reprojected from 22992) using QGIS.
have you checked primary key is set in vector settings?--> yes i checked it .
12-11-2017 02:49 AM
Can you please show the problem you are getting?
BTW a vectorset cannot be used in BI, please check you are using a vectorset and not a standard cached vector feature.
In addition there is not need to reproject the data externally, the system can do it for you.
12-13-2017 06:35 PM
Is there anything in the log that looks suspicious?
I had issues with displaying some polygon feature classes in analyzer due to having GeometryCollection and Curvepolygons. Had to remove them to have only polygon features to make the layer display
12-17-2017 04:40 AM - edited 12-17-2017 04:41 AM
i can`t see polygons from vector set but I can make charts so I can access data but i can`t view it on the map
see attached pic
02-15-2018 07:52 AM
I have the same problem.
I can use (and see) my cached vectorset in the rich client application, but not in feature analyzer. As asdf already mentioned, I can see all the diagrams.
Seems like it's caused by the view in postgres - I tried to use the feature class, this works fine as there is a Primary Key field. In my view the information about the PK is lost and I'm not able to add a constraint. Contrary to Oracle and SQLServer postgres obviously does not support PKs in views.
I need the view to join data for my analyzer view. Has anyone an idea for a workaround?
02-15-2018 07:58 AM
are you using the vectorset in the rich client client or vector data as standard cache? Please check if the primary key is set in the vector data properties in Studio, we do not use constraints from the database.