Probably a silly question, but what purpose is the map service that is generated with the feature service?
I ask this because the only reason I create a feature service is for editing purposes. When I lock the feature service, it locks the associated map service. If I want to create a publicly viewable map, I can not use the map service associated with the feature service as it is locked. I have to create a separate but similarly named map service:
So now my system resources has three processes taxing it as opposed to just two. What am I missing here?
Solved! Go to Solution.
Hi Venus,
One reason is that Feature service does not display labels, hence we can use the underlying map service in our web apps to display the labels.
Regards,
Richardson
I feel like a lot of people have this same issue and there hasn't been a good solution to this just yet. I am hoping Esri sees the value in this and will make changes to it soon but who knows what will happen. I am also hoping that I am wrong and there is something easily fixed here too!
Hi Venus,
One reason is that Feature service does not display labels, hence we can use the underlying map service in our web apps to display the labels.
Regards,
Richardson
Ah! Good to know!
Thank you!