-
-
Notifications
You must be signed in to change notification settings - Fork 278
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
Problem Displaying Labels #41
Comments
Can you send the url to the map services you are trying to use (the ones with labels)? Are you trying to use a label layer or are the labels in the map service? |
The labels are included in the map service. Here is a sample of a map service: http://cookviewer2.cookcountyil.gov/webadapter/rest/services/enviroSrvc/MapServer/2 |
They are working fine for me. You need to add the whole map service like so: |
Alright, I think I almost have it figured out. I had the map service in the operational layers broken up by each individual layer (with the layer number on the end and the operational layer type set to "feature"). Adding the map service without the layer number essentially added the layers as a group (and they are now labeled on the map). How can I do this and still be able to control each map service layer individually - for instance controlling the data that displays in the pop up window. |
I am working on an identify widget that will do this. Should be out soon. |
@gregoryaroberts1 I added the identify functionality. |
Hello All,
I am fairly new to this project but from the short time I have spent with it, this has been very helpful and easy to use.. thank you for all of your work David!
I have several map service layers that I have included in the operational layers in config.js. These layers included labels when they were published, however those labels aren't showing up when they are viewed in the ConfigurableViewerJSAPI map. I haven't been able to figure out how to get these labels to show up on the map.
Thanks in advance for any help!
Gregory Roberts
The text was updated successfully, but these errors were encountered: