arcgis online layer did not draw completely

RoyMol1 · ‎04-03-2018

Hi, I am a bit new to ArcGIS online.

Most stuff is pretty straightforward for an experienced GIS specialist but I have an issue that I can't seem to resolve...

I have created a point featureclass in a gdb, including domains, using ArcGIS Pro.

Shared this as a Web Layer and in ArcGIS online and I receive the message "arcgis online layer did not draw completely".

This would be explainable when the featureclass would contain a lot of points but there is only one point feature in the weblayer.

The layer shows up in a webscene and in the collector app but not in the map viewer.

What did I do wrong?

Anonymous User · ‎08-13-2018

It's only for hosted services.

MTorres · ‎08-16-2018

Thank you Katie. I have only partially fixed the problem. I added more points to my empty feature class, recalculated the index for my server hosted layers within ArcCatalog, then republished my service. I chose recalculate because I'm using SQL servers. This fixed the orange triangle/drawing issue. However, when I initially add my recalculated layer to the web map, it does something odd. The web map automatically zooms to the extent of the two features (about 1:3000). My other "healthy" layers have never done this. What are your thoughts on this odd behavior? Thank you for your time.

MTorres · ‎10-11-2018

bump

Anonymous User · ‎10-11-2018

If you are experiencing a similar issue non-hosted services please open a case with Support so they can investigate.

Anonymous User · ‎05-21-2018

Hi Katie,

I'm experiencing a similar issue. A point feature layer won't draw on an AGOL web map and I get the orange triangle. The layer has more than one point (just over 500) and I tried rebuilding the indexes. Rebuilding indexes got rid of the orange triangle but the layer still won't draw. I've built several similar web maps with no such errors. Any help would be appreciated.

Update: Had the same problem with a different point feature layer. Both of the problem layers came from z-enabled feature classes, but z data was disabled using "Feature to Feature" tool prior to adding to the map document that is published as a feature service. Not sure if this is relevant, since analyzing the service before publishing didn't give the error for containing m or z data, but it's something that these two problem layers share in common.

Update-Resolution: It appears the problem was in one of the data fields. The points in the feature class were collected in the field with a GPS receiver and there were some errors in the GPS metadata. The field in question was PDOP, which is always a positive number. For some reason, the GPS collected a negative exponent (-1.797693e+308) PDOP which while not useful as data, did not flag as an error in the data field (double). The issue arose when trying to upload to AGOL because the Azure SQL databases that store the online data convert double fields into numeric fields which have a higher minimum value than doubles. So the values in my data field were incompatible and AGOL simply rejected the feature class entirely. PDOP is not a spatial reference so it's still kind of frustrating that it would prevent drawing instead of just nulling or flagging the problem data field, but at least we know the problem. Changing the error PDOP values to "1" remedied the drawing issue.

RykerRobinson · ‎03-04-2022

I tried rebuilding and it didn’t work, while it no longer displays an error message the item still doesn’t show up on the map only the attribute table also it’s been 4 years how has this problem not been fixed

CarolBaker · ‎05-17-2018

I too get the dreaded orange triangle saying layer did not draw completely, in fact, it did not draw at all. Went to rebuild the spatial index but the rebuild spatial index button is greyed out for my feature layer, HELP!!!!

Anonymous User · ‎05-17-2018

is this a hosted feature layer with only one point? There can be more explanations for the warning than just a need to rebuild spatial indexes.

CarolBaker · ‎05-17-2018

Katie,

There are 2653 points, I’m trying to create Collector app for Catchbasins, was able to do the same for Outfalls in March without this problem……

But, just rebuilt the mxd in ArcMap, publishing the service several times as I added info and features, including my related inspection table, and it worked this time…. Go figure?

Thanks for your quick response, this is my first time posting on GeoNet and I will do it again!

Carol

Carol P. Baker

GIS Administrator

Town of South Kingstown

180 High Street

Wakefield, RI 02879

401 789-9331 x1249

cbaker@southkingstownri.com

gis.southkingstownri.com/webgis

CarolBaker · ‎05-17-2018

Spoke to soon.

Fine tuned by mxd, updating symbology, adding one field to the related inspection table, turned off some fields in the catchbasin feature class.

Shared as a map service, and got the same error again in AGO, ARGGHHHHHHH…..

The original simpler one is still working though…….

This is a simple Collector app, one FC, catchbasins, one empty related table for inspections. I don’t have AGS, served up directly in AGOL