|
Selecting this option loads the Preferences screen where you can specify various program settings.
The items listed are either those that apply globally or those that cannot be specified elsewhere. RoboGEO stores all of its configuration settings under the following key:
HKEY_CURRENT_USER\Software\Pretek\RoboGEO\
You can safely delete the 'Pretek' key and subkeys if you want to reset everything to the default values. Don't manually edit the Windows registry if you don't know what you're doing or without first backing it up.
To set an option in the RoboGEO preferences, select it from the tree view and then enter the new value into the 'Current Value' box. Click the 'Save' button to save it.
If an item requires a True/False value, select the appropriate option. Other items require that you type a value directly into the textbox. Some items, such as the Datum and CameraOffset, require an additional input form - double click on the 'Current Value' box to load it.
If True, the program will overwrite the existing images when they're processed.
If False (the default), you'll be prompted for an output folder and the images will be copied to and processed from there, i.e. the original images will not be modified.
This must be set to False if you specify multiple options on the robogeo.exe command line.
Note: You can override this setting when renaming or redating images.
If both this and EditOriginalImages are True, the original images will be backed up to a new folder under \My Documents\RoboGEO\Backup\ before they are processed. The name of the new folder will be based on the current time and will be of the form yyyymmddhhmmss. For example, if the time is 4:49:01am on December 31, 2007, the new folder will be named \My Documents\RoboGEO\Backup\20071231044901\.
Specify the image quality to use when saving JPG files. This can range from 1 (lowest quality, highest compression, smallest file size) to 100 (highest quality, lowest compression, largest file size).
As the quality increases, so does the resulting file size. High quality is good. Large file size is bad. The goal is to reach a happy compromise where the quality is acceptable without having huge files. The default value of 98 produces reasonably sized images with no perceptible loss of image quality.
The program writes EXIF and IPTC data in a lossless manner, so this option doesn't matter when you're only doing that.
Specify the datum. The datum that you select should be the same as your GPS unit and/or the same datum that's associated with the tracklog files that you import. Select WGS 1984 if you're unsure.
Double click on the Current Value box to select a recognized datum from the list.
If True, altitudes are expressed in feet. Otherwise, meters are used. The units are used for display purposes only, like when stamping images or displaying trackpoint statistics. Altitudes are always written as meters when saved to the EXIF headers, regardless of what is specified here, because that's what the EXIF specification requires.
If your GPS unit doesn't support altitude data and if you never manually enter the values, it won't matter what you use.
This option allows you to compensate for an inaccurate camera clock. The camera offset is specified in seconds and is added to the GPS time so that it matches the camera's time.
To geocode images from a GPS tracklog, the camera's time must be in sync with the GPS's time. If they aren't, there will be errors in the image locations as described here.
The camera offset should be positive if the camera clock is ahead of where it should be or negative if the clock is running slow. Normally, you should simply ensure that the camera clock is accurate by using the method below and specifying zero for this option.
This option isn't intended to be used for specifying the UTC offset for your time zone. Use the UtcTimeBias option for that or let the program determine it automatically by looking at your computer's time zone information.
The best way to ensure that the camera's clock is accurate is to simply set it so that it matches the GPS. Turn on your GPS and go to the page where the time is displayed. Assume that it shows 11:22:02. Now go to the setup screen in your camera where you set the time. It doesn't matter if your camera displays seconds or not. Set it to the next highest minute (11:23 in this case) and wait for the GPS to reach that time. When it does, save the camera time. Be quick.
Since camera clocks drift, it's a good practice to do this fairly often and, at least, once on the day before you take any pictures.
Note that some GPS units don't support the display of daylight savings time. In you live in a locality that does and if it's in effect, the time that displays on your GPS will be 1 hour behind (or ahead of) the actual local time. Don't be alarmed by this and don't think that you need to set a 3600 second offset or set your camera's time back an hour to account for it. Just ignore the 1 hour error because it's not really an error. GPSs always use UTC time - the local time that a GPS displays is for human eyes only.
When your camera and GPS clocks are in sync, the camera offset should be set zero.
If you must specify a camera offset, either type it in or double click on the Current Value to load an interactive form. The form gives you 2 methods for determining the camera offset:
For the 1st method, when prompted whether to load an image of your GPS unit showing the time, select 'NO'.
You'll then be prompted to enter the offset (in seconds) between the camera and GPS. If the camera's time is behind the GPS, the number should be negative. Otherwise it should be positive.
For example, if the GPS time is 11:30:00 and the Camera time is 13:31:01, the offset would be 7261 (2 hr + 1 min + 1 sec = 7261 sec). Note that the offset is positive since the camera time is ahead of the GPS time.
The 2nd method is the "picture of the GPS" method. To do that:
1. Turn on your GPS and obtain a position fix.
2. Page to a screen that displays the time.
3. Take a picture of the GPS screen.
4. Transfer the image to your computer.
5. From the Preferences, double click the CameraOffset box.
6. Select 'YES' when prompted whether to load the picture.
7. When the picture loads, note the displayed time.
8. Close the picture and delete it from your disk.
9. Enter the time that you noted in the box.
The program will then calculate the offset and save it.
Note that the "picture of the GPS" method isn't as accurate as manually setting the camera's clock to match the GPS. A GPS only displays time in 1 second increments, so the error in automatically determining the offset can be as great as 1 second. On the other hand, when you're manually setting the camera clock, you can probably do that with a maximum error of about 1/4 of second if you're quick.
Specify the number of minutes that your camera's clock was ahead of or behind Greenwich Mean Time at the time you took the pictures. The number should be positive for areas west of Greenwich England, like Canada and the USA. For areas to the east, like India and Australia, the number should be negative.
For example, in New York City, NY USA during the summer when daylight savings time (DST) is in effect the UtcTimeBias should be 240. Note that it's positive and that it's expressed in minutes. In the winter when DST isn't in effect, it would be 300.
If your camera's clock is set to UTC time, set this option to 0.
If you specify -1 (the default), the program will automatically determine the bias by looking at your computer's time zone information. This can be problematic if your camera and computer are not set to the same time zone, if Windows cannot accurately report whether DST is in effect for your locale, or if DST changes between the time you record a tracklog and the time that you use it to geocode images.
Specify the local path to a WAV sound file. If robogeo.exe is started in automode by using the /a command line parameter, the sound file will be played at program startup. You can double-click on the file path in the associated text box to preview the sound.
If True and if robogeo.exe is started in automode by using the /a command line parameter, you'll be prompted at program startup whether to cancel the execution of the other command line parameters. This prompt occurs after the WAV file is played.
Specify a file path to an ASCII text file. When the program is started in automode by using the /a command line parameter, status information and/or errors are written to this file instead of being displayed to the user. The file is created if it doesn't currently exist.
If not specified, the log file will be named AutoMode.log and will be located in the current Windows user's 'My Documents' folder. Note that because of that, different Windows users will have different log files.
If True and if the log file size exceeds what's specified in CmdLineAutoModeLogFileArchiveSize, it will be renamed to a dated format (YYYYMMDDHHMMSS with an extension that matches the original log file name), compressed, and then added to an archive named LogArchive.zip located in the same folder as the original log file. Once added, the original log file will be deleted.
Specify a number between 65536 and 2147483647. When the log file size (in bytes) exceeds this number, it'll be archived per CmdLineAutoModeLogFileArchive.
If True and if exporting to Google Earth (/g) in automode (/a), the generated KML or KMZ file will be launched in Google Earth upon completion.
If True and if exporting to Google Maps (/m) in automode (/a), the folder containing the generated files will be launched in Windows Explorer upon completion.
If True and if exporting a Shapefile (/h) in automode (/a), the folder containing the generated files will be launched in Windows Explorer upon completion.
If True and if exporting a DXF file (/c) in automode (/a), the generated DXF file will be launched in the Windows program associated with the .DXF file extension upon completion.
If True and if exporting a CSV file for MapPoint (/b) in automode (/a), the generated CSV file will be launched in the Windows program associated with the .CSV file extension upon completion. Note that MapPoint isn't usually associated with .CSV files - that's usually a spreadsheet program.
If True and if exporting a GPX file (/b) in automode (/a), it will be launched in the Windows program associated with that file extension upon completion.
When only an image path is passed on the robogeo.exe command line, the image is loaded and added to the grid just as if you selected it from the pull-down menu. In addition to that and if this is set to True, the Google Earth geocoder will load and allow you to quickly (manually) geocode the image.
To use this efficiently in your normal workflow, it may be necessary to temporarily associate robogeo.exe (instead of your normal graphics program) with the image format that you're dealing with. That way when you launch an image file, it'll automatically load in the Google Earth geocoder. Another option is to eliminate the association with the image format. When that's the case and when you try to launch an image file, Windows will prompt you for the program to use - select robogeo.exe or your normal graphics program depending on what you want to do.
In Windows XP you can change an association by loading Windows Explorer and then selecting Tools-->Folder Options-->File Types. In Vista, select 'Default Programs' in the Control Panel.
When only a tracklog file is passed on the robogeo.exe command line, the tracklog is loaded just as if you selected it from the pull-down menu. In addition to that and if this is set to True, it'll also be loaded in Google Earth, allowing you to quickly view it.
This serves as a very quick way to view tracklogs, so you may want to manually associate robogeo.exe with .GPX files on your computer.
If just a tracklog is passed on the command line and if CmdLineTracklogExportGoogleEarth is True, robogeo.exe will automatically end after it launches it.
If this is True and if CmdLine.txt exists in the same folder as robogeo.exe, the contents of that file will be used for robogeo.exe's command line. If something is also specified on the command line, it'll be ignored, i.e. CmdLine.txt overrides what may exist on the command line.
CmdLine.txt should be plain ASCII text and contain a single line of text that conforms to the requirements of a normal robogeo.exe command line. For example, CmdLine.txt may contain a single line of text that reads (without quotes), '/p:c:\robogeo\projects\hike.rgw /s /e /g /a'. That CmdLine.txt file would be equivalent to starting RoboGEO using the command line parameters 'C:\Program Files\RoboGEO\robogeo.exe /p:c:\projects\hike.rgw /s /e /g /a'.
There are other options that relate to the use of Cmdline.txt command line file including CmdLineCmdLineDotTxtDeleteAfterUse, AutoStartLaunchApp & AutoStartWaitForCmdLineDotTxtExist. The intent of this feature is to allow you to develop independent applications that dynamically create the CmdLine.txt file so that you can control RoboGEO's behavior when running in automode.
If True, Cmdline.txt is deleted after it's used. You should usually do this if you're using a 3rd party application to dynamically create the file.
If True, Cmdline.txt is deleted at program startup.
If specified and if it represents a local file path to an application, the application is launched at program startup. What robogeo.exe does after it launches the application depends on what you specify for AutoStartWaitForAppEnd, AutoStartWaitForCmdLineDotTxtExist, and AutoStartWaitTimeOut.
Your application could, for example, preprocess images or dynamically create the CmdLine.txt file.
If the application associated with AutoStartLaunchApp is launched at program startup, robogeo.exe will resume either when the application ends or when there's a timeout.
If the application associated with AutoStartLaunchApp is launched at program startup, robogeo.exe will resume either when this file path exists (such as c:\robogeo\CmdLine.txt) or when there's a timeout.
If the application associated with AutoStartLaunchApp is launched at program startup, robogeo.exe will resume if the application has not ended in this amount of time. The number is expressed in seconds. If you specify -1, the program will wait indefinitely for the program to end.
If specified and if it represents a local file path to an application, the application is launched asynchronously before the program ends.
If True, some of the visual effects associated with the user interface will be turned off, which may speed up the application on slower computers.
This has no effect on the program's functionality - just how it looks. The default value is False.
Specify the height, in pixels, of the grid rows. The default value is 18.
Specify the grid font height in points. Depending on the font, the actual font size may differ from what you specify here. The default is 8.
GridFontFace
Specify the grid font face. The font must exist on your system. The default is MS Sans Serif.
FolderPickerShowFiles
If True, the folder picker dialog will show files in addition to folders. The default is False.
If True, image disk dates are preserved when data is written to the EXIF, when stamped, or when they are renamed. Otherwise, the image disk date reflects the date when the image was last modified. The default value is False.
If True and if an image title exists, it's stamped at the top of the image. The header font size is automatically determined so that the title is as wide as possible without exceeding the image width and without being taller than 4% of the overall image height.
Specify the header font face for stamped images. The font should be a TrueType and must be installed on your system. The default is Arial.
Specify the header font size. If you enter 0 (the default), the program will automatically determine the optimal size so that the width is as wide as possible without exceeding the image width, but never being taller than 4% of the overall image height.
When True, a bold font will be used for the header. Note that making a font bold also makes it wider.
Specify header's 24-bit long font color. This ranges from 0 (black) to 16777216 (white). The default value (12632256 = gray) corresponds to RGB(128, 128, 128). Red is 255. Green is 65280, yellow is 65535, blue is 16711680, etc.
Specify the header font opacity. This should be a whole number between 0 (invisible) and 255 (totally solid).
This controls the brightness of the header text background and it should range between -100 (solid black) and 100 (solid white). Numbers in between those, like 0, result in a partially transparent background.
Specify the latitude/longitude format to use when stamping images.
There are 4 formats to choose from: DD (decimal degrees, the default), DM (degrees and minutes), DMS (degrees, minutes and seconds), or UTM coordinates. These are case sensitive and must entered exactly as shown.
Specify the footer font face for stamped images. The font should be a TrueType and must be installed on your system. The default is Arial.
Specify the footer font size. If you enter 0 (the default), the program will automatically determine the optimal size so that the width is as wide as possible without exceeding the image width, but never being taller than 4% of the overall image height.
When True, a bold font will be used for the footer. Note that making a font bold also makes it wider.
Specify the footer's 24-bit long font color. This ranges from 0 (black) to 16777216 (white). The default value (12632256 = gray) corresponds to RGB(128, 128, 128). Red is 255. Green is 65280, yellow is 65535, blue is 16711680, etc.
Specify the footer font opacity. This should be a whole number between 0 (invisible) and 255 (totally solid).
This controls the brightness of the footer text background and it should range between -100 (solid black) and 100 (solid white). Numbers in between those, like 0, result in a partially transparent background.
If True, the image date is not included in the footer when stamping. Use this if the date isn't important or if you're running out of horizontal space on the image.
If True, the map datum is not included in the footer when stamping.
If True, the UTC offset is not included in the footer as part of the timestamp when stamping.
If True, the timestamp that's used when stamping is per your computer system's Short Date format instead of the Long Date format, i.e. no time component will be included on the image, only the date. The UTC Offset will also also omitted.
If True, the altitude is not included in the footer when stamping.
When True and when stamping images, cardinal directions (N, NNE, NE, ENE, etc.) are used in the footer instead of decimal degrees measured clockwise from true north.
When stamping images with degrees-minutes format (DM), this many decimal places will be used for the minutes.
When True and when stamping images, the elapsed time relative to the earliest image will be stamped on the image footer instead of the image's local timestamp.
When StampElapsedTime is True and when stamping images, this word is placed after the elapsed time. The default word is "Elapsed".
If False, the program will not update the EXIF Software field whenever it updates the EXIF data.
When this is specified and when other data is written to the EXIF headers, this is written to the photographer copyright notice EXIF field.
If (c) or (year) exists, they are replaced with © and the year of the EXIF timestamp, respectively. So, for example, Copyright (c) (year) Nort McGurski would become Copyright © 2008 Nort McGurski. Note that (c) and (year) are case sensitive.
If False (the default value), existing photographer copyright notices are never overwritten.
If specified and when writing other data to the EXIF headers, this value is used to construct the EXIF Artist field. Normally, you should also specify the ExifArtistPhotographer and ExifArtistImageCreator fields in conjunction with this.
The final form of the Artist field will be similar to "Camera owner, John Smith; Photographer, Michael Brown; Image creator, Ken James", with this option shown in bold.
If specified and when writing other data to the EXIF headers, this value is used to construct the EXIF Artist field. Normally, you should also specify the ExifArtistCameraOwner and ExifArtistImageCreator fields in conjunction with this.
The final form of the Artist field will be similar to "Camera owner, John Smith; Photographer, Michael Brown; Image creator, Ken James", with this option shown in bold.
If specified and when writing other data to the EXIF headers, this value is used to construct the EXIF Artist field. Normally, you should also specify the ExifArtistCameraOwner and ExifArtistPhotographer fields in conjunction with this.
The final form of the Artist field will be similar to "Camera owner, John Smith; Photographer, Michael Brown; Image creator, Ken James", with this option shown in bold.
For your location, this is the difference between magnetic and true north. East values should be positive, west negative.
This number is added to the photo directions that you enter. You should only specify this number if your photo directions were obtained using a magnetic compass. You can determine the magnetic declination for a given location from here.
If True, the program will use the image disk date as the timestamp instead of trying to determine it from the EXIF headers. This is useful for webcams or older cameras that don't produce EXIF compliant images.
If True, the program writes latitude and longitude values to the EXIF with a precision of 2 decimal places on the minutes. This results in a maximum error of 0.005 minutes, but it ensures compatibility with almost all 3rd party EXIF reader programs. If False (the default), the latitude and longitude values are written to the EXIF with exact precision.
Normally, you should only set this to True if your EXIF reader program can't read the high precision values that the program writes.
If True, the program always renames the original images regardless of the EditOriginalImages setting.
If True, the program always redates the original images regardless of the EditOriginalImages setting.
If True and if orientation information exists in the EXIF headers, images will be automatically rotated when loaded and the EXIF Orientation field will be reset to 1. The process is entirely lossless.
RoboGEO does not support writing the raster data in certain RAW formats including NEF, CR2, MRW, and ERF. These image formats, if they exist in your list, will not be rotated when loaded.
WARNING: The rotation is always performed on the original images.
If both this and RotateWhenLoaded are True, you'll be prompted whether to rotate images prior to loading them.
The direction in which an image is projected is per the photo's direction. It's presumed that when you project a photo location that the new location represents the true location of the photo's subject, making the photo direction value obsolete.
If False (the default), the photo direction will be removed after projecting the image to the new location.
If True, the image altitude will be removed after projecting the image. The default value is True.
When projecting a photo location in airplane mode, the altitude value associated with the image will also change depending on the GPS receiver's distance above the ground and the camera angle. Since the distance above the ground can vary with the terrain below or with the skill of the pilot, this can cause the resulting altitudes after projecting to be inaccurate.
If specified, this URL will be launched when the Edit-->Locate-->World Map menu option is chosen. If the URL contains the bracketed terms [lat] or [lon], the program will automatically insert the current image's true values for them. For example, your URL may look like http://www.yourmap.com/script.php?lat=[lat]&lon=[lon]. Leave this setting blank (the default) if you want to use multimap.com.
If specified and if the selected image doesn't already have latitude and longitude values associated with it, this ampersand delimited string of name=value pairs is appended to the end of the URL (http://www.robogeo.com/latlonfinder/map.asp) associated with the 'Lookup Lat/Lon Values' option under the 'Edit' pull-down menu. This allows you to specify the default 'view' (normal, satellite, hybrid, physical), 'zoom' (1 to 15), 'lat' (-90 to 90), and/or 'lon' (-180 to 180). For example if you want the terrain view to be the default, specify (without the quotes) 'view=terrain'. If you want a hybrid view with a zoom value of 10, specify 'view=hybrid&zoom=10' (note the ampersand). Do not include a leading question mark.
When True and when geocoding images from a tracklog, previously geocoded images will be skipped. The default value is False.
You should set this to True, for example, if you use the GPS tracklog as a backup method for geocoding images in the event that a real-time hardware solution fails.
If True and if the program is unable to geocode an image normally from a tracklog, the closest trackpoint will be used for the photo location. The closest trackpoint is the one with a timestamp that is the closest to the image timestamp.
Images that were geocoded from the nearest trackpoint will show up as red (non-bold)in the resulting list.
Use this option with care because it can result in (very) inaccurate results or mask other problems.
If True, all of the tracklog segments will be combined into one before being used for geocoding photos.
You should use this option if your tracklog contains many unintentional tracklog segments and if you're unable to geocode the images because the image timestamps fall between these segments.
If True and if geocoding images from a tracklog, the image direction will be set to the current tracklog heading. Headings are measured clockwise from North.
For example, if you were traveling west when a photo was taken, the photo direction will be set to 270.
If PhotoDirFromTracklog is True and if geocoding images from a tracklog, this number is added to the tracklog heading to determine the photo direction.
For example, if you were traveling east when a photo was taken and if this is set 45, the photo direction will be set to 135.
This option should normally be used if all of your photo directions are at a constant angle relative to your direction of movement. For example, if all of the photos are taken out of the left hand window of a moving car, use 270 for this option. If taken out the right window, use 90. If taken straight ahead, use 0.
Note: When you manually enter a photo direction by typing directly into the main grid, you can use directions relative to the current tracklog heading by preceding the number with an @ symbol, i.e. setting PhotoDirFromTracklogOffset = 45 is the same as manually entering @45 for the photo direction. The benefit of manually entering directions is that each image can have a different relative direction, which is easy to determine if there is foreground data (like a cockpit or car window) in the image that gives a clue as to the relative direction. The benefit of using PhotoDirFromTracklogOffset is that it calculates all of the directions automatically when it geocodes the images, meaning that you don't have to manually enter the data.
When geocoding photos from an imported JTR file, if the time difference between an image and the closest trackpoint exceeds this values, the image will be skipped and not geocoded. The number is expressed in seconds. If you specify -1, the time difference will be ignored.
When geocoding photos from a tracklog, if the time difference between an image and the closest trackpoint exceeds this value, the image will be skipped and not geocoded. The number is expressed in seconds. If you specify -1 (the default), the time difference will be ignored.
When geocoding photos from waypoints in an imported GPX file, the photos are matched to the waypoint having a timestamp that's closest to the photo's EXIF timestamp if the time difference is less than this number, specified in seconds. If you specify -1 (the default) the difference is ignored.
Enter the maximum number of characters that your Garmin GPS supports for waypoint identifiers. When uploading waypoints, you'll be warned if any of the waypoint name lenghts exceed this number.
Enter the Garmin Protocol waypoint symbol number. Not all Garmin units support all symbol numbers. Set this value to -1 to force the Garmin unit to use its default waypoint symbol.
Enter the maximum number of characters that your Garmin GPS supports for waypoint comments. When uploading waypoints, you'll be warned if any of the waypoint comment lenghts exceed this number.
When uploading waypoints, if this is True the program will automatically create waypoint comments based on the photo's EXIF timestamp. These timestamps are for human eyes only and cannot be used by any program that's fully compliant with the Garmin Protocol. Set this to False if you want to manually enter the comments or if you want to leave them blank.
If True, the 'Place Lookup' form will stay on top of all other windows.
When looking up places, this is the maximum number of records that will be returned. The default is 100, but the actual number can be as high as 1000. Each record will be about 700 bytes so, depending on the speed of your internet connection, 1000 records may take a long time to download.
When you double click on a place lookup result, you can search for places near the current one. The number that you specify here (in km) is the radius of that search.
If True, and if exporting the photo locations as a list of waypoints, the local image file path will be written to the comment field in the form file:<path>.
When False (the default), the image title, if it exists, is written to the waypoint comment field. You should set this to True if you're using the GPX files in a 3rd party application that can make use of the local path.
When exporting a GPX file and if this value is set to True, the image's EXIF title will be used for the waypoint name instead of the filename.
When exporting a GPX file that contains photos and if this value is set to True, a <link> element with an HREF attribute that points to the image's local file path is included in the resulting GPX file. This makes the GPX file suitable for importing into Memory-Map.
If GpxMemoryMapCompatible is True when exporting a GPX file, a <sym> element is added to the GPX file. The symbol value should be a Memory-Map icon name. The default value is 'Dot'.
If GpxMemoryMapCompatible is True when exporting a GPX file, a <type> element is added to the GPX file. The type value should be a Memory-Map category name.
If GpxMemoryMapCompatible is True when exporting a GPX file that includes a tracklog, a <type> element is added to the GPX file under the <trk> element. The value that you enter should represent a broad category name. The default value is 'Track'.
If GpxMemoryMapCompatible is True when exporting a GPX file that includes a tracklog, a <name> element is added to the GPX file under the <trk> element. The value that you enter should represent a specific track name that falls under the category name that you specify. The default value is 'Track'.
If GpxMemoryMapCompatible is True when exporting a GPX file that includes a tracklog and if this value is set to True, you'll be prompted for the GpxMemoryMapTrkCategory and GpxMemoryMapTrkName values at the time you're exporting the GPX file instead of you having to go back to the preferences area and changing it from there each time. The default value is 'False'.
If True and if exporting a GPX file that uses the photo locations as waypoints, Garmin's GPX extension will be added to the output. This will allow you to view the associated images from within MapSource.
If GpxMapSourceWaypointCompatible is True and if exporting a GPX file, this setting controls how the waypoints are displayed in Garmin's MapSource program. You can specify SymbolOnly, SymbolAndName, or SymbolAndDescription.
If GpxMapSourceWaypointCompatible is True, this is used for the <sym> element in the exported GPX file. If must be something that MapSource recognizes. The default value is Waypoint.
If True and if an image has dictation associated with it, the audio will automatically play whenever the image is selected. Normally, you'll have to click the small paperclip icon in the lower left corner of the image preview to play the associated audio file.
The default value is False. Setting it to True can be functional, but can also get very annoying very quickly.
When True (the default) audio and image files are automatically associated when either is loaded. Set to False if you intend to manually associate the audio files to the images.
Instead of using the built-in audio player, set to True if you want to use the program on your system that's associated with the current audio format. The default value is False.
Set to True to keep the built-in audio player on top of all other windows.
If True and when resuming play after pausing, the audio will 1st rewind per the AudioRewindTime preference before resuming play.
If False, the audio will simply resume play at the point from which it was paused.
The number of seconds to rewind per 1 click of the rewind button. The default value is 3 seconds.
Enter the maximum time (in seconds) that the image and audio times can differ.
The program associates images with audio by comparing an image's EXIF time to the audio file's disk date. For a given image, the associated audio file is the one with the disk date that's closest to the EXIF time. It doesn't matter if the audio time is before or after the image time.
If True, you'll be able to select and associate any type of file (not just audio files) with the images.
To execute the unsupported file types within the program, there must be a program currently associated with the given file extension.
Unless the unsupported file type has a disk date stamp that equates back to the photo (which it probably doesn't), you should also set AudioAutoAssociate to False to prevent the automatic association that occurs when they are loaded. In that case, you'll need to manually associate them.
If True, thumbnail images are used for the Google Earth icons instead of the standard camera or directional icons. This works best when there are only a few images. Otherwise, the map can become very cluttered.
Newly created KML or KMZ files will be automatically launched in the program associated with the file extension you specify.
Since Google Earth associates itself when KML files when it's installed, newly created KML or KMZ files load in Google Earth if KML (the default) is specified. If you want KML files to load into your default ASCII editor, for example, specify TXT for this option.
If True, the waypoints node in Google Earth's left hand pane will be expanded when the KML/KMZ file is opened. The default is False.
If True, the tracklog path node in Google Earth's left hand pane will be selected when the KML/KMZ file is opened, causing the tracklog path to be visible. The default value is False if there are photos and True if there's only a tracklog.
If True, the photo route node in Google Earth's left hand pane will be selected when the KML/KMZ file is opened, causing the photo route to be visible. The default value is False.
If True, the bounding box node in Google Earth's left hand pane will be selected when the KML/KMZ file is opened, causing the bounding box to be visible. The default value is False if there are photos and True if there's only a tracklog.
If True, the tracklog points node in Google Earth's left hand pane will be selected when the KML/KMZ file is opened, causing the tracklog points to be visible. The default value is False if there are photos and True if there's only a tracklog.
If True, the key points node in Google Earth's left hand pane will be selected when the KML/KMZ file is opened, causing the key points to be visible. The default value is False if there are photos and True if there's only a tracklog.
When exporting to Google Earth, if this is True and if the photos have valid EXIF timestamps, a photo timeline will be included in the output.
When exporting to Google Earth, if this is True and if there's a tracklog currently loaded, a tracklog timeline will be included in the output.
When geocoding photos with Google Earth, this is the port through which all communication occurs. If you encounter problems using the default value or if a 3rd party application on your computer prevents the access, try any arbitrary number between 1024 and 32767.
When geocoding photos with Google Earth, this is the local host name with which all communication occurs. This should usually be either (without quotes) "127.0.0.1" or "localhost".
When True and after geocoding a photo in Google Earth, the next image in the set is automatically selected. Setting this to True is equivalent to clicking the Next button after geocoding an image. The default value is False, but you'll probably want to set it to True once you get used to the workflow.
When using the Google Earth Geocoder, this is the default altitude. It's expressed in meters.
Expressed in pixels, this is the width of the thumbnail image on the Google Earth Geocoder form. The corresponding thumbnail height is automatically calculated to maintain the correct aspect ratio. If it's too small, you won't be able to see the image. If it's too big, you'll obstruct your view of Google Earth. The default is 120 pixels.
When True and when geocoding images with Google Earth, the current heading in Google Earth is used for the photo direction. The default value is False.
If specified, this is used for the path to Google Earth when the Google Earth geocoder is launched. If it's blank (the default), the program automatically determines the path.
You should only set this option if the program is unable to automatically locate the Google Earth executable. If that's the case, you'll receive an error message when you try to load the Google Earth geocoder that reads, "The program associated with KML files on this computer 'C:\Program' does not exist or is...'. This happens because of a bug in the Windows FindExecutable API function.
When -1 (the default), the program automatically determines an optimal initial zoom level for Google Maps based on the coverage of the photos and/or tracklog.
You can manually specify the initial zoom by entering a whole number between 0 and 17. The amount of zoom increases with the number.
If True, a map overview window is added to the lower right corner of the Google Maps output.
If True, a small scale is added to the lower left corner of the Google Maps output.
If True, buttons are added to the upper right corner of the Google Maps output that allows selecting different map types.
Enter a number that indicates the type of zoom/pan control to use with Google Maps. 0=none, 1=small (zoom only), 2=medium (zoom and pan), 3=large (zoom and pan).
If True, the mouse's scroll wheel can be used to zoom the Google Maps in and out. The default value is False.
If True, icons are shown over some metropolitan areas that, when clicked, show the current traffic conditions. This option does not add a traffic button to the Google Map, only the icons. The default value is False
If True (the default) and if direction information exists for an image, custom icons will be used with Google Maps that indicate the photo direction.
When the 'Include Dictation' box is checked in a Google Earth or Google Maps description, an HTML link is created and added to the description. This option specifies the text that displays for the link.
The default value is 'Dictation', but you can use any phrase such as 'Click here to listen to the associated audio'.
If specified and if the Flickr account has been previously authorized, it'll be automatically selected when the Flickr upload form is loaded. Loading the account can take anywhere from a few to several seconds, so be patient.
You must specify this option if you intend to automate your Flickr uploads by using the /f command line parameter.
If True and when uploading Flickr photos, the photo's location will automatically be added to Flickr's internal database. This will cause the resulting Flickr photo page to contain 'Map' links that allow you to view the photo locations using Yahoo! Maps.
Note: To use this feature you must first set your Flickr account's default setting for viewing location data. If you haven't done this, you'll be prompted to do so.
If both this and the FlickrGeoAddLocation options are set to True, anyone on Flickr will be able to view the location of your photos.
If both this and the FlickrGeoAddLocation options are set to True, only your Flickr contacts will be able to view the location of your photos.
If both this and the FlickrGeoAddLocation options are set to True, only your Flickr friends will be able to view the location of your photos.
If both this and the FlickrGeoAddLocation options are set to True, only your Flickr family will be able to view the location of your photos.
If True (the default), the image's full local file path is written to the path field. If False, only the file name is written.
You should set this to False if the paths to the images will change after you create the shapefile and if the shapefile and images will reside in the same folder.
When exporting line shapefiles, this is appended to the end of the basename when writing the output files. For example, if the basename is 'Shapefile' and this value is '-lines' (the default), the resulting filenames will be Shapefile-lines.shp, Shapefile-lines.shx, and Shapefile-lines.dbf. This value must differ from the ShapefilePointsFileSuffix setting.
When exporting point shapefiles, this is appended to the end of the basename when writing the output files. For example, if the basename is 'Shapefile' and this value is '-points' (the default), the resulting filenames will be Shapefile-points.shp, Shapefile-points.shx, and Shapefile-points.dbf. This value must differ from the ShapefileLinesFileSuffix setting.
|
