I am trying to upload a layer as part of some analysis in the UK. It is a very large file because it has dissolved polygons of roads and track sin England, to give you an idea of the size.
When I upload the file it should look like the red layer in the picture below but instead it looks like the blue triangles, like it has been simplified.
I have tried uploading as a zip through the browser and also as a web service for Arc Pro.
Is this a Feature Service? These services will simplify the geometries on the fly for viewing at great scales. Maybe the dataset is so big that it takes a while to completely load. If waiting doesn't solve it, try using the corresponding Map Image Layer.
Hi Johannes,
Yes it is a feature service created from a shapefile. I have left the layer to load and it either takes a seriously long time (hours) or it doesn't load. Sorry, I am a bit of a novice, where would I find the Map Image Layer?
TIA
It should be in your content. I don't know about AGOL, but this is how it looks in Portal:
Each service you publish is automatically published as Map Image Layer, optionally you can also publish a Feature Service.
I think it must be different in AGOL because it looks like this...
Thanks
Rosie
Ah. Hosted layers—ArcGIS Online Help | Documentation doesn't list MapImage layers as type of hostable layer. Seems like you can't use them in AGOL, only in Portal.
I'm sorry, I can't really help you here. Only tip I have is to host only a small set of features. If these get displayed correctly, the problem is probably the amount/complexity of the data. If they also have display errors, it could be a problem with your geometries, which might be resolved with the Repair Geometry tool.
Hi Rosie, I know it's been a year since you posted this, but just in case anyone else has this problem, the issue for me seemed to be the Optimize Layer Drawing functionality (in the feature layer settings). This gets turned on automatically once any feature in your layer hits 500,000 vertices. It also increases the size of the layer, though it does improve performance.
Other stuff I tried:
-Disabling z-values
-Checking and repairing geometry (OGC method, which found a handful of "non-simple" shapes)
Repairing the geometry was probably good to do anyway, but it didn't seem to resolve the problem. I'm dealing with river shapes, so they're fairly complex, and I'll maybe see where simplifying the shapes gets me in terms of reducing the layer size, but for now, disabling the Optimize Layer Drawing functionality fixed the issue.
Nicole, thanks for posting this update! That solved this issue for me.