Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is possible and what is not? #435

Open
strech345 opened this issue Jan 26, 2017 · 4 comments
Open

What is possible and what is not? #435

strech345 opened this issue Jan 26, 2017 · 4 comments

Comments

@strech345
Copy link

Hello, for me it is not really clear what functionalities i will get from ol3 and cesium.

Does i have the full features of Cesium? for example ...

Does it have the full features of OL3 ? for example ...

  • Heatmaps
  • Clustering of Marker
  • loading Vector Tiles
  • loading KML, Json,...
  • Interactions

Would be great to get a comsumption about what is possible and what's not.

@jmgomezpoveda
Copy link
Contributor

A lot of things work. Now, I don't know about most of these, but I do know about a few of them:

@gberaudo
Copy link
Member

You create and pass the OL map so you have full control on it.
The Cesium globe is created by OL3-Cesium but you get notably the reference to the Cesium.Scene, you can then use the Cesium API.

For missing features it is possible to:

  • improve OL3-Cesium by contributing patches;
  • use hooks to implement own logics (eg synchronize a raster layer in OL3 to a vector layer in Cesium / gltf ...)

@strech345
Copy link
Author

@gberaudo
for me it is important to have the reference on cesium viewer also and to control it like i want. It would be nice to create boath instances (ol3 and cesium) and to use this framework to connect boath with each other. But i think this will not be the case.

@jmgomezpoveda
So. its possible with cesium feature request to request also ol3 features?

@jmgomezpoveda
Copy link
Contributor

@strech345 I am not sure I understand your question. With ol3-cesium you use the same API as ol3, and ol3-cesium internally translates the API requests into the Cesium API. You create the map once and you are able to switch between the ol3 and Cesium views at will.

In most cases you only need to use the ol3 API for this. In some cases, though, you may need to interact directly with the Cesium object exposed by ol3-cesium.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants