• Home Page
• Documentazione devel
• Documentazione 2.10
• More documentation
• Examples gallery

Esempi:

var layerMapnik = new OpenLayers.Layer.OSM.Mapnik("Mapnik (updated weekly)");

var markers = new OpenLayers.Layer.Markers("Markers");

var pois = new OpenLayers.Layer.Text("My Points", {
    location:"./textfile.txt", projection: map.displayProjection });

var track_style = new OpenLayers.Style();
track_style.strokeColor = "#6636e1";
track_style.strokeWidth = 7;
track_style.strokeOpacity = 0.7;
var object_trk = new OpenLayers.Layer.GML("GPX Track", "track.gpx", {
    format: OpenLayers.Format.GPX,
    style: track_style,
    projection: map.displayProjection});
map.addLayer(object_trk);

var gsat = new OpenLayers.Layer.Google(
    "Google Satellite", {type: G_SATELLITE_MAP, numZoomLevels: 20});

Several imagery sets exists from NASA, among them:

• Blue Marble next generation (1 pixel = 500×500 m)
• Land Sat 7 (1 pixel = 15×15 m)

The original Blue Marble images came from MODIS, the spectroradiometer aboard of Terra and Aqua satellites. Blue Marble Next Generation added more spatial resolution.

http://onearth.jpl.nasa.gov/

OnEarth WMS server by NASA offers a standard WMS service plus a “Tiled WMS” (prerendered tiles).

• http://onearth.jpl.nasa.gov/wms.cgi?request=GetCapabilities
• http://onearth.jpl.nasa.gov/wms.cgi?request=GetTileService

NASA World Wind

World Wind is a software (open source but MS-Windows only) developed by NASA which allows to pan and zoom into several raster datasets offered by NASA servers. World Wind uses (among others) Blue Marble imagery.

The same imagery server can be used by other software, e.g. OpenLayers via the OpenLayers.Layer.WorldWind() function.

• Tiled WMS

This is an extension to the standard WMS protocol, the capabilities of such services are exposed at:

• http://onearth.jpl.nasa.gov/wms.cgi?request=GetTileService

Some of the tags announced by the service are:

We want to refresh the contents of a layer using a timer, every time we want to fetch new data from the server.

This is an example of a GeoRSS layer, updated every 120 seconds. Every point is drawn with the same icon, a pop-up will appear when the icon is clicked.

var friends;
 
function init() {
    ...
    // Add tangoGPS friends layer.
    friends = new OpenLayers.Layer.GeoRSS("Friends", "tangogps-friend.php", {
        projection: map.displayProjection
    });
    friends.icon = new OpenLayers.Icon(
        "icons/tangogps-friend.png");
    map.addLayer(friends);
    ...
    var tim = setInterval ("updateFriends()", 120000);
}
 
function updateFriends() {
    friends.clearMarkers();
    friends.clearFeatures();
    friends.loaded = false;
    friends.loadRSS();
}

The code tangogps-friend.php should return GeoRSS formatted text (like this example), with proper expire and no cache headers:

header("Cache-Control: no-cache, must-revalidate");
header("Expires: Sat, 26 Jul 1997 05:00:00 GMT");
header("Content-Type: text/xml");
...

This is a more complex example, using a GML layer in GML format. The GML geometry is drawn with the default style. The layer is reloaded by a timer every 120 seconds. We use a BBOX strategy, so that the layer is reloaded also when the bounding box changes. Layer is loaded via HTTP protocol.

var friends;
 
function init() {
    ...
    // Add tangoGPS friends layer.
    friends = new OpenLayers.Layer.GML("GML", "friends-gml.php", {
        strategies: [new OpenLayers.Strategy.BBOX()],
        projection: map.displayProjection,
        protocol: new OpenLayers.Protocol.HTTP({
            url: "friends-gml.php",
            format: new OpenLayers.Format.GML()
        }),
    });
    map.addLayer(friends);
    ...
    var tim = setInterval ("updateFriends()", 120000);
}
 
function updateFriends() {
    var now = new Date().valueOf();
    var bbox = map.getExtent().toBBOX();
    friends.setUrl("friends-gml.php?bbox=" + bbox + "&time=" + now);
}

The friends-gml.php should return a valid GML file (like this example) and it should be non cacheable (using the same headers of GeoRSS layer above). The script will be called with the following arguments:

friends-gml.php

The first call (without query parameters) is triggered by the second argument of the layer constructor. To optimize memory usage in the browser, the script friends-gml.php should honor the bbox request and return only the relevant features. Called without the parameter, it can return no features.

friends-gml.php?bbox=-10.77,41.32,11.72,52.57

Immediately after the layer creation, a new call is triggered by the BBOX strategy. This time the bbox parameter is automatically appended to the url declared with OpenLayers.Protocol.HTTP. A similar call is performed whenever a bounding box change event is detected.

friends-gml.php?bbox=-15.15,44.13,16.12,49.75&time=1232668479793

Every timer interval, the layer is refreshed. Reading new data is forced by setting a new and unique time parameter. In this case bbox is not automatically added (it was the timer which trigger the call, not the BBOX strategy), so we have to add it programmatically.

This is a very versatile example: every point can be represented by a different icon, a pop-up appears when you click an icon. The disadvantage is that all the layer features are loaded at every timer interval, no bounding box limit is enforced.

var friends;
 
function init() {
    ...
    // Add tangoGPS friends layer.
    friends = new OpenLayers.Layer.Text("Friends", {
        location:"friends-text.php",
        projection: map.displayProjection});
    map.addLayer(friends);
    ...
    var tim = setInterval ("updateFriends()", 120000);
}
 
function updateFriends() {
    // Remove markers and features.
    friends.clearMarkers();
    friends.clearFeatures();
    // Pretend the layers is not yet loaded.
    friends.loaded = false;
    friends.location = "friends-text.php";
    friends.loadText();
}

The text returned by friends-text.php should be non cacheable as always and contains a tab separated text, like this example.

This recipe can be improved by adding a bbox parameter (calculated at runtime) to the location of the layer, and forcing a call to updateFriends() whenever the viewport of the map changes.

Il rapporto di scala tra la mappa principale e l'overview fornita dall'oggetto OpenLayers.Control.OverviewMap() è controllato dalle proprietà minRatio e maxRatio.

Per entrambi i valori si intende il rapporto overview_map_resolution / main_map_resolution. Se la mappa è in metri la risoluzione si misura in metri/pixel.

Il valore di minRatio deve essere minore di maxRatio.

Se ad esempio si impostano i seguenti valori:

minRatio: 2.0
maxRatio: 10.0

il rettangolo che evidenzia l'estensione nella overview potrà variare dalla metà dell'estensione dell'overview fino a un decimo. Oltre questi limiti l'overview viene zoommata opportunamente.

OpenLayers supporta nativamente alcuni sistemi di riferimento, per cui è posibile fare la riproiezione al volo di layer vettoriali. Tra i sistemi supportati notiamo:

• EPSG:900913
• EPSG:4326

Per supportare altri sistemi di riferimento è possibile definirli nel codice JavaScript, ad esempio ( da verificare):