OpenLayers OpenLayers

Ticket #389 (reopened feature)

Opened 2 years ago

Last modified 10 months ago

Custom Google Maps Tile Layer

Reported by: crschmidt Assigned to:
Priority: blocker Milestone: Future
Component: Layer Version:
Keywords: custom google layer Cc:
State:

Description

It appears that Google's custom tile layer support sends 3 parameters (zoom, tile x/y, something else) to a function which is set to customTileURL in order to get custom tile layers.

OpenLayers should be able to create a CustomGoogle layer which would replicate this behavior exactly with a certain setup. This would let us load tiles from any CustomMapTile service for Google.

Change History

04/05/07 14:11:55 changed by sderle

  • milestone set to 2.5 Release.

06/07/07 15:33:11 changed by sderle

actually one can accomplish this by sending a suitable function as the getURL option to the Layer.TMS constructor. should this actually be formalized or documented somewhere (perhaps in a FAQ)?

06/07/07 15:38:31 changed by sderle

  • priority changed from minor to blocker.

08/03/07 12:12:30 changed by crschmidt

  • milestone changed from 2.5 Release to 2.6 Release.

10/06/07 21:36:23 changed by crschmidt

  • status changed from new to closed.
  • resolution set to fixed.
  • milestone changed from 2.6 Release to 2.5 Release.

UsingCustomTiles

10/08/07 21:10:14 changed by euzuro

  • keywords set to custom google layer.
  • resolution deleted.
  • status changed from closed to reopened.
  • component changed from general to Layer.
  • milestone changed from 2.5 Release to Future.

Chris and I discussed this and agreed that this might be worth looking into formalizing a bit. The wiki page he's created is great and provides a functional solution to the problem.

At some point in the future, however, we might want to make a stronger effort to attract people making custom google layers to use an OpenLayers / TileCache setup.

We could make an OpenLayers.Layer.GoogleCustom layer or something that does this automatically by subclassing TMS and taking a standard 'getURL' function as an input option.... or something like that.

Sliding this into the "Future" bucket as it doesn't appear there's any immediate interest in this feature.