So you never see white boundaries.

I believe this is because of wrong string id used.

We treated _init method kind of special which I didn't really like since it could cause confusions to the developers. Also, along with it fixed some other bugs.

This is a fairly big file to put into the javascript source. If it is needed somewhere, I would suggest we include it as a separate json file and load it on demand.

At the moment, there is a function in the renderer class worldToDisplay. In my mind, this should convert from latitude/longitude into display pixel coordinates; however, it seems to be converting from GCS (mercator, for the currently implemented OSM base layer) to pixel coordinates. For the pointFeature class, the code performs the world to GCS conversion on call to positions, which is opaque to both the user and the renderer. I think makes more sense to have renderer.worldToDisplay moved to renderer.gcsToDisplay, unless I am misunderstanding something.

I understand the need to have coordinates used in features stored internally in GCS coordinates (i.e. making it possible to make shapes) as it is now, but for external layers, like the GRITS jquery plugin I am making, it makes adding geocoded features difficult.

The div will be created and managed by the layer.

@jbeezley @cjh1 please review this branch: implement_plane_feature_new_api

README.md, LICENSE, etc. missing. Also gh-pages branch is just using a GitHub template right now.

It seems that we are applying translation two times. First using the group node, second directly applying translation to the points.

In this commit 7325742, I have add a jQuery like interface for binding and triggering events. The idea is that classes will interact with each other like this (for example panning in the layer class)

this.map().on(geo.event.pan, function (arg) {
  if (arg.layer !== this) {
    this.trigger(geo.event.pan, arg);
  }
});
this.on(geo.event.pan, function (arg) {

  // layer specific implementation here

  this.map().trigger(geo.event.pan, arg);
});

The only problem is that this kind of propagation through the tree will have to be coded for every event type. I'm wondering if it might be useful to add standard parent/children attributes to the object, then the map would copy its layers into children and layer would put the map in parent and the renderer in children, etc. This way we could implement this generically in geo.object. Also, we would want to bind the triggerer to this in the handler to prevent circular propagation. What does everyone think?

There are other features that could be implemented as well like namespacing of handlers, but I think that could be added later if needed.

Make it easy to set up an openstreetmap tile server

Like openstreetmaps, mapquest, etc.

This would eliminate the problem of dragging outside the view and releasing the mouse. That action currently drops the mouseup and will continue the drag or zoom movement when the user's mouse hovers back into the view.

Needed for geoweb issue 29.

References #10

This will be low priority for now as we need some other features to get in before we can tackle this.

Currently seems to only be pixel perfect at the fully zoomed out threshold for a layer, so the layer is always super-sampled, which can get bad-looking just before another layer appears when zooming in. Seems a better default would be to start with a subsampled layer, move to pixel perfect, then supersample for the remaining half of the level while zooming in. There could be a parameter that adjusts where the pixel-perfect level is reached (e.g. have a 0 to 1 continuous setting where 0 = always subsample, 1 = always supersample, and the default is 0.5).

Currently we do this:

foo.setBar(10);
foo.setLength(20);
foo.bar()

Instead we want to do this:
foo.bar(10).length(20);

But we don't want to write each function where we would have to check
for the argument.

Approved and merged into master

This should boost the performance of the tile rendering

Let the user zoom on mousewheel. This might be an option that can be turned off in case the map is part of a page that can be scrolled.