Cannot add item to ArcGIS online about koop-socrata HOT 12 CLOSED

This dataset is cached and this endpoint takes 9 seconds to response. http://koop.dc.esri.com/socrata/nola/5fn8-vtui/FeatureServer/0
Something must be unhappy here...

from koop-socrata.

@dmfenton sure, its 460k features that the provider is retrieving, building extents, and then returning. Super inefficient

from koop-socrata.

But the data is already cached...I downloaded this as a csv already.

from koop-socrata.

yes its cached but the socrata providers still talks to the database...

from koop-socrata.

The response time may have nothing to do with it (though I'm not buying that it can't be faster). Here are the two calls make by ArcGIS Online:

• http://dc.mapsqa.arcgis.com/sharing/checkUrl.jsp?url=http%3A//koop.dc.esri.com/socrata/nola/5fn8-vtui/FeatureServer/0%3Ff%3Djson&f=json
• http://koop.dc.esri.com/socrata/nola/5fn8-vtui/FeatureServer/0?f=json&callback=dojo.io.script.jsonp_dojoIoScript1._jsonpCallback

Neither fail so I'm wondering who we can bring in to figure out why AGOL doesn't like the service. @slibby @pholleran thoughts?

from koop-socrata.

@dmfenton Pretty sure the issue is that you can't register a feature service that only consists of tables. ArcGIS Server cannot publish a feature service without a spatial layer (as feature services are a capability of mapservers), so this is an edge case that would only work with Koop. It needs a dummy geography at least.

from koop-socrata.

If the intent is to support a table-from-Koop the same way you support a csv, then there's some more work to do I think.

from koop-socrata.

It can't publish a table service?

from koop-socrata.

ArcGIS Server cannot publish a feature service without a spatial layer (as feature services are a capability of mapservers). You can certainly have tables as part of a service, but not all by their lonesomes. To further clarify, you can't publish a map service with only a table either.

from koop-socrata.

So a table service would have to be part of a map server?

from koop-socrata.

Sorry, not technically. A FeatureServer is a capability of a MapServer and cannot exist alone (unless through Portal/Hosted Data Store) so to get a "table layer at a REST Endpoint" it must be part of a mapserver or a hosted service through Portal

from koop-socrata.

Can be worked-around with pure REST API calls.

from koop-socrata.