Skip to main content

Print output includes layers not visible in viewer

Comments

19 comments

  • Kevin Penner

    Hi Justin,

    Thanks very much for the clear reproduction steps and sample site. I was able to spot the problem very quickly due to details.

    I have filed this issue under GVH-7040 here and I will see that this gets into the next maintenance release.

    Sorry for any inconveniences this has caused you.

    -Kevin

    0
  • Permanently deleted user

    Good to hear! 

    0
  • Permanently deleted user

    +1

    The print doesn't have the same behaviour as Silverlight. For us, the print will always show the first layer. 

    For the print request, we're getting:

    https://myserver/Geocortex/Essentials/4.2.1/REST/sites/ValtusTest/printtemplates/0/print?f=json&scale=10795657.24826074&bboxSR=4326&bbox=[...]&layers=3(show:0,1,2,3,4);4(show:0,2)

    Instead of : 

    https://myserver/Geocortex/Essentials/4.2.1/REST/sites/ValtusTest/printtemplates/0/print?f=json&scale=10795657.24826074&bboxSR=4326&bbox=[...]&layers=3(show:0,1,2,3,4);4(show:2)

     

    <MapService ConnectionString="url=https://myserver/ValtusWMSProxy;version=1.1.1" DefaultAllowSymbolization="true" DisplayName="Valtus Imagery Services - VIEWS(TM)" Function="Operational" ID="4" ImpersonateWithActor="false" IncludeInLayerList="true" InstantSearch="false" IsExpanded="true" Opacity="1" OverrideTemporalSettings="false" PasswordEncrypted="false" ProviderInvariantName="Geocortex.Gis.Services.Wms" SearchNonTextFields="false" SupportedImageHeight="0" SupportedImageWidth="0" UseHttpAuthentication="false" Visible="true">

     

            <CachedServiceData />

     

            <Layers>

     

              <GroupLayer DisplayName="Valtus - VIEWS" IncludeInLayerList="false" IsCatalogLayer="false" IsExpanded="false" Name="Valtus - VIEWS" Visible="false">

     

                <SubLayers>

     

                  <Layer CanCopyFeature="true" DisplayName="VIEWS_CA_AB" Identifiable="false" IncludeInLayerList="true" IncludeInLegend="true" IsCatalogLayer="false" IsExpanded="true" Name="VIEWS_CA_AB" NativeID="VIEWS_CA_AB" Queryable="true" Searchable="false" ShowFeatureHyperlinks="ShowAll" ShowLabels="true" ShowMapTips="false" Snappable="true" SnappingEnabled="false" UnconfiguredFieldsCanSymbolizeClassBreaks="true" UnconfiguredFieldsCanSymbolizeUniqueValue="true" UnconfiguredFieldsSearchable="true" UnconfiguredFieldsVisible="true" UnconfiguredRelationshipsVisible="true" Visible="false" />

     

                  <Layer CanCopyFeature="true" DisplayName="VIEWS_MDA" Identifiable="false" IncludeInLayerList="true" IncludeInLegend="true" IsCatalogLayer="false" IsExpanded="true" Name="VIEWS_MDA" NativeID="VIEWS_MDA" Queryable="true" Searchable="false" ShowFeatureHyperlinks="ShowAll" ShowLabels="true" ShowMapTips="false" Snappable="true" SnappingEnabled="false" UnconfiguredFieldsCanSymbolizeClassBreaks="true" UnconfiguredFieldsCanSymbolizeUniqueValue="true" UnconfiguredFieldsSearchable="true" UnconfiguredFieldsVisible="true" UnconfiguredRelationshipsVisible="true" Visible="false" />

     

                  <Layer CanCopyFeature="true" DisplayName="VIEWS" Identifiable="false" IncludeInLayerList="true" IncludeInLegend="true" IsCatalogLayer="false" IsExpanded="true" Name="VIEWS" NativeID="VIEWS" Queryable="true" Searchable="false" ShowFeatureHyperlinks="ShowAll" ShowLabels="true" ShowMapTips="false" Snappable="true" SnappingEnabled="false" UnconfiguredFieldsCanSymbolizeClassBreaks="true" UnconfiguredFieldsCanSymbolizeUniqueValue="true" UnconfiguredFieldsSearchable="true" UnconfiguredFieldsVisible="true" UnconfiguredRelationshipsVisible="true" Visible="false" />

     

                  <Layer CanCopyFeature="true" DisplayName="VIEWS_2" Identifiable="false" IncludeInLayerList="true" IncludeInLegend="true" IsCatalogLayer="false" IsExpanded="true" Name="VIEWS_2" NativeID="VIEWS_2" Queryable="true" Searchable="false" ShowFeatureHyperlinks="ShowAll" ShowLabels="true" ShowMapTips="false" Snappable="true" SnappingEnabled="false" UnconfiguredFieldsCanSymbolizeClassBreaks="true" UnconfiguredFieldsCanSymbolizeUniqueValue="true" UnconfiguredFieldsSearchable="true" UnconfiguredFieldsVisible="true" UnconfiguredRelationshipsVisible="true" Visible="false" />

     

                </SubLayers>

     

              </GroupLayer>

     

            </Layers>

     

          </MapService>

     

     

     

     

    0
  • Kevin Penner

    Hi Vincent,

    What version of the viewer are you using? I noticed that the 4(show:0,2) notation is not used anymore as of GVH 2.4.

    Thanks,

    Kevin

    0
  • Permanently deleted user

    Oh, we are one version below (2.3.0). I will try in 2.4. Does this bug have been resolved in GVH 2.4?

    Thanks a lot!

    Vincent

     

    0
  • Kevin Penner

    Latitude overhauled the printing process for version 2.4. The new format is on par with how Silverlight performs prints. Many old issue were resolved due to the new format.

    Try to use 2.4.1 if possible. 2.4 was the initial rollout and even more issues were resolved in 2.4.1.

    Thanks,

    Kevin

    0
  • Justin Kraemer

    Vincent: I just want to clarify my bug noted above is not resolved in 2.4.1, because that's the version in which I'm experiencing it.

    0
  • Permanently deleted user
    Is 7040 scheduled to be fixed yet?  I'm on 2.5 and it is still a problem, and the release notes for 2.5.1 don't mention it.
    0
  • Permanently deleted user
    Hello Stephanie!  This is set to be released next week, as part of GVH 2.5.2.

     

     
    0
  • Permanently deleted user
    great, thanks!  :)
    0
  • Permanently deleted user
    I just upgraded to 2.5.2 on the dev server and I am still seeing this problem.  The release notes show GE-7040 as fixed but it only mentions printing cluster and heat map layers, so I am not sure if that is the same bug as GVH-7040?
    0
  • Permanently deleted user
    Oh, it is mentioned in the GVH release notes (I was looking at GE release notes).  Nonetheless it still isn't fixed for me.  I don't have a public facing site with this, unfortunately.  Is anyone else in the same boat?
    0
  • Permanently deleted user
    It's just our reports that are the problem, regular prints are fine.
    0
  • Kevin Penner
    Hi Stephanie, 

     

    Is this affecting the parcel report that is on VicMap?

     

    -Kevin
    0
  • Permanently deleted user
    Yes.  It is the same workflow on the dev server and all the layers are turned on in the printed reports.
    0
  • Kevin Penner

    Hi Stephanie,

     

    Can you run the report on dev while using fiddler on the client? Send over a fidller capture of the 'export' (http://vicmap.victoria.ca/Geocortex/Essentials/REST/sites/Victoria_Public/map/export) request which is exactly the 5th request after the workflow starts. This contains all information used to export the image for the report and we can learn a lot from it.

     

    Thanks,

     

    Kevin
    0
  • Permanently deleted user
    I finally figured this out.  VicMap contains mostly grouped layers.  For example, all of our Water utility layers are in a "Water" group, and the majority of the child layers are turned on so that the user just has to turn on "Water" and all water layers (mains, manholes, laterals, hydrants, fittings, valves, etc.) turn on.  This worked great until a few versions ago.  Now all of the child layers that are on, but not visible on the map because the parent layers are off, are showing up on our reports.

     

    The only workaround I have found so far is to turn off all the child layers in Essentials, but that makes the map really annoying to use, because now the user has to expand the parent and turn on all the children, which is a time consuming, not to mention confusing, change.  Ugh.  We also have child layers that are not visible in the layer list, so there's no workaround for those.
    0
  • Permanently deleted user
    Is it possible to choose which map service is shown in the printed report?  If I can change it to my aerial photo map instead, that would work.  I don't see how to make that change in report designer, all it says is "FeatureMapImage" for the data field, and there's nothing in the script about the map image.
    0
  • Permanently deleted user
    For anyone still reading... I changed the map service shown by changing the mapRestEndpoint that the report uses from the Geocortex export map rest endpoint to the ArcGIS Server export map rest endpoint.  (In the properties of my workflow in Essentials Manager).

     

    (e.g.

     

    http://servername/Geocortex/Essentials/REST/sites/SiteName/map/export

     

    http://servername/arcgis/rest/services/AerialsMapServiceName/MapServer/export)

     

    It doesn't look fantastic because the aspect ratio is off and I don't know where to change that, and the parcel is not highlighted anymore.  But at least it is a clean map image of the ortho instead of a complete mess.  I would still like to figure out how to make it work as it did before the upgrade if anyone has any thoughts.
    0

Please sign in to leave a comment.