Displaying themes based on Zoom levels in base map

I am using Oracle AS MapViewer 10131.I have 3 themes added to a base map.
I am using Oracle Mapbuilder to create Mapping metadata.I want to display the 3rd theme based on the zoom levels.I want to display it only at lower zoom levels.I have followed necessary instructions given in the Mapviwer user guide and mapbuilder help.
But I am not able to display particular theme based on Zoom levels.
For example I have min/max scale 70,000/0 for Streets theme set using mapbuilder.This theme should be displayed only at that scale.But I am getting this theme displayed at all min/max scales (zoom levels).While creating the Map Cache Instance given the min/max scales 1000/25000000, the default values.Here the scale values look contradictory to the theme scale values given in mapbuilder.Is this where I am going wrong? or while setting scale for themes?
I hope you understand my problem.Please help me about this.this is urgent.
Thanks in advance!!

My problem is solved now.I am able to display themes on zoom levels.The solution is, I set the min/max scale (zoom levels) in Map Cache Instance as "Ratio" and in theme i set it to "Screen-Inch".The scale of theme is not understood by the map cache instance.So finally i set both the scales to "Ratio" and it is working fine as i expected.
Anyway thanks for yout interest in helping me.I will surely make a post here if i got stuck in further work.

Similar Messages

  • Hierarchy Viewer: Setting default zoom level and levelFetchSize

    I have couple of questions on Hierarchy Viewer:
    (1) Is it possible to set the zoom level to say 50% by default when the HV is rendered first time. By default the nodes are rendered at 100%, but I would like to render them at 50% by default - and on hover show the 100%. Is this doable ? User can then decide to zoom to 100% if desired.
    (2) Is it possible to change the levelFetchSize based on zoom level ? For example if the zoom level is 100%, levelFetchSize could be 4 but at 50%, it would be increased to 8 (since more real estate is available) ?

    It seems like the DVT by default zooms to fit the available real estate. But is it possible to set a fixed zoom level (say 75%) even if the node does have 100% zoom level. We would like to show the 100% zoom level only on hover to the node. But by default, wanted to to set the viewer to always show 75% or 50% zoom level.

  • Using image as theme on top of base map

    I have a table which contains JPEG image stored as BLOB. I want to display this image as theme on top of my base map. I also want to display point on this theme.
    Is it possible to do this?
    Please provide me useful pointers for achieving this scenario.
    Thanks in advance.

    To setup image themes, besides the BLOB column you need a geometry column to specify the bounds of the image (MBR). Take a look at MapViewer's Users Guide section about Image themes (section 2.3.5).
    About the points, you can setup another theme to render the points.
    Once you have the themes you can add them to your base map, or render them on top of your base map. Notice that in Oracle Maps, currently image themes must be part of the base map, and you can not render it alone on top of the base map.

  • Zoom level in WPF Application consuming Bing Maps Web Services

    Hi,
    I am having trouble in setting the zoom level for the map with 7 pushpins (P1 through P7). The map is centered with point P1. I want all the push pins to show on the map. I have set the zoom level as follows.
    Zoom Level 15 - if the points (P2...P7) are within 1 mile from P1
    Zoom Level 14 - if the points (P2...P7) are between 1.1 and 1.5 miles from P1
    Zoom Level 10 - if the points (P2...P7) are > 1.5 miles from P1.
    If there a better way (like autozoom) to do this?
    Thanks.
    Regards, Venkat

    Rick,
    I have attached the map generated using SOAP services.
    I tried to generate the same map using REST services as follows.
    http://dev.virtualearth.net/REST/v1/Imagery/Map/Road?mapSize=640,480&pp=36.150928,-83.439971;10;S&pp=36.171645820140839,-83.410888686776161;32;S1&pp=36.168693,-83.415779;32;S2&pp=36.185192,-83.435401;32;S3&pp=36.140907,-83.472549;23;L1&pp=36.174339,-83.425415;23;L2&pp=36.17805,-83.433433;23;L3&key=BingKey&format=jpeg
    The REST services map looks like its zoomed in compared to the SOAP services map. However the road/street names are missing. Is there any way to get the road/street names in the REST services map like in the online bing maps? Please advise.
    SOAP SERVICES MAP
    REST SERVICES MAP
    Regards, Venkat

  • CS4 NOT capable of sharp displays at all zoom levels

    I must have been asleep, until now, and missed the significance and importance of what follows.
    In post #11 here:
    http://forums.adobe.com/thread/375478?tstart=30
    on 19 March 2009 Chris Cox (Adobe Photoshop Engineer - his title on the old forums) said this, in a discussion regarding sharpness in CS4:
    "You can't have perfectly sharp images at all zoom levels.". Unfortunately, my experience with CS4 since its release late last year has repeatedly confirmed the correctness of this statement.
    What makes this statement so disturbing is that it contradicts an overwhelming amount of the pre- and post-release promotional advertising of CS4 by Adobe, to the effect that the OpenGL features of CS4 enable it to display sharp images at all zoom levels and magnifications. What is surprising is that this assertion has been picked up and regurgitated in commentary by other, sometimes highly experienced, Ps users (some unconnected with, but also some directly connected with, Adobe). I relied upon these representations when making my decision to purchase the upgrade from CS3 to CS4. In fact, they were my principal reason for upgrading. Without them, I would not have upgraded. Set out in numbered paragraphs 1 to 6 below is a small selection only of this material.  
    1. Watch the video "Photoshop CS4: Buy or Die" by Deke McClelland (inducted into the Photoshop Hall of Fame, according to his bio) on the new features of CS4 in a pre-release commentary to be found here:
    http://fyi.oreilly.com/2008/09/new-dekepod-deke-mcclelland-on.html
    Notice what he says about zooming with Open GL: "every zoom level is a bicubically rendered thing of beauty". That, when viewed with the zooming demonstrated, can only be meant to convey that your image will be "sharp" at all zoom levels. I'm sure he believes it too - Deke is someone who is noted for his outspoken criticism of Photoshop when he believes it to be deserved. It would seem that he must not have experimented and tested to the extent that others posting in this forum have done so.
    2. Here's another Adobe TV video from Deke McClelland:
    http://tv.adobe.com/#vi+f1584v1021
    In this video Deke discusses the "super smooth" and "very smooth" zooming of CS4 at all zoom levels achieved through the use of OpenGL. From the context of his comments about zooming to odd zoom levels like 33.33% and 52.37%, it is beyond doubt that Deke's use of the word "smooth" is intended to convey "sharp". At the conclusion of his discussion on this topic he says that, as a result of CS4's "smooth and accurate" as distinct from "choppy" (quoted words are his) rendering of images at odd zoom levels (example given in this instance was 46.67%), "I can actually soft proof sharpening as it will render for my output device".
    3. In an article by Philip Andrews at photoshopsupport.com entitled 'What's New In Adobe Photoshop CS4 - Photoshop 11 - An overview of all the new features in Adobe Photoshop CS4',
    see: http://www.photoshopsupport.com/photoshop-cs4/what-is-new-in-photoshop-cs4.html
    under the heading 'GPU powered display', this text appears :
    "Smooth Accurate Pan and Zoom functions – Unlike previous versions where certain magnification values produced less than optimal previews on screen, CS4 always presents your image crisply and accurately. Yes, this is irrespective of zoom and rotation settings and available right up to pixel level (3200%)." Now, it would be a brave soul indeed who might try to argue that "crisply and accurately" means anything other than "sharply", and certainly, not even by the wildest stretch of the imagination, could it be taken to mean "slightly blurry but smooth" - to use the further words of Chris Cox also contained in his post #11 mentioned in the initial link at the beginning of this post.
    4. PhotoshopCAFE has several videos on the new features of CS4. One by Chris Smith here:
    http://www.photoshopcafe.com/cs4/vid/CS4Video.htm
    is entitled 'GPU Viewing Options". In it, Chris says, whilst demonstrating zooming an image of a guitar: "as I zoom out or as I zoom in, notice that it looks sharp at any resolution. It used to be in Photoshop we had to be at 25, 50 , 75 (he's wrong about 75) % to get the nice sharp preview but now it shows in every magnification".
    5. Here's another statement about the sharpness of CS4 at odd zoom levels like 33.33%, but inferentially at all zoom levels. It occurs in an Adobe TV video (under the heading 'GPU Accererated Features', starting at 2 min 30 secs into the video) and is made by no less than Bryan O'Neil Hughes, Product Manager on the Photoshop team, found here:
    http://tv.adobe.com/#vi+f1556v1686
    After demonstrating zooming in and out of a bunch of documents on a desk, commenting about the type in the documents which is readily visible, he says : "everything is nice and clean and sharp".
    6. Finally, consider the Ps CS4 pdf Help file itself (both the original released with 11.0 and the revised edition dated 30 March 2009 following upon the release of the 11.0.1 update). Under the heading 'Smoother panning and zooming' on page 5, it has this to say: "Gracefully navigate to any area of an image with smoother panning and zooming. Maintain clarity as you zoom to invididual pixels, and easily edit at the highest magnification with the new Pixel Grid." The use of the word "clarity" can only mean "sharpness" in this context. Additionally, the link towards the top of page 28 of the Help file (topic of Rotate View Tool) takes you to yet another video by Deke McClelland. Remember, this is Adobe itself telling you to watch this video. 5 minutes and 40 seconds into the video he says: "Every single zoom level is fluid and smooth, meaning that Photoshop displays all pixels properly in all views which ensures more accurate still, video and 3D images as well as better painting, text and shapes.". Not much doubt that he is here talking about sharpness.
    So, as you may have concluded, I'm pretty upset about this situation. I have participated in another forum (which raised the lack of sharp rendering by CS4 on several occasions) trying to work with Adobe to overcome what I initially thought may have been only a problem with my aging (but nevertheless, just-complying) system or outdated drivers. But that exercise did not result in any sharpness issue fix, nor was one incorporated in the 11.0.1 update to CS4. And in this forum, I now read that quite a few, perhaps even many, others, with systems whose specifications not only match but well and truly exceed the minimum system requirements for OpenGL compliance with CS4, also continue to experience sharpness problems. It's no surprise, of course, given the admission we now have from Chris Cox. It seems that CS4 is incapable of producing the sharp displays at all zoom levels it was alleged to achieve. Furthermore, it is now abundently clear that, with respect to the issue of sharpness, it is irrelevant whether or not your system meets the advertised minimum OpenGL specifications required for CS4, because the OpenGl features of CS4 simply cannot produce the goods. What makes this state of affairs even more galling is that, unlike CS3 and earlier releases of Photoshop, CS4 with OpenGL activated does not even always produce sharp displays at 12.5, 25, and 50% magnifications (as one example only, see posts #4 and #13 in the initial link at the beginning of this post). It is no answer to say, and it is ridiculous to suggest (as some have done in this forum), that one should turn off OpenGL if one wishes to emulate the sharp display of images formerly available.

    Thanks, Andrew, for bringing this up.  I have seen comments and questions in different forums from several CS4 users who have had doubts about the new OpenGL display functionality and how it affects apparent sharpness at different zoom levels.  I think part of the interest/doubt has been created by the over-the-top hype that has been associated with the feature as you documented very well.
    I have been curious about it myself and honestly I didn't notice it at first but then as I read people's comments I looked a little closer and there is indeed a difference at different zoom levels.  After studying the situation a bit, here are some preliminary conclusions (and I look forward to comments and corrections):
    The "old", non-OpenGL way of display was using nearest-neighbor interpolation.
    I am using observation to come to this conclusion, using comparison of images down-sampled with nearest-neighbor and comparing them to what I see in PS with OpenGL turned off.  They look similar, if not the same.
    The "new", OpenGL way of display is using bilinear interpolation.
    I am using observation as well as some inference: The PS OpenGL preferences have an option to "force" bilinear interpolation because some graphics cards need to be told to force the use of shaders to perform the required interpolation.  This infers that the interpolation is bilinear.
    Nothing is truly "accurate" at less than 100%, regardless of the interpolation used.
    Thomas Knoll, Jeff Schewe, and others have been telling us that for a long time, particularly as a reason for not showing sharpening at less than 100% in ACR (We still want it though ).  It is just the nature of the beast of re-sampling an image from discrete pixels to discrete pixels.
    The "rule of thumb" commonly used for the "old", non-OpenGL display method to use 25%, 50%, etc. for "accurate" display was not really accurate.
    Those zoom percentages just turned out to be less bad than some of the other percentages and provided a way to achieve a sort of standard for comparing things.  Example: "If my output sharpening looks like "this" at 50% then it will look close to "that" in the actual print.
    The "new", OpenGL interpolation is certainly different and arguably better than the old interpolation method.
    This is mainly because the more sophisticated interpolation prevents drop-outs that occurred from the old nearest-neighbor approach (see my grid samples below).  With nearest-neighbor, certain details that fall into "bad" areas of the interpolated image will be eliminated.  With bilinear, those details will still be visible but with less sharpness than other details.  Accuracy with both the nearest-neighbor and bilinear interpolations will vary with zoom percentage and where the detail falls within the image.
    Since the OpenGL interpolation is different, users may need to develop new "rules of thumb" for zoom percentages they prefer when making certain judgements about an image (sharpening, for example).
    Note that anything below 100% is still not "accurate", just as it was not "accurate" before.
    As Andrew pointed out, the hype around the new OpenGL bilinear interpolation went a little overboard in a few cases and has probably led to some incorrect expectations from users.
    The reason that some users seem to notice the sharpness differences with different zooms using OpenGL and some do not (or are not bothered by it) I believe is related to the different ways that users are accustomed to using Photoshop and the resolution/size of their monitors.
    Those people who regularly work with images with fine details (pine tree needles, for example) and/or fine/extreme levels of sharpening are going to see the differences more than people who don't.  To some extent, I see this similar to people who battle with moire: they are going to have this problem more frequently if they regularly shoot screen doors and people in fine-lined shirts.   Resolution of the monitor used may also be a factor.  The size of the monitor in itself is not a factor directly but it may influence how the user uses the zoom and that may in turn have an impact on whether they notice the difference in sharpness or not.  CRT vs LCD may also play a role in noticeability.
    The notion that the new OpenGL/bilinear interpolation is sharp except at integer zoom percentages is incorrect.
    I mention this because I have seen at last one thread implying this and an Adobe employee participated who seemed to back it up.  I do not believe this is correct.  There are some integer zoom percentages that will appear less sharp than others.  It doesn't have anything to do with integers - it has to do with the interaction of the interpolation, the size of the detail, and how that detail falls into the new, interpolated pixel grid.
    Overall conclusion:
    The bilinear interpolation used in the new OpenGL display is better than the old, non-OpenGL nearest-neighbor method but it is not perfect.  I suspect actually, that there is no "perfect" way of "accurately" producing discrete pixels at less than 100%.  It is just a matter of using more sophisticated interpolation techniques as computer processing power allows and adapting higher-resolution displays as that technology allows.  When I think about it, that appears to be just what Adobe is doing.
    Some sample comparisons:
    I am attaching some sample comparisons of nearest-neighbor and bilinear interpolation.  One is of a simple grid made up of 1 pixel wide lines.  The other is of an image of a squirrel.  You might find them interesting.  In particular, check out the following:
    Make sure you are viewing the Jpegs at 100%, otherwise you are applying interpolation onto interpolation.
    Notice how in the grid, a 50% down-sample using nearest-neighbor produces no grid at all!
    Notice how the 66.67% drops out some lines altogether in the nearest-neighbor version and these same lines appear less sharp than others in the bilinear version.
    Notice how nearest-neighbor favors sharp edges.  It isn't accurate but it's sharp.
    On the squirrel image, note how the image is generally more consistent between zooms for the bilinear versions.  There are differences in sharpness though at different zoom percentages for bilinear, though.  I just didn't include enough samples to show that clearly here.  You can see this yourself by comparing results of zooms a few percentages apart.
    Well, I hope that was somewhat helpful.  Comments and corrections are welcomed.

  • REQ: Add 'Fit-width' or 'Fit-visible' view mode, in which the zoom level is automatically set based on the width of the _current_ page.

    Currently, the default zoom level when viewing a page of a PDF file is automatically calculated based on the width of the "widest" page of the document. This means that, if the document contains one page that is wider than the others or is in landscape orientation, then the default zoom, when viewing all the other narrower pages, is set in a way so that the page does not use the full width of the screen. This results in very poor experience, because the zoom level and the visible area of the page have to be constantly adjusted for each page. The latest update (at the time of writing) has added some extra view modes, but not the much needed 'Fit width' or 'Fit visible'.
    Personally, I can find no reason valid enough to justify the lack of such a view mode. Automatically setting the zoom level based on the width of the current page so as to take advantage of the full width of the screen should be a must have feature for mobile devices, if not the default behavior. The current default behavior regarding the zoom level is pretty much useless, even on 8"/10" screens. There should be a view mode in which the full width of the screen is always used to display the document.
    Examples of documents for which the Adobe Reader for Android provides a poor reading experience are:
    documents which contain some of their pages in landscape orientation.
    publications which, apart from the main content, also contain the full front and back cover in a single page (usually first page which is much wider than the content pages) or any other extra pages like cards or application forms (that are meant to be printed) which usually use an A4/Letter page size etc.
    documents which have been cropped by external utilities or scripts so as to eliminate unneeded white margins (in some cases not all pages have the same width).
    Please consider fixing the default behavior in future releases of the Reader for Android or add a 'Fit width' or 'Fit visible' view mode.
    Thank you in advance.
    Message was edited by: George Notaras
    Improved descriptions of example documents.

    To add to this, if you prefer you can separate your JavaScript from your JSF pages.
    Add a folder (I named mine 'js') to your application's ViewController project's public_html folder.
    Via JDeveloper, create a new JavaScript file inside your newly created folder and place your JavaScript functions inside it.
    You can then 'load' the .js file using the method Shantala described, with the addition of an added 'source' property to the af:reference tag.
    (This can also be a URI reference to a JavaScript file hosted on a web server)
    <f:facet name="metaContainer">
      <af:resource source="/js/myJsFile.js" type="javascript"/>
    </f:facet>The benefits of this 'split' are cleaner JSF page source and also code-highlighting and formatting within the .js file making finding and fixing bugs in your JavaScript much easier.
    It appears however, that when using <af:resource> to load scripts, once the page has been submitted even once, the JavaScript is no longer available to the page. Which isn't very useful.
    A solution is to use <trh:script>.
    Add xmlns:trh="http://myfaces.apache.org/trinidad/html" to your <jsp:root> tag and install the library.
    then in place of the above code use:
    <f:facet name="metaContainer">
      <trh:script id="script1" source="/js/myJsFile.js"/>
    </f:facet>Now after a page submit the JavaScript still functions.
    Edited by: Matthew Carrigy on 12/08/2009 10:39

  • Displaying report in PDF with Zoom level at 100%

    Hi,
    I am using ReportDocument.ExportToHttpResponse() to export the desired reports to the PDF format. The report is being displayed on the screen immediately. I want to show the report at 100% zoom level every time the user export the report. My existing code segment for this purpose as follows:
                    ExportOptions exportOpts = new ExportOptions();
                    PdfFormatOptions pdfOpts = ExportOptions.CreatePdfFormatOptions();
                    pdfOpts.UsePageRange = true;
                    pdfOpts.FirstPageNumber = 2;
                    pdfOpts.LastPageNumber = Int32.MaxValue;
                    exportOpts.ExportFormatType = ExportFormatType.PortableDocFormat;
                    exportOpts.ExportFormatOptions = pdfOpts;
                    rptDoc.ExportToHttpResponse(exportOpts, Response, false, "");
    tried to find out any related setting in PdfFormatOptions object but to no avail. Please suggest any possible option to force the viewer to open the report at 100%.
    Regards,
    Ali
    Edited by: ali.net on Jan 11, 2012 2:17 PM

    Hi Ali,
    Please refer to the 'Rules of Engagement' alwas provide enough information.
    - Version of Crystal Reports with detail patch level.
    - Version of Visual Studio
    - Do you see the same behaviour when the report is exported from CR viewer export button?
    - Try using [ExportToStream|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_bi/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes%7B6163636573733d36393736354636443646363436353344333933393338323636393736354637333631373036453646373436353733354636453735364436323635373233443330333033303331333133393338333533383337%7D.do]
    rd.ExportToDisk(ExportFormatType.PortableDocFormat, "C:
    ep1.pdf");
    See if it reproduces the issue.
    - Bhushan.

  • Google maps don't display right, part is good but about half of it says "we are sorry, but we don't have maps at this zoom level for this region." Zooming out doesn't help.

    When displaying a Google map I get about four vertical strips that alternately display good and in gray bands. The gray area displays the message "we are sorry, but we don't have maps at this zoom level for this region." Zooming out doesn't get rid of the gray areas.
    I've had this problem for over a year and get around it by using either MS Internet Explorer or Google Chrome which work Ok. Otherwise Firefox works fine and I use it for everything else except Google Maps.
    I've tried an uninstall of FireFox and then reinstall but it didn't help. I don't remember what I was doing when this problem first showed up.

    You're welcome

  • Acrobat Pro X stamps, comments do not display at certain zoom level

    A user found a bug in Adobe Pro 10.1.6.
    We have both Adobe Reader and Pro installed on Server 2008.
    A document stamped with dynamic signature: "APPROVED" do not show in Adobe Pro when opening.
    If the zoom level is being change then the stamp do show.
    Same document show the dynamic stamps in Adobe Reader.
    I reported the bug through this form https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
    Is there a workaround until a fix is comitted ?

    > Well, "Default" is what's in the maker.ini file as it exists "out of the box".
    That's to be expected, as up until the program is run for the first time, there's no opportunity at all for it to discover the screen size. I suppose Adobe could ask during the install, but not only is that annoying (and would complicate blind installs), the answer might be impossible to know (running FM in a VM window rather than on a real display, or historically, in an X-window on Unix).
    Even after FM is running, and even if using EDID API calls, I doubt FM is making such calls. When FM was first written, it was impossible for an ap to discover screen size. Up until VESA DDC2 in 1996, monitors were rarely capable of reporting anything to the attached computer. Had FM implemented DDC calls, it would have needed to add DDC/CI, then E-DDC, then several generations of EDID calls. And APIs for any of these would have been different for Unix, Mac and Windows, plus normal Windows churn.
    Most users don't care. Those that do have traditionally made inquiries and discovered the maker.ini entry for this.
    I might add that FM apparently can detect the aspect ratio of the screen (4:3, 16:9, 16:10), because it must know the raster extents in order to paint the windows and place the dialogs (it just doesn't know what inches or mm that corresponds to). This, I presume, is why it doesn't need to encode the A/R in maker.ini.

  • Displaying default styles in an advanced style as theme based foi

    Hi,
    I have a problem to display the default style of an advanced style as theme based foi.
    According to the mapviewer log x feature were found to display but no one was rendered into the map.
    MapViewer with image layer works, MapBuilder, too.
    MapViewer version:
    Ver1033p5_B081010
    MapBuilder marker definition:
    <?xml version="1.0" ?>
    <AdvancedStyle>
    <BucketStyle>
    <Buckets default_style="C.ORANGE">
    <CollectionBucket seq="0" type="string" style="C.BLUE">90002,19208</CollectionBucket>
    <CollectionBucket seq="1" type="string" style="C.RED">14002,13004</CollectionBucket>
    </Buckets>
    </BucketStyle>
    </AdvancedStyle>
    The mapviewer log indicates 7 found featuers, but only 2 of them are displayed. The 5 items are using the default style and are not visible.
    LOG
    May 28, 2009 3:46:26 PM oracle.sdovis.LoadThemeData run
    FINER: LoadThemeData running thread: Thread-6894
    May 28, 2009 3:46:26 PM oracle.sdovis.theme.PredGeomThemeProducer loadFeaturesInWindow
    FINER: [Master scale] 46.091784655389 [Theme scale factor] 1.0
    May 28, 2009 3:46:26 PM oracle.sdovis.theme.PredGeomThemeProducer loadFeaturesInWindow
    FINEST: [ TEST_FOI_POI_2 ]: 2xxx973.7866666666,5xxx599.714666666,2xxx466.072533333,5xxx968.929066666
    May 28, 2009 3:46:26 PM oracle.sdovis.theme.PredGeomThemeProducer loadFeaturesInWindow
    FINEST: Theme query [ TEST_FOI_POI_2 ]: SELECT ID, GEOM, 'M.TEST_IMAGE2', null, 'null', -1, 'rule#0', ID, BEMERKUNG FROM FOI_TEST_POI WHERE MDSYS.SDO_FILTER(GEOM, MDSYS.SDO_GEOMETRY(2003, 31466, NULL, MDSYS.SDO_ELEM_INFO_ARRAY(1, 1003, 3), MDSYS.SDO_ORDINATE_ARRAY(:mvqboxxl, :mvqboxyl, :mvqboxxh, :mvqboxyh)), 'querytype=WINDOW') = 'TRUE'
    May 28, 2009 3:46:26 PM oracle.sdovis.theme.PredGeomThemeProducer loadFeaturesInWindow
    FINER: [ TEST_FOI_POI_2 ] Fetch size: 100
    May 28, 2009 3:46:26 PM oracle.sdovis.theme.PredGeomThemeProducer loadFeaturesInWindow
    INFO: [ TEST_FOI_POI_2 ] sql exec time: 0ms, total time loading 7 features: 31ms.
    May 28, 2009 3:46:26 PM oracle.lbs.mapserver.core.MapperPool freeMapper
    FINER: freeMapper() begins...
    May 28, 2009 3:46:26 PM oracle.lbs.foi.ThemeRenderingThread render
    FINER: 7 features loaded.31
    May 28, 2009 3:46:26 PM oracle.lbs.foi.ThemeRenderingThread render
    FINER: Total time rendering foi data:0
    May 28, 2009 3:46:26 PM oracle.lbs.foi.FOIServlet doPost
    FINEST: ---- begin FOI response ----
    {"foiarray":[{"id":"201","gtype":"2001","imgurl":"http://server02/mapviewer/images/foi/23_p_Sj_28_24.png","x":2xxx200,"y":5xxx800,"width":28,"height":24,"attrs":["201",]},{"id":"200","gtype":"2001","imgurl":"http://server02/mapviewer/images/foi/23_p_Sj_28_24.png","x":2xxx200,"y":5xxx866,"width":28,"height":24,"attrs":["200",]}],attrnames:["Bezeichnung","BEMERKUNG"],themeMBR:[1.0,0.0,0.0,2xxx422.22678222],hiliteImgPref:"Sh",hiliteMW:10,hiliteMH:10,isWholeImg:false}
    ---- end FOI response ----
    May 28, 2009 3:46:26 PM oracle.lbs.foi.FOIServlet sendGZippedResponse
    FINEST: Sending FOI response in gzip format.
    Regards,
    Cord

    Hi Joao,
    thanks!
    Do you know a workaround or alternative for that problem?
    I have a request of our customer. He has about 400 different group items. Only a few of them (40-60) should be defined with an individual style and the rest with a default style.
    The problem is, that the number of group items rises nearly daily. The new ones should automatically be displayed with the default style.
    Cord

  • Displaying a theme-based FOI layer as a whole image with javascript API v2

    Hi,
    I have looked the Oracle maps V2 tutorial developed in mvdemo.war application provided with Oracle Mapviewer v11.1.1.7. I have looked how to use theme-based FOI layers and I have not found how to set the "whole image" property for these layers. This feature is present in javascript API V1 and it greatly improves application performance. Our applications use this property very often.
    Is this property present in javascript API V2 but not documented?
    If it's not present, do you know if it will be?
    How can we show a layer with many geometry features and obtain the same performance we have now with the whole image property?
    Thanks,
    Arturo

    Hi,
    since this is a very crucial feature for us I'm very interested in that functionality as well. Is there a comparable functionality in the V2 API or will it be available in feature releases?
    Thanks
    Dominik

  • Image not displayed correctly in image control at small zoom level

    I am displaying an image in an image control with a zoom factor of ~0.015 and it appears as shown in image 1.jpg.  When I zoom in a little more to ~0.016 the image is displayed correctly as shown in image 2.jpg.  Both images are attached.
    Why is the image displayed as a "grey strip" in the first image?  What do I need to do to have the image displayed correctly at any zoom factor?  I am using LV 2011 with the associated vision development module on Windows 7.
    Thanks,
    Jonathan-LV
    Solved!
    Go to Solution.
    Attachments:
    Image 1.jpg ‏133 KB
    Image 2.jpg ‏152 KB

    Hi Jonathan,
    Did you try resizing your image dimensions, as I suggested in my previous post? Anti-aliasing is an expected behavior; as you zoom out, the image has to be resampled in order to be displayed properly. At some point, LabVIEW assumes that the image has been resampled to the point where it no longer resembles the initial image, and so it greys the image out. In the case of your image, that is not the case. As I said, I believe an acceptable workaround would be to use IMAQ resample to half or quarter the pixel dimensions of your image, at which point it should be able to be displayed at a higher zoom factor. 
    Best,
    Dan N
    Applications Engineer
    National Instruments 

  • Is there a feature that will display the current zoom level like Internet Explorer does?

    Zoom level appears in the lower right hand corner of MS IE

    Sorry, there's no built-in feature like what you mean in original Firefox that you download. But you can use this add-ons: [https://addons.mozilla.org/en-us/firefox/addon/default-fullzoom-level/ Default FullZoom Level] . I hope this add-ons can help you.

  • How can I open files using a default zoom level?

    When I open a file in acrobat reader, the letters are too small that I have to zoom out the documents in order to read them. Is it a way to pre-set the zoom level every time I open the files?

    I have the same issue - .
    We NEED a way to have OUR default zoom override whatever some author thought was a wonderful zoom level.
    The Zoom setting in Page Display and also in Accessibility are not honored in V10.1.7, and from other posts, not in earlier versions either.
    And, yes I can provide many documents which apparently have author created zoom levels to prove the point, if needed.

  • Refreshing predefined theme based FOI in ADF 11g

    I am working on Jdeveloper 11g using ADF on a mapviewer application (i.e. geographical maps). I managed to display the base map and predefined theme FOI. I am now trying to just refresh the theme based FOI (predefinedTheme1) on user clicking the 'Refresh Now' command button, How do I do it?. I am attaching the JSPX file with the code.
    <?xml version='1.0' encoding='windows-1252'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.0"
    xmlns:h="http://java.sun.com/jsf/html"
    xmlns:f="http://java.sun.com/jsf/core"
    xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
    xmlns:dvt="http://xmlns.oracle.com/dss/adf/faces">
    <jsp:directive.page contentType="text/html;charset=windows-1252"/>
    <f:view>
    <af:document>
    <script type="text/javascript">
    <![CDATA[
    var mapview;
    baseURL = "http://"+document.location.host+"/mapviewer";
    mapview = new MVMapView(document.getElementById("map"), baseURL);
    alert(baseURL);
    function refreshFoi()
    var themebasedfoi1 = mapview.getThemeBasedFOI('themebasedfoi1');
    var themebasedfoi2 = mapview.getThemeBasedFOI('themebasedfoi2');
    var themebasedfoi3 = mapview.getThemeBasedFOI('themebasedfoi3');
    var themebasedfoi4 = mapview.getThemeBasedFOI('themebasedfoi4');
    themebasedfoi1.refresh();
    themebasedfoi2.refresh();
    themebasedfoi3.refresh();
    themebasedfoi4.refresh();
    function autoRefresh()
    if ((document.getElementById('foiVisible').checked) && (document.getElementById('refreshAuto').checked))
    refreshFoi();
    ]]>
    </script>
    <af:messages/>
    <af:form>
    <af:panelWindow closeIconVisible="false"
    title="Oracle Maps in JDeveloper 11g" id="pw1">
    <dvt:mapToolbar mapId="map"/>
    <dvt:map id="map" startingX="-100.04" mapServerConfigId="mapConfig1"
    baseMapName="MVDEMO.DEMO_MAP" mapZoom="0"
    startingY="40" unit="METERS"
    inlineStyle="width:100%; height:600px;"
    partialTriggers="::cb1">
    <dvt:predefinedTheme id="predefinedTheme1"
    themeName="MVDEMO.CUSTOMERS"/>
    </dvt:map>
    </af:panelWindow>
    <af:selectBooleanCheckbox
    label="Show Locations" id="foiVisible"/>
    <af:selectBooleanCheckbox
    label="Auto Refresh" id="refreshAuto"/>
    <af:commandButton text="Refresh Now" id="cb1" action="refreshFoi()"/>
    </af:form>
    </af:document>
    </f:view>
    </jsp:root>
    Thanks

    I am attaching the jspx file and the backing bean. I want to know how do I now refresh the predefinedtheme1.
    JSPX file
    <?xml version='1.0' encoding='windows-1252'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
              xmlns:f="http://java.sun.com/jsf/core"
              xmlns:h="http://java.sun.com/jsf/html"
              xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
              xmlns:dvt="http://xmlns.oracle.com/dss/adf/faces" >
      <jsp:directive.page contentType="text/html;charset=windows-1252"/>
      <f:view>
        <af:document id="d1" binding="#{backingBeanScope.backing_AVMap.d1}">
          <af:form id="f1" binding="#{backingBeanScope.backing_AVMap.f1}">
            <af:panelStretchLayout binding="#{backingBeanScope.backing_AVMap.psl1}"
                                   id="psl1" bottomHeight="55px">
              <f:facet name="bottom">
                <af:panelGroupLayout layout="scroll"
                                     xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
                                     binding="#{backingBeanScope.backing_AVMap.pgl1}"
                                     id="pgl1">
                  <af:panelGroupLayout binding="#{backingBeanScope.backing_AVMap.pgl2}"
                                       id="pgl2">
                    <af:commandButton text="Refresh Now"
                                      binding="#{backingBeanScope.backing_AVMap.cb1}"
                                      id="cb1"
                                      action="#{backingBeanScope.backing_AVMap.refresh}"/>
                  </af:panelGroupLayout>
                </af:panelGroupLayout>
              </f:facet>
              <f:facet name="center">
                <af:group binding="#{backingBeanScope.backing_AVMap.g1}" id="g1">
                  <dvt:mapToolbar mapId="map"/>
                  <dvt:map startingY="40.0" startingX="-100.04" mapZoom="0"
                           mapServerConfigId="mapConfig1"
                           baseMapName="MVDEMO.DEMO_MAP"
                           inlineStyle="width:97%; height:681px;"
                           binding="#{backingBeanScope.backing_AVMap.m1}" id="map">
                    <f:facet name="rtPopup"/>
                    <f:facet name="popup"/>
                    <dvt:predefinedTheme id="*predefinedTheme1*"
                                         themeName="CUSTOMERS"/>
                  </dvt:map>
                </af:group>
              </f:facet>
              <f:facet name="top"/>
            </af:panelStretchLayout>
          </af:form>
        </af:document>
      </f:view>
      <!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_AVMap-->
    </jsp:root>Backing bean
    package backing;
    import oracle.adf.view.faces.bi.component.geoMap.ThemeFOI;
    import oracle.adf.view.faces.bi.component.geoMap.UIGeoMap;
    import oracle.adf.view.rich.component.rich.RichDocument;
    import oracle.adf.view.rich.component.rich.RichForm;
    import oracle.adf.view.rich.component.rich.layout.RichPanelGroupLayout;
    import oracle.adf.view.rich.component.rich.layout.RichPanelStretchLayout;
    import oracle.adf.view.rich.component.rich.nav.RichCommandButton;
    import org.apache.myfaces.trinidad.component.UIXGroup;
    public class AVMap {
        private RichForm f1;
        private RichDocument d1;
        private RichPanelStretchLayout psl1;
        private UIGeoMap m1;
        private UIXGroup g1;
        private RichCommandButton cb1;
        private RichPanelGroupLayout pgl1;
        private RichPanelGroupLayout pgl2;
        public void setF1(RichForm f1) {
            this.f1 = f1;
        public RichForm getF1() {
            return f1;
        public void setD1(RichDocument d1) {
            this.d1 = d1;
        public RichDocument getD1() {
            return d1;
        public void setPsl1(RichPanelStretchLayout psl1) {
            this.psl1 = psl1;
        public RichPanelStretchLayout getPsl1() {
            return psl1;
        public void setM1(UIGeoMap m1) {
            this.m1 = m1;
        public UIGeoMap getM1() {
            return m1;
        public void setG1(UIXGroup g1) {
            this.g1 = g1;
        public UIXGroup getG1() {
            return g1;
        public void setCb1(RichCommandButton cb1) {
            this.cb1 = cb1;
        public RichCommandButton getCb1() {
            return cb1;
        public void setPgl1(RichPanelGroupLayout pgl1) {
            this.pgl1 = pgl1;
        public RichPanelGroupLayout getPgl1() {
            return pgl1;
        public void setPgl2(RichPanelGroupLayout pgl2) {
            this.pgl2 = pgl2;
        public RichPanelGroupLayout getPgl2() {
            return pgl2;
        *public void refresh(){*        System.out.println("In refresh method");
    }Edited by: Shay Shmeltzer on Apr 2, 2010 10:15 AM

Maybe you are looking for