Mobile Crossing WayPoint Map Loader Manual del operador Pagina 102

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 130
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 101
8 fields in the source data, you must have 8 fields selected to put it into as shown in the example screen above. Some
fields like Lat/Lon are inherently doubles and are counted as 2. If you count the commas, there should be one less than
the number of fields. The above example has 5 commas for 6 fields. If, during the import, the program encounters a
waypoint with more or fewer fields, it will announce the fact and allow you to make a decision as to how to proceed.
Files created in Excel sometimes have extra blank fields that do not impact the process, so the proper response would be
Ignore.
The structure of these files is called comma separated variables (CSV) or comma delimited, which means that all fields
are separated by commas. Text fields may be also enclosed with quotation marks but don't have to be. If your text fields
have embedded commas, replace them with something else like periods. Extra commas will shift the data for that
waypoint into inappropriate fields that could mess up the import. The program will complain if the number of commas
encountered on any row is not what it was expecting.
There are 15 fields you can import data into. In some cases, you will find there is no suitable field for the data in the file,
so options are available to 'skip it' or mark it as ‘unknown’ and let it be added to the Comments column. Some of the
newer GPS types allow a user to group waypoints. If you have a large number of waypoints, grouping is a good way to
manage them in the GPS. There is a field for the group name for each waypoint. This is useful in the import and export
of not only waypoints, but routes and tracks too. In these cases, the group field is used for the route or track name.
Note that the longitude might be shown as negative. This is OK and is a standard worldwide convention for West
longitudes. This program uses a non-standard plus sign for West longitudes since the vast majority of our customers are
in the USA and this avoids extra keystrokes. However, when exchanging data between other programs and this one, it is
usually necessary to use the conventional sign. A check box allows you to change the sign if the source uses the other
choice for sign. If the latitude and longitude include non-number parts other than degree, minute and second symbols or
N/S indicators, the program may not be able to handle that. Separate degree and minute fields are a no-no. You can fix
them using Microsoft Excel by creating two extra columns that have a formula to combine the degrees and minutes. For
example, if column A has the Degrees of latitude, column B has the minutes, column C has the hemisphere, etc., then
insert a column G and put in G1 the formula: "=A1 + B1/60". Column G must be formatted for numbers with 5 decimal
places for this case. Then highlight G1 and grab the lower right hand corner and drag it down the column, filling in the
rest of the column. Do the same for Longitude with a column H. When you are done with this, the two new columns for
latitude and longitude should be adjacent in the spreadsheet with latitude first. Then Save the file and import it. You can
mark the columns with the individual degrees and minutes, like A through F in the above example, for skipping in the
import. If you are using Excel for manipulating your data, you will do a Save-As to a Type-of-File called a CSV file for
creating the import file. Once done, you can import the file into SeaMarks.
After importing a Text file, go to: File>File Properties and make sure the center Lat/Lon (and inlet) are set right. The
program will take an estimate of the center if there is Lat/Lon data, or it will use your User Preferences setting, but if the
file contains spurious data, the estimate can be very far off. I have seen many cases of a stray South latitude or East
Longitude in a USA based list and that will greatly effect the calculated center Lat/Lon. If the user did not clear the
waypoints in a new Garmin, then there will be a point in Kansas at their headquarters and ones in Taiwan and Italy too.
Those could mess up the average Lat/Lon. You can also change the file name if desired. If the data was loran and the
Lat/Lon fields (or TD fields) are zero or wrong, don't worry, you can calculate the Lat/Lon (or TDs) using
Tools>Recalculate Lat/Lon (or Tools>Convert to Loran) later.
Vista de pagina 101
1 2 ... 97 98 99 100 101 102 103 104 105 106 107 ... 129 130

Comentarios a estos manuales

Sin comentarios