My organization manages web applications drawing from standalone ArcGIS Server Map Layers. Often we would like to move those layers into ArcGIS Online as hosted feature layers. However we sometimes find incompatibles in the query API that mean the applications must be changed to make it work.
For this example when a MapServer is queried and the results are empty, we still get back the fields and aliases and good stuff for showing a small table that says "nothing found for these fields".
https://gispub.epa.gov/arcgis/rest/services/OW/ATTAINS_Assessment/MapServer/0/query?f=json&outFields...
However, an ArcGIS Online hosted feature layer when presented with the same exact query, just returns nuthin.
https://services.arcgis.com/cJ9YHowT8TU7DUyn/arcgis/rest/services/ATTAINS_Assessment/FeatureServer/0...
I suppose there is a design question here, is there an intention that MapServer and FeatureServer queries return the same format of results? Or is the current "almost parity" just a coincidence? that will gradually evolve into two unrelated products? Or could hosted feature layers have a compatibility switch to make them match the old MapServer results?
Thanks,
Paul
