Export Full EXIF (inluding lens data)

It would be nice if exporting would include all of the EXIF from the original image. In particular, I would like the lens data included. (Yes, I do not have "Minimize Embedded Metadata" checked.)
For example (among other things), the original image (taken with Nikon D200) includes (exported with exiftool):
]Focus Distance : 10.00 m
Focus Mode : AF-S
Focus Position : 0x05
Lens : 18-50mm f/2.8 G
Lens Data Version : 0201
Lens F Stops : 6.00
Lens ID : Unknown (7F 48 2D 50 24 24 1C 06)
Lens ID Number : 127
Lens Type : G
Max Aperture At Max Focal : 2.8
Max Aperture At Min Focal : 2.8
Max Focal Length : 50.4mm
Min Focal Length : 18.3mm
All of which I would love to see in the exported images. (I'm sure there are other ones too that I just didn't notice off-hand.)
jon

Yes, I found this morning that camera data is not exported. This is a major problem. I am entering contests which require the metadata to verify that the photo was taken within a certain period. I just realized that this data is lacking on every picture that I have exported from LR. Luckily I can process those photos in DxO to retain the data.

Similar Messages

Export full database

How does export full database work in data-pump .Does it also exports system and sysaux tablespaces or only all schema data and related metadata.

DataPump is a logical export, so it works with DB objects - schemas, tables, views, etc.
So when you perform full export - then all info from sys/system and other users is exported to the dump

Lens data from Exif

This is a question that was raised in the Lightroom Forum, but I think it might fit better in here. In Lightroom there is an option to sort images with respect to lens used, a very neat function, but when using raw files from Minolta (.mrw) or DNG's converted from these, no lens data is provided. The only information in there is "Unknown lens". Can this be fixed?

Dana Gartenlaub wrote:
> In File Info, Camera Data 1 lists any lens that is recent enough
> to communicate its identity to the camera. This works on Pentax
> PEFs or DNGs even when run through the DNG converter.
It may work this way with Pentax PEF files but unfortunately doesn't with Minolta MRW or Sony ARW files. Of course, Minolta AF (and now Sony Alpha) lenses do report their identities to the camera, and the camera does write this info into the EXIF data but it ends up as an obscure lens ID in the Minolta (or Sony) Maker Notes where most 3rd-party software (including Adobe's) cannot (or would not) access it.
Eric DeSilva wrote:
> Adobe apps will store it in XMP format, but all the makernote
> EXIF data is gone.
This is not true! Adobe XMP won't read the Maker Notes sections but it does preserve them. When I convert an MRW file to DNG (with Adobe DNG Converter) and then create a TIFF or JPEG file from the DNG (with Camera Raw) then the Minolta Maker Notes will still be present in the final TIFF or JPEG file (and of course in the DNG file, too).
Thomas Knoll wrote:
> The problem of the lens data for Minolta/Sony cameras is the
> lens ID codes have lots and lots of overlaps. Mostly because
> Sigma released lenses that duplicate lots of the Minolta lenses
> ID codes.
Sigma lenses don't have Minolta/Sony lens IDs but just random numbers. Kindly ignore what Sigma lenses do. And please don't bother which lens 'was really used.' Just provide us with the lens ID found in the EXIF Minolta/Sony Maker Notes data. Please!
By the way, is there a way to access the Minolta Maker Note LensID tag (or any tag) in the EXIF data through the JavaScript API? If not then please add one!
Currently, I enter the names of the Minolta/Sony lenses manually into the metadata. I customized my File Info Panel 'Camera Data 1' so I can enter the data there in a fairly comfortable way. This is not too hard to do because usually I am using no more than two or three different lenses per assignment usually. This way, the lens names go into the exif/1.0/aux tag named 'Lens.' Unfortunatey, due to a bug in Bridge or in XMP, raw files and DNG files won't accept changes in this and a few more tags; only TIFF and JPEG files will. Instead, the change will get stored in Bridge's cache only. So I wrote a Bridge script to manipulate the XMP sidecar files' contents directly, to 'burn' the changes from the volatile cache permanently into the disk files' metadata.
All this would become *much* easier when 1) we had access to the lens ID in the Minolta (or Sony) Maker Notes and 2) someone would eventually care about fixing that $#!+ metadata bug in Bridge (or XMP) which was already there in Bridge 1.0 and still is around in Bridge 2.1.
-- Olaf

Export from photo library loses date in half the photos

I used a separate iPhoto library to pare down duplicates from a folder of assorted photos that I eventually wanted to integrate into my main iPhoto library. All 3000+ photos had the correct date. Approximately half of these survived the purge, and were exported (full size, with file name included) to a file folder. When I imported these photos into my main library, I discovered that approximate half of these now had today's date. Inspecting the folder they were imported from, I found that the creation date and modification date of these 750 or so photos were both today's date, rather than the date they had had when in the separate small iPhoto library.
What would cause just some of the photos to lose their original date?
(As a work-around, I have now imported the original 3000+ photos into my main library, where they show the correct original date. I have further given them all a unique keyword, and created a smart folder for them so that I can continue to import other photos while I work to once again remove the unwanted duplicates from this set.)

I had chosen JPEG, but I subsequently ran the same export using "Original" and then "Current". The last two exports changed the dates in about 95% of the images to the current date. The JPEG export changed only about half of the dates.
I seem to have had a problem with some of the subject images being corrupt where the Information panel showed the Kind as "_" in iPhoto, but the Extended Photo Info still showed the correct date in the File Modified field. This field then got changed to the current date when the file was exported, regardless of which export "Kind" was chosen. This changed date was consistent viewing the image in the finder or in iPhoto, either in the Information panel or in the "Extended Photo Info" panel, and was the date used by iPhoto for sorting the photos.
Not very useful for hunting down duplicate photos.
So I imported ALL the 3000 or so photos directly into my main iPhoto file, where they kept their original modification date, and then spent the last day or so comparing them to my main database of about 13000 photos.
So why does the Export feature modify the date to the current date? I know you specify that the file data and the exif data are different beasts, but I don't see any place that they differ.

JPEG Export = Save EXIF Infos as part of the image

Is there a way to export jpegs with some exif info (creation date and tile) which should be saved directly on the image. Like the showing of the timestamp on the picture which can be turned on on some cameras.
Reasoin is: I want to use those pics on a digital image frame and I want to show some image data as well. As there are no options in the software of the digiframe to display exifs I have to integrate them in the pictures...
if it is not possible with lightroom then probably you can tell me another way (bridge, photoshop, ...) - just not manually...
thanks

You can do a text overlay in the print Module and then print to JPG file.
Text overlay is done in the "Photo Info" panel.
Print to JPG is done by selecting JPGf file under "Print to:"
For details read up in the Help menu.

Exporting whole database (10GB) using Data Pump export utility

Hi,
I have a requirement that we have to export the whole database (10GB) using Data Pump export utility because it is not possible to send the 10GB dump in a CD/DVD to the system vendor of our application (to analyze few issues we have).
Now when i checked online full export is available but not able to understand how it works, as we never used this data pump utility, we use normal export method. Also, will data pump reduce the size of the dump file so it can fit in a DVD or can we use Parallel Full DB export utility to split the files and include them in a DVD, is it possible.
Please correct me if i am wrong and kindly help.
Thanks for your help in advance.

You need to create a directory object.
sqlplus user/password
create directory foo as '/path_here';
grant all on directory foo to public;
exit;
then run you expdp command.
Data Pump can compress the dumpfile if you are on 11.1 and have the appropriate options. The reason for saying filesize is to limit the size of the dumpfile. If you have 10G and are not compressing and the total dumpfiles are 10G, then by specifying 600MB, you will just have 10G/600MB = 17 dumpfiles that are 600MB. You will have to send them 17 cds. (probably a few more if dumpfiles don't get filled up 100% due to parallel.
Data Pump dumpfiles are written by the server, not the client, so the dumpfiles don't get created in the directory where the job is run.
Dean

Can i export without double quotes in data files?

How can i export without double quotes in data files using dataexport commands in MaxL?

I don't know of any way to do any formatting in a straight export out of Essbase. BSO lets you choose between a columnar vs. free form (really Essbase) format. That lack of formatting includes removing double quotes.
If you're willing to put up with the limitations (and formatting issues) of an MDX extract to a log file, that approach does not put double quotes around member names. The same is true in Report Scripts although I have a vague recollection that you can put in double quotes if you want it -- obviously you do not.
There are limitations to the above two approaches, the biggest being that they they are not as efficient as a true MaxL export. OTOH, you may want only part of a database to get exported out in which case either approach may be more to your needs.
If in fact you do want to do a full export, there are lots of OS-level ways of removing double quotes. Here's a Windows-based approach:
Removing double quotes in a batch program in Windows 2003 - Stack Overflow
What would life be without hacks like the above? Probably not worth living.
Regards,
Cameron Lackpour

Get export of cpce schema without data

exp system/***** file=cpceschema.dmp log=cpceschema.log rows=n full=n owner=cpce
Is this the right command, for getting export of cpce schema without data, i took export and Export terminated successfully with warnings, need suggestions.

Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, Real Application Clusters, OLAP and Data Mining options
Export done in WE8ISO8859P15 character set and AL16UTF16 NCHAR character set
server uses WE8ISO8859P1 character set (possible charset conversion)
Note: table data (rows) will not be exported
About to export specified users ...
. exporting pre-schema procedural objects and actions
. exporting foreign function library names for user CPCE
. exporting PUBLIC type synonyms
. exporting private type synonyms
. exporting object type definitions for user CPCE
About to export CPCE's objects ...
. exporting database links
. exporting sequence numbers
. exporting cluster definitions
. about to export CPCE's tables via Conventional Path ...
. . exporting table COLLECTEDDATA
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table CONFIGURATION
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table DCCONTEXT
. . exporting table DCPLAN
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table EQUIPMENT
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table FDCCONTEXT
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table GPCDATA
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table INDICATOR
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table JOBS_TBL
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table MAINTENANCEERROR
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table MAINTENANCELOG
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table MESCONTEXT
. . exporting table MODULE
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table PARTITIONMETHOD1
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table PARTITIONMETHOD2
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table RECIPE
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table REQUESTS_TBL
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table STRATEGY
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table TREATEDDATA
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. . exporting table VARIABLE
EXP-00091: Exporting questionable statistics.
EXP-00091: Exporting questionable statistics.
. exporting synonyms
. exporting views
. exporting stored procedures
. exporting operators
. exporting referential integrity constraints
. exporting triggers
. exporting indextypes
. exporting bitmap, functional and extensible indexes
. exporting posttables actions
. exporting materialized views
. exporting snapshot logs
. exporting job queues
. exporting refresh groups and children
. exporting dimensions
. exporting post-schema procedural objects and actions
. exporting statistics
Export terminated successfully with warnings.

Lens Data

When Pentax updated its firmware for the K10D to version 1.1, the raw files (PEF or DNG) changed in some way where LR no longer is able to interpret the lens data to know what lens was used. As I understand it, Pentax's numbering system internal to the raw file that identifies the lens changed, and LR no longer interprets it.
I believe that this will probably be a temporary situation; eventually a newer version of LR will come out that supports lens metadata for Pentax K10D raw files.
My concern is this: when and if this problem is ever corrected, will I have to re-import my raw images so that their lens metadata will be acquired into the LR database?
A lot of "if's", I know. Hopefully my question actually makes sense! haha

Talk to Canon and Tokina - if that data is properly given to the camera and properly recorded in the EXIF data by the camera then iPhoto will display it - if it is not there then iPhoto can not do anything about it - only the manufactures can fix that
LN

Exporting full database...

Dear All,
While exporting full database objects of sys user are exported or not?
Please tell me in details.
Thanks In advance.
PSP.

I agree all your point. But, what will you do when an object is dropped such as TABLE >when the DB is 5 T or more.
Would you do a PIT? would you?
I accept that we use this exp/imp as one way of data migration. It doesn't become it is a >migration tool not a backup tool.
Then why would ppl say it is a logical backup not as migration tool. ppl say we can use >this as one way for data migration.Then there's when your sounded backup plan comes in play.
We use to do a full exp every day from our small databases, and the retention policy is 14 days.
In the Biggest database a full exp is not possible due batch processing at night, so we take a home made incremental export for the big objects and the rest of tables.
In 10g i think you can set the flashback to 2 weeks and that's all we need. (ya its a lot of space but it depends on your policy and your database size).
I'm not against EXP/ IMP at all, but you cant rely on them other than getting back a table or a stored procedure from certain date.
what i've noticed is that lot of people use exp/imp in small databases and this is their main backup strategy, but when they start working with big databases this approach is just not enough.
This is why you have to work and review your corporate backup policy.
It doesn't matter if you are an excellent DBA, if you took 3 days (or more) to restore your database you are just not doing your work.
my 2c.
Edit:
May be i need to clarify something.
Physical backup is intended to fast restore your database from a crash.
Logical Backup is used to migrate data, even if its into the same database.

Export to PDF, Excel, Excel (Data Only) formatting issues

Hi Community
I have a report that consists of 5 subreports. Out of the 5 subreports, 3 of them have a similar format whereas the other 2 are different.
Iu2019m currently facing an issue whereby the exports to excel works fine, but excel (data only) has some alignment issues(i.e. the data appears below the correct columns). However, when the report is tweaked to make export to excel (data only) appear correctly, the export to excel had its data shifted out of alignment. There is no impact to pdf exporting at the moment.
Are there any people who are facing similar issues? Is there any resolution or workaround? I appreciate any help. Thanks.
FYI, the version of crystal reports is Crystal reports is Crystal reports 2008 and we are using the crystal report viewer interface to export into excel and pdf formats. The excel version is 2007.
Regards

DW, i've also run into issues with multiple sub reports. I resolved it by putting each sub report into it's own section, and then suppressing the sub report (Note, if ur trying to export subreport data to excel, I don't think its going to work. You'd need to create shared variables and then bring those sub report shared variables into your main report).
Once you bring your shared variables into the main report, suppress your sub reports, and then export to excel, you're still left with a dataset that has missing rows. This is ok. You can solve it easily within the excel file itself by sorting the data on a unique ID like Account #. This removes the extra rows.
Not the most elegant solution, but it works.

How to get the Full and final settelment date from PC_payresults

Hi Experts..sairam.
We are preparing Functional specification for a report on Full and final settelement.
We need to extract the full and final settelement date from payresults.
Full and final settelement would be an offcycle run.
How can we identify the particular Offcycle is meant for full and final settelment.
Full and final settelement can be done after date of relieving.
Please share your ideas to get the field names and logic to fetch.
Thanks in advance.
Regards,
Sairam.

Hi Praveen,
I found it from HRPY_RGDIR through SE11.
But im in confusion in thinking on Logic to find the Full and final settelment processed date.
First of all..Report has to check WPBP table weather Employment status is Zero.
Later..It has to read the HRPY_RGDIR table.
Here what the system to check.What conditions to be validated to fetch the Full and final settelment processed date.Will it be FPPER and INPER as 00000000 or shall we do it from offcycle reason.
Please share your ideas.Thanks in advance.
Regards,Sairam.

Is it possible to export the "Mediathek" in a data file (excel or word) ?

Is it possible to export the "Mediathek" in a data file (excel or word) ?

see my old post:
https://discussions.apple.com/message/6272619?messageID=6272619#6272619?messageI D=6272619

Export and Import of Configuration Data

Hi All,
I have created a number of custom properties, structures, groups, renderers, layout sets etc and would like to move them from Dev to Test system.
I have found the following in the help doco:
"Export and Import of Configuration Data"
http://help.sap.com/saphelp_nw04/helpdata/en/e1/029c414c79b25fe10000000a1550b0/content.htm
However I am unable to see its functionality in our portal systems (namely the Actions->Export and Actions->Import functions).
Our version of Portal is: 6.0.9.6.0
KM: 6.0.9.3.0 (NW04 SPS09 Patch3)
Therefore we should be able to see it? no?
Are there any special settings to see these buttons?
Cheers,
Vic

Thanks for your replies.
OK, so in otherwords, it is not available in SP09 and only in SP12+.
So, to "transport" this information I will have to manually reapply thes settings in the Test system!
Message was edited by: Victor Yeoh

Export and import a table data

Hi All,
There is table abc which is having appprox 40lak records without partitions(and have dmp of this data). Due to space constraints I want to compress the data and put it in archive schema.
My question is:
1) Can we import the data into other schema(say: archive schema) in compressed mode. If so could you please let me know the syntax for that.
2) Can we import the data into some temporary table(say: temp) in same schema?
3) And if any blob column exists in table then can we import the data without this blob column data.(Supposing the export dump has the blob data).
Is it possible, or whould we export without this blob column and import this to other table?
Please help me out.
Edited by: user11942774 on 4 Dec, 2011 10:33 PM

Thanks Mahir,
Could you please let me know the syntax or with any examples if possible.
is it possible to drop any column say blob column after the table is in compressed mode?
Edited by: user11942774 on 4 Dec, 2011 10:53 PM
Edited by: user11942774 on 4 Dec, 2011 10:54 PM

Export Full EXIF (inluding lens data)

Similar Messages

Maybe you are looking for