Zum Hauptinhalt gehen

Site Inheritance Issues

Permanently deleted user

We have a very complex site inheritance set up here, in which we herite most of everything but then remove it in the child site and reimport it so show more attribute fields than we are inheriting.  We have noticed that if we have a inherited layers and we turn on a base ortho layer our operational cadastral layer turns off.  Both of those happen to be inherited.  If we turn on the non inherited layers and turn on the ortho they can be on at the same time.  But none of the inherited layers seem to be able to be on at the same time.

 

All this happens in the HTML5 Viewer 1.3. 

 

Any thoughts?

 

 

0

Kommentare

7 Kommentare

Datum Stimmen
  • Tom Neer

    Check for layer ID conflicts in your Site.xml

    0
  • Permanently deleted user

    I have also experienced issues with the site inhertance causing more headache than convenience. This would be with layer re-ordering.

    I have a "child" site where I've added an inherited "parent" site.

    The parent site has a cached basemap and this basemap refuses to stay at the bottom of the layer order in the child site. I have taken no layers/map services of the parent out of the child site. The child site refuses to be reordered, regardless of what order is saved in essential manager. It will look fine for one moment in the essential preview, then refresh or launch viewer and next moment it will revert. I don't see how you can check the layer ID conflicts in the Site.xml when this is done in the merge process that is difficult to decipher what is going in terms of layer orders.

    Is there enough cause to think this is a bug?

    Versions:

    Essesntials - v3.15.1

    HTML5 Viewer - 1.3.1 

    0
  • Permanently deleted user

    I was able to solve my issue after seeing that not all of the map services are accounted for in the <MapServices MergeMode="Layout">.

    Let's say you have 9 map services in a site, including the inherited map services. There will only be 4 that are explicitly ordered in the <MapServices MergeMode="Layout">. You have to add the extra 5 map services as custom code in the Site.xml, being mindful of which map service has which layer ID in the geocortex rest url.

    Here is a small example of the xml where you see what comes in by default. You would have to add to this list of map services, assuming there were more, to create your desired order. Otherwise, the order of the map services will be at the mercy of geocortex. In my case, this consistently placed the basemap half way up the table of contents.

    <MapServices MergeMode="Layout">

     

        <MapService ID="0" ConnectionString="url=http://www3.Original1/mapservice/here" ProviderInvariantName="Geocortex.Gis.Services.ArcGisServer.Rest" />

     

        <MapService ID="REF_CW_TL_BASE-7" ConnectionString="url=http://www3.Reference/mapservice/here" ProviderInvariantName="Geocortex.Gis.Services.ArcGisServer.Rest" />

     

        <MapService ID="REF_CW_County_Aerials-19" ConnectionString="url=http://www3.Reference/mapservice/here" ProviderInvariantName="Geocortex.Gis.Services.ArcGisServer.Rest" />

     

        <MapService ID="REF_CW_TL_BASE-13" ConnectionString="url=http://www3.Original2/mapservice/here" ProviderInvariantName="Geocortex.Gis.Services.ArcGisServer.Rest" />

     

    </MapServices>

    Hope this can help someone else

     

    0
  • Chase Carter

    Benjamin, is this what you were seeing prior to trying your fix?

    https://support.geocortex.com/SupportForums/Thread.aspx?thread=55454&mid=2&pageid=0&ItemID=7

    I thought 4.1 would fix some of the inheritance issues I am seeing but if your code editting works on the situation I'm seeing then I can live with that for now :)

    Chase

    0
  • Permanently deleted user

    Hi Chase,

     

    Yes, this is exactly the behavior that I'm experiencing. So, I guess I was wrong to assume this was limited to the HTML5 viewer. I too was crossing my fingers for a site inheritance fix in 4.1. Bummer.

     

    The code fix is do-able for sure, but when you want to make iterative changes and test, it's that much slower of a process.

     

    Thanks for validating the issue. If you need any clues to where changes have to be made in site.xml, feel free to hit me up <benjamin.harper@multco.us>

     

    -Ben

     

     
    0
  • Chase Carter

    The four that are in you <MapServices MergeMode="Layout"> are all inherited sites correct?  Then you are adding your other mapservices into the MergeMode area and ordering them accordingly?

    So in my case if I have one site inherited I would see this:

        <MapServices MergeMode="Layout">

     

          <MapService ID="13" ConnectionString="url=http://site.inherited /Infrastructure/MapServer" ProviderInvariantName="Geocortex.Gis.Services.ArcGisServer.Rest" />

     

        </MapServices>

    and add my other services like:

        <MapServices MergeMode="Layout">

     

          <MapService ConnectionString="url=http://site.not.inherited /Collars/MapServer" ProviderInvariantName="Geocortex.Gis.Services.ArcGisServer.Rest"

     

          <MapService ID="13" ConnectionString="url=http://site.inherited /Infrastructure/MapServer" ProviderInvariantName="Geocortex.Gis.Services.ArcGisServer.Rest" />

     

        </MapServices>

     

     

     

     

    0
  • Permanently deleted user

    What I did was script the whole layer list ordered how I wanted it to be, including both inherited and non-inherited map services.

    Yes, sounds like you have it.

    So, the <MapServices MergeMode="Layout"> area is telling the viewer(SVL or H5) what things should look like for the end user (client), and this would be a list of all map services used in the site.

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post