Enhancement: allow the SGID Index to work with MapServer layers

[eneemann]

We'd like to add two FFSL fire layers to the SGID index, but they use Map Services. Currently the SGID Index assumes Feature Services are used, so the Map Services won't work.

• Fire Origins: https://maps3.wildfiresuite.com/arcgis/rest/services/utwrap/FireAreas/MapServer/0
• Fire Perimeters: https://maps3.wildfiresuite.com/arcgis/rest/services/utwrap/FireAreas/MapServer/1

[steveoh]

We have some mapserver's in the index now that are broken. They aren't showing up in the nag comment either.

My proposal for this would be to add another field to choose the type and use that value to build the url.

[eneemann]

That sounds good to me. Should I go ahead and add the column and start updating the sheet to reflect the proper values?

[steveoh]

Couldn't hurt. @stdavis what do you think?

[stdavis]

I'm good with it. My only thought is I wondered if we could just check the service URL for "mapserver" or "featureserver" to determine the type rather than add a separate field.

[eneemann]

So in that case, would the script check the service URL from the AGOL item? And then decide which service type to use? If so, that would be easier and prevent the need to track it ourselves. But I guess one caveat is that some items seem to be hosted directly from an ArcGIS Server and not registered in AGOL. For example the FFSL Fire Perimeter and Fire Origin layers don't seem to exist in AGOL, but we'd like include them in the index.

[eneemann]

So in that case, would the script check the service URL from the AGOL item? And then decide which service type to use? If so, that would be easier and prevent the need to track it ourselves. But I guess one caveat is that some items seem to be hosted directly from an ArcGIS Server and not registered in AGOL. For example the FFSL Fire Perimeter and Fire Origin layers don't seem to exist in AGOL, but we'd like include them in the index.

Thinking a little more about this, I believe our index currently requires items to be in AGOL and uses the AGOL item ID to build links and info. Mostly this is fine, but like the FFSL fire layers, there may be some layers that we'd want in the index that aren't in AGOL. Would enabling non-AGOL items in the SGID Index be better handled as a separate issue?

[stdavis]

I think that keeping everything in this issue makes sense since map server layers are not supported in AGOL anyways. Forgive me for being slow to respond and uncertain. I haven't taken the time to dive back into the code for the validation script yet.

[eneemann]

Okay, no problem. But there are some cases where Map Services can be hosted through AGOL in some way, I think probably published from a Portal into AGOL. UDOT had several layers, but coincidentally, has republished many of them as Feature Services since July. Here's an old Barriers "map image layer" that they had with a 'MapServer' URL: https://utah.maps.arcgis.com/home/item.html?id=d9fc0a3ce0644988902cc8f1db10421f