search

cmv / cmv-app

CMV - The Configurable Map Viewer - A community supported open source mapping framework built with the Esri JavaScript API and the Dojo Toolkit
https://demo.cmv.io/
MIT License
325 stars 278 forks source link

AGOL webmaps #72

Closed ebonan closed 10 years ago

ebonan commented 10 years ago

Hi and thank you very much for your viewer. We would like to use it with agol webmap and we tried to integrate the funcion from the mentioned fork without success...(see closed post)

We noticed that the config and controller are very different maybe because the fork is older. Could you give us some help to integrate agol webmaps in the recent version? thank you in advance!!

Enrico

tmcgee commented 10 years ago

Hi Enrico,

The config and controller are in midst of some upheaval right now (in a good way!). I recently contributed here an updated way to load operational layers to support more map types and @gobsmack is working on the configuration and loading of basemaps. I'm sure there will be more changes to both in the very near term. As that progresses, I'll re-look at the @swingley AGOL fork to see how that fits in.

For reference to all: the previous issue that Enrico is referring to is #22

gobsmack commented 10 years ago

A dedicated ago webmap viewer would probably be good as a separate project. And, that's almost what @swingley did by having two separate controllers.

That being said, I'd really like to leverage the webmap specification in the viewer. I'd like to start with optionally accepting a webmapID, download the webmap json, and then parse out the basemap, operational layers, and bookmarks. Then, we mxin that config with our config, and pass it to the controller.

I've gotten really close to this. But, one thing that's tripped me up is that the webmap spec does not include a layer type, such as "tiled", "dynamic", or "image". So, I don't know what type of layer to add. Help?

DavidSpriggs commented 10 years ago

Sorry that I have not commented sooner. I decided early on in this project not to support web maps because I wanted to provide something that is not dependant on AGOL. With the config you can do everything (pop up definitions) that you can do on AGOL and more.

To support AGOL web maps this will take some significant refactoring as some widgets are dependant on layers before they can be created, etc. I am not opposed to creating a second controller for this but I do not have time to pursue it. I would leave it to the community to propose and build it.

tmcgee commented 10 years ago

@DavidSpriggs I agree with the focus and staying away from dependence on AGOL. there's a little too much of that going around... ;)

ebonan commented 10 years ago

Thank you all for the answers! I udenrsand the complexity of the request and and the dependancies on other widgets. We use either mapservices and webmaps but in many circustancies the use of AGOS webmap is essential for us because we already have webapplication based on that type of layer with custom symbology, configured popups etc... We will continue to hope and look at future deveklopments!