Editing Feature Service - Labels drawing under polygons
I'm experiencing a bizarre issue. Tech support has been able to re-create it and has reported it as a bug, which doesn't really help me right now. I have a very simple viewer with one map service and the associated feature service. The map service has the polygons labelled (in this case they are plot ID numbers for cemetery plots). Even when I order the layers in GE with the map service on top of the feature service the labels are drawing under the polygons. This seems like it should be such a simple thing! One suggestion was to create a separate annotation layer but I really don't want to maintain a separate layer. Is anyone else experiencing this? I'm using GE 4.1.2 and GVH 2.3. There has to be a way to make this work...
/customer/servlet/servlet.FileDownload?file=00P6000000elzmBEAQ /customer/servlet/servlet.FileDownload?file=00P6000000em1M2EAI
-
I get this problem. I have 4.3.1 and GVH 2.4.1. Feature services apparently draw on top of map services no matter how I configure the order in manager. I want to use a hosted feature layer from ArcGIS Online in my application but I can't because it draws over everything else including my labels and looks terrible. Any solution?
David
0 -
No solution yet. As a workaround I've made the polygon fill transparent but it looks terrible and is not a good solution. The site won't be launched until I can figure out a better workaround. This is the response I got from tech support:
~~We were able to reproduce this issue here in the same scenario and I have filed it with our development team. It seems as though the feature service always draws on top, which is causing the issue. The odd thing, however, is why this is not happening to other sites. Clients may be finding ways around it, but it definitely looks like a bug or poor functionality that needs to be addressed.
I will keep you informed with updates as I receive them.~~
This was on June 22 and I haven't received an update.
0 -
I just updated to GE 4.4 and GVH 2.5. The same issue is still present. I built a new site from scratch with only the map service (with labels) and the feature service hoping it would work. I had recently tried to create an annotation layer (not ideal, dynamic labels are far better) and placed that on top of all the other map services. The feature service still draws on top, no matter how I order things. Our users can search to locate features but some will want to scan the map using labels as a guide. Maybe someone from Latitude can chime in? This is a fairly significant issue, in my opinion.
0 -
I just changed the display setting to make the feature service have 0 opacity. It looks ok initially, crossing fingers it works!
0 -
GE 4.4.1 and HTML 2.5 - still have same issue.
The workaround Rebecca mentioned sort of works. It makes the label appear, but if polygons are being editing, sometimes there is a bit of a delay in showing the new polygon boundary from the non-feature-service layer.0 -
Has this been resolved at all? I see the same issue for polyline feature service layers as well. We are currently using GVH 2.7 and Essentials Manager 4.6.1. 0 -
The way that I have my cemetery editor set up is very similar to the way you have it set up Rebecca.
I have a Map Service to display the labels and symbology appropriatly. Then I have the same Feature Service for editing. In the Feature Service, there is a 'Functional' tab that I change the 'Query Mode' from 'On Demand' to 'Selection Only'.
This way the feature service doesn't display at all, but will return a result if you identify on the grave. It also decreases load time because the feature service doesn't have to render anything on the map.
That being said, to avoid confusion for the user, I turn off the identify on the map service. The only issue I run into is linking the map service and feature service together (so if you turn one on/off the other turns on/off as well) If I place them in a folder in the layer list, it works, but then you lose the opacity slider...so there's that.
Does that make sense?
?Marshall0 -
Hi Daniel,
This has been identified as a 3rd party issue and is a limitation to the ESRI API. We are waiting to hear from ESRI when this issue is likely to be addressed.
Thanks,
Ali
0
Please sign in to leave a comment.
Comments
8 comments