OK, I've got around six tidal station maps done, which is enough for now.
Tidal Stations for Australasia and the Far East.
Tidal Stations for North America (East Coast and Gulf of Mexico).
Tidal Stations for North America (West Coast).
Tidal Stations for Europe and Africa.
Tidal Stations for South America.
Tidal Stations for the Ocean Tropics.
So, I took a look at your data, and saw you have all the info you need and more in your SQL statement.
What you must do is to convert the data fields you want to put on the Google Maps Engine in CSV format. Here is an example from our data:
Moderator's Comments:
Sample data removed due to misuse.
Note in the first line, to plot on the map using coords, you must label the two fields in the header, exactly:
Code:
Lon, Lat
If you go with the "free" version of Google Maps Engine, you can only import 100 points per map (or map layer); but if you pay $5 USD a month, you can put up to 2000 points per map (map layer).
For over 2000 points per map (layer) you must contact Google and talk pricing.
We pay $5 a month for the 2000 points per map (layer) option, so if you want me to display a test map of your buoys for you, please upload a CSV file with 2000 points or less and I am happy to do it for you.
Found this archive on the net: TCP-IP discussions from 1982 to 1991.... very interesting reading!!
http://www-mice.cs.ucl.ac.uk/multimedia/misc/tcp_ip/ (0 Replies)
Dear All,
I run a website for a non-profit. Does anyone know where I can get free or cheap software to run threaded discussions for our website?
Our website is obviously running off a unix platform.
Thanks (4 Replies)
I am trying to transpose tables listed in the format into format. Any help would be greatly appreciated.
Input:
test_data_1
1 2 90%
4 3 91%
5 4 90%
6 5 90%
9 6 90%
test_data_2
3 5 92%
5 4 92%
7 3 93%
9 2 92%
1 1 92%
...
Output:... (7 Replies)
You may have noticed a lot of big blue buttons" on the site, replacing the Font Awesome icons for creating new discussions and replying to discussions.
Here are the reasons for this change:
A number of unix.com moderators, including Don Cragun and Ravinder Singh, have commented that new... (6 Replies)
Hi,
for quite a while this feature "xxx More Discussions You Might Find Interesting" is added below a topic here.
For desktop view this is ok. I didn't make use of it so far, but it isn't disturbing me either.
In mobile view however it's annoying me, because when I scroll down to the end... (3 Replies)
Discussion started by: stomp
3 Replies
LEARN ABOUT REDHAT
auto.master
AUTO.MASTER(5) File Formats Manual AUTO.MASTER(5)NAME
/etc/auto.master - Master Map for automounter
DESCRIPTION
The auto.master map is consulted when the autofs(8) script is invoked to set up the necessary mount points for the automounter. Each line
in this file describes a mount point and points to another file describing the file systems to be mounted under this mountpoint. The access
to those maps is governed by a key.
Access to an automounted file system is customarily done using the path scheme:
/mountpoint/key/path/file,
where the mountpoint will be listed in the auto.master configuration file. The key is matched in the map file pointed to by the master map
(See autofs(5)). The path and the file are referring to the file on the file system mounted.
FORMAT
The file has three fields separated by an arbitrary number of blanks or tabs. Lines beginning with # are comments. The first field is the
mount point. Second field is the map file to be consulted for this mount-point. This field is of the form maptype:mapname, where maptype
is one of the supported map types (file, program, yp, nisplus, hesiod, userdir, ldap), and mapname is the name of the map. The third field
is optional and can contain options to+ be applied to all entries in the map. Options are cumulative, which is a difference from the behav-
ior of the SunOS automounter.
The format of the map file and the options are described in autofs(5).
EXAMPLE
/home /etc/auto.home
/misc /etc/auto.misc
/mnt yp:mnt.map
This will generate three mountpoints /home, /misc, and /mnt. All accesses to /home will lead to the consultation of the map in
/etc/auto.home, all accesses to /misc will consult the map in /etc/auto.misc, and all accesses to /mnt will consult the NIS map mnt.map.
SEE ALSO automount(8), autofs(5), autofs(8).
AUTHOR
This manual page was written by Christoph Lameter <chris@waterf.org>, for the Debian GNU/Linux system. Edited by <hpa@transmeta.com>.
19 Jun 2000 AUTO.MASTER(5)
02-25-2014
