controlling mechanism, to reduce code duplication between Grid/KaMap/other
layers that need a different grid origin. r=euzuro (Closes#1349)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@6231 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
With this patch you should no longer see tiles loading if your layer is out of
range or not visible. Hopefully! r=crschmidt (closes#937)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5913 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
for the definition of a 'projection' option on a layer. IF this projection
object exists, it will be used to create the format's internal/external
projection options, making it such that any data loaded will be reprojected
to the map's projection automatically. r=pagameba (Closes#1273, #1225, #1269)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5828 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
the Layer.Google constructor, we check if the type we are given is not in the
map's list of types, and if so, add it. (Closes#1082)
r=tschaub
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5504 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
that Andreas has been working so hard on. I think this is the single most
awesome commit I've ever had the pleasure of committing. The results of this
commit are described on http://trac.openlayers.org/wiki/Styles: essentially,
this makes it possible to style features in all kinds of fun ways based on
rules, and will also form the underlying basis for #533. Things this patch
adds:
* OL.Rule classes. These classes allow you to do tests against the propertie
of a feature, and set a style based on these properties -- so you can
compare the 'speedlimit' property of a line, and test if it is > 60, and if
it is greater than 60, render it in a different color. You can also test
combinations of rules using the OL.Rule.Logical class, and test featureids
with the FeatureID class.
* OL.Style class: The OL.Style class lets you wrap up Rules into styles that
can be used with drawFeature to draw the feature in the selected style.
* OL.Layer.Vector.drawFeature will check if the given style is an OL.Style
object, and if so, it will draw the feature accordingly.
examples/georss-flickr.html shows usage of these classes.
Many, many thanks go to Andreas for all his hard work on this: this code really
is very pretty, and includes unit tests for all the classes (and we know that I
am a big fan of tests.)
Three cheers for Andreas: Hip hip, hooray! hip hip, hooray! hip hip, hooray!
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5429 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
the SphericalMercator mixin register two transformations to/from EPSG:900913,
EPSG:4326. Thanks to Tim for the feedback and review. (Closes#1210)
This allows us to transform points to/from SphericalMercator
without proj4js support -- and if other projects need similar functionality,
they can write their own custom transformation functions rather than
modifying proj4js to support some custom projection.
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5410 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
go ahead and commit this (relatively lighttweight) patch to the code so that
the projection library base API is there, even though for the most part, it's
not usable yet. This changes map.projection from being a string to being a
class, with a projCode on it. (Closes#1035)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5401 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
canonical way of transforming data, and we should make sure users feel
comfortable using it.
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5350 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
and our geography doesn't, so the numbers end up off in the north-south
direction when *not* using spherical mercator. Now, if someone comes to use us
and says 'oh my! you ruined me!' we can say 'options! we love options!' and do
a rain dance. (Closes#1164)
git-svn-id: http://svn.openlayers.org/trunk/openlayers@5229 dc9f47b5-9b13-0410-9fdd-eb0c1a62fdaf
