Zum Hauptinhalt gehen

Kommentare

9 Kommentare

Datum Stimmen
  • Permanently deleted user
    Remember that the dsplay and print engines are different.  Also, note that the print will turn on and off what layers are supposed to be on at the scale that you are printing, not the scale that you are viewing.  So first thing to do is to view at same scale that you are printing.  Do things still look different?
    0
  • Permanently deleted user
    Hi Fatin,

     

     

     

    Why not to try to consume the web services (layers) in question in ArcMap and printing out there so that you can compare between what the screen displays and the printed out paper.

     

     

     

    This is important to find out if it is ArcGIS Desktop\Server or Geocortex issue.

     

     
    0
  • Permanently deleted user
    Hi Mike and Jamal,

     

    A web service like parcel layer was consumed and printed out in ArcMap, then the printed-out paper was compared with the screen display and printed out paper from our portal: Geomolg.ps.

     

    I found that all results are matching except the printed map from our portal.

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000Chtl&feoid=Body&refid=0EM600000001TSv" _/_img_

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000Chtl&feoid=Body&refid=0EM600000001TT0" _/_img_

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000Chtl&feoid=Body&refid=0EM600000001TT5" _/_img_

     

    What do you think?

     

    All the Best,

     

    Fatin
    0
  • Permanently deleted user
    Hi Fatin,

     

    I took a quick look at your application. I chose a building at random and traced its outline with the polygon markup tool. I also drew a line between it and a point on the Communitites layer with snapping turned on to see if it was just the markup that was offset when printing, or whether other feature layers also showed the offset.

     

    I noticed a couple of things when I tried this:

     

    1) The four Orthophoto layers are not quite aligned with one another -- the features in the imagery are slightly offset (a meter or two) from both the feature layers and the markup as you switch between layers.

     

    2) Only the 2016 Orthophoto layer is offset from itself when printing or exporting the map. If you use 2015, 2014, or 2011, the exported image is the same as what you see in the map itself. But, as you've indicated, the 2016 layer is offset by about 4 meters when comparing the viewer map to the exported image. I think that's the problem: for some reason, that 2016 Orthophoto layer is offset when printed or exported.

     

    Based on #2, you may want to look at how the 2016 map service has been published to ArcGIS Server, relative to the other three services.
    0
  • Permanently deleted user
    Hi Jordan,

     

     

     

     

     

    With THE SAME SERVICES consumed in ArcMap, there is no difference between what appears on the screen display and the printed out paper. This issue appears just with these services are consumed in Geocortex.

     

     

     

    Then how can we expect that the issue is with the services? Why the ArcMap manages to match between the display and printing while the geocortex fails?

     

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000Chwz&feoid=Body&refid=0EM600000001TXR" _/_img_

     

    _img_ alt="User-added image" src="https://latitudegeo--c.na53.content.force.com/servlet/rtaImage?eid=90760000000Chwz&feoid=Body&refid=0EM600000001TXW" _/_img_

     

     
    0
  • Permanently deleted user
    The services are here. please, consume them in ArcMap and geocortex and compare between the screen display and the printing

     

     

     

    Orthophoto:

     

     

     

    http://geo.molg.pna.ps:6080/arcgis/rest/services/Orthophoto_WestBank_Aerial_2016_10cm_ITM_jpg_09/MapServer

     

     

     

    parcels

     

    http://geo.molg.pna.ps:6080/arcgis/rest/services/ParcelsRegistered_09/MapServer

     

     
    0
  • Dan Giersz
    There is something weird going on with that orthophoto service.  Besides that fact that you are serving it up as a Map service and not an Image service, the image shifts at certain scales.  Just looking at it using the generic javascript viewer shows the data/image shift for levels 9 and 10.  It looks like those levels actually have a different source than the other layers.
    0
  • Permanently deleted user
    Hi Dan,

     

     

     

    Correct. But my issue here is how the ArcMap manages to match between the screen display and printing while the geocortex fails to do so having the same conditions?!

     

     
    0
  • Permanently deleted user
    Jamal, as Mike said, what you see in the viewer and what the server prints are determined by two different processes, so they will differ to some extent. Essentially, when you print a map via the the viewer, the viewer passes the desired extent, scale, resolution, and the user's choice of print template, and the server generates its own view based on those parameters. The extent of the print template may differ from the viewer's extent; the print resolution may require that cached layers are requested at a different layer of detail; and so forth. ArcMap, on the other hand, is a desktop application that prints exactly what it displays.
    0

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

Sie haben nicht gefunden, wonach Sie suchten?

Neuer Post