Closed NatalieCampos closed 7 years ago
Maritime Boundary and Shipping Fairways, Lanes, and Zones layers point to Feature Service layers that do not exit. This issue transferred over from our production environment.
@NatalieCampos @ACueva The service Military/MaritimeBoundaries/FeatureServer does exist however the web map references layer 28 (Maritime Boundary) and layer 39 (Shipping Fairways, Lanes, and Zones) do not.
Shipping Fairways, Lanes, and Zones is layer 0 Maritime Boundaries is layer 1
Let me see if I can edit the json file for this data in the released set of files.
layer 28 (Maritime Boundary) -> layer 1 layer 39 (Shipping Fairways, Lanes, and Zones) -> layer 0
@NatalieCampos @ACueva On the production portal I edited the webmap json to correct the feature service layer ids and then extracted the item and integrated the item files into the final release. I also edited the webmap json on the test portal to simulate how the corrected item will behavior. Closing this issue.
FYI @jfrygeo I think the service must have been republished with a different layer order.
The following portal item (id=45a50df9d8554cec99d3b4e1101f1624) has a layer that does not load.