OpenLayers is set up to use Proj4js internally which will do the
coordinate conversion for you on the client side.. Have a look at
http://trac.osgeo.org/proj4js/
Mike
On 7/20/2010 9:23 AM, Subhani Minhas wrote:
Hello All, I recently came across, the site
Zoran,
It looks like you are using Proj4js where it dynamically loads the
required projection code files. In some earlier versions of Proj4js
that had problems in IE (possibly in Chrome as well) but I think that is
fixed in the latest version. In any case, you can get around the issue
by
Zac,
I've done that for the color and graphic like so:
var HLDefaultStyle = new OpenLayers.Style({
fillColor: '${getStatusColor}',
graphicName: '${getStatusShape}',
pointRadius: 4
}, {
context: {
Heiko,
The problem might be that the implementation of the ortho code in
Proj4js hasn't been validated yet (see the bottom of this page
http://trac.osgeo.org/proj4js/wiki/UserGuide). However there is a bug
report with a proposed fix in the trac system
Note also that the UTM transformations are not built into OpenLayers so
you will also need to:
- include the Proj4js library in a script tag
- include the projection definition for EPSG:25832
Proj4js.defs[EPSG:25832] = +proj=utm +zone=32 +ellps=GRS80 +units=m
+no_defs;
Mike
Mapmaker wrote:
At the moment, no it's not possible to disable that, however if all your
projection definitions are properly loaded, it should never get to the
part where it calls spatialreference.org.
That said, to make sure it never gets called, comment out the call to
Proj4js.loadScript in the
First thing to check is that you don't have any extraneous commas in
your JSON structures, eg.:
var jsonData = {
propertyA: valueA,
propertyB: valueB, --- this comma will break IE
};
Mike
J. Brian Adams wrote:
I have written several OL applications that work well on OS X using
Firefox,
If that fixed it then all you should need is like this:
script src=./proj4js/lib/proj4js-compressed.js/script
script src=./proj4js/lib/defs/EPSG2913.js/script
merc.js and lcc.js are included in the proj4js-compressed.js version and not in
proj4js.js
Mike
Dash wrote:
Thanks for the quick
If I recall correctly when I was doing something similar, IE didn't
accept fractions in the symbol definition. Scaling it up so that all
points were integers solved the problem.
Mike
Andreas Hocevar wrote:
Thanks for the symbol defs, these still render incorrectly in IE indeed.
#1836 needs
I'm testing with that patch in the application I'm currently working on
and for the most part it is a big improvement. The one remaining issue
I'm seeing is feature labels don't show up in IE7 with the document in
IE7 standards mode. Labels do show up in IE7 in quirks mode though.
(Isn't it
= OpenLayers.Util.upperCaseObject(layers.params) then use
it with upper cases parameters could do the trick.
Anyway, thanks again and keep up the good work.
Alexandre
Mike Adair wrote:
I've added an example of using the WFS DescribeFeatureType response
to create a form in my sandbox at:
http
[1] http://trac.openlayers.org/wiki/Addins
Mike Adair wrote:
I did a EditFeatureAttributes control a few months ago that first did
a WFS DescribeFeatureType query to determine the attributes for a
feature type and then created a form with inputs for each attribute.
It registered
Mike Adair wrote:
I did a EditFeatureAttributes control a few months ago that first did
a WFS DescribeFeatureType query to determine the attributes for a
feature type and then created a form with inputs for each attribute.
It registered with featureAdded and featureSelected events on the WFS
there is an example online anywhere yet but I could
probably put the code somewhere if you were interested.
Mike Adair
Stephen Woodbridge wrote:
Hi all,
Does anyone have a public page/example that demonstrates creating a
point feature and adding text attributes to it? This seems like it would
And you also need to include proj4js (http://trac.osgeo.org/proj4js/)
and and definition for EPSG:42304. There is an example included in the
recently updated graticule patch v2 for this
http://trac.openlayers.org/ticket/1083
Mike
Eric Lemoine wrote:
On Monday, May 18, 2009,
It's marked for review and with the 2.8 milestone, so hopefully this
will get in the next release.
Mike
gingerbbm wrote:
Thanks Mike.
Mike Adair wrote:
there is a patch available for the OL MapGuide layer that removes the
asynchronous behaviour
How long is it likely
I'm not sure of the performance differences between between WMS and the
MapGuide layer, but there is a patch available for the OL MapGuide layer
that removes the asynchronous behaviour in the MapGuide Layer. See:
http://trac.openlayers.org/ticket/1756. This is currently marked for
review in
EPSG:4326 is included in Proj4js by default, EPSG:900913 isn't but I've
just updated Proj4js to include it now,
http://trac.osgeo.org/proj4js/ticket/20. If you are including
Proj4js.defs elements, make sure they are put after Proj4js.js. There
is a Proj4js.libPath property but it should be
Proj4js wiki and download is here: http://trac.osgeo.org/proj4js/. That
is only for transforming point coordinates on the client side, it can't
help you with re-projecting raster images.
EPSG:21781 uses the somerc projection which I've been able to verify
that it is working correctly with a
There is a Trac instance setup for Proj4js at
http://trac.osgeo.org/proj4js/ where you can file tickets. I've also
put up a 1.0 release candidate there for testing recently. As for
getting laea working (and the others not validated) I would like to get
those fixed for the final release, it
There are several of the projection classes that haven't been validated
with test points yet in Proj4js. I will post a list of those that have
been validated and not validated on the wiki, but the list is
currently in the file tests/staticLoad.html. I seem to recall that all
of the ones
WMS animations is implemented in the MapBuilder project (which uses the
OpenLayers library). See:
http://demo.communitymapbuilder.org/demo/mapbuilder/demo/timeSeries/index.html
(one of the WMS servers used by the demo is down, but the animation
layers are up).
Mike
Jon Blower wrote:
Hi
Note that you can also load the file lib/proj4js-compressed.js which
includes all files required (or lib/proj4js-combined.js if you want to
debug) and the libPath setting is not used.
Mike
Alessio Di Lorenzo wrote:
Hi list,
with the precious suggestions of Giovanni Allegri I solved this
I just encountered something similar with the latest MS4W. I was
getting an error on the image requests:
loadForm(): Web application error. Invalid mode.
but when I change the MapServer URL from 'localhost' to
http://127.0.0.1/cgi-bin/mapserv.exe
it worked, not at all sure why.
Mike
just an email typo perhaps but in your Map constructor below you are
using EPSG:23345, not 2345 as described in your message.
Mike
Xin wrote:
Is your marker projected?
If not, see
http://crschmidt.net/~crschmidt/spherical_mercator.html#reprojecting-points
John,
Please note that EPSG:3573 uses an laea projection which is supported in
proj4js, but the code is from the GCTPC package which only supports the
spherical form of laea. That will get you close to the correct coords
but not an exact transformation. What needs to happen to fix this is a
Hufjan,
It looks like the SRS input fields on that form need an onchange event
to load the projection definition, i.e. just typing in a SRS code in the
field doesn't create the Proj4js object required, that only gets created
by selecting a code from the drop down list.
We can fix that, but
I just tested by creating a tiled version of the Sheboygan sample
dataset with 8 zoom levels and it worked fine:
var extent = new
OpenLayers.Bounds(-87.865114442365922,43.665065564837931,-87.595394059497067,43.823852564430069);
var tempScales =
EPSG:23030 is a UTM projection, so yes it is supported.
Mike
David E. Reksten wrote:
Take a look at:
http://spatialreference.org/ref/epsg/23030/
http://spatialreference.org/ref/epsg/23030/proj4js/
.david
On 13/02/2008, Ruben Pardo [EMAIL PROTECTED] wrote:
hi,
does proj4js support
Lance Dyas wrote:
Mike Adair wrote:
EPSG:3003 uses a tmerc projection and is supported by Proj4js. Did
you remember to include the Proj4js library with a script tag in
your application?
Mike
___
Users mailing list
Users
:
Mike Adair wrote:
EPSG:3003 uses a tmerc projection and is supported by Proj4js. Did you
remember to include the Proj4js library with a script tag in your
application?
Mike
___
Users mailing list
Users@openlayers.org
http://openlayers.org
That error is normal and expected. What happens is that proj4js first
tries to load the projection definition from the local server and if it
can't find it (that's the error you see) it will try to look it up from
spatialreference.org. However to do that you need to define a proxy
script
Note that this should work too, and allows you to handle points in
coordinate systems other than EPSG:4326:
- include proj4js in your app via the script tag
- then:
preFeatureInsert = function(feature) {
var src = new OpenLayers.Projection('EPSG:4326');
var dest = new
I've added a test point for EPSG:27700 to proj4js and it is accurate to
less than a mm. I was encountering a problem in that the proj4 C code
codes the datum name as 'OSGB36' whereas spatialreference.org is
returning 'OSB36', not sure why. In any case I've added an alias for
that in proj4js
work!
Steve
On 12/24/2007 at 10:04 AM, in message [EMAIL PROTECTED], Mike
Adair [EMAIL PROTECTED] wrote:
Steve,
I've updated Proj4js with the proj4 version of the stereographic
projection and my test point now comes out at the correct location.
You can get the update
Steve,
I've updated Proj4js with the proj4 version of the stereographic
projection and my test point now comes out at the correct location.
You can get the update at
https://svn.codehaus.org/mapbuilder/cscs/trunk/proj4js/lib and use the
file proj4js-compressed.js (or proj4js-combined.js if
Steve,
Many (or most) of the projection class code hasn't been tested or
validated yet in Proj4js, and I'm seeing some issues with datum
transformations that I'm trying to track down, so it's not ready yet for
every projection that might be thrown at it. UTM, transverse mercator
and LCC
We had to implement an override of the Layer.Grid.initGriddedTiles
method for the MapGuide Layer since the tile origin for MGOS is
upper-left. (See
http://svn.openlayers.org/sandbox/madair/lib/OpenLayers/Layer/MapGuide.js)
That could easily be implemented using an option on the Layer.
Mike
Try this?
(-111.7, 40.3, -111.6, 40.4)
swapping your min/max x values.
Mike
miles wrote:
Tim Schaub wrote:
Hey-
miles wrote:
How can a simple jpeg image map be added as a layer(assuming the lat
long corner pts are known) so that clicking on the layer can return lat
Mike Adair wrote:
FYI, I'm hoping to have the Proj4js (or cscs) library finished up in a
few weeks so you should also be able to use that to convert point coords
between projections, and do the math in map projected space.
Proj4js is a port of Proj4 to Javascript, and will use
Hi,
On the subject of coordinate transformations, I'd like to propose
incorporating Proj4js into OpenLayers for coordinate transformations
like this. Proj4js is a JavaScript port of the Proj4 C library
(currently called cscs in the MapBuilder svn:
http://svn.codehaus.org/mapbuilder/cscs and
Yes cscs did have that problem. However the Proj4js version loads only
the projection class code required based on the projection definition so
you never need to worry about that. If you know beforehand what
projections your app will be dealing with, you can also load the code
statically.
42 matches
Mail list logo