Cropping to keyed in dimensions...........

I am having problems with the cropping tool, can anyone help please?
Working with a fine art 800dpi 16 bit scan and I want to create an accurate crop to keyed in dimensions, in this case 12 cm x 12cm. Everytme I try to key in the width and height dimensions, leaving resolution blank, I get varying results. Either the crop box just sticks to the original scan size which is bigger or is not drawing to 12 x 12cm, usually smaller when I check off aginast rulers, despite keying in 12 x 12cm! Erratic results for any other dimensions I type in when I view against rulers. Tried clearing in case settings are sticky but to no avail. Can do this all day long in Elements 11 with consistent results. Tried everything in CS 6. Welcome any help, thanks.
SZ

Hi,
If you need an area in the scan that is exactly 12 cm x 12 cm, you might use the Rectangular Marquee Tool and
set the Style to Fixed Size and enter the width an height dimensions.

Similar Messages

  • About Surrogate Key and Dimension Key on OWB 10.2

    Hi, everyone.
    I am using OWB 10.2 and I have a question about Surrogate key and Dimension Key.
    I indicated the foreign key as VARCHAR2 type in Fact Table and Dimension Key as VARCHAR2 type is operated as Primary key in Dimension Table. I made Single Level in Dimension Table.
    I know that Dimension Key stores the surrogate ID for dimension and is the primary key of the table. Also, Surrogate ID should be only NUMBER type.
    So, in this case, Surrogate ID is NUMBER type
    Dimension key should be NUMBER type to store the surrogate ID.
    But, Dimension key also should operate the primary to relate Foreign key as VARCHAR2 type.
    How I can solve this confusing condition?
    Please let me know that.
    JWS

    Hi JWS,
    From a SQL point of view it should not be a problem to join a NUMBER field to a VARCHAR2 field because during execution there will be an implicite cast for the NUMBER value to a VARCHAR2 value. See the example below.
       SELECT * FROM DUAL
       WHERE   1 = '1'From an OWB point of view it is not possible to have a Dimension with an NUMBER value Key that has a relation to a VARCHAR2 value Foreign key in a Fact table. This is caused due to the creation of a Fact table in OWB in which the Foreign keys in it are build from de Dimension tables that refer to them.
    You will loose the reference to the Dimension when changing the type of the Foreign Key.
    To resolve this issue I would advise you to use a Sequence that generates your Surrogate Key (NUMBER type) for the Dimension table and store it in the Primary Key Column (VARCHAR2 type).
    When validating the mapping you will get a warning, but when executing this should give no problems.
    Regards,
    Ilona

  • How to get the "Key" for Dimension in SSAS.

    Hi
    How to get the "Key" for Dimension in SSAS.
    (Below value is the PPSParameters table XML column value in PPSDatabase in SharePoint.
    Below three key values are belongs to "Dimension". I have tried to find the key but I could net get it.)
    <NewDataSet>
    <UserValues><Key>16A201A9E75128559F947D58E6D187A9</Key></UserValues>
    <UserValues><Key>7FBEA449A6ED5606973306445839619E</Key></UserValues>
    <UserValues><Key>A8F75F9720817BCD2E1DFC1C1CF1E678</Key></UserValues>
    </NewDataSet>
    Thanks & Regards
    Poomani Sankaran

    To Be Honest there is not one straight Cmdlet that atleast I have come across 
    The best way would if you have Lync monitoring server 
    Using the Lync Server 2013 Monitoring Server
    If you have the Monitoring Server role configured in your environment, and for Lync Server 2013 everyone should!, you can use information contained in the LcsCDR database to pull back the last time a user signed in.  You can run the following query* to
    pull back the user's SIP URI and their last login time:
    USE LcsCDR
    SELECT dbo.Users.UserUri, dbo.UserStatistics.LastLogInTime
    FROM dbo.UserStatistics
    JOIN dbo.Users ON dbo.Users.UserId = dbo.UserStatistics.UserId
    ORDER BY UserUri
    Which produces the following output:
    The advantage to using the Monitoring Server to obtain this data is that unlike the information contained in the rtcdyn database, the information from the LcsCDR data will persist even when the user isn't signed into Lync.
    To get approx count of users enable for Lync Server in your organisation 
    Get-CsUser -Filter {Enabled -eq $true} | MeasurE
    Please not the above command let will give you an approx number not exact 
    From the Monitoring report yet the SIP account that signed in and then from count find out how many user havent signed in this is manual task 
    Hope this is helpful 
    Please remember, if you see a post that helped you please click ;Vote As Helpful" and if it answered your question please click "Mark As Answer" Regards Edwin Anthony Joseph

  • Ugly: WebI XI 3.1 - Universe doesnt display the Character Key in Dimension

    Dear Forum members,
    I develop a Web Intelligence Report based on a OLAP Universe which is based on a BEx Query.
    When I generated the universe from the BEx Query I left the default values. So I got "database delegated" aggregations and so on. Characteristics from BEx are generated as Dimensions with the Attributes as details. The important attributes for me are "KEY" and "NAME" of the Characteristic.
    I need the Characteristic "KEY" as dimension value. So I set in BEx "Display characteristic KEY" to force this.
    Now I expect, that after generating the universe the Dimension value contains the KEY-Value, and I can also pull the NAME-Attribute if I like.
    But WebI brings back the NAME-Value.
    What is wrong here?
    Edited by: frank_m on Jan 29, 2012 11:14 PM

    Hi,
    those BEx properties aren't exposted by the MDX interface, therefore not consumed by WebI
    Please check Note 1387793 - BEx functionality features that are not supported or integrated in WebIntelligence
    And the reason at source : Note 820925 - MDX - Restrictions
    these articles can be checked at service.sap.com/notes
    What you need to do is (customize your OLAP universe) by changing the syntax and qualification of the generated UNV objects. More information can be found here http://www.sdn.sap.com/irj/boc/go/portal/prtroot/docs/library/uuid/c0a45246-ce76-2b10-e688-f5c8206203eb?QuickLink=index&overridelayout=true
    Regards,
    H

  • Primary key in Dimension

    Dear Colleague,
    We have SAP BPC 7.5 NW, SP10.
    In any dimension primary key is ID. So dimension members can't repeated with same ID.
    Our requrement is set our property RNN unique. We mean our dimension members can't repeated with same RNN.
    Is it possible in SAP BPC 7.5 NW. If no, could we solved it in BW side?
    Thanks,
    Kadraliyev Yerlan
    Edited by: Erlan Kadraliev on Feb 7, 2012 4:19 PM

    Dear Colleague
    Thanks for your answer Siva Namuduri .
    This solution can be usefull for us and at the moment we looking advantages and disadvantages.
    But do we have any other solution to make Property unique? Is it possible in BW side or FrontEnd(BPC)
    Thanks,
    Kadraliyev Yerlan

  • How to create surrogate key in dimension without unique value

    Hi, I have a dimension where there is no column with unique value. I want to add a surrogate key to replace the existing primary key which is derived from concatenating 3 columns(e.g. 'A'||'B'||'C'). I'm thinking of using sequence. But this won't allow me to link the dimension to fact table. How do I come up with surrogate key under this situation? Thanks. ~Tracy

    I'm actually trying to accomplish something similar myself.
    In my sources I've got two sorts of customers, ones that are directly reported, and ones whose information is provided with sales records (this is stored in module ODS).
    Of course identification is different, but in the datamart (module DWH) I'm sort of forced to use an equivalent way of loading (due to the way it first used to work). To accelerate lookups on dimensions, I copy the ODS surrogate key to DWH dimensions, but this does not work for the 'inbuilt' customers because they do not have a surrogate key in the ODS.
    They DO have means of unique identification, and at first I thought I could concatenate these (also 3) columns to use as identification code. Unfortunately this is VARCHAR2, where the surrogate key is (naturally) NUMBER.
    So now it looks like I'm forced to first build a table in ODS especially for these 'inbuilt' customers and assign a surrogate key (by sequence) to it, this way it conforms to how 'normal' customers are loaded into DWH.
    I guess you'll have to pull of the same trick, i.e. create a table with either only the 'translation' of D-code to a surrogate key or all information that is fed into the dimension, which then can be used as a lookup or as complete source when loading data into your datamart.
    Good luck, Patrick

  • Implementing surrogate keys in dimensions

    hello,
    First thing, I'm new to ODI! I am using Oracle data integrator 10.1.3.
    I have a dimension table 'Dim_Contracts' as target table. The structure is as follows:
    PK_Dim_Contract Primary key (surrogate key - to be populated from an Oracle database sequence in the target)
    Contract_ID (normal field in target - no constraints in target- to be populated from source - originally a primary key in source)
    + other dimension attributes.
    from what i have googled out and read in the forum, i cannot define 'PK_Dim_Contract' as the primary key of my dimension (target) table, to be able to update it from the oracle sequence defined - rather the 'contract_ID', which is the natural key should be the primary key. Is that correct? If yes, isn't it against dimension modelling principle?
    More to the point, my question is: How do I populate a sequence in my primary key field in the target table?
    Thanks for your help.
    Regards,
    Anju

    Hello Anju,
    Welcome in the ODI community ;).
    What I suggest you is to set the UNIQUE KEY on Contract_ID in your target. This way you will be able to use flow control and do Incremental Update Loading.
    PK_Dim_Contract (surrogate key) can be your primary key in the dabatase.
    To populate PK_Dim_Contract from an Oracle Sequence, create it first in your Oracle DB. Add a new sequence to your project (left pane), choose Natural Sequence, choose your schema and enter the name of your Oracle Sequence.
    In your interface, define the mapping of PK_Dim_Contract as
    :<ODI_SEQUENCE_NAME>_NEXTVALand execute this mapping on the target.
    Note: :<ODI_SEQUENCE_NAME>_NEXTVAL works only for SQL Statements. If you want to use the sequence somewhere else, use the following syntax :
    #<ODI_SEQUENCE_NAME>_NEXTVALHope it helps,
    Jerome

  • How to load composite business key into Dimension

    Hi,
    Maybe what I'm asking is very basic but, well, here I go:
    I have a dimension, CollectingAgent, and several tables to populate from:
    Bank (bank_code, bank_name ) [PK: bank_code]
    Agency (bank_code, agency_code, agency_name, address, etc) [PK: bank_code, agency_code]
    Now, for my purposes, collecting agent is the bank+agency descriptions concatenated. I don't know hoy to load, or map, the combinated key (bank_code, agency_code) into the business field of the dimension. OWB won't let me define more than one attribute as business key.
    I'm using OWB 10g Rel2.
    Thanks in advance for your help,
    --oswaldo.
    [osantos]

    Ok, let me try to give an example made up with completely bogus information. I'm going to make a dimension called clothing that has two hierarchies that look like this:
    "Item" hierarchy:
    All Clothing --> Item Type --> Color / Item
    "Color" hierarchy:
    All Clothing --> Color --> Color / Item
    Item type would be values such as pants, shirts, dresses, etc. The low level "color / item" is just a combination of those two (i.e. "Blue Shirt") - and note in this example that it will have 2 composite natural keys. It will roll up over the item type hierarchy under shirts, and under the color hierarchy in blue. Here's a sample of what I'm talking about:
    (Item hier)
    All Products
    ...Pants
    ......Blue Pants
    ......Red Pants
    ......Green Pants
    ...Shirts
    ......Blue Shirts
    ......Red Shirts
    etc.
    (Color Hier)
    All Products
    ...Blue
    ......Blue Pants
    ......Blue Shirts
    ...Red
    ......Red Pants
    ......Red Shirts
    like I said, completely bogus, but this will let me illustrate how to set up the dimension. I'd create the following attributes (hard to format, sorry):
    Key....................Surrogate Key
    ID.......................Natural Key
    Item_Type_ID......Natural Key
    Color_ID..............Natural Key
    Short_Desc.........short description
    Long_Desc..........long description
    Having created these attributes, I'd then create the following levels and assign the attributes as follows:
    All_Products_Level:
    ...Key
    ...ID
    ...Short_Desc
    ...Long_Desc
    Item_Type_Level:
    ...Key
    ...Item_Type_ID
    ...Short_Desc
    ...Long_Desc
    Color_Level:
    ...Key
    ...Color_ID
    ...Short_Desc
    ...Long_Desc
    Color_Item_Level:
    ...Key
    ...Color_ID
    ...Item_Type_ID
    ...Short_Desc
    ...Long_Desc
    Should be pretty easy from there. The whole trick is to have a SERIES of different natural keys - a "generic" one (ID) for dimension levels you don't really care about, and "named" ones (color_id, item_type_id) you can use for given levels. And note that you CAN have more than one natural key at any level, and you can have some natural keys that are not used at all levels.
    For your simple dimension, you can probably do the following (note that I'm assuming the lowest level has your composite two business keys, while the top level is completely separate):
    TOP_LEVEL:
    ...Key (for the surrogate key)
    ...ID (for the business natural key)
    ...Short_Desc
    ...Long_Desc
    BOTTOM_LEVEL:
    ...Key (for the surrogate key)
    ...Business_natural_key_1 (rename to be match your first business key)
    ...Business_natural_key_2 (rename to match your second business key)
    ...Short_Desc
    ...Long_Desc
    Hope this helps! If you need to see something a little more concrete, feel free to email me at SPowell at columbus.rr.com, send me some details on exactly what your keys are, etc. and I'll whip up a quick example for you.
    Thanks,
    Scott

  • What can I do to create natural keys for dimension (cwm2, dbms_aw)?

    I create OLAP catalog and AW via cwm2 and dbms_aw packages. Unfortunately made AW uses surrogate keys (that is names of levels are stuck to values of the dimensions, e.g. LEVELNAME_value). Is there any way to change it?

    You should be able use the API invocation:
    dbms_awm.set_awdimload_spec_parameter(<loadspec>,
    <cwm source dim owner>,
    <cwm source dim name>,
    'UNIQUE_RDBMS_KEY',
    'NO')
    Change the last parameter from NO to YES.
    This requires that the key (dimension) values in your source RDBMS tables are unique across levels.
    For example, if you have source RDBMS data like:
    CITIES_TABLE
    KEY PARENT
    BOSTON MASSACHUSETTS
    NEW_YORK NEW_YORK
    HARTFORD CONNECTICUT
    STATES_TABLE
    MASSACHUSETTS
    NEW_YORK
    CONNECTICUT
    Then you need to leave the parameter as NO to get 6 AW dimension values of:
    CITY_BOSTON
    CITY_NEW_YORK
    CITY_HARTFORD
    STATE_MASS
    STATE_NEW_YORK
    STATE_CONNECTICUT
    If you set it to YES for source data like above, you will only incorrectly get 5 AW dimension values of:
    BOSTON
    NEW_YORK
    HARTFORD
    MASSACHUSETTS
    CONNECTICUT
    Alternatively you could set it to YES and change your source data for the offending row to something like:
    CITIES_TABLE
    KEY PARENT
    BOSTON MASSACHUSETTS
    NEW_YORK_CITY NEW_YORK
    HARTFORD CONNECTICUT

  • Export of cropped/rotated images: wrong dimensions!

    Aperture 2 on 10.5.2
    Import a NEF
    Rotate/crop it
    Try to save as JPG with fixed dimensions, e.g. 800 px width
    Some pics will be 800 px, some 798, 799 etc... Hey, we cannot work with this... What´s going wrong there?
    Any workarounds?
    Message was edited by: snafroth

    Oups, I had fooled myself. I take everything back.
    I had exported a second webgallery with cropped images and then copied the cropped images into the 'pictures' folder of the first webgallery (which had been created with uncropped images). I somehow thought that the html code generated by Aperture would not contain the image size (since the browser should be smart enough to figure out the image size once it opens the image itself, or so I thought).

  • CS5  how do I crop to a given dimension???

    trying to crop to 12.5 by 18.5 inches.  do it all the time in CS3, but damned if I can find out how in CS5.  please help...many many thanks
    tom

    Using the Crop Tool simply enter the numbers in the fields to the right of the crop tool symbol in the Options bar. If you type the numbers given it will figure it is in inches.
    If you are going to use those dimensions a lot,you can save it as a preset,so you won't have to keep entering those numbers.

  • Custom cropping using pixel dimension

    The banner image module for my website requires images cropped to 940 x 400 pixels. When I use the Custom cropping function in PSE 12 (on a Mac OSX 10.9.2), it only shows a cm dimension. Can I do a custom crop using a pixel dimension?

    You should just be able to type 940 px and 400 px in the width and height fields
    Another way is to use the Rectangular Marquee Tool and use Aspect>Fixed Size then enter 940 px X 400 px

  • Multi key (or composite key) dimension for operational reporting

    Hi, I am creating operational reports in OBIEE 11g with PeopleSoft FSCM as source. As they are straight forward reports, I am planning to use OLTP tables directly for my OBIEE reporting.
    Here is the simplified scenario - ACCOUNT_TBL_VW is dimension table which has BUSINESS_UNIT & ACCOUNT_ID as keys.
    I have LEDGER Fact that has BUSINESS_UNIT, ACCOUNT_ID & other dimension keys with amount measures.
    How do I link my LEDGER Fact with ACCOUNT Dimension?
    Can I join multiple keys of Dimension with multiple keys of Fact? like this
    ACCDIM.BUSINESS_UNIT ---> LEDGFACT.BUSINESS_UNIT
    ACCDIM.ACCOUNT_ID ---> LEDGFACT.ACCOUNT_ID
    As it is operational reporting, I don't have any ETL type process to prepare single column primary key(surrogate key) in Dimension Table & modifying Fact Table with dimension surrogate key value.

    Hi,
    on the principal of how (in the absence of ETL); -
    1. Physical layer should reflect the actual physical joins, in some cases you may need the same table more than once to reflect self joins
    2. The business model layer is where you transform the physical into your desired star schema, hence here you will frequently (when using RDBMS tables) have numerous physical tables forming the source for a single logical table - this is also where you flatten the snowflake (or worse) into a star
    Make sense?
    regards,
    Robert.

  • Multi-key dimension handling in OTBI report design - How?

    In OTBI reporting (i.e. from transactional DB) design , how to handle multi-key dimensions? I don't have option to have a staging/DW area where I can generate surrogate key for dimensions & use it in facts. Currently we are thinking creating Views on top of transactional tables and use it as dimensions & facts. What is the best way to tackle?

    In OTBI reporting (i.e. from transactional DB) design , how to handle multi-key dimensions? I don't have option to have a staging/DW area where I can generate surrogate key for dimensions & use it in facts. Currently we are thinking creating Views on top of transactional tables and use it as dimensions & facts. What is the best way to tackle?

  • Can I crop a photo inside aperture to any custom dimension?

    can i crop inside aperature

    romeo700 wrote:
    can i crop inside aperature
    You have asked two different questions and, I believe, have gotten correct answers for both.
    I assume by cropping you mean to use a "portion" of an image not to simply resize an image to new dimensions. That's another problem.
    The easy answer is to use an external editor such as Photoshop or Photoshop Elements (or other resizing software, of which I am not familiar).
    Using the above software to create an image with exact pixel dimensions is made easier by sending an image with the correct aspect ratio from Aperture. Say you want an image 636 px x 892 px. Simply determine the aspect ratio by dividing 892 by 636. The result being about 1.4. Your aspect ration then is either 1 to 1.4 or 1.4 to 1 depending on whether you desire a landscape or portrait aspect. In the Cropping HUD, choose "Custom" Ratio Aspect, put the numbers you have calculated in the Width and Height boxes, and crop as desired. Then go to an editor capable of accurately resizing the image to specific dimensions.
    If using additional software is not possible or is unavailable, you can use a trial and error method inside Aperture. This technique offers 2 possibilities. 1) It will allow you to "test" the crop within an image to determine what size crop is possible and/or which size is required to fulfill your need. 2) With patience, it will allow you to crop to specific pixel dimensions.
    As before, calculate the ratio aspect your project requires. Make your crop and press Return to finalize it (for now!). (You can always "erase" the crop by bringing up the crop tool and clicking outside you original crop.) Then bring up the "Info" or "Metadata" (depending on Aperture version) HUD. (Hint: switching between "Library" and "Metadata" will update the information there.) Check "Pixel Size". Those dimensions should equate to the pixel size of your current crop.
    In the trial and error method you can adjust crops, larger or smaller as needed, to match your size requirements. This is tedious and time consuming, but works.
    In my experience I have found that Photoshop image size and Aperture cropped image sizes often disagree. I do not know which is more accurate, though I suspect Aperture crops are a bit inaccurate.
    Jerry

Maybe you are looking for