Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators Support and Discussions for Tide Charts and Tide Tables Post 302890009 by Neo on Monday 24th of February 2014 06:07:10 PM
Old 02-24-2014
Support and Discussions for Tide Charts and Tide Tables

This is the discussion thread to ask questions about the tide charts and tables. Please note that all users must register to post here.

List of Supported Tidal Station Maps:


Quote:
Thank you for stopping by.
Google Maps Engine has been discontinued. We want to thank all our loyal Google Maps Engine customers.

Sincerely,

The Google Maps Engine team

Frequently-asked questions
What will happen to my Google Maps Engine data?
All data stored with Google Maps Engine will be systematically deleted from Google servers.

Will there be any way to retrieve my subscription data from Google in the future?
No -- all data stored in Google Maps Engine will be permanently and irrevocably deleted. Google will not be able to recover any Google Maps Engine data for any user after February 1st, 2016.
 

5 More Discussions You Might Find Interesting

1. IP Networking

TCP-IP discussions from 1982 to 1991

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)
Discussion started by: Neo
0 Replies

2. UNIX for Dummies Questions & Answers

Threaded Discussions for Webpages

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)
Discussion started by: evertk
4 Replies

3. Shell Programming and Scripting

Converting tables of row data into columns of tables

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)
Discussion started by: justthisguy
7 Replies

4. What is on Your Mind?

New Buttons to Create New Discussions and Reply to Existing One

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)
Discussion started by: Neo
6 Replies

5. What is on Your Mind?

Disable More Discussions You Might Find Interesting in Mobile View

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
Geo::Coder::Googlev3(3pm)				User Contributed Perl Documentation				 Geo::Coder::Googlev3(3pm)

NAME
Geo::Coder::Googlev3 - Google Maps v3 Geocoding API SYNOPSIS
use Geo::Coder::Googlev3; my $geocoder = Geo::Coder::Googlev3->new; my $location = $geocoder->geocode(location => 'Brandenburger Tor, Berlin'); my @locations = $geocoder->geocode(location => 'Berliner Strasse, Berlin, Germany'); DESCRIPTION
Use this module just like Geo::Coder::Google. Note that no "apikey" is used in Google's v3 API, and the returned data structure differs. Please check also <http://code.google.com/intl/en/apis/maps/documentation/geocoding/> for more information about Google's Geocoding API and especially usage limits. CONSTRUCTOR new $geocoder = Geo::Coder::Googlev3->new; $geocoder = Geo::Coder::Googlev3->new(language => 'de', gl => 'es'); Creates a new geocoding object. The "ua" parameter may be supplied to override the default LWP::UserAgent object. The default "LWP::UserAgent" object sets the "timeout" to 15 seconds and enables the "env_proxy" option. The Geo::Coder::Google's "oe" and "apikey" parameters are not supported. The parameters "region", "language", and "bounds" are also accepted. The "bounds" parameter should be in the form: [{lat => ..., lng => ...}, {lat => ..., lng => ...}] METHODS geocode $location = $geocoder->geocode(location => $location); @locations = $geocoder->geocode(location => $location); Queries $location to Google Maps geocoding API. In scalar context it returns a hash reference of the first (best matching?) location. In list context it returns a list of such hash references. The returned data structure looks like this: { "formatted_address" => "Brandenburger Tor, Pariser Platz 7, 10117 Berlin, Germany", "types" => [ "point_of_interest", "establishment" ], "address_components" => [ { "types" => [ "point_of_interest", "establishment" ], "short_name" => "Brandenburger Tor", "long_name" => "Brandenburger Tor" }, { "types" => [ "street_number" ], "short_name" => 7, "long_name" => 7 }, { "types" => [ "route" ], "short_name" => "Pariser Platz", "long_name" => "Pariser Platz" }, { "types" => [ "sublocality", "political" ], "short_name" => "Mitte", "long_name" => "Mitte" }, { "types" => [ "locality", "political" ], "short_name" => "Berlin", "long_name" => "Berlin" }, { "types" => [ "administrative_area_level_2", "political" ], "short_name" => "Berlin", "long_name" => "Berlin" }, { "types" => [ "administrative_area_level_1", "political" ], "short_name" => "Berlin", "long_name" => "Berlin" }, { "types" => [ "country", "political" ], "short_name" => "DE", "long_name" => "Germany" }, { "types" => [ "postal_code" ], "short_name" => 10117, "long_name" => 10117 } ], "geometry" => { "viewport" => { "southwest" => { "lat" => "52.5094785", "lng" => "13.3617711" }, "northeast" => { "lat" => "52.5230586", "lng" => "13.3937859" } }, "location" => { "lat" => "52.5162691", "lng" => "13.3777785" }, "location_type" => "APPROXIMATE" } }; The raw option may be set to a true value to get the uninterpreted, raw result from the API. Just the JSON data will be translated into a perl hash. $raw_result = $geocoder->geocode(location => $location, raw => 1); region Accessor for the "region" parameter. The value should be a country code ("es", "dk", "us", etc). Use this to tell the webservice to prefer matches from that region. See the Google documentation for more information. language Accessor for the "language" parameter. bounds Accessor for the "bounds" parameter. AUTHOR
Slaven Rezic <srezic@cpan.org> This package is free software; you can redistribute it and/or modify it under the same terms as Perl itself. SEE ALSO
Geo::Coder::Google, Geo::Coder::Many. perl v5.14.2 2011-12-22 Geo::Coder::Googlev3(3pm)
All times are GMT -4. The time now is 08:35 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy