Happy Spring everybody. I'm having an issue with polygons disappearing as soon as I finish drawing them. I am tracing features on top of a jpeg I imported of an aerial image. I'm not having a problem drawing line features. The polygons that disappear show up in the attribute table, but with values of zero. I've tried using several different feature class files. Any ideas? Thanks.
-Dan
Solved! Go to Solution.
Kelly, thanks for your help. The problem was that the coordinate systems didn't match. I thought the transformation feature fixed this, but I had to actually match the coordinate systems. Thanks!
Thanks for the feedback. It's possible- how can I check this? I'm not familiar.
Hi Daniel,
Is your data source a hosted feature service? If so, try adding it to a new web map and change the symbology to show location only. This will show all of the data in the service.
If you are storing the data in the web map (map notes, drag and drop files), modify the symbology in the same way in your saved map.
If the data isn't storing, contact technical support or monitor the web traffic using a web debugging tool to see if something is preventing the edits from being submitted.
-Kelly
Kelly, cool map . In this case that will not work. I already have a layer of information and labels that only come on when the data is zoomed. This data set that is hidden from is so many data points it clogs the visibility of the other sets. I don't want the end user to have to know they have to toggle the layer on and off to make this work.
Are you using a hosted feature service or a server service?
Do you only want a specific subset of features to appear when searching? Is there logic in how to filter some of the data out? An option may be to look into the filter configurable app
-Kelly
THis is in the wrong post. I'll move the discussion over to https://community.esri.com/message/679614-is-there-a-way-to-visually-activate-a-data-layer-only-afte...
Kelly, thanks for your help. The problem was that the coordinate systems didn't match. I thought the transformation feature fixed this, but I had to actually match the coordinate systems. Thanks!