From eric.c2c at gmail.com Sat Sep 1 10:11:36 2007 From: eric.c2c at gmail.com (Eric Lemoine) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Fwd: [OpenLayers-Commits] r4148 - in trunk/openlayers/tests: . Handler In-Reply-To: <20070830235604.C9381B31BD@openlayers.org> References: <20070830235604.C9381B31BD@openlayers.org> Message-ID: <5ec103de0709010711x36ea483u96978a0ed76887d0@mail.gmail.com> Hi In case this was missed, I added tests for the Feature Handler a while back. -- Eric ---------- Forwarded message ---------- From: commits@openlayers.org Date: Aug 31, 2007 1:56 AM Subject: [OpenLayers-Commits] r4148 - in trunk/openlayers/tests: . Handler To: commits@openlayers.org Author: tschaub Date: 2007-08-30 19:56:04 -0400 (Thu, 30 Aug 2007) New Revision: 4148 Added: trunk/openlayers/tests/Handler/test_Feature.html Modified: trunk/openlayers/tests/list-tests.html Log: adding basic tests for the feature handler Added: trunk/openlayers/tests/Handler/test_Feature.html =================================================================== --- trunk/openlayers/tests/Handler/test_Feature.html (rev 0) +++ trunk/openlayers/tests/Handler/test_Feature.html 2007-08-30 23:56:04 UTC (rev 4148) @@ -0,0 +1,88 @@ + + + + + + +
+ + Modified: trunk/openlayers/tests/list-tests.html =================================================================== --- trunk/openlayers/tests/list-tests.html 2007-08-30 23:25:49 UTC (rev 4147) +++ trunk/openlayers/tests/list-tests.html 2007-08-30 23:56:04 UTC (rev 4148) @@ -71,6 +71,7 @@
  • Control/test_Permalink.html
  • Control/test_Scale.html
  • test_Handler.html
  • +
  • Handler/test_Feature.html
  • Handler/test_MouseWheel.html
  • Handler/test_Keyboard.html
  • Handler/test_Drag.html
  • _______________________________________________ Commits mailing list Commits@openlayers.org http://openlayers.org/mailman/listinfo/commits From ahhughes at gmail.com Sun Sep 2 21:23:40 2007 From: ahhughes at gmail.com (Andrew Hughes) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #686: Treat Google Layer as projected data In-Reply-To: <20070831203041.GA31208@metacarta.com> References: <053.3cdb7d9be1072ed94fe4948f38d1c85b@openlayers.org> <062.3c6f533b6db25b092d4a1edc2d5a2851@openlayers.org> <20070831203041.GA31208@metacarta.com> Message-ID: <5f528cf40709021823y483b8c3axf95bc4a3d589ba38@mail.gmail.com> Sounds good to me! Just a consideration here... is there any way to easily limit the maxExtent of commercial coverage? Because I can see the zoom levels and the max/min resolutions... but this does not limit the coverage, just the scale of the 'entire earth'*. I know that people would really need to pick a maxExtent that is relative to the 900913 grid. I'm sure calculating this is most certainly possible, just wondering if this option could be addressed with the proposed API in the future. I think it can, but I'd like the clarification of others. --AH On 9/1/07, Christopher Schmidt wrote: > > On Fri, Aug 31, 2007 at 08:18:50PM -0000, OpenLayers wrote: > > #686: Treat Google Layer as projected data > > > I don't know how much testing we want to do on this, but I'm tapped out > on > > it: for now, marking review just to garner comments from anyone > interested > > in the code. This is just a diff between > > http://dev.openlayers.org/sandbox/tschaub/google/ and trunk -- The code > > can be checked out from: > > > > http://svn.openlayers.org/sandbox/tschaub/google/ > > > > and the way you use it is to set: > > > > sphericalMercator: true > > > > as an option on the layer. > > > > I think this is going to be the final API: the GoogleMercator layer is > > going to go away, and it's just going to be an option on the layer. > > Essentially, this is probably now API complete: > * You create your map with a maxExtent in spherical-mercator projected > meters. > * You add a Commercial base layer to that map with the > 'sphericalMercator': true option set. > * You add overlays to that map. > > This means that your overlays must support EPSG:900913 (or you can > override it after creating your layer if they support it via some other > number) -- the proj4/WKT is in the SphericalMercator.js file (which will > also show in the docs once this is in trunk). > > The canonical example is: > > > http://dev.openlayers.org/sandbox/tschaub/google/examples/spherical-mercator.html > > Tim's put together a number of different layers here, demonstrating the > functionality of the layer with a TileCache-powered WMS overlay, to > demonstrate that yes, Virginia, there really is a Google layer you can > lay TileCache down on top of. > > Now is the time for API complaints -- and also the time for tests, if > you want to write them. Things which could use testing: > * In the test_SphericalMercator.html file, add functions for > initialization of each: > * Google > * VirtualEarth > * Yahoo > and ensure that: > * If sphericalMercator is set, they have inverse/forward proj > functions > * RESOLUTIONS is set to appropriate values if sphericalMercator is > set > * If sphericalMercator is not set, those layers dont have the > inverse/forward projection functions > * if sphericalMercator is not set, units aren't touched > * Create a test in SphericalMercator.html for checking tha > initMercatorParameters sets the proper units, and resolutions based > on MIN_ZOOM_LEVEL and MAX_ZOOM_LEVEL. > > If you've got a sandbox account, feel free to commit tests directly into > the sandbox. > > Questions? Comments? Complaints? > > Regards, > -- > Christopher Schmidt > MetaCarta > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070903/c8de5067/attachment.html From richard.thurbin at cloudamber.com Mon Sep 3 07:04:27 2007 From: richard.thurbin at cloudamber.com (Richard Thurbin) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Large Vector Layer In-Reply-To: <20070817131619.GA1861@metacarta.com> References: <46C492F2.5030507@hostgis.com><5ec103de0708170602v17c7c7fakf661678731496859@mail.gmail.com> <20070817131619.GA1861@metacarta.com> Message-ID: <46DBEA3B.2020206@cloudamber.com> An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070903/d7530c7e/attachment.html From crschmidt at metacarta.com Mon Sep 3 10:20:05 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #686: Treat Google Layer as projected data In-Reply-To: <5f528cf40709021823y483b8c3axf95bc4a3d589ba38@mail.gmail.com> References: <053.3cdb7d9be1072ed94fe4948f38d1c85b@openlayers.org> <062.3c6f533b6db25b092d4a1edc2d5a2851@openlayers.org> <20070831203041.GA31208@metacarta.com> <5f528cf40709021823y483b8c3axf95bc4a3d589ba38@mail.gmail.com> Message-ID: <20070903142005.GC27048@metacarta.com> On Mon, Sep 03, 2007 at 10:53:40AM +0930, Andrew Hughes wrote: > Sounds good to me! > > Just a consideration here... is there any way to easily limit the maxExtent > of commercial coverage? Because I can see the zoom levels and the max/min > resolutions... but this does not limit the coverage, just the scale of > the 'entire > earth'*. I know that people would really need to pick a maxExtent that is > relative to the 900913 grid. I'm sure calculating this is most certainly > possible, just wondering if this option could be addressed with the proposed > API in the future. I think it can, but I'd like the clarification of others. Should work in the normal way, with a maxExtent: new OL.Bounds() in the map options. Regards, -- Christopher Schmidt MetaCarta From emanuel at intevation.de Mon Sep 3 11:38:35 2007 From: emanuel at intevation.de (Emanuel =?utf-8?q?Sch=C3=BCtze?=) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Thesis about Smart Map Browsing & OpenLayers online Message-ID: <200709031738.35414.emanuel@intevation.de> Hi list, in the last months I wrote my thesis about the new term "Smart Map Browsing" (used for the usability of web mapping applications). One part of the work was the analysis of 11 selected Free web mapping applications and Google Maps. I published the work (available in german and english!) on this website: http://www.smartmapbrowsing.org/index_en.html For the practical part of this thesis I have realized the animated zooming feature for OpenLayers [1]. You find a live demo on my thesis website. The complete subject of the thesis: "Current state of technology and potential of Smart Map Browsing in web browsers - using the example of the Free web mapping application OpenLayers" About me: I studied multimedia technology in Bremen/Germany and I wrote my thesis at the Free software company Intevation GmbH in Osnabrueck/Germany. Special thanks go to the OpenLayers community for your help while my realization of the animated zooming feature! I'm looking forward to getting feedback. Best regards, Emanuel PS: Sorry for cross-posting. [1] http://trac.openlayers.org/ticket/442 From louvy.joseph at gmail.com Mon Sep 3 11:54:25 2007 From: louvy.joseph at gmail.com (louvy.joseph@gmail.com) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Some of the WMS tiles not getting refreshed Message-ID: <46DC2E31.7080504@gmail.com> Has anybody seen this behavior? I have lot of dynamic content on the server (i.e. geoserver); hence the WMS content is supposed to change all the time. When I refresh my WMS layer, 5% of the time, some of the tiles don't get refreshed. And these tiles are random. Rest of the tiles get refreshed fine. Has anybody seen this behavior? What could be happening? When I look at the WMS requests in my firebug, browser doesn't seem to generate the WMS tile requests in the first place (but I could be wrong on this fact). Any tips appreciated on how to debug? (I don't have any tilecache configured. It is plain geoserver to openlayers configuration. BTW, I don't have a public facing example to publish to the mailing list) Thanks in advance.. Louvy From aaime at openplans.org Mon Sep 3 13:22:48 2007 From: aaime at openplans.org (Andrea Aime) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Some of the WMS tiles not getting refreshed In-Reply-To: <46DC2E31.7080504@gmail.com> References: <46DC2E31.7080504@gmail.com> Message-ID: <46DC42E8.1090007@openplans.org> louvy.joseph@gmail.com ha scritto: > Has anybody seen this behavior? I have lot of dynamic content on the > server (i.e. geoserver); hence the WMS content is supposed to change all > the time. When I refresh my WMS layer, 5% of the time, some of the tiles > don't get refreshed. And these tiles are random. Rest of the tiles get > refreshed fine. Hum, quick sanity check... in GeoServer your feature types aren't configured with cache headers enabled right? Shouldn't be it, but checking does not cost much.... Cheers Andrea From crschmidt at metacarta.com Mon Sep 3 16:44:44 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Some of the WMS tiles not getting refreshed In-Reply-To: <46DC2E31.7080504@gmail.com> References: <46DC2E31.7080504@gmail.com> Message-ID: <20070903204444.GA9230@metacarta.com> On Mon, Sep 03, 2007 at 09:24:25PM +0530, louvy.joseph@gmail.com wrote: > Has anybody seen this behavior? I have lot of dynamic content on the > server (i.e. geoserver); hence the WMS content is supposed to change all > the time. When I refresh my WMS layer, 5% of the time, some of the tiles > don't get refreshed. And these tiles are random. Rest of the tiles get > refreshed fine. > > Has anybody seen this behavior? What could be happening? When I look at > the WMS requests in my firebug, browser doesn't seem to generate the WMS > tile requests in the first place (but I could be wrong on this fact). > > Any tips appreciated on how to debug? (I don't have any tilecache > configured. It is plain geoserver to openlayers configuration. BTW, I > don't have a public facing example to publish to the mailing list) Browsers tend to assume that the content in a given URL hasn't changed for longer than they should. Override your getURL function and make it append a random=Math.random(): http://openlayers.org/pipermail/users/2007-January/000615.html is close, but if you wnat 'constant' refresh, you'll have to do a bit more legwork. Regards, -- Christopher Schmidt MetaCarta From cameron.shorter at gmail.com Mon Sep 3 17:04:36 2007 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Some of the WMS tiles not getting refreshed In-Reply-To: <20070903204444.GA9230@metacarta.com> References: <46DC2E31.7080504@gmail.com> <20070903204444.GA9230@metacarta.com> Message-ID: <46DC76E4.5030907@gmail.com> Yes, we had this problem in Mapbuilder and added a ×tamp=122233 to the end of the URL. Christopher Schmidt wrote: > On Mon, Sep 03, 2007 at 09:24:25PM +0530, louvy.joseph@gmail.com wrote: > >> Has anybody seen this behavior? I have lot of dynamic content on the >> server (i.e. geoserver); hence the WMS content is supposed to change all >> the time. When I refresh my WMS layer, 5% of the time, some of the tiles >> don't get refreshed. And these tiles are random. Rest of the tiles get >> refreshed fine. >> >> Has anybody seen this behavior? What could be happening? When I look at >> the WMS requests in my firebug, browser doesn't seem to generate the WMS >> tile requests in the first place (but I could be wrong on this fact). >> >> Any tips appreciated on how to debug? (I don't have any tilecache >> configured. It is plain geoserver to openlayers configuration. BTW, I >> don't have a public facing example to publish to the mailing list) >> > > Browsers tend to assume that the content in a given URL hasn't changed > for longer than they should. Override your getURL function and make it > append a random=Math.random(): > http://openlayers.org/pipermail/users/2007-January/000615.html is close, > but if you wnat 'constant' refresh, you'll have to do a bit more > legwork. > > Regards, > -- Cameron Shorter Systems Architect, http://lisasoft.com.au Tel: +61 (0)2 8570 5050 Mob: +61 (0)419 142 254 From crschmidt at metacarta.com Tue Sep 4 07:03:14 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OSM tiles and other overlays simultaneously In-Reply-To: References: <20070831142312.GA16909@metacarta.com> Message-ID: <20070904110314.GA16952@metacarta.com> On Tue, Sep 04, 2007 at 02:22:02PM +0400, Vladimir Elistratov wrote: > This solution seems to be complicated for the task of simply > displaying OSM or VMAP0 tiles and an overlay or markers defined with > longitude and latitude. Yep. > Is to possible to reproject OSM tiles back to "normal" longitude and > latitude not through the server but with javascript code? Nope. Javascript can't manipulate images in any fashion other than a linear stretch -- and linearly stretching images is functionality we're moving *away* from in OpenLayers because it had too much behavior that users couldn't accept. > So the OSM > layer would be treated like "normal" OpenLayers layer. And and > application developer could easy substitute the OSM Layer with any > other OpenLayers layers and still could be able to map a marker on the > same location on the earth. If you want that, you want to set up your own tiles -- or use another service on the web which provides up to date, unprojected tiles. OSGeo used to host one of these, but I let it lapse after recent planet.osm troubles. I can take the time to set it up again -- then you'd just point to http://t1.hypercube.telascience.org/tiles? , with a layer of osm-4326, which would allow you to use tiles that are compatible with all the 'unprojected' services out there. If I set it up again, would you use it? If so, I can set it up again. Regards, -- Christopher Schmidt MetaCarta From v_elistratov at rambler.ru Tue Sep 4 07:43:47 2007 From: v_elistratov at rambler.ru (Vladimir Elistratov) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OSM tiles and other overlays simultaneously In-Reply-To: <20070904110314.GA16952@metacarta.com> References: <20070831142312.GA16909@metacarta.com> <20070904110314.GA16952@metacarta.com> Message-ID: > If you want that, you want to set up your own tiles -- or use >another > service on the web which provides up to date, unprojected tiles. > OSGeo used to host one of these, but I let it lapse after recent > planet.osm troubles. I can take the time to set it up again -- then > you'd just point to http://t1.hypercube.telascience.org/tiles? , >with a > layer of osm-4326, which would allow you to use tiles that are > compatible with all the 'unprojected' services out there. > > If I set it up again, would you use it? If so, I can set it up >again. I'd like to use my own tiles since they will be used locally or in a local network. Is there a way to use them and all the 'unprojected' services out there without installing a WMS server? From v_elistratov at rambler.ru Tue Sep 4 07:57:47 2007 From: v_elistratov at rambler.ru (Vladimir Elistratov) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Sector and Arc Geometry Message-ID: I suggested to include Sector and Arc Geometry to the library. Example application is pie charts on a map. What do you think? I have already implemented Sector for SVG. From damien.corpataux at camptocamp.com Tue Sep 4 10:28:52 2007 From: damien.corpataux at camptocamp.com (Damien Corpataux) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <46CF42ED.30502@openplans.org> References: <46C1B940.2030407@camptocamp.com> <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> Message-ID: <46DD6BA4.4010404@camptocamp.com> Hi Tim, I just posted a patch on ticket #927. The patch suits the requirements: - KML extends XML - XML class methods are used for XML manipulation - tested on FF2/Linux and IE7 - KML.write() returns a string (using XML.write()) - GGE import of OL exported KML is working, and vice-versa My 2 cents Cheers, Damien Tim Schaub wrote: > I've opened ticket #927 to track this. > > If anybody has a patch for KML, please attach it to that ticket. > Damien, I've referenced your email on the ticket. > > Since XML flavors should now all inherit from the XML format class, I'd > say that write will always return a string. > > Thanks for any contributions. > Tim > > > Damien Corpataux wrote: > >> Hello, >> >> As far as I can see, the advantages of doing so are obvious. Althought I >> didn't have time to apply these, here is a new version of the patch: >> - puts placemarks in a folder tag (for google earth import) >> - bugfix with geometry tags >> >> Is the question about write() return type (string or DOMDocuemt/DOMNode) >> still open? >> >> Cheers, >> Damien >> >> >> Patch: >> Index: /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >> =================================================================== >> --- >> /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >> (revision 3900) >> +++ >> /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >> (working copy) >> @@ -8,8 +8,8 @@ >> * @requires OpenLayers/Ajax.js >> * >> * Class: OpenLayers.Format.KML >> - * Read only KML. Largely Proof of Concept: does not support advanced >> Features, >> - * including Polygons. Create a new instance with the >> + * Read/write KML 2.0. Does not support advanced Features. >> + * Create a new instance with the >> * constructor. >> * >> * Inherits from: >> @@ -24,6 +24,24 @@ >> kmlns: "http://earth.google.com/kml/2.0", >> >> /** >> + * APIProperty: placemarksDesc >> + * Default description for a placemark >> + */ >> + placemarksDesc: "No description available", >> + >> + /** >> + * APIProperty: foldersName >> + * Default name for a folder >> + */ >> + foldersName: "OpenLayers export", >> + >> + /** >> + * APIProperty: foldersDesc >> + * Default description for a folder >> + */ >> + foldersDesc: "Exported on " + new Date(), >> + >> + /** >> * Constructor: OpenLayers.Format.KML >> * Create a new parser for KML >> * >> @@ -46,7 +64,7 @@ >> if (typeof data == "string") { >> data = OpenLayers.parseXMLString(data); >> } >> - var featureNodes = OpenLayers.Ajax.getElementsByTagNameNS(data, >> this.kmlns, "", "Placemark"); >> + var featureNodes = OpenLayers.Ajax.getElementsByTagNameNS(data, >> this.kmlns, "kml", "Placemark"); >> >> var features = []; >> >> @@ -100,6 +118,19 @@ >> // TBD Bounds only set for one of multiple geometries >> geom.extendBounds(p.bounds); >> } >> + >> + // match Polygon >> + } else if (OpenLayers.Ajax.getElementsByTagNameNS(xmlNode, >> + this.kmlns, "", "Polygon").length != 0) { >> + var polygon = OpenLayers.Ajax.getElementsByTagNameNS(xmlNode, >> + this.kmlns, "", "Polygon")[0]; >> + p = this.parseCoords(polygon); >> + if (p.points) { >> + var linearRing = new >> OpenLayers.Geometry.LinearRing(p.points); >> + geom = new OpenLayers.Geometry.Polygon(linearRing); >> + // TBD Bounds only set for one of multiple geometries >> + geom.extendBounds(p.bounds); >> + } >> } >> >> feature.geometry = geom; >> @@ -191,5 +222,171 @@ >> return p; >> }, >> >> + /** >> + * Method: write >> + * Accept Feature Collection, and return an XML Document. >> + * >> + * Parameters: >> + * features - An array of features. >> + * >> + * Returns: >> + * >> + */ >> + write: function(features) { >> + var kml = document.createElementNS(this.kmlns, "kml"); >> + var folder = this.createFolderXML(); >> + for (var i=0; i < features.length; i++) { >> + folder.appendChild(this.createPlacemarkXML(features[i])); >> + } >> + kml.appendChild(folder); >> + return kml; >> + }, >> + >> + /** >> + * Method: createFolderXML >> + * Creates and returns a KML Folder node with default name and >> description >> + * >> + * Returns: >> + * xmlNode - {} >> + */ >> + createFolderXML: function() { >> + // Folder name >> + var folderName = document.createElementNS(this.kmlns, "name"); >> + var folderNameText = document.createTextNode(this.foldersName); >> + folderName.appendChild(folderNameText); >> + >> + // Folder description >> + var folderDesc = document.createElementNS(this.kmlns, >> "description"); >> + var folderDescText = document.createTextNode(this.foldersDesc); >> + folderDesc.appendChild(folderDescText); >> + >> + // Folder >> + var folder = document.createElementNS(this.kmlns, "Folder"); >> + folder.appendChild(folderName); >> + folder.appendChild(folderDesc); >> + >> + return folder; >> + }, >> + >> + /** >> + * Method: createPlacemarkXML >> + * Accept an OpenLayers.Feature.Vector, and create a KML Placemark node >> + * >> + * Parameters: >> + * feature - {} >> + * >> + * Returns: >> + * xmlNode - {} >> + */ >> + createPlacemarkXML: function(feature) { >> + // Placemark name >> + var placemarkName = document.createElementNS(this.kmlns, "name"); >> + var placemarkNameText = document.createTextNode(feature.id); >> + placemarkName.appendChild(placemarkNameText); >> + >> + // Placemark description >> + var placemarkDesc = document.createElementNS(this.kmlns, >> "description"); >> + var placemarkDescText = >> document.createTextNode(this.placemarksDesc); >> + placemarkDesc.appendChild(placemarkDescText); >> + >> + // Placemark >> + var placemarkNode = document.createElementNS(this.kmlns, >> "Placemark"); >> + placemarkNode.appendChild(placemarkName); >> + placemarkNode.appendChild(placemarkDesc); >> + >> + // Geometry node (Point, LineString, etc. nodes) >> + var geometryNode = this.buildGeometryNode(feature.geometry); >> + placemarkNode.appendChild(geometryNode); >> + >> + return placemarkNode; >> + }, >> + >> + /** >> + * Method: buildGeometryNode >> + * Builds a KML geometry node with a given geometry >> + * >> + * Parameters: >> + * geometry - {} >> + * >> + * Returns: >> + * xmlNode - {} >> + */ >> + buildGeometryNode: function(geometry) { >> + // TBD test if geoserver can be given a Multi-geometry for a >> simple-geometry data store >> + // ie if multipolygon can be sent for a polygon feature type >> + var kml = ""; >> + // match MultiPolygon or Polygon >> + if (geometry.CLASS_NAME == "OpenLayers.Geometry.MultiPolygon" >> + || geometry.CLASS_NAME == "OpenLayers.Geometry.Polygon") { >> + kml = document.createElementNS(this.kmlns, 'Polygon'); >> + >> + var outerRing = document.createElementNS(this.kmlns, >> 'outerBoundaryIs'); >> + var linearRing = document.createElementNS(this.kmlns, >> 'LinearRing'); >> + >> + // TBD manage polygons with holes >> + >> linearRing.appendChild(this.buildCoordinatesNode(geometry.components[0])); >> + outerRing.appendChild(linearRing); >> + >> + kml.appendChild(outerRing); >> + } >> + // match MultiLineString or LineString >> + else if (geometry.CLASS_NAME == >> "OpenLayers.Geometry.MultiLineString" >> + || geometry.CLASS_NAME == >> "OpenLayers.Geometry.LineString") { >> + kml = document.createElementNS(this.kmlns, >> 'LineString'); >> + >> + kml.appendChild(this.buildCoordinatesNode(geometry)); >> + } >> + // match MultiPoint or Point >> + else if (geometry.CLASS_NAME == "OpenLayers.Geometry.Point" || >> + geometry.CLASS_NAME == >> "OpenLayers.Geometry.MultiPoint") { >> + kml = document.createElementNS(this.kmlns, 'Point'); >> + >> + // FIXME: There should be only one Point node per >> Placemark node >> + var parts = ""; >> + if (geometry.CLASS_NAME == >> "OpenLayers.Geometry.MultiPoint") { >> + parts = geometry.components; >> + } else { >> + parts = [geometry]; >> + } >> + >> + for (var i = 0; i < parts.length; i++) { >> + kml.appendChild(this.buildCoordinatesNode(parts[i])); >> + } >> + } >> + return kml; >> + }, >> + /** >> + * Method: buildCoordinatesNode >> + * builds the KML coordinates node >> + * >> + * Parameters: >> + * geometry - {} >> + * >> + * Returns: >> + * xmlNode - {} >> + */ >> + buildCoordinatesNode: function(geometry) { >> + var coordinatesNode = document.createElementNS(this.kmlns, >> "coordinates"); >> + >> + var points = null; >> + if (geometry.components) { >> + points = geometry.components; >> + } >> + >> + var path = ""; >> + if (points) { >> + for (var i = 0; i < points.length; i++) { >> + path += points[i].x + "," + points[i].y + " "; >> + } >> + } else { >> + path += geometry.x + "," + geometry.y + " "; >> + } >> + >> + var txtNode = document.createTextNode(path); >> + coordinatesNode.appendChild(txtNode); >> + >> + return coordinatesNode; >> + }, >> + >> CLASS_NAME: "OpenLayers.Format.KML" >> }); >> >> >> Tim Schaub wrote: >> >>> Hi- >>> >>> So, we're mid-way through changing how XML flavors are read/written in >>> OpenLayers. >>> >>> I've checked a new XML format in to the trunk. This format has most of >>> the methods we need for reading/writing XML cross-browser. >>> >>> To parse other XML flavors, format classes should be created that >>> inherit from the XML format. >>> >>> For an (incomplete) example, see: >>> http://dev.openlayers.org/sandbox/tschaub/xml/lib/OpenLayers/Format/GML.js >>> >>> (The important part to notice in the above example is that the GML >>> format inherits from the XML format.) >>> >>> Instead of using OpenLayers.Ajax methods or document methods, DOM >>> creation and traversal should be done with OpenLayers.Format.XML >>> methods. I've created methods to reflect the W3C standard XML DOM >>> methods - wrapping the standard ones and accommodating for non-compliant >>> browsers. >>> >>> If you (or anyone) needs additional XML DOM methods, they should be >>> added to the XML format. The next addition (in my mind) is >>> setAttributeNS. Aside from that, you should be able to do efficient >>> parsing and dom creation with the XML format methods. >>> >>> Please make modifications to the KML format in the trunk. Create a >>> ticket and attach patches in Trac. I can offer review or other help as >>> needed. >>> >>> I don't have time to keep these sandboxes entirely clean right now - so >>> please forgive anything you find that is in a half-developed state. >>> >>> Tim >>> >>> PS - Eventually, I'll move the following example into the trunk. It >>> would be nice if we could demonstrate read/write capability for all >>> vector formats in this way: >>> http://dev.openlayers.org/sandbox/tschaub/xml/examples/vector-formats.html >>> >>> (note again that this reflects partially complete work - and you should >>> not be surprised to encounter errors or see changes at any time) >>> >>> >>> Damien Corpataux wrote: >>> >>> >>>> Hello, >>>> >>>> Here's what I did so far... Reading KML only work for KML 2.0 namespaces >>>> for write() uses OpenLayers.Ajax.getElementsByTagNameNS(), but I'm >>>> pretty sure it will work on future versions (2.1 parsing successful). >>>> Also, GML and KML write() returns a Dom Document rather than a string. >>>> Should one change the result type, breaking OpenLayers.Format interface, >>>> or parse it into a string using OpenLayers.XML.....? >>>> >>>> Cheers, >>>> Damien >>>> >>>> >>>> >> [patch stripped] >> >> -- >> Camptocamp SA >> Damien Corpataux >> PSE A >> CH-1015 Lausanne >> +41 21 619 10 22 (Direct) >> +41 21 619 10 10 (Centrale) >> +41 21 619 10 00 (Fax) >> P Please consider the environment >> Do you really need to print this email? >> !DSPAM:4033,46cd662e41812090977483! >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev >> >> >> !DSPAM:4033,46cd662e41812090977483! >> > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -- Camptocamp SA Damien Corpataux PSE A CH-1015 Lausanne +41 21 619 10 22 (Direct) +41 21 619 10 10 (Centrale) +41 21 619 10 00 (Fax) P Please consider the environment Do you really need to print this email? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070904/e2418c7e/attachment.html From crschmidt at metacarta.com Tue Sep 4 10:40:47 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <46DD6BA4.4010404@camptocamp.com> References: <46C1B940.2030407@camptocamp.com> <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> Message-ID: <20070904144047.GA30803@metacarta.com> On Tue, Sep 04, 2007 at 04:28:52PM +0200, Damien Corpataux wrote: > Hi Tim, > > I just posted a patch on ticket #927. The patch suits the requirements: > - KML extends XML > - XML class methods are used for XML manipulation > - tested on FF2/Linux and IE7 > - KML.write() returns a string (using XML.write()) > - GGE import of OL exported KML is working, and vice-versa > Looks pretty good. Any chance you could write some tests for KML.write() -- just a few simple ones, to confirm it works? Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Tue Sep 4 11:15:34 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Sector and Arc Geometry In-Reply-To: References: Message-ID: <20070904151534.GA2292@metacarta.com> On Tue, Sep 04, 2007 at 03:57:47PM +0400, Vladimir Elistratov wrote: > I suggested to include Sector and Arc Geometry to the library. Example > application is pie charts on a map. > What do you think? > > I have already implemented Sector for SVG. """ For the most part, geometries in OpenLayers correspond to those described by the GML Simple Features Profile (http://www.ogcnetwork.net/gml-sf). In particular, they are "points, lines, polygons (and collections of these)." In order to fit in with the other geometry classes, it is important that geometry.calculateBounds sets geometry.bounds as the the envelope of the geometry. In addition, the geometry.toString method returns Well-Known Text for all geometries. Geometries cannot only be serialized into WKT, but also GML, KML, GeoRSS, and GeoJSON. This is accomplished with the Format classes. This last bit allows all geometries to be serialized and sent to some persistance layer. All these things (in my mind) are important (and defining) characteristics of the geometry classes. """ -- tschaub, #903 I'd be surprised to find that sectors and arcs can not be represented by sufficiently complex polygons. There is an outstanding patch to add support for a Class instance on Polygon to support creation of regular-polygons: that is, multisided polygons with the same angle between each side. These approximate a circle for a sufficiently large side value. I would expect that a sector or arc would simply be a partial-circle, possibly a linestring instead of a polygon. Either of these are probably welcome helper functions to the appropriate geometry types, given sufficient tests. I think this would resolve your specific use case. If it doesn't, I may be misunderstanding: further feedback welcome. Regards, -- Christopher Schmidt MetaCarta From damien.corpataux at camptocamp.com Tue Sep 4 11:21:53 2007 From: damien.corpataux at camptocamp.com (Damien Corpataux) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <20070904144047.GA30803@metacarta.com> References: <46C1B940.2030407@camptocamp.com> <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> <20070904144047.GA30803@metacarta.com> Message-ID: <46DD7811.8000204@camptocamp.com> Thanks! I think you mean unit tests... Glurp, I never played around with testanotherway. Although I'm interested in doing it when I get to have a little time, here is the test code I ran in firebug, using the openlayers/examples/vector-features.html example: ---8<------------------------------------------------------------------- var kml = new OpenLayers.Format.KML(); var kmlOut = kml.write(map.layers[1].features); kmlOut; map.layers[1].eraseFeatures(map.layers[1].features); map.layers[1].features = []; var features = kml.read(kmlOut); features; map.layers[1].addFeatures(features); ---8<------------------------------------------------------------------- Cheers, Damien Christopher Schmidt wrote: > On Tue, Sep 04, 2007 at 04:28:52PM +0200, Damien Corpataux wrote: > >> Hi Tim, >> >> I just posted a patch on ticket #927. The patch suits the requirements: >> - KML extends XML >> - XML class methods are used for XML manipulation >> - tested on FF2/Linux and IE7 >> - KML.write() returns a string (using XML.write()) >> - GGE import of OL exported KML is working, and vice-versa >> >> > > Looks pretty good. Any chance you could write some tests for KML.write() > -- just a few simple ones, to confirm it works? > > Regards, > -- Camptocamp SA Damien Corpataux PSE A CH-1015 Lausanne +41 21 619 10 22 (Direct) +41 21 619 10 10 (Centrale) +41 21 619 10 00 (Fax) P Please consider the environment Do you really need to print this email? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070904/7a5a19c1/attachment.html From crschmidt at metacarta.com Tue Sep 4 11:33:35 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] [OpenLayers-Users] Handler problems In-Reply-To: <4fe6dd700709040814k48bd7e21x44339cde05ec4ad2@mail.gmail.com> References: <4fe6dd700708310720n6675d01ala33af447d304499b@mail.gmail.com> <4fe6dd700709010247g25028b77vcbedee637084f77d@mail.gmail.com> <4fe6dd700709040139i3f90a2a4qf55372f5894a0b18@mail.gmail.com> <20070904111018.GB16952@metacarta.com> <4fe6dd700709040814k48bd7e21x44339cde05ec4ad2@mail.gmail.com> Message-ID: <20070904153335.GC8348@metacarta.com> On Tue, Sep 04, 2007 at 04:14:42PM +0100, Tom (JDi Solutions) wrote: > Also, any ideas how I can workaround this problem or am I going to have to > use an old style click event? I have no idea why it's happening, so no idea how to work around it: sorry. Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Tue Sep 4 11:54:45 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <46DD7811.8000204@camptocamp.com> References: <46C1B940.2030407@camptocamp.com> <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> <20070904144047.GA30803@metacarta.com> <46DD7811.8000204@camptocamp.com> Message-ID: <20070904155445.GD8348@metacarta.com> On Tue, Sep 04, 2007 at 05:21:53PM +0200, Damien Corpataux wrote: > Thanks! > > I think you mean unit tests... Glurp, I never played around with > testanotherway. Although I'm interested in doing it when I get to have a > little time, here is the test code I ran in firebug, using the > openlayers/examples/vector-features.html example: Okay, I've put together a stub for you in the tests/Format/test_KML.html file. What I would do here is very similar to what you have below: * Create a KML parser. * Create a feature -- point, line, polygon, whatever. * In Firebug or elsewhere, create a text string which you can copy paste with the expected output KML: set that as the expectedOut variable. * Create kmlOut against that feature: kmlOut = kml.write([myFeature]); * Test that expectedOut matches KML Out: t.eq(expectedOut, kmlOut, "KML output matches given point feature"); * If you feel up to it, add a test to write, which reads the output KML (as below) and test things like: t.eq(outputFeatures.length, 1, "Got correct number of features back"); t.eq(outputFeatures[0].geometry.CLASS_NAME, "OpenLayers.Geometry.Point", "Correct geom type returned."); etc. If you don't get a chance, I'll bang something out soon, since we're trying not to shove things in without at least some tests -- but thanks for the patch regardless! > ---8<------------------------------------------------------------------- > var kml = new OpenLayers.Format.KML(); > var kmlOut = kml.write(map.layers[1].features); > > map.layers[1].eraseFeatures(map.layers[1].features); > map.layers[1].features = []; > > var features = kml.read(kmlOut); > > features; > > map.layers[1].addFeatures(features); > ---8<------------------------------------------------------------------- -- Christopher Schmidt MetaCarta From fporcelli at taic.net Tue Sep 4 12:05:28 2007 From: fporcelli at taic.net (fporcelli@taic.net) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Scale dependencies with TileCache Message-ID: <51468.192.168.1.70.1188921928.webmail@192.168.1.70> Hello -- I was interested in creating a cached layer with scale dependencies using TileCache. The layer configuration using just OpenLayers works fine and is shown below. However I want to cache this layer and have tileCache only request tiles from within the minScale and maxScale parameters. Is this possible? layer_test = new OpenLayers.Layer.WMS("test", "http://gis.test.com/cgi-bin/dir/test_wms.cgi", {layers: '1'}, {isBaseLayer: false, reproject: false, minScale: 100000, maxScale: 100}); Thanks, Frank From crschmidt at metacarta.com Tue Sep 4 12:22:31 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Scale dependencies with TileCache In-Reply-To: <51468.192.168.1.70.1188921928.webmail@192.168.1.70> References: <51468.192.168.1.70.1188921928.webmail@192.168.1.70> Message-ID: <20070904162231.GA13986@metacarta.com> On Tue, Sep 04, 2007 at 12:05:28PM -0400, fporcelli@taic.net wrote: > Hello -- > > I was interested in creating a cached layer with scale dependencies using TileCache. The layer configuration using just OpenLayers works fine and is shown below. However I want to cache this layer and have tileCache only request tiles from within the minScale and maxScale parameters. Is this possible? TileCache needs to be handed a list of resolutions. It's not clear to me what your units, maxExtent, etc. are. You should set your TileCache layer up to have the *resolutions of the base layer* which exist between those scales. OpenLayers.Util.getResolutionFromScale may be useful. Regards, -- Christopher Schmidt MetaCarta From fporcelli at taic.net Tue Sep 4 15:28:20 2007 From: fporcelli at taic.net (fporcelli@taic.net) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Scale dependencies with TileCache Message-ID: <47087.192.168.1.70.1188934100.webmail@192.168.1.70> Chris -- I passed the resolutions array to TileCache but I get pink tiles when the layer is turned on outside the boundaries of the resolutions array. The layer does render properly when zoomed in at the supported resolution. My units are decimal degrees, and my TileCache layer looks like so. I'm scratching my head on this one... [testlayer] type=WMSLayer url=http://gis.test.com/cgi-bin/dir/test_wms.cgi transparent=true extension=png layers=1 resolutions=0.00034332275390625,0.000171661376953125,0.0000858306884765625,0.00004291534423828125 Regards, Frank -----Original Message----- From: Christopher Schmidt Sent: Tue, September 4, 2007 12:22 pm To: fporcelli@taic.net Cc: dev@openlayers.org Subject: Re: [OpenLayers-Dev] Scale dependencies with TileCache On Tue, Sep 04, 2007 at 12:05:28PM -0400, fporcelli@taic.net wrote: > Hello -- > > I was interested in creating a cached layer with scale dependencies using TileCache. The layer configuration using just OpenLayers works fine and is shown below. However I want to cache this layer and have tileCache only request tiles from within the minScale and maxScale parameters. Is this possible? TileCache needs to be handed a list of resolutions. It's not clear to me what your units, maxExtent, etc. are. You should set your TileCache layer up to have the *resolutions of the base layer* which exist between those scales. OpenLayers.Util.getResolutionFromScale may be useful. Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Tue Sep 4 17:14:38 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Scale dependencies with TileCache In-Reply-To: <47087.192.168.1.70.1188934100.webmail@192.168.1.70> References: <47087.192.168.1.70.1188934100.webmail@192.168.1.70> Message-ID: <20070904211438.GA1270@metacarta.com> On Tue, Sep 04, 2007 at 03:28:20PM -0400, fporcelli@taic.net wrote: > Chris -- > > I passed the resolutions array to TileCache but I get pink tiles when the layer is turned on outside the boundaries of the resolutions array. The layer does render properly when zoomed in at the supported resolution. My units are decimal degrees, and my TileCache layer looks like so. I'm sorry: "When the layer is turned on outside the boundaries of the resolutions aray" -- how? The minScale/maxScale should be causing the layer's visibility to be set to false outside of that min/max scale range -- if it's not, that's a bug, as far as I'm aware. Can you create a minimal demo? -- Chris > I'm scratching my head on this one... > > [testlayer] > type=WMSLayer > url=http://gis.test.com/cgi-bin/dir/test_wms.cgi > transparent=true > extension=png > layers=1 > resolutions=0.00034332275390625,0.000171661376953125,0.0000858306884765625,0.00004291534423828125 > > Regards, > > Frank > > > -----Original Message----- > From: Christopher Schmidt > Sent: Tue, September 4, 2007 12:22 pm > To: fporcelli@taic.net > Cc: dev@openlayers.org > Subject: Re: [OpenLayers-Dev] Scale dependencies with TileCache > > On Tue, Sep 04, 2007 at 12:05:28PM -0400, fporcelli@taic.net wrote: > > Hello -- > > > > I was interested in creating a cached layer with scale dependencies using TileCache. The layer configuration using just OpenLayers works fine and is shown below. However I want to cache this layer and have tileCache only request tiles from within the minScale and maxScale parameters. Is this possible? > > TileCache needs to be handed a list of resolutions. It's not clear to me > what your units, maxExtent, etc. are. You should set your TileCache > layer up to have the *resolutions of the base layer* which exist between > those scales. > > OpenLayers.Util.getResolutionFromScale may be useful. > > Regards, > -- > Christopher Schmidt > MetaCarta > > -- Christopher Schmidt MetaCarta From louvy.joseph at gmail.com Tue Sep 4 20:39:49 2007 From: louvy.joseph at gmail.com (louvy.joseph@gmail.com) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Some of the WMS tiles not getting refreshed In-Reply-To: <20070903204444.GA9230@metacarta.com> References: <46DC2E31.7080504@gmail.com> <20070903204444.GA9230@metacarta.com> Message-ID: <46DDFAD5.8080306@gmail.com> Thanks Crhis, Andrea & Cameron. I still have the problem. Couple of notes. 1) Yes, I was already using the random number with mergeNewParams(). wmsLayer.mergeNewParams({'foo': Math.random()}); And I do see that there is FOO value getting embedded in my WMS url. 2) Funny thing is that when I look at the tile in firebug by clicking Net->Images->wms->Response, I see my new tile with proper image but the browser itself seem to display old tile. Why? Most of the tiles are okay except for one tile or rarely two tiles. 3) The response headers from firebug are: Response Headers Server Apache-Coyote/1.1 Content-Type image/png Transfer-Encoding chunked Date Wed, 05 Sep 2007 00:23:53 GMT Request Headers Host wms1.localhost:8080 User-Agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6 Accept image/png,*/*;q=0.5 Accept-Language en-us,en;q=0.5 Accept-Encoding gzip,deflate Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive 300 Connection keep-alive Referer http://localhost:8080/polaris-web/edit Do you see anything wrong in the header? I don't see "Pragma: No-Cache" in the header. Is that something to be worried about? 4) Andrea, are you referring to "Cache Enabled" & "Cache Time" field in geoserver console's under WFS feature edit screen? The "Cache Enabled" check box is not enabled and the "Cache Time" text field is empty. 5) The problem happens in both IE & Firefox. 6) Chris, is there anything I can debug around using the checkImagURL() event handler? Thanks again Louvy Christopher Schmidt wrote: > On Mon, Sep 03, 2007 at 09:24:25PM +0530, louvy.joseph@gmail.com wrote: > >> Has anybody seen this behavior? I have lot of dynamic content on the >> server (i.e. geoserver); hence the WMS content is supposed to change all >> the time. When I refresh my WMS layer, 5% of the time, some of the tiles >> don't get refreshed. And these tiles are random. Rest of the tiles get >> refreshed fine. >> >> Has anybody seen this behavior? What could be happening? When I look at >> the WMS requests in my firebug, browser doesn't seem to generate the WMS >> tile requests in the first place (but I could be wrong on this fact). >> >> Any tips appreciated on how to debug? (I don't have any tilecache >> configured. It is plain geoserver to openlayers configuration. BTW, I >> don't have a public facing example to publish to the mailing list) >> > > Browsers tend to assume that the content in a given URL hasn't changed > for longer than they should. Override your getURL function and make it > append a random=Math.random(): > http://openlayers.org/pipermail/users/2007-January/000615.html is close, > but if you wnat 'constant' refresh, you'll have to do a bit more > legwork. > > Regards, > From jachym.cepicky at gmail.com Wed Sep 5 00:57:53 2007 From: jachym.cepicky at gmail.com (Jachym Cepicky) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] snapping patch Message-ID: <1188968273.7778.3.camel@mellon> hallo, I added patch, which enables snapping function. The patch adds this.snapDist to OL.Handler.Point(.js) and apart from intern snapping functions, it also defines empty this.customSnap method, which can be used by user to define her own (e.g. raster-based) snapping. http://trac.openlayers.org/ticket/954 hope, it works also for another devs... jachym -- Jachym Cepicky e-mail: jachym.cepicky@gmail.com URL: http://les-ejk.cz GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070905/1cf2436b/attachment.bin From daiy115 at yahoo.co.jp Wed Sep 5 01:44:38 2007 From: daiy115 at yahoo.co.jp (Daisuke YOSHIDA) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Auto-refresh layers Message-ID: <46DE4246.50708@yahoo.co.jp> I would like to have auto-refresh layer function. And I tried webcam.html which is in the examples directory under OpenLayers-2.4. It blinks when its function works but the layer does not be redraw.

    OpenLayers Webcam

    Thank you very much, Daisuke -------------------------------------- Easy + Joy + Powerful = Yahoo! Bookmarks x Toolbar http://pr.mail.yahoo.co.jp/toolbar/ From aaime at openplans.org Wed Sep 5 03:27:13 2007 From: aaime at openplans.org (Andrea Aime) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Some of the WMS tiles not getting refreshed In-Reply-To: <46DDFAD5.8080306@gmail.com> References: <46DC2E31.7080504@gmail.com> <20070903204444.GA9230@metacarta.com> <46DDFAD5.8080306@gmail.com> Message-ID: <46DE5A51.4090801@openplans.org> louvy.joseph@gmail.com ha scritto: > Thanks Crhis, Andrea & Cameron. I still have the problem. Couple of notes. > > 1) Yes, I was already using the random number with mergeNewParams(). > wmsLayer.mergeNewParams({'foo': Math.random()}); > > And I do see that there is FOO value getting embedded in my WMS url. > > 2) Funny thing is that when I look at the tile in firebug by clicking > Net->Images->wms->Response, I see my new tile with proper image but the > browser itself seem to display old tile. Why? Most of the tiles are okay > except for one tile or rarely two tiles. > > 3) The response headers from firebug are: > > Response Headers > Server Apache-Coyote/1.1 > Content-Type image/png > Transfer-Encoding chunked > Date Wed, 05 Sep 2007 00:23:53 GMT > Request Headers > Host wms1.localhost:8080 > User-Agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.6) > Gecko/20070725 Firefox/2.0.0.6 > Accept image/png,*/*;q=0.5 > Accept-Language en-us,en;q=0.5 > Accept-Encoding gzip,deflate > Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7 > Keep-Alive 300 > Connection keep-alive > Referer http://localhost:8080/polaris-web/edit > > > > Do you see anything wrong in the header? I don't see "Pragma: No-Cache" > in the header. Is that something to be worried about? Frankly, I don't know... good question thought. One more check is about the date field: the date is generated on the server, any chance a server having a clock in the future compared to the client may cause this? > > 4) Andrea, are you referring to "Cache Enabled" & "Cache Time" field in > geoserver console's under WFS feature edit screen? The "Cache Enabled" > check box is not enabled and the "Cache Time" text field is empty. Yes, correct, and as you see, there are no caching headers there. Thought without the nocache pragma, who knows, it may be... in fact it's something I always set in dynamic web pages, maybe we should set it in uncached responses too... Wondering, does mapserver add that pragma to its responses? Cheers Andrea From damien.corpataux at camptocamp.com Wed Sep 5 06:27:09 2007 From: damien.corpataux at camptocamp.com (Damien Corpataux) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <20070904155445.GD8348@metacarta.com> References: <46C1B940.2030407@camptocamp.com> <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> <20070904144047.GA30803@metacarta.com> <46DD7811.8000204@camptocamp.com> <20070904155445.GD8348@metacarta.com> Message-ID: <46DE847D.3030705@camptocamp.com> Hi Christopher, Thanks for the stub! It got me into writing the tests (very quick). Everything's fine on ff2, but a problem occurs on IE7 (only when running the tests, not on using the component within OL). I put all the information and patch into the ticket, which I now wonder whether it's a good idea, http://trac.openlayers.org/ticket/927#comment:5 Anybody might have ran into a similar problem with test.anotherway? Cheers, Damien Christopher Schmidt wrote: > On Tue, Sep 04, 2007 at 05:21:53PM +0200, Damien Corpataux wrote: > >> Thanks! >> >> I think you mean unit tests... Glurp, I never played around with >> testanotherway. Although I'm interested in doing it when I get to have a >> little time, here is the test code I ran in firebug, using the >> openlayers/examples/vector-features.html example: >> > > Okay, I've put together a stub for you in the tests/Format/test_KML.html > file. What I would do here is very similar to what you have below: > * Create a KML parser. > * Create a feature -- point, line, polygon, whatever. > * In Firebug or elsewhere, create a text string which you can copy > paste with the expected output KML: set that as the expectedOut > variable. > * Create kmlOut against that feature: > kmlOut = kml.write([myFeature]); > * Test that expectedOut matches KML Out: > t.eq(expectedOut, kmlOut, "KML output matches given point feature"); > * If you feel up to it, add a test to write, which reads the output > KML (as below) and test things like: > t.eq(outputFeatures.length, 1, "Got correct number of features > back"); > t.eq(outputFeatures[0].geometry.CLASS_NAME, "OpenLayers.Geometry.Point", > "Correct geom type returned."); > > etc. > > If you don't get a chance, I'll bang something out soon, since we're > trying not to shove things in without at least some tests -- but thanks > for the patch regardless! > > >> ---8<------------------------------------------------------------------- >> var kml = new OpenLayers.Format.KML(); >> var kmlOut = kml.write(map.layers[1].features); >> >> map.layers[1].eraseFeatures(map.layers[1].features); >> map.layers[1].features = []; >> >> var features = kml.read(kmlOut); >> >> features; >> >> map.layers[1].addFeatures(features); >> ---8<------------------------------------------------------------------- >> > > > > -- Camptocamp SA Damien Corpataux PSE A CH-1015 Lausanne +41 21 619 10 22 (Direct) +41 21 619 10 10 (Centrale) +41 21 619 10 00 (Fax) P Please consider the environment Do you really need to print this email? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070905/7848d915/attachment.html From fporcelli at taic.net Wed Sep 5 07:12:01 2007 From: fporcelli at taic.net (Frank Porcelli) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Scale dependencies with TileCache In-Reply-To: <20070904211438.GA1270@metacarta.com> References: <47087.192.168.1.70.1188934100.webmail@192.168.1.70> <20070904211438.GA1270@metacarta.com> Message-ID: <00f401c7efad$9535a510$6401a8ac@ISLANDER> Chris -- My bad. The minScale setting was incorrect. The resolutions array you suggested works fine. Thanks, Frank -----Original Message----- From: Christopher Schmidt [mailto:crschmidt@metacarta.com] Sent: Tuesday, September 04, 2007 5:15 PM To: fporcelli@taic.net Cc: dev@openlayers.org Subject: Re: [OpenLayers-Dev] Scale dependencies with TileCache On Tue, Sep 04, 2007 at 03:28:20PM -0400, fporcelli@taic.net wrote: > Chris -- > > I passed the resolutions array to TileCache but I get pink tiles when the layer is turned on outside the boundaries of the resolutions array. The layer does render properly when zoomed in at the supported resolution. My units are decimal degrees, and my TileCache layer looks like so. I'm sorry: "When the layer is turned on outside the boundaries of the resolutions aray" -- how? The minScale/maxScale should be causing the layer's visibility to be set to false outside of that min/max scale range -- if it's not, that's a bug, as far as I'm aware. Can you create a minimal demo? -- Chris > I'm scratching my head on this one... > > [testlayer] > type=WMSLayer > url=http://gis.test.com/cgi-bin/dir/test_wms.cgi > transparent=true > extension=png > layers=1 > resolutions=0.00034332275390625,0.000171661376953125,0.0000858306884765625,0 .00004291534423828125 > > Regards, > > Frank > > > -----Original Message----- > From: Christopher Schmidt > Sent: Tue, September 4, 2007 12:22 pm > To: fporcelli@taic.net > Cc: dev@openlayers.org > Subject: Re: [OpenLayers-Dev] Scale dependencies with TileCache > > On Tue, Sep 04, 2007 at 12:05:28PM -0400, fporcelli@taic.net wrote: > > Hello -- > > > > I was interested in creating a cached layer with scale dependencies using TileCache. The layer configuration using just OpenLayers works fine and is shown below. However I want to cache this layer and have tileCache only request tiles from within the minScale and maxScale parameters. Is this possible? > > TileCache needs to be handed a list of resolutions. It's not clear to me > what your units, maxExtent, etc. are. You should set your TileCache > layer up to have the *resolutions of the base layer* which exist between > those scales. > > OpenLayers.Util.getResolutionFromScale may be useful. > > Regards, > -- > Christopher Schmidt > MetaCarta > > -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Wed Sep 5 07:54:55 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <46DE847D.3030705@camptocamp.com> References: <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> <20070904144047.GA30803@metacarta.com> <46DD7811.8000204@camptocamp.com> <20070904155445.GD8348@metacarta.com> <46DE847D.3030705@camptocamp.com> Message-ID: <20070905115455.GA30152@metacarta.com> On Wed, Sep 05, 2007 at 12:27:09PM +0200, Damien Corpataux wrote: > Hi Christopher, > > Thanks for the stub! It got me into writing the tests (very quick). > Everything's fine on ff2, but a problem occurs on IE7 (only when running > the tests, not on using the component within OL). > > I put all the information and patch into the ticket, which I now wonder > whether it's a good idea, http://trac.openlayers.org/ticket/927#comment:5 > > Anybody might have ran into a similar problem with test.anotherway? Interesting. I'll see if I can figure out why: The GML tests should be using something similar, and they don't have any problems I'm aware of. Regards, -- Christopher Schmidt MetaCarta From damien.corpataux at camptocamp.com Wed Sep 5 08:40:12 2007 From: damien.corpataux at camptocamp.com (Damien Corpataux) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <20070905115455.GA30152@metacarta.com> References: <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> <20070904144047.GA30803@metacarta.com> <46DD7811.8000204@camptocamp.com> <20070904155445.GD8348@metacarta.com> <46DE847D.3030705@camptocamp.com> <20070905115455.GA30152@metacarta.com> Message-ID: <46DEA3AC.1010605@camptocamp.com> Christopher Schmidt wrote: > On Wed, Sep 05, 2007 at 12:27:09PM +0200, Damien Corpataux wrote: > >> Hi Christopher, >> >> Thanks for the stub! It got me into writing the tests (very quick). >> Everything's fine on ff2, but a problem occurs on IE7 (only when running >> the tests, not on using the component within OL). >> >> I put all the information and patch into the ticket, which I now wonder >> whether it's a good idea, http://trac.openlayers.org/ticket/927#comment:5 >> >> Anybody might have ran into a similar problem with test.anotherway? >> > > Interesting. I'll see if I can figure out why: The GML tests should be > using something similar, and they don't have any problems I'm aware of. > > Regards, > Unfortunately, test_GML.html doesn't test GML.write() and GML and is not yet using XML class methods for Doc manipulation... I wish I could help a little further, but I think my knowledge of Test.AnotherWay is too limited to rapidly make out what's going on... :\ http://trac.openlayers.org/browser/trunk/openlayers/tests/Format/test_GML.html http://trac.openlayers.org/browser/trunk/openlayers/lib/OpenLayers/Format/GML.js Regards, Damien -- Camptocamp SA Damien Corpataux PSE A CH-1015 Lausanne +41 21 619 10 22 (Direct) +41 21 619 10 10 (Centrale) +41 21 619 10 00 (Fax) P Please consider the environment Do you really need to print this email? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070905/584c0657/attachment.html From crschmidt at metacarta.com Wed Sep 5 08:54:53 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <46DEA3AC.1010605@camptocamp.com> References: <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> <20070904144047.GA30803@metacarta.com> <46DD7811.8000204@camptocamp.com> <20070904155445.GD8348@metacarta.com> <46DE847D.3030705@camptocamp.com> <20070905115455.GA30152@metacarta.com> <46DEA3AC.1010605@camptocamp.com> Message-ID: <20070905125453.GA10326@metacarta.com> On Wed, Sep 05, 2007 at 02:40:12PM +0200, Damien Corpataux wrote: > Christopher Schmidt wrote: > > On Wed, Sep 05, 2007 at 12:27:09PM +0200, Damien Corpataux wrote: > > > >> Hi Christopher, > >> > >> Thanks for the stub! It got me into writing the tests (very quick). > >> Everything's fine on ff2, but a problem occurs on IE7 (only when running > >> the tests, not on using the component within OL). > >> > >> I put all the information and patch into the ticket, which I now wonder > >> whether it's a good idea, http://trac.openlayers.org/ticket/927#comment:5 > >> > >> Anybody might have ran into a similar problem with test.anotherway? > >> > > > > Interesting. I'll see if I can figure out why: The GML tests should be > > using something similar, and they don't have any problems I'm aware of. > > > > Regards, > > > Unfortunately, test_GML.html doesn't test GML.write() and GML and is not > yet using XML class methods for Doc manipulation... I wish I could help > a little further, but I think my knowledge of Test.AnotherWay is too > limited to rapidly make out what's going on... :\ > > http://trac.openlayers.org/browser/trunk/openlayers/tests/Format/test_GML.html > http://trac.openlayers.org/browser/trunk/openlayers/lib/OpenLayers/Format/GML.js Right, sorry: the GML tests I was talking about haven't made it back to trunk yet, they're still at: http://svn.openlayers.org/sandbox/tschaub/xml/tests/Format/test_GML.html It's possible we're still missing something in the XML format though, so I'll take a look at it: thanks for the tests you've got so far! :) Sorry something seems to be more complex than it otherwise should be. Regards, -- Christopher Schmidt MetaCarta From lkoszanski at ncct.uottawa.ca Wed Sep 5 10:21:15 2007 From: lkoszanski at ncct.uottawa.ca (Lukasz Koszanski) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Inserting the marker layer in DOM Message-ID: <46DEBB5B.6090006@ncct.uottawa.ca> Hi everyone, I would like to insert the a markers layer in a custom place in my DOM document, that is, instead of inserting it in the default openlayers container div like in the following example ...
    ... I would like to insert the "OpenLayers.Layer.Markers_103" in an arbitrary place in my DOM. For example in a div with id="blah".Anyone knows hot to do it? Thanks, Luke From crschmidt at metacarta.com Wed Sep 5 11:21:52 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Inserting the marker layer in DOM In-Reply-To: <46DEBB5B.6090006@ncct.uottawa.ca> References: <46DEBB5B.6090006@ncct.uottawa.ca> Message-ID: <20070905152152.GA6332@metacarta.com> On Wed, Sep 05, 2007 at 10:21:15AM -0400, Lukasz Koszanski wrote: > I would like to insert the "OpenLayers.Layer.Markers_103" in an > arbitrary place in my DOM. For example in a div with id="blah".Anyone > knows hot to do it? I might be able to figure out why, but I've been trained for a long time to ask for 'Requirements in the form of a requirement', so I don't tell you how to do something which will only break later. Can you explain why you want to do this? Examples of other, similar sites on the web, for example, which do what you want to do, would be useful, so that I can picture in my head what problem you're trying to solve, and possibly offer a better solution. Regards, -- Christopher Schmidt MetaCarta From v_elistratov at rambler.ru Thu Sep 6 06:53:41 2007 From: v_elistratov at rambler.ru (Vladimir Elistratov) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Sector and Arc Geometry In-Reply-To: <20070904151534.GA2292@metacarta.com> References: <20070904151534.GA2292@metacarta.com> Message-ID: On Tue, 4 Sep 2007 11:15:34 -0400 Christopher Schmidt wrote: > On Tue, Sep 04, 2007 at 03:57:47PM +0400, Vladimir Elistratov wrote: >> I suggested to include Sector and Arc Geometry to the library. >>Example >> application is pie charts on a map. >> What do you think? >> >> I have already implemented Sector for SVG. >For the most part, geometries in OpenLayers correspond to those > described by the GML Simple Features Profile > (http://www.ogcnetwork.net/gml-sf). In particular, they are "points, > lines, polygons (and collections of these)." > > In order to fit in with the other geometry classes, it is important that > geometry.calculateBounds sets geometry.bounds as the the envelope of >the geometry. > > In addition, the geometry.toString method returns Well-Known Text for > all geometries. Geometries cannot only be serialized into WKT, but also > GML, KML, GeoRSS, and GeoJSON. This is accomplished with the Format > classes. > > This last bit allows all geometries to be serialized and sent to some > persistance layer. > > All these things (in my mind) are important (and defining) > characteristics of the geometry classes. > """ > > -- tschaub, #903 > > I'd be surprised to find that sectors and arcs can not be >represented by > sufficiently complex polygons. There is an outstanding patch to add > support for a Class instance on Polygon to support creation of > regular-polygons: that is, multisided polygons with the same angle > between each side. These approximate a circle for a sufficiently >large > side value. I would expect that a sector or arc would simply be a > partial-circle, possibly a linestring instead of a polygon. Either >of > these are probably welcome helper functions to the appropriate >geometry > types, given sufficient tests. > > I think this would resolve your specific use case. If it doesn't, I >may > be misunderstanding: further feedback welcome. This function should solve the problem of Arc and Sector. Where can it be found? Is it available under the same license as OpenLayers? The other solution would be to explicitly allow the use of SVG images loaded from a string or from a file like it is done now with markers. Is there a plan to do so? From crschmidt at metacarta.com Thu Sep 6 07:26:38 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Sector and Arc Geometry In-Reply-To: References: <20070904151534.GA2292@metacarta.com> Message-ID: <20070906112638.GB15898@metacarta.com> On Thu, Sep 06, 2007 at 02:53:41PM +0400, Vladimir Elistratov wrote: > On Tue, 4 Sep 2007 11:15:34 -0400 > Christopher Schmidt wrote: > >On Tue, Sep 04, 2007 at 03:57:47PM +0400, Vladimir Elistratov wrote: > >>I suggested to include Sector and Arc Geometry to the library. > >>Example > >>application is pie charts on a map. > >>What do you think? > >> > >>I have already implemented Sector for SVG. > > >For the most part, geometries in OpenLayers correspond to those > >described by the GML Simple Features Profile > >(http://www.ogcnetwork.net/gml-sf). In particular, they are "points, > >lines, polygons (and collections of these)." > > > >In order to fit in with the other geometry classes, it is important that > >geometry.calculateBounds sets geometry.bounds as the the envelope of > >the geometry. > > > >In addition, the geometry.toString method returns Well-Known Text for > >all geometries. Geometries cannot only be serialized into WKT, but also > >GML, KML, GeoRSS, and GeoJSON. This is accomplished with the Format > >classes. > > > >This last bit allows all geometries to be serialized and sent to some > >persistance layer. > > > >All these things (in my mind) are important (and defining) > >characteristics of the geometry classes. > >""" > > > >-- tschaub, #903 > > > >I'd be surprised to find that sectors and arcs can not be > >represented by > >sufficiently complex polygons. There is an outstanding patch to add > >support for a Class instance on Polygon to support creation of > >regular-polygons: that is, multisided polygons with the same angle > >between each side. These approximate a circle for a sufficiently > >large > >side value. I would expect that a sector or arc would simply be a > >partial-circle, possibly a linestring instead of a polygon. Either > >of > >these are probably welcome helper functions to the appropriate > >geometry > >types, given sufficient tests. > > > >I think this would resolve your specific use case. If it doesn't, I > >may > >be misunderstanding: further feedback welcome. > > This function should solve the problem of Arc and Sector. Where can it > be found? Is it available under the same license as OpenLayers? It will be once it's in trunk. Currently, it's only in a patch, here: http://trac.openlayers.org/attachment/ticket/828/regular_polygon_trunk.2.patch > The other solution would be to explicitly allow the use of SVG images > loaded from a string or from a file like it is done now with markers. > Is there a plan to do so? SVG images, or raster graphics? VML can't render SVG, so allowing SVG graphics goes against the "don't expose platform differences to the user whenever possible", but external raster graphics are already supported: see http://openlayers.org/dev/examples/vector-features.html and the description at the bottom of the page. Regards, -- Christopher Schmidt MetaCarta From v_elistratov at rambler.ru Fri Sep 7 06:19:19 2007 From: v_elistratov at rambler.ru (Vladimir Elistratov) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Sector and Arc Geometry In-Reply-To: <20070906112638.GB15898@metacarta.com> References: <20070904151534.GA2292@metacarta.com> <20070906112638.GB15898@metacarta.com> Message-ID: > SVG images, or raster graphics? VML can't render SVG, so allowing SVG > graphics goes against the "don't expose platform differences to the user > whenever possible", but external raster graphics are already supported: > see http://openlayers.org/dev/examples/vector-features.html and the > description at the bottom of the page. Ok, let's wait till Internet Explorer supports SVG. From crschmidt at metacarta.com Fri Sep 7 06:34:35 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Sector and Arc Geometry In-Reply-To: References: <20070904151534.GA2292@metacarta.com> <20070906112638.GB15898@metacarta.com> Message-ID: <20070907103435.GA2867@metacarta.com> On Fri, Sep 07, 2007 at 02:19:19PM +0400, Vladimir Elistratov wrote: > >SVG images, or raster graphics? VML can't render SVG, so allowing SVG > >graphics goes against the "don't expose platform differences to the user > >whenever possible", but external raster graphics are already supported: > >see http://openlayers.org/dev/examples/vector-features.html and the > >description at the bottom of the page. > > Ok, let's wait till Internet Explorer supports SVG. I'm not sure if this is serious or tongue-in-cheek, but in case it was serious, I don't expect Internet Explorer to *ever* support SVG: they have VML, which is a similar (but different enough to not be compatible) technology, and have made no moves towards supporting SVG. Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Fri Sep 7 07:57:10 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] ModifyFeature control comments Message-ID: <20070907115710.GA11005@metacarta.com> Comments on use of the current modify feature control: * Deleting points does not offer enough feedback to external applications to actually make use of it. If we're going to support deletion of features, there needs to be a better hook -- something like 'onDelete' -- which is passed the feature. * Point modifications are iffy at best. Clicking them to select typically works, but clicking to unselect doesn't work so well, and after 'deleting' a feature, it seems impossible to get off that feature and edit something else. * It would be nice if the DragFeature control could be integrated as well: if you have a feature selected, and you drag it, the feature could move. * Current code is lacking an onModification call inside the handleKeypress code, so deletes don't trigger onModification. (This is a simple one line fix, just writing it down cause I don't have time to muck with it at the moment.) In general, it's looking very nice -- these are just things I came across when setting up http://labs.metacarta.com/atompub/app-demo.html -- note that there is no point drawing here, because the point modification stuff just felt a bit too rough for me to mess with. Thanks to all the hard work that everyone has been doing on this! I'm looking forward to Tim getting back and working on getting all this into trunk for 2.5. Regards, -- Christopher Schmidt MetaCarta From pspencer at dmsolutions.ca Sat Sep 8 14:51:33 2007 From: pspencer at dmsolutions.ca (Paul Spencer) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] foss4g coding sprint Message-ID: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> Just wondering who is going to join the OL coding sprint and what folks are interested in working on? Cheers Paul PS I'll be there and I am interested in animated zooming, adding a renderer, performance and visual improvements (maps 'flash' a lot!), and generally anything else that will move OL forward. +-----------------------------------------------------------------+ |Paul Spencer pspencer@dmsolutions.ca | +-----------------------------------------------------------------+ |Chief Technology Officer | |DM Solutions Group Inc http://www.dmsolutions.ca/ | +-----------------------------------------------------------------+ From lorenzo at ominiverdi.com Sat Sep 8 15:10:23 2007 From: lorenzo at ominiverdi.com (Lorenzo Becchi) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] foss4g coding sprint In-Reply-To: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> References: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> Message-ID: <46E2F39F.2010200@ominiverdi.com> Hi Paul, there's a list here: http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers Paul Spencer wrote: > Just wondering who is going to join the OL coding sprint and what > folks are interested in working on? > > Cheers > > Paul > > PS I'll be there and I am interested in animated zooming, adding a > renderer, performance and visual improvements (maps 'flash' > a lot!), and generally anything else that will move OL forward. > > +-----------------------------------------------------------------+ > |Paul Spencer pspencer@dmsolutions.ca | > +-----------------------------------------------------------------+ > |Chief Technology Officer | > |DM Solutions Group Inc http://www.dmsolutions.ca/ | > +-----------------------------------------------------------------+ > > > > > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > From pspencer at dmsolutions.ca Sat Sep 8 15:29:11 2007 From: pspencer at dmsolutions.ca (Paul Spencer) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] Allowing zoom to arbitrary extents in OL Message-ID: <19ACD497-9ECA-4A53-9400-8EBA39B142A1@dmsolutions.ca> Hi, apologies for the cross post, but Chris indicated that mapbuilder was also looking for a solution to this problem. And thanks to Chris for helping me to solve this one. My problem: when using OL with singleTile layers, I need to be able to allow users to zoom to arbitrary extents. OL internally keeps a list of fixed resolutions and snaps to those, meaning that zooming to extents often has the appearance of being 'buffered' somewhat. In some cases, zooming results in panning. My solution: assuming that I can track when I am only using singleTile layers, and that I always use zoomToExtent: if (this.bSingleTile) { var viewSize = this.oMapOL.getSize(); var idealResolution = Math.max( extent.getWidth() / viewSize.w, extent.getHeight() / viewSize.h ); this.oMapOL.baseLayer.resolutions = [idealResolution]; this.oMapOL.zoom = 1; } this.oMapOL.zoomToExtent(extent); Cheers Paul +-----------------------------------------------------------------+ |Paul Spencer pspencer@dmsolutions.ca | +-----------------------------------------------------------------+ |Chief Technology Officer | |DM Solutions Group Inc http://www.dmsolutions.ca/ | +-----------------------------------------------------------------+ From pspencer at dmsolutions.ca Sat Sep 8 15:39:13 2007 From: pspencer at dmsolutions.ca (Paul Spencer) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] foss4g coding sprint In-Reply-To: <46E2F39F.2010200@ominiverdi.com> References: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> <46E2F39F.2010200@ominiverdi.com> Message-ID: <2A41ADD8-CA27-43B3-B947-435334F6815F@dmsolutions.ca> Thanks Lorenzo! I guess I should pay attention ;) On 8-Sep-07, at 3:10 PM, Lorenzo Becchi wrote: > Hi Paul, > there's a list here: > http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers > > > > Paul Spencer wrote: >> Just wondering who is going to join the OL coding sprint and what >> folks are interested in working on? >> >> Cheers >> >> Paul >> >> PS I'll be there and I am interested in animated zooming, adding >> a renderer, performance and visual improvements (maps >> 'flash' a lot!), and generally anything else that will move OL >> forward. >> >> +-----------------------------------------------------------------+ >> |Paul Spencer pspencer@dmsolutions.ca | >> +-----------------------------------------------------------------+ >> |Chief Technology Officer | >> |DM Solutions Group Inc http://www.dmsolutions.ca/ | >> +-----------------------------------------------------------------+ >> >> >> >> >> >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev >> +-----------------------------------------------------------------+ |Paul Spencer pspencer@dmsolutions.ca | +-----------------------------------------------------------------+ |Chief Technology Officer | |DM Solutions Group Inc http://www.dmsolutions.ca/ | +-----------------------------------------------------------------+ From lorenzo at ominiverdi.com Sat Sep 8 16:09:56 2007 From: lorenzo at ominiverdi.com (Lorenzo Becchi) Date: Wed Sep 1 17:23:31 2010 Subject: [OpenLayers-Dev] foss4g coding sprint In-Reply-To: <2A41ADD8-CA27-43B3-B947-435334F6815F@dmsolutions.ca> References: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> <46E2F39F.2010200@ominiverdi.com> <2A41ADD8-CA27-43B3-B947-435334F6815F@dmsolutions.ca> Message-ID: <46E30194.6030207@ominiverdi.com> > Thanks Lorenzo! I guess I should pay attention ;) > you're welcome, so many things are happing all around... I was guessing if it's time to book a room for the WebMap BOF, does anybody asked for one? probably we should just choose one, before they are finished, and tell everybody. ciao Lorenzo > On 8-Sep-07, at 3:10 PM, Lorenzo Becchi wrote: > > >> Hi Paul, >> there's a list here: >> http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers >> >> >> >> Paul Spencer wrote: >> >>> Just wondering who is going to join the OL coding sprint and what >>> folks are interested in working on? >>> >>> Cheers >>> >>> Paul >>> >>> PS I'll be there and I am interested in animated zooming, adding >>> a renderer, performance and visual improvements (maps >>> 'flash' a lot!), and generally anything else that will move OL >>> forward. >>> >>> +-----------------------------------------------------------------+ >>> |Paul Spencer pspencer@dmsolutions.ca | >>> +-----------------------------------------------------------------+ >>> |Chief Technology Officer | >>> |DM Solutions Group Inc http://www.dmsolutions.ca/ | >>> +-----------------------------------------------------------------+ >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@openlayers.org >>> http://openlayers.org/mailman/listinfo/dev >>> >>> > > +-----------------------------------------------------------------+ > |Paul Spencer pspencer@dmsolutions.ca | > +-----------------------------------------------------------------+ > |Chief Technology Officer | > |DM Solutions Group Inc http://www.dmsolutions.ca/ | > +-----------------------------------------------------------------+ > > > > > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > From andreas.hocevar at gmail.com Sun Sep 9 10:26:48 2007 From: andreas.hocevar at gmail.com (Andreas Hocevar) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] foss4g coding sprint In-Reply-To: <46E30194.6030207@ominiverdi.com> References: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> <46E2F39F.2010200@ominiverdi.com> <2A41ADD8-CA27-43B3-B947-435334F6815F@dmsolutions.ca> <46E30194.6030207@ominiverdi.com> Message-ID: <5b021dd0709090726x18630f35rf1024b1b268c8fe7@mail.gmail.com> Hi, I would also love to attend the code sprint. I am working on some SLD parsing/rendering stuff right now, which obviously would fit in there. Regards, Andreas. From bluecarto at gmail.com Mon Sep 10 05:41:57 2007 From: bluecarto at gmail.com (Pierre GIRAUD) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] foss4g coding sprint In-Reply-To: <46E30194.6030207@ominiverdi.com> References: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> <46E2F39F.2010200@ominiverdi.com> <2A41ADD8-CA27-43B3-B947-435334F6815F@dmsolutions.ca> <46E30194.6030207@ominiverdi.com> Message-ID: I'm now in the list and I'm looking forward to helping the coding team. Regards On 9/8/07, Lorenzo Becchi wrote: > > > Thanks Lorenzo! I guess I should pay attention ;) > > > > you're welcome, so many things are happing all around... > > I was guessing if it's time to book a room for the WebMap BOF, > does anybody asked for one? > > probably we should just choose one, before they are finished, and tell > everybody. > > ciao > Lorenzo > > > > On 8-Sep-07, at 3:10 PM, Lorenzo Becchi wrote: > > > > > >> Hi Paul, > >> there's a list here: > >> http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers > >> > >> > >> > >> Paul Spencer wrote: > >> > >>> Just wondering who is going to join the OL coding sprint and what > >>> folks are interested in working on? > >>> > >>> Cheers > >>> > >>> Paul > >>> > >>> PS I'll be there and I am interested in animated zooming, adding > >>> a renderer, performance and visual improvements (maps > >>> 'flash' a lot!), and generally anything else that will move OL > >>> forward. > >>> > >>> +-----------------------------------------------------------------+ > >>> |Paul Spencer pspencer@dmsolutions.ca | > >>> +-----------------------------------------------------------------+ > >>> |Chief Technology Officer | > >>> |DM Solutions Group Inc http://www.dmsolutions.ca/ | > >>> +-----------------------------------------------------------------+ > >>> > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> Dev mailing list > >>> Dev@openlayers.org > >>> http://openlayers.org/mailman/listinfo/dev > >>> > >>> > > > > +-----------------------------------------------------------------+ > > |Paul Spencer pspencer@dmsolutions.ca | > > +-----------------------------------------------------------------+ > > |Chief Technology Officer | > > |DM Solutions Group Inc http://www.dmsolutions.ca/ | > > +-----------------------------------------------------------------+ > > > > > > > > > > > > _______________________________________________ > > Dev mailing list > > Dev@openlayers.org > > http://openlayers.org/mailman/listinfo/dev > > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > From madair at dmsolutions.ca Mon Sep 10 08:52:20 2007 From: madair at dmsolutions.ca (Mike Adair) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] foss4g coding sprint In-Reply-To: <46E2F39F.2010200@ominiverdi.com> References: <1466B2E9-FA15-43AF-95DB-439ECCB6295A@dmsolutions.ca> <46E2F39F.2010200@ominiverdi.com> Message-ID: <46E53E04.5000701@dmsolutions.ca> I'll be attending as well. How about adding coordinate transformation support from the Proj4js/cscs library? Mike Lorenzo Becchi wrote: > Hi Paul, > there's a list here: > http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers > > > > Paul Spencer wrote: > >> Just wondering who is going to join the OL coding sprint and what >> folks are interested in working on? >> >> Cheers >> >> Paul >> >> PS I'll be there and I am interested in animated zooming, adding a >> renderer, performance and visual improvements (maps 'flash' >> a lot!), and generally anything else that will move OL forward. >> >> +-----------------------------------------------------------------+ >> |Paul Spencer pspencer@dmsolutions.ca | >> +-----------------------------------------------------------------+ >> |Chief Technology Officer | >> |DM Solutions Group Inc http://www.dmsolutions.ca/ | >> +-----------------------------------------------------------------+ >> >> >> >> >> >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev >> >> > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > > From john.cole at uai.com Mon Sep 10 11:40:57 2007 From: john.cole at uai.com (John Cole) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OL 2.4 conflict with MS Ajax.Net Message-ID: <76758090F8686C47A44B6FF52514A1D307909E61@hermes.uai.int> I?ve run into an issue with OL 2.4 (branch HEAD) and Microsoft Ajax.Net. In BaseTypes.js, the following function: String.prototype.trim = function() { var b = 0; while(this.substr(b,1) == " ") { b++; } var e = this.length - 1; while(this.substr(e,1) == " ") { e--; } return this.substring(b, e+1); }; Is failing because e is going negative and goes into an endless loop. The string being fed (from an Ajax.Net call) is simply two spaces (? ?). It appears that Ajax.Net is also prototyping a trim function onto String, and commenting out the one in BaseTypes.js gets everything working again. How do you detect that a function has already been prototyped on to a class so OL doesn?t have to do it? Here is a test_String.html that confirms the issue. Thanks, John No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.13/998 - Release Date: 9/10/2007 8:48 AM This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070910/b667fa77/attachment.html From lorenzo at ominiverdi.com Mon Sep 10 12:50:23 2007 From: lorenzo at ominiverdi.com (Lorenzo Becchi) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Users] drag and drop layer control Message-ID: <46E575CF.8070709@ominiverdi.com> > > Hi list, > > is there anybody who has implemented (and is willing to share) a layer > control which can do drag and drop of layers and/or change the opacity of > layers? > > Thanks in advance. > > Best regards, > Bart > Hi Bart, I have to admit that in OL lists it's not clear to me what should go in Dev-List and what on User-List. Sorry for cross posting. I have no plan for a drag&drop for layers but I've worked to enhance OL legend while working at WMSManager [1]. There is a simple (no images just HTML) interface for Opacity control, Drop Layer, Switch Layer Up/Down. There is also a Zoom to Layer Extent button, supposing that you've set it somewhere. I don't know who can be interested in such a set of functions and if OL team could be interested to include in the official legend at least the opacity control. ciao Lorenzo [1] http://www.ominiverdi.org/openlayers/sandbox/openlayers/examples/wms_manager.html From dgraf at progeny.net Mon Sep 10 14:26:35 2007 From: dgraf at progeny.net (Graf, David) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Marker Vector Trouble Message-ID: <58F745CA67B0F449BF5B237DD460FE6C17DB7D@es-22a.manassas.progeny.net> I have a Vector Layer and a Marker Layer on a map. I'm having difficulty getting the features from the vector layer to match up with the markers in the marker layer. Meaning that if I set up a marker with a LonLat and give the same LonLat to the feature from the vector layer they don't end up in the same spot on the map. And when zooming in the two objects get farther way and zooming in the objects become closer until they are at the same spot. I am thoroughly confused as to why there should be a problem like this. Thanks, - Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070910/f10ba67e/attachment.html From ryan.hofschneider at ngc.com Mon Sep 10 15:42:47 2007 From: ryan.hofschneider at ngc.com (Ryan Hofschneider) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Marker Vector Trouble In-Reply-To: <58F745CA67B0F449BF5B237DD460FE6C17DB7D@es-22a.manassas.progeny.net> References: <58F745CA67B0F449BF5B237DD460FE6C17DB7D@es-22a.manassas.progeny.net> Message-ID: On Sep 10, 2007, at 11:26 AM, Graf, David wrote: > I'm having difficulty getting the features from the vector layer to > match up with the markers in the marker layer. Meaning that if I > set up a marker with a LonLat and give the same LonLat to the > feature from the vector layer they don't end up in the same spot on > the map. When using markers with the WFS layer class I discovered that the default icon that is created in Marker.js (line 195 in the trunk copy) offsets it by a certain amount. Maybe you've come across the same thing. If you want it exactly centered over the position, I believe you want something like OpenLayers.Pixel(-(size.w/2), -(size.h/2)) when you define your Icon. For my particular case of WFS markers, I sub- classed the OpenLayers.Feature.WFS class and provided a new implementation of createMarker() which provided an icon with my desired offsets. Although you aren't using the WFS class, you could do something similar. Cheers, Ryan From fporcelli at taic.net Mon Sep 10 20:02:13 2007 From: fporcelli at taic.net (Frank Porcelli) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] KML support Message-ID: <003d01c7f407$01cc40a0$6401a8ac@ISLANDER> Hello dev list - I was wondering if anyone can tell me to what extent cross browser support for KML data will be supported in the 2.5 release of OL? Currently we're able to get KML data to display using Firefox, but IE6 does not work. Also we noticed that KML files that use the 2.1 spec do not work because the 2.0 kml namespace is explicitly referenced in the code. I apologize if this has been asked before. Thanks, Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070910/320cb7fc/attachment.html From crschmidt at metacarta.com Mon Sep 10 21:37:40 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] KML support In-Reply-To: <003d01c7f407$01cc40a0$6401a8ac@ISLANDER> References: <003d01c7f407$01cc40a0$6401a8ac@ISLANDER> Message-ID: <20070911013740.GA21342@metacarta.com> On Mon, Sep 10, 2007 at 08:02:13PM -0400, Frank Porcelli wrote: > Hello dev list - > > I was wondering if anyone can tell me to what extent cross browser support > for KML data will be supported in the 2.5 release of OL? I'm not 100% sure yet, but it looks like: * KML will have better geometry support for reading * KML will have write support * KML will have cross browser support Will be the state in 2.5. (Tim and I are currently bouncing the code back and forth.) > Currently we're > able to get KML data to display using Firefox, but IE6 does not work. Also > we noticed that KML files that use the 2.1 spec do not work because the 2.0 > kml namespace is explicitly referenced in the code. Patches to change this behavior are welcome, but at the moment, you need to know what you're going to parse. If it's 2.1, you can simply change the kmlns: var k = new OpenLayers.Format.KML({'kmlns':'http://earth.google.com/kml/2.1'}); Regards, -- Christopher Schmidt MetaCarta From frederic.junod at camptocamp.com Tue Sep 11 03:02:02 2007 From: frederic.junod at camptocamp.com (=?UTF-8?B?RnLDqWTDqXJpYw==?= Junod) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OL 2.4 conflict with MS Ajax.Net In-Reply-To: <76758090F8686C47A44B6FF52514A1D307909E61@hermes.uai.int> References: <76758090F8686C47A44B6FF52514A1D307909E61@hermes.uai.int> Message-ID: <20070911090202.6d400b30@localhost.localdomain> John, I have opened a ticket for that, see: http://trac.openlayers.org/ticket/961 fredj Le Mon, 10 Sep 2007 10:40:57 -0500, John Cole a ?crit : > I?ve run into an issue with OL 2.4 (branch HEAD) and Microsoft Ajax.Net. > In BaseTypes.js, the following function: > String.prototype.trim = function() { > var b = 0; > while(this.substr(b,1) == " ") { > b++; > } > var e = this.length - 1; > while(this.substr(e,1) == " ") { > e--; > } > return this.substring(b, e+1); > > }; > > Is failing because e is going negative and goes into an endless loop. The > string being fed (from an Ajax.Net call) is simply two spaces (? ?). > > It appears that Ajax.Net is also prototyping a trim function onto String, > and commenting out the one in BaseTypes.js gets everything working again. > How do you detect that a function has already been prototyped on to a class > so OL doesn?t have to do it? > > > Thanks, > > John -- Fr?d?ric Junod Camptocamp SA From crschmidt at metacarta.com Tue Sep 11 07:48:22 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OL 2.4 conflict with MS Ajax.Net In-Reply-To: <20070911090202.6d400b30@localhost.localdomain> References: <76758090F8686C47A44B6FF52514A1D307909E61@hermes.uai.int> <20070911090202.6d400b30@localhost.localdomain> Message-ID: <20070911114822.GA13702@metacarta.com> On Tue, Sep 11, 2007 at 09:02:02AM +0200, Fr??d??ric Junod wrote: > John, > > I have opened a ticket for that, see: > http://trac.openlayers.org/ticket/961 #961 should fix the OL bug, and #962 has been opened to fix the larger issue (clobbering existing prototypes) for 2.6. Regards, -- Christopher Schmidt MetaCarta From john.cole at uai.com Tue Sep 11 08:56:02 2007 From: john.cole at uai.com (John Cole) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OL 2.4 conflict with MS Ajax.Net Message-ID: <76758090F8686C47A44B6FF52514A1D307909E69@hermes.uai.int> Christopher, What is the policy on applying bug fixes to released versions? I've added a patch to 961 for 2.4 HEAD, and I was wondering if it can get applied to 2.4. Thanks, John -----Original Message----- From: Christopher Schmidt [mailto:crschmidt@metacarta.com] Sent: Tuesday, September 11, 2007 6:48 AM To: Fr??d??ric Junod Cc: John Cole; dev@openlayers Subject: Re: [OpenLayers-Dev] OL 2.4 conflict with MS Ajax.Net On Tue, Sep 11, 2007 at 09:02:02AM +0200, Fr??d??ric Junod wrote: > John, > > I have opened a ticket for that, see: > http://trac.openlayers.org/ticket/961 #961 should fix the OL bug, and #962 has been opened to fix the larger issue (clobbering existing prototypes) for 2.6. Regards, -- Christopher Schmidt MetaCarta No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.13/998 - Release Date: 9/10/2007 8:48 AM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.13/998 - Release Date: 9/10/2007 8:48 AM This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. From crschmidt at metacarta.com Tue Sep 11 09:53:35 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OL 2.4 conflict with MS Ajax.Net In-Reply-To: <76758090F8686C47A44B6FF52514A1D307909E69@hermes.uai.int> References: <76758090F8686C47A44B6FF52514A1D307909E69@hermes.uai.int> Message-ID: <20070911135335.GB25686@metacarta.com> On Tue, Sep 11, 2007 at 07:56:02AM -0500, John Cole wrote: > Christopher, > What is the policy on applying bug fixes to released versions? I've added > a patch to 961 for 2.4 HEAD, and I was wondering if it can get applied to > 2.4. We've never touched a release once we tagged a final, and given that we'll have an RC out for 2.5 in the next two weeks, I'm hesitant to change that now. Doing an RC cycle against a 2.4.1 at the same time we're doing an RC cycle against 2.5 sounds... suboptimal. It's certainly something that could be brought up, but the current tendancy is not to do much with the branches once we release, to lower our releng cost. The best path for you is to roll your own by patching 2.4, and help test/review to get 2.5 out the door :) Regards, -- Christopher Schmidt MetaCarta From john.cole at uai.com Tue Sep 11 11:50:01 2007 From: john.cole at uai.com (John Cole) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] updating release versions (was: OL 2.4 conflict with MS Ajax.Net) Message-ID: <76758090F8686C47A44B6FF52514A1D307909E6B@hermes.uai.int> Christopher, This may be something that deserves more discussion, especially as OL continues to grow. It's not going to effect me much now, as I'm already running a separate copy of OL (pre 2.4 because we went live before 2.4 went gold), but in the future, as existing apps continue to run on older versions of OL, it will effect me greatly. Bug fixes might not require a new RC cycle, depending on the scope of the changes, and one could argue that any fix that would require a new RC shouldn't be applied. However, small bugs or security issues will crop up and it would be nice to have the release branch actually contain the fixes, instead of having everyone maintain their own, partially fixed versions. As I said, it isn't a large issue now, but it would be nice to have a version receive updates for some planned period of time, especially when it?s the current version. :-) As more apps go online with OL, this will be an issue in the future. Thanks, John -----Original Message----- From: Christopher Schmidt [mailto:crschmidt@metacarta.com] Sent: Tuesday, September 11, 2007 8:54 AM To: John Cole Cc: Fr??d??ric Junod; dev@openlayers Subject: Re: [OpenLayers-Dev] OL 2.4 conflict with MS Ajax.Net On Tue, Sep 11, 2007 at 07:56:02AM -0500, John Cole wrote: > Christopher, > What is the policy on applying bug fixes to released versions? I've added > a patch to 961 for 2.4 HEAD, and I was wondering if it can get applied to > 2.4. We've never touched a release once we tagged a final, and given that we'll have an RC out for 2.5 in the next two weeks, I'm hesitant to change that now. Doing an RC cycle against a 2.4.1 at the same time we're doing an RC cycle against 2.5 sounds... suboptimal. It's certainly something that could be brought up, but the current tendancy is not to do much with the branches once we release, to lower our releng cost. The best path for you is to roll your own by patching 2.4, and help test/review to get 2.5 out the door :) Regards, -- Christopher Schmidt MetaCarta No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.14/999 - Release Date: 9/10/2007 5:43 PM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.14/999 - Release Date: 9/10/2007 5:43 PM This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. From tschaub at openplans.org Tue Sep 11 13:11:30 2007 From: tschaub at openplans.org (Tim Schaub) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <46DD6BA4.4010404@camptocamp.com> References: <46C1B940.2030407@camptocamp.com> <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com> <46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> Message-ID: <46E6CC42.3000901@openplans.org> Damien Corpataux wrote: > Hi Tim, > > I just posted a patch on ticket #927. The patch suits the requirements: > - KML extends XML > - XML class methods are used for XML manipulation > - tested on FF2/Linux and IE7 > - KML.write() returns a string (using XML.write()) > - GGE import of OL exported KML is working, and vice-versa > > My 2 cents > > Cheers, > Damien > Thanks for the patch Damien. I rewrote things a bit and put this in with r4219 [1]. I added support for KML MultiGeometry and improved the read/write stuff so all OL geometries are supported. Also, name/description attributes and feature id survive a round trip through read/write. There are likely still issues with the parser. In particular, we don't write out feature attributes (beyond name/description). You can play with the vector formats example to see OL KML output [2]. Paste in any KML you can find and report back any trouble with the parser. Tim [1] http://trac.openlayers.org/changeset/4219 [2] http://openlayers.org/dev/examples/vector-formats.html > > Tim Schaub wrote: >> I've opened ticket #927 to track this. >> >> If anybody has a patch for KML, please attach it to that ticket. >> Damien, I've referenced your email on the ticket. >> >> Since XML flavors should now all inherit from the XML format class, I'd >> say that write will always return a string. >> >> Thanks for any contributions. >> Tim >> >> >> Damien Corpataux wrote: >> >>> Hello, >>> >>> As far as I can see, the advantages of doing so are obvious. Althought I >>> didn't have time to apply these, here is a new version of the patch: >>> - puts placemarks in a folder tag (for google earth import) >>> - bugfix with geometry tags >>> >>> Is the question about write() return type (string or DOMDocuemt/DOMNode) >>> still open? >>> >>> Cheers, >>> Damien >>> >>> >>> Patch: >>> Index: /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >>> =================================================================== >>> --- >>> /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >>> (revision 3900) >>> +++ >>> /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >>> (working copy) >>> @@ -8,8 +8,8 @@ >>> * @requires OpenLayers/Ajax.js >>> * >>> * Class: OpenLayers.Format.KML >>> - * Read only KML. Largely Proof of Concept: does not support advanced >>> Features, >>> - * including Polygons. Create a new instance with the >>> + * Read/write KML 2.0. Does not support advanced Features. >>> + * Create a new instance with the >>> * constructor. >>> * >>> * Inherits from: >>> @@ -24,6 +24,24 @@ >>> kmlns: "http://earth.google.com/kml/2.0", >>> >>> /** >>> + * APIProperty: placemarksDesc >>> + * Default description for a placemark >>> + */ >>> + placemarksDesc: "No description available", >>> + >>> + /** >>> + * APIProperty: foldersName >>> + * Default name for a folder >>> + */ >>> + foldersName: "OpenLayers export", >>> + >>> + /** >>> + * APIProperty: foldersDesc >>> + * Default description for a folder >>> + */ >>> + foldersDesc: "Exported on " + new Date(), >>> + >>> + /** >>> * Constructor: OpenLayers.Format.KML >>> * Create a new parser for KML >>> * >>> @@ -46,7 +64,7 @@ >>> if (typeof data == "string") { >>> data = OpenLayers.parseXMLString(data); >>> } >>> - var featureNodes = OpenLayers.Ajax.getElementsByTagNameNS(data, >>> this.kmlns, "", "Placemark"); >>> + var featureNodes = OpenLayers.Ajax.getElementsByTagNameNS(data, >>> this.kmlns, "kml", "Placemark"); >>> >>> var features = []; >>> >>> @@ -100,6 +118,19 @@ >>> // TBD Bounds only set for one of multiple geometries >>> geom.extendBounds(p.bounds); >>> } >>> + >>> + // match Polygon >>> + } else if (OpenLayers.Ajax.getElementsByTagNameNS(xmlNode, >>> + this.kmlns, "", "Polygon").length != 0) { >>> + var polygon = OpenLayers.Ajax.getElementsByTagNameNS(xmlNode, >>> + this.kmlns, "", "Polygon")[0]; >>> + p = this.parseCoords(polygon); >>> + if (p.points) { >>> + var linearRing = new >>> OpenLayers.Geometry.LinearRing(p.points); >>> + geom = new OpenLayers.Geometry.Polygon(linearRing); >>> + // TBD Bounds only set for one of multiple geometries >>> + geom.extendBounds(p.bounds); >>> + } >>> } >>> >>> feature.geometry = geom; >>> @@ -191,5 +222,171 @@ >>> return p; >>> }, >>> >>> + /** >>> + * Method: write >>> + * Accept Feature Collection, and return an XML Document. >>> + * >>> + * Parameters: >>> + * features - An array of features. >>> + * >>> + * Returns: >>> + * >>> + */ >>> + write: function(features) { >>> + var kml = document.createElementNS(this.kmlns, "kml"); >>> + var folder = this.createFolderXML(); >>> + for (var i=0; i < features.length; i++) { >>> + folder.appendChild(this.createPlacemarkXML(features[i])); >>> + } >>> + kml.appendChild(folder); >>> + return kml; >>> + }, >>> + >>> + /** >>> + * Method: createFolderXML >>> + * Creates and returns a KML Folder node with default name and >>> description >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + createFolderXML: function() { >>> + // Folder name >>> + var folderName = document.createElementNS(this.kmlns, "name"); >>> + var folderNameText = document.createTextNode(this.foldersName); >>> + folderName.appendChild(folderNameText); >>> + >>> + // Folder description >>> + var folderDesc = document.createElementNS(this.kmlns, >>> "description"); >>> + var folderDescText = document.createTextNode(this.foldersDesc); >>> + folderDesc.appendChild(folderDescText); >>> + >>> + // Folder >>> + var folder = document.createElementNS(this.kmlns, "Folder"); >>> + folder.appendChild(folderName); >>> + folder.appendChild(folderDesc); >>> + >>> + return folder; >>> + }, >>> + >>> + /** >>> + * Method: createPlacemarkXML >>> + * Accept an OpenLayers.Feature.Vector, and create a KML Placemark node >>> + * >>> + * Parameters: >>> + * feature - {} >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + createPlacemarkXML: function(feature) { >>> + // Placemark name >>> + var placemarkName = document.createElementNS(this.kmlns, "name"); >>> + var placemarkNameText = document.createTextNode(feature.id); >>> + placemarkName.appendChild(placemarkNameText); >>> + >>> + // Placemark description >>> + var placemarkDesc = document.createElementNS(this.kmlns, >>> "description"); >>> + var placemarkDescText = >>> document.createTextNode(this.placemarksDesc); >>> + placemarkDesc.appendChild(placemarkDescText); >>> + >>> + // Placemark >>> + var placemarkNode = document.createElementNS(this.kmlns, >>> "Placemark"); >>> + placemarkNode.appendChild(placemarkName); >>> + placemarkNode.appendChild(placemarkDesc); >>> + >>> + // Geometry node (Point, LineString, etc. nodes) >>> + var geometryNode = this.buildGeometryNode(feature.geometry); >>> + placemarkNode.appendChild(geometryNode); >>> + >>> + return placemarkNode; >>> + }, >>> + >>> + /** >>> + * Method: buildGeometryNode >>> + * Builds a KML geometry node with a given geometry >>> + * >>> + * Parameters: >>> + * geometry - {} >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + buildGeometryNode: function(geometry) { >>> + // TBD test if geoserver can be given a Multi-geometry for a >>> simple-geometry data store >>> + // ie if multipolygon can be sent for a polygon feature type >>> + var kml = ""; >>> + // match MultiPolygon or Polygon >>> + if (geometry.CLASS_NAME == "OpenLayers.Geometry.MultiPolygon" >>> + || geometry.CLASS_NAME == "OpenLayers.Geometry.Polygon") { >>> + kml = document.createElementNS(this.kmlns, 'Polygon'); >>> + >>> + var outerRing = document.createElementNS(this.kmlns, >>> 'outerBoundaryIs'); >>> + var linearRing = document.createElementNS(this.kmlns, >>> 'LinearRing'); >>> + >>> + // TBD manage polygons with holes >>> + >>> linearRing.appendChild(this.buildCoordinatesNode(geometry.components[0])); >>> + outerRing.appendChild(linearRing); >>> + >>> + kml.appendChild(outerRing); >>> + } >>> + // match MultiLineString or LineString >>> + else if (geometry.CLASS_NAME == >>> "OpenLayers.Geometry.MultiLineString" >>> + || geometry.CLASS_NAME == >>> "OpenLayers.Geometry.LineString") { >>> + kml = document.createElementNS(this.kmlns, >>> 'LineString'); >>> + >>> + kml.appendChild(this.buildCoordinatesNode(geometry)); >>> + } >>> + // match MultiPoint or Point >>> + else if (geometry.CLASS_NAME == "OpenLayers.Geometry.Point" || >>> + geometry.CLASS_NAME == >>> "OpenLayers.Geometry.MultiPoint") { >>> + kml = document.createElementNS(this.kmlns, 'Point'); >>> + >>> + // FIXME: There should be only one Point node per >>> Placemark node >>> + var parts = ""; >>> + if (geometry.CLASS_NAME == >>> "OpenLayers.Geometry.MultiPoint") { >>> + parts = geometry.components; >>> + } else { >>> + parts = [geometry]; >>> + } >>> + >>> + for (var i = 0; i < parts.length; i++) { >>> + kml.appendChild(this.buildCoordinatesNode(parts[i])); >>> + } >>> + } >>> + return kml; >>> + }, >>> + /** >>> + * Method: buildCoordinatesNode >>> + * builds the KML coordinates node >>> + * >>> + * Parameters: >>> + * geometry - {} >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + buildCoordinatesNode: function(geometry) { >>> + var coordinatesNode = document.createElementNS(this.kmlns, >>> "coordinates"); >>> + >>> + var points = null; >>> + if (geometry.components) { >>> + points = geometry.components; >>> + } >>> + >>> + var path = ""; >>> + if (points) { >>> + for (var i = 0; i < points.length; i++) { >>> + path += points[i].x + "," + points[i].y + " "; >>> + } >>> + } else { >>> + path += geometry.x + "," + geometry.y + " "; >>> + } >>> + >>> + var txtNode = document.createTextNode(path); >>> + coordinatesNode.appendChild(txtNode); >>> + >>> + return coordinatesNode; >>> + }, >>> + >>> CLASS_NAME: "OpenLayers.Format.KML" >>> }); >>> >>> >>> Tim Schaub wrote: >>> >>>> Hi- >>>> >>>> So, we're mid-way through changing how XML flavors are read/written in >>>> OpenLayers. >>>> >>>> I've checked a new XML format in to the trunk. This format has most of >>>> the methods we need for reading/writing XML cross-browser. >>>> >>>> To parse other XML flavors, format classes should be created that >>>> inherit from the XML format. >>>> >>>> For an (incomplete) example, see: >>>> http://dev.openlayers.org/sandbox/tschaub/xml/lib/OpenLayers/Format/GML.js >>>> >>>> (The important part to notice in the above example is that the GML >>>> format inherits from the XML format.) >>>> >>>> Instead of using OpenLayers.Ajax methods or document methods, DOM >>>> creation and traversal should be done with OpenLayers.Format.XML >>>> methods. I've created methods to reflect the W3C standard XML DOM >>>> methods - wrapping the standard ones and accommodating for non-compliant >>>> browsers. >>>> >>>> If you (or anyone) needs additional XML DOM methods, they should be >>>> added to the XML format. The next addition (in my mind) is >>>> setAttributeNS. Aside from that, you should be able to do efficient >>>> parsing and dom creation with the XML format methods. >>>> >>>> Please make modifications to the KML format in the trunk. Create a >>>> ticket and attach patches in Trac. I can offer review or other help as >>>> needed. >>>> >>>> I don't have time to keep these sandboxes entirely clean right now - so >>>> please forgive anything you find that is in a half-developed state. >>>> >>>> Tim >>>> >>>> PS - Eventually, I'll move the following example into the trunk. It >>>> would be nice if we could demonstrate read/write capability for all >>>> vector formats in this way: >>>> http://dev.openlayers.org/sandbox/tschaub/xml/examples/vector-formats.html >>>> >>>> (note again that this reflects partially complete work - and you should >>>> not be surprised to encounter errors or see changes at any time) >>>> >>>> >>>> Damien Corpataux wrote: >>>> >>>> >>>>> Hello, >>>>> >>>>> Here's what I did so far... Reading KML only work for KML 2.0 namespaces >>>>> for write() uses OpenLayers.Ajax.getElementsByTagNameNS(), but I'm >>>>> pretty sure it will work on future versions (2.1 parsing successful). >>>>> Also, GML and KML write() returns a Dom Document rather than a string. >>>>> Should one change the result type, breaking OpenLayers.Format interface, >>>>> or parse it into a string using OpenLayers.XML.....? >>>>> >>>>> Cheers, >>>>> Damien >>>>> >>>>> >>>>> >>> [patch stripped] >>> >>> -- >>> Camptocamp SA >>> Damien Corpataux >>> PSE A >>> CH-1015 Lausanne >>> +41 21 619 10 22 (Direct) >>> +41 21 619 10 10 (Centrale) >>> +41 21 619 10 00 (Fax) >>> P Please consider the environment >>> Do you really need to print this email? >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@openlayers.org >>> http://openlayers.org/mailman/listinfo/dev >>> >>> >>> !DSPAM:4033,46cd662e41812090977483! >>> >> >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev >> > > > -- > Camptocamp SA > Damien Corpataux > PSE A > CH-1015 Lausanne > +41 21 619 10 22 (Direct) > +41 21 619 10 10 (Centrale) > +41 21 619 10 00 (Fax) > P Please consider the environment > Do you really need to print this email? > !DSPAM:4033,46dd6bc8182553362379201! From fporcelli at taic.net Tue Sep 11 20:50:21 2007 From: fporcelli at taic.net (Frank Porcelli) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OpenLayers.Format.KML.write() In-Reply-To: <46E6CC42.3000901@openplans.org> References: <46C1B940.2030407@camptocamp.com> <20070814152052.GA22295@metacarta.com> <46C30F52.6030000@camptocamp.com> <46C3182F.7060801@openplans.org> <46CD6611.5040501@camptocamp.com><46CF42ED.30502@openplans.org> <46DD6BA4.4010404@camptocamp.com> <46E6CC42.3000901@openplans.org> Message-ID: <004b01c7f4d6$e59cb6a0$6401a8ac@ISLANDER> Hi Tim -- The only thing I noticed is when using IE6 the KML features do not overlay with the same map when using IE7 or Firefox. It seems the features in IE6 are not displaying at the correct locations. Is this a known bug? Regards, Frank -----Original Message----- From: dev-bounces@openlayers.org [mailto:dev-bounces@openlayers.org] On Behalf Of Tim Schaub Sent: Tuesday, September 11, 2007 1:12 PM To: dev@openlayers.org Subject: Re: [OpenLayers-Dev] OpenLayers.Format.KML.write() Damien Corpataux wrote: > Hi Tim, > > I just posted a patch on ticket #927. The patch suits the requirements: > - KML extends XML > - XML class methods are used for XML manipulation > - tested on FF2/Linux and IE7 > - KML.write() returns a string (using XML.write()) > - GGE import of OL exported KML is working, and vice-versa > > My 2 cents > > Cheers, > Damien > Thanks for the patch Damien. I rewrote things a bit and put this in with r4219 [1]. I added support for KML MultiGeometry and improved the read/write stuff so all OL geometries are supported. Also, name/description attributes and feature id survive a round trip through read/write. There are likely still issues with the parser. In particular, we don't write out feature attributes (beyond name/description). You can play with the vector formats example to see OL KML output [2]. Paste in any KML you can find and report back any trouble with the parser. Tim [1] http://trac.openlayers.org/changeset/4219 [2] http://openlayers.org/dev/examples/vector-formats.html > > Tim Schaub wrote: >> I've opened ticket #927 to track this. >> >> If anybody has a patch for KML, please attach it to that ticket. >> Damien, I've referenced your email on the ticket. >> >> Since XML flavors should now all inherit from the XML format class, I'd >> say that write will always return a string. >> >> Thanks for any contributions. >> Tim >> >> >> Damien Corpataux wrote: >> >>> Hello, >>> >>> As far as I can see, the advantages of doing so are obvious. Althought I >>> didn't have time to apply these, here is a new version of the patch: >>> - puts placemarks in a folder tag (for google earth import) >>> - bugfix with geometry tags >>> >>> Is the question about write() return type (string or DOMDocuemt/DOMNode) >>> still open? >>> >>> Cheers, >>> Damien >>> >>> >>> Patch: >>> Index: /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >>> =================================================================== >>> --- >>> /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >>> (revision 3900) >>> +++ >>> /home/dcorpataux/workspace/openlayers/lib/OpenLayers/Format/KML.js >>> (working copy) >>> @@ -8,8 +8,8 @@ >>> * @requires OpenLayers/Ajax.js >>> * >>> * Class: OpenLayers.Format.KML >>> - * Read only KML. Largely Proof of Concept: does not support advanced >>> Features, >>> - * including Polygons. Create a new instance with the >>> + * Read/write KML 2.0. Does not support advanced Features. >>> + * Create a new instance with the >>> * constructor. >>> * >>> * Inherits from: >>> @@ -24,6 +24,24 @@ >>> kmlns: "http://earth.google.com/kml/2.0", >>> >>> /** >>> + * APIProperty: placemarksDesc >>> + * Default description for a placemark >>> + */ >>> + placemarksDesc: "No description available", >>> + >>> + /** >>> + * APIProperty: foldersName >>> + * Default name for a folder >>> + */ >>> + foldersName: "OpenLayers export", >>> + >>> + /** >>> + * APIProperty: foldersDesc >>> + * Default description for a folder >>> + */ >>> + foldersDesc: "Exported on " + new Date(), >>> + >>> + /** >>> * Constructor: OpenLayers.Format.KML >>> * Create a new parser for KML >>> * >>> @@ -46,7 +64,7 @@ >>> if (typeof data == "string") { >>> data = OpenLayers.parseXMLString(data); >>> } >>> - var featureNodes = OpenLayers.Ajax.getElementsByTagNameNS(data, >>> this.kmlns, "", "Placemark"); >>> + var featureNodes = OpenLayers.Ajax.getElementsByTagNameNS(data, >>> this.kmlns, "kml", "Placemark"); >>> >>> var features = []; >>> >>> @@ -100,6 +118,19 @@ >>> // TBD Bounds only set for one of multiple geometries >>> geom.extendBounds(p.bounds); >>> } >>> + >>> + // match Polygon >>> + } else if (OpenLayers.Ajax.getElementsByTagNameNS(xmlNode, >>> + this.kmlns, "", "Polygon").length != 0) { >>> + var polygon = OpenLayers.Ajax.getElementsByTagNameNS(xmlNode, >>> + this.kmlns, "", "Polygon")[0]; >>> + p = this.parseCoords(polygon); >>> + if (p.points) { >>> + var linearRing = new >>> OpenLayers.Geometry.LinearRing(p.points); >>> + geom = new OpenLayers.Geometry.Polygon(linearRing); >>> + // TBD Bounds only set for one of multiple geometries >>> + geom.extendBounds(p.bounds); >>> + } >>> } >>> >>> feature.geometry = geom; >>> @@ -191,5 +222,171 @@ >>> return p; >>> }, >>> >>> + /** >>> + * Method: write >>> + * Accept Feature Collection, and return an XML Document. >>> + * >>> + * Parameters: >>> + * features - An array of features. >>> + * >>> + * Returns: >>> + * >>> + */ >>> + write: function(features) { >>> + var kml = document.createElementNS(this.kmlns, "kml"); >>> + var folder = this.createFolderXML(); >>> + for (var i=0; i < features.length; i++) { >>> + folder.appendChild(this.createPlacemarkXML(features[i])); >>> + } >>> + kml.appendChild(folder); >>> + return kml; >>> + }, >>> + >>> + /** >>> + * Method: createFolderXML >>> + * Creates and returns a KML Folder node with default name and >>> description >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + createFolderXML: function() { >>> + // Folder name >>> + var folderName = document.createElementNS(this.kmlns, "name"); >>> + var folderNameText = document.createTextNode(this.foldersName); >>> + folderName.appendChild(folderNameText); >>> + >>> + // Folder description >>> + var folderDesc = document.createElementNS(this.kmlns, >>> "description"); >>> + var folderDescText = document.createTextNode(this.foldersDesc); >>> + folderDesc.appendChild(folderDescText); >>> + >>> + // Folder >>> + var folder = document.createElementNS(this.kmlns, "Folder"); >>> + folder.appendChild(folderName); >>> + folder.appendChild(folderDesc); >>> + >>> + return folder; >>> + }, >>> + >>> + /** >>> + * Method: createPlacemarkXML >>> + * Accept an OpenLayers.Feature.Vector, and create a KML Placemark node >>> + * >>> + * Parameters: >>> + * feature - {} >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + createPlacemarkXML: function(feature) { >>> + // Placemark name >>> + var placemarkName = document.createElementNS(this.kmlns, "name"); >>> + var placemarkNameText = document.createTextNode(feature.id); >>> + placemarkName.appendChild(placemarkNameText); >>> + >>> + // Placemark description >>> + var placemarkDesc = document.createElementNS(this.kmlns, >>> "description"); >>> + var placemarkDescText = >>> document.createTextNode(this.placemarksDesc); >>> + placemarkDesc.appendChild(placemarkDescText); >>> + >>> + // Placemark >>> + var placemarkNode = document.createElementNS(this.kmlns, >>> "Placemark"); >>> + placemarkNode.appendChild(placemarkName); >>> + placemarkNode.appendChild(placemarkDesc); >>> + >>> + // Geometry node (Point, LineString, etc. nodes) >>> + var geometryNode = this.buildGeometryNode(feature.geometry); >>> + placemarkNode.appendChild(geometryNode); >>> + >>> + return placemarkNode; >>> + }, >>> + >>> + /** >>> + * Method: buildGeometryNode >>> + * Builds a KML geometry node with a given geometry >>> + * >>> + * Parameters: >>> + * geometry - {} >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + buildGeometryNode: function(geometry) { >>> + // TBD test if geoserver can be given a Multi-geometry for a >>> simple-geometry data store >>> + // ie if multipolygon can be sent for a polygon feature type >>> + var kml = ""; >>> + // match MultiPolygon or Polygon >>> + if (geometry.CLASS_NAME == "OpenLayers.Geometry.MultiPolygon" >>> + || geometry.CLASS_NAME == "OpenLayers.Geometry.Polygon") { >>> + kml = document.createElementNS(this.kmlns, 'Polygon'); >>> + >>> + var outerRing = document.createElementNS(this.kmlns, >>> 'outerBoundaryIs'); >>> + var linearRing = document.createElementNS(this.kmlns, >>> 'LinearRing'); >>> + >>> + // TBD manage polygons with holes >>> + >>> linearRing.appendChild(this.buildCoordinatesNode(geometry.components[0])); >>> + outerRing.appendChild(linearRing); >>> + >>> + kml.appendChild(outerRing); >>> + } >>> + // match MultiLineString or LineString >>> + else if (geometry.CLASS_NAME == >>> "OpenLayers.Geometry.MultiLineString" >>> + || geometry.CLASS_NAME == >>> "OpenLayers.Geometry.LineString") { >>> + kml = document.createElementNS(this.kmlns, >>> 'LineString'); >>> + >>> + kml.appendChild(this.buildCoordinatesNode(geometry)); >>> + } >>> + // match MultiPoint or Point >>> + else if (geometry.CLASS_NAME == "OpenLayers.Geometry.Point" || >>> + geometry.CLASS_NAME == >>> "OpenLayers.Geometry.MultiPoint") { >>> + kml = document.createElementNS(this.kmlns, 'Point'); >>> + >>> + // FIXME: There should be only one Point node per >>> Placemark node >>> + var parts = ""; >>> + if (geometry.CLASS_NAME == >>> "OpenLayers.Geometry.MultiPoint") { >>> + parts = geometry.components; >>> + } else { >>> + parts = [geometry]; >>> + } >>> + >>> + for (var i = 0; i < parts.length; i++) { >>> + kml.appendChild(this.buildCoordinatesNode(parts[i])); >>> + } >>> + } >>> + return kml; >>> + }, >>> + /** >>> + * Method: buildCoordinatesNode >>> + * builds the KML coordinates node >>> + * >>> + * Parameters: >>> + * geometry - {} >>> + * >>> + * Returns: >>> + * xmlNode - {} >>> + */ >>> + buildCoordinatesNode: function(geometry) { >>> + var coordinatesNode = document.createElementNS(this.kmlns, >>> "coordinates"); >>> + >>> + var points = null; >>> + if (geometry.components) { >>> + points = geometry.components; >>> + } >>> + >>> + var path = ""; >>> + if (points) { >>> + for (var i = 0; i < points.length; i++) { >>> + path += points[i].x + "," + points[i].y + " "; >>> + } >>> + } else { >>> + path += geometry.x + "," + geometry.y + " "; >>> + } >>> + >>> + var txtNode = document.createTextNode(path); >>> + coordinatesNode.appendChild(txtNode); >>> + >>> + return coordinatesNode; >>> + }, >>> + >>> CLASS_NAME: "OpenLayers.Format.KML" >>> }); >>> >>> >>> Tim Schaub wrote: >>> >>>> Hi- >>>> >>>> So, we're mid-way through changing how XML flavors are read/written in >>>> OpenLayers. >>>> >>>> I've checked a new XML format in to the trunk. This format has most of >>>> the methods we need for reading/writing XML cross-browser. >>>> >>>> To parse other XML flavors, format classes should be created that >>>> inherit from the XML format. >>>> >>>> For an (incomplete) example, see: >>>> http://dev.openlayers.org/sandbox/tschaub/xml/lib/OpenLayers/Format/GML.js >>>> >>>> (The important part to notice in the above example is that the GML >>>> format inherits from the XML format.) >>>> >>>> Instead of using OpenLayers.Ajax methods or document methods, DOM >>>> creation and traversal should be done with OpenLayers.Format.XML >>>> methods. I've created methods to reflect the W3C standard XML DOM >>>> methods - wrapping the standard ones and accommodating for non-compliant >>>> browsers. >>>> >>>> If you (or anyone) needs additional XML DOM methods, they should be >>>> added to the XML format. The next addition (in my mind) is >>>> setAttributeNS. Aside from that, you should be able to do efficient >>>> parsing and dom creation with the XML format methods. >>>> >>>> Please make modifications to the KML format in the trunk. Create a >>>> ticket and attach patches in Trac. I can offer review or other help as >>>> needed. >>>> >>>> I don't have time to keep these sandboxes entirely clean right now - so >>>> please forgive anything you find that is in a half-developed state. >>>> >>>> Tim >>>> >>>> PS - Eventually, I'll move the following example into the trunk. It >>>> would be nice if we could demonstrate read/write capability for all >>>> vector formats in this way: >>>> http://dev.openlayers.org/sandbox/tschaub/xml/examples/vector-formats.html >>>> >>>> (note again that this reflects partially complete work - and you should >>>> not be surprised to encounter errors or see changes at any time) >>>> >>>> >>>> Damien Corpataux wrote: >>>> >>>> >>>>> Hello, >>>>> >>>>> Here's what I did so far... Reading KML only work for KML 2.0 namespaces >>>>> for write() uses OpenLayers.Ajax.getElementsByTagNameNS(), but I'm >>>>> pretty sure it will work on future versions (2.1 parsing successful). >>>>> Also, GML and KML write() returns a Dom Document rather than a string. >>>>> Should one change the result type, breaking OpenLayers.Format interface, >>>>> or parse it into a string using OpenLayers.XML.....? >>>>> >>>>> Cheers, >>>>> Damien >>>>> >>>>> >>>>> >>> [patch stripped] >>> >>> -- >>> Camptocamp SA >>> Damien Corpataux >>> PSE A >>> CH-1015 Lausanne >>> +41 21 619 10 22 (Direct) >>> +41 21 619 10 10 (Centrale) >>> +41 21 619 10 00 (Fax) >>> P Please consider the environment >>> Do you really need to print this email? >>> >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@openlayers.org >>> http://openlayers.org/mailman/listinfo/dev >>> >>> >>> !DSPAM:4033,46cd662e41812090977483! >>> >> >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev >> > > > -- > Camptocamp SA > Damien Corpataux > PSE A > CH-1015 Lausanne > +41 21 619 10 22 (Direct) > +41 21 619 10 10 (Centrale) > +41 21 619 10 00 (Fax) > P Please consider the environment > Do you really need to print this email? > !DSPAM:4033,46dd6bc8182553362379201! _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev From crschmidt at metacarta.com Wed Sep 12 09:56:48 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add attribution control to map by default In-Reply-To: <053.fefc2b369d56006ebe6d841879fc449e@openlayers.org> References: <053.fefc2b369d56006ebe6d841879fc449e@openlayers.org> Message-ID: <20070912135648.GA919@metacarta.com> On Wed, Sep 12, 2007 at 01:43:22PM -0000, OpenLayers wrote: > #966: Add attribution control to map by default > -----------------------+---------------------------------------------------- > Reporter: crschmidt | Owner: > Type: bug | Status: new > Priority: major | Milestone: 2.6 Release > Component: Control | Version: 2.4 > Keywords: | > -----------------------+---------------------------------------------------- > In order to maek the attribution control useful, it should be on by > default. That way, layers can simply provide 'attribution' inside them, > and they will automatically be displayed on the map unless someone has > taken deliberate steps to ensure otherwise. Can I get a vote on this? By default, this control will do nothing -- if no layers have attribution on them, then nothing shows up. However, if someone adds 'attribution' to the layer options, then it will show up -- rather than needing to add attribution *and* the control. The benefit is that some commercial organization can now provide a .js file on their website that is *just* a layer class - and nothing else -- and expect it to work. I personally think this is kind of cool, and would be in favor of it. Can I get a vote on this? All in favor of adding the Control.Attribution to the map by default? I'm +1. (Demo of functionality is at http://openlayers.org/dev/examples/attribution.html , original ticket is at http://trac.openlayers.org/ticket/103) -- Christopher Schmidt MetaCarta From pspencer at dmsolutions.ca Wed Sep 12 10:01:48 2007 From: pspencer at dmsolutions.ca (Paul Spencer) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add attribution control to map by default In-Reply-To: <20070912135648.GA919@metacarta.com> References: <053.fefc2b369d56006ebe6d841879fc449e@openlayers.org> <20070912135648.GA919@metacarta.com> Message-ID: Chris, by default, do you mean that if you construct a new map with an empty controls option, the attribution would be created anyway, or would not be created? Cheers Paul PS +1 On 12-Sep-07, at 9:56 AM, Christopher Schmidt wrote: > On Wed, Sep 12, 2007 at 01:43:22PM -0000, OpenLayers wrote: >> #966: Add attribution control to map by default >> ----------------------- >> +---------------------------------------------------- >> Reporter: crschmidt | Owner: >> Type: bug | Status: new >> Priority: major | Milestone: 2.6 Release >> Component: Control | Version: 2.4 >> Keywords: | >> ----------------------- >> +---------------------------------------------------- >> In order to maek the attribution control useful, it should be on by >> default. That way, layers can simply provide 'attribution' inside >> them, >> and they will automatically be displayed on the map unless >> someone has >> taken deliberate steps to ensure otherwise. > > Can I get a vote on this? > > By default, this control will do nothing -- if no layers have > attribution on them, then nothing shows up. However, if someone adds > 'attribution' to the layer options, then it will show up -- rather > than > needing to add attribution *and* the control. > > The benefit is that some commercial organization can now provide a .js > file on their website that is *just* a layer class - and nothing > else -- > and expect it to work. I personally think this is kind of cool, and > would be in favor of it. > > Can I get a vote on this? All in favor of adding the > Control.Attribution > to the map by default? > > I'm +1. > > (Demo of functionality is at > http://openlayers.org/dev/examples/attribution.html , original > ticket is > at http://trac.openlayers.org/ticket/103) > > -- > Christopher Schmidt > MetaCarta > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev +-----------------------------------------------------------------+ |Paul Spencer pspencer@dmsolutions.ca | +-----------------------------------------------------------------+ |Chief Technology Officer | |DM Solutions Group Inc http://www.dmsolutions.ca/ | +-----------------------------------------------------------------+ From crschmidt at metacarta.com Wed Sep 12 10:07:58 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add attribution control to map by default In-Reply-To: References: <053.fefc2b369d56006ebe6d841879fc449e@openlayers.org> <20070912135648.GA919@metacarta.com> Message-ID: <20070912140758.GA2311@metacarta.com> On Wed, Sep 12, 2007 at 10:01:48AM -0400, Paul Spencer wrote: > Chris, > > by default, do you mean that if you construct a new map with an empty > controls option, the attribution would be created anyway, or would > not be created? Not created. That's a 'deliberate action' in my mind -- If you're overriding the controls, you're doing it with that goal in mind, and you would then need to add the control back. If a commercial data provider really wants to ensure that their data is only used with an attribution control on the map, they can loop through the controls list when setmap is called and throw an error in some way if the attribution control is not present (by checking CLASS_NAME). As with anything, it isn't foolproof -- just handy. Regards, -- Christopher Schmidt MetaCarta From erik.uzureau at metacarta.com Wed Sep 12 10:14:25 2007 From: erik.uzureau at metacarta.com (Erik Uzureau) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add attribution control to map by default In-Reply-To: <20070912140758.GA2311@metacarta.com> References: <053.fefc2b369d56006ebe6d841879fc449e@openlayers.org> <20070912135648.GA919@metacarta.com> <20070912140758.GA2311@metacarta.com> Message-ID: <6ae3fb590709120714xc4ced9et1dfe8e168712c2e5@mail.gmail.com> As long as we're batting it around, can anyone toss out a use case when one would *not* want to have the attribution control on the map? e On 9/12/07, Christopher Schmidt wrote: > On Wed, Sep 12, 2007 at 10:01:48AM -0400, Paul Spencer wrote: > > Chris, > > > > by default, do you mean that if you construct a new map with an empty > > controls option, the attribution would be created anyway, or would > > not be created? > > Not created. That's a 'deliberate action' in my mind -- If you're > overriding the controls, you're doing it with that goal in mind, and you > would then need to add the control back. > > If a commercial data provider really wants to ensure that their data is > only used with an attribution control on the map, they can loop through > the controls list when setmap is called and throw an error in some way > if the attribution control is not present (by checking CLASS_NAME). > > As with anything, it isn't foolproof -- just handy. > > Regards, > -- > Christopher Schmidt > MetaCarta > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > From john.cole at uai.com Wed Sep 12 10:14:12 2007 From: john.cole at uai.com (John Cole) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add att ribution control to map by default Message-ID: <76758090F8686C47A44B6FF52514A1D307909E73@hermes.uai.int> -1 And my reason for this is because of printing. We have to put a copyright notice for our HUD site, and we do it with a DIV tag similar to the scale control and I assume the new attribution control. But, when we print maps, we merge all of the layers into a single one for printing to work, and I have MapServer put the copyright notice at the bottom of the map (normally we do not want a layer just for copyright notice and a separate WMS call, so the div tag works great for the interactive map). I really don't see it as too big a problem for developers to add the control when necessary, but then I'm not a data provider and view the notices poorly anyway :-) John -----Original Message----- From: dev-bounces@openlayers.org [mailto:dev-bounces@openlayers.org] On Behalf Of Christopher Schmidt Sent: Wednesday, September 12, 2007 8:57 AM To: dev@openlayers.org Subject: Re: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add attribution control to map by default On Wed, Sep 12, 2007 at 01:43:22PM -0000, OpenLayers wrote: > #966: Add attribution control to map by default > -----------------------+---------------------------------------------------- > Reporter: crschmidt | Owner: > Type: bug | Status: new > Priority: major | Milestone: 2.6 Release > Component: Control | Version: 2.4 > Keywords: | > -----------------------+---------------------------------------------------- > In order to maek the attribution control useful, it should be on by > default. That way, layers can simply provide 'attribution' inside them, > and they will automatically be displayed on the map unless someone has > taken deliberate steps to ensure otherwise. Can I get a vote on this? By default, this control will do nothing -- if no layers have attribution on them, then nothing shows up. However, if someone adds 'attribution' to the layer options, then it will show up -- rather than needing to add attribution *and* the control. The benefit is that some commercial organization can now provide a .js file on their website that is *just* a layer class - and nothing else -- and expect it to work. I personally think this is kind of cool, and would be in favor of it. Can I get a vote on this? All in favor of adding the Control.Attribution to the map by default? I'm +1. (Demo of functionality is at http://openlayers.org/dev/examples/attribution.html , original ticket is at http://trac.openlayers.org/ticket/103) -- Christopher Schmidt MetaCarta _______________________________________________ Dev mailing list Dev@openlayers.org http://openlayers.org/mailman/listinfo/dev No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.15/1003 - Release Date: 9/12/2007 10:56 AM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.15/1003 - Release Date: 9/12/2007 10:56 AM This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. From crschmidt at metacarta.com Wed Sep 12 10:36:36 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add att ribution control to map by default In-Reply-To: <76758090F8686C47A44B6FF52514A1D307909E73@hermes.uai.int> References: <76758090F8686C47A44B6FF52514A1D307909E73@hermes.uai.int> Message-ID: <20070912143636.GA5012@metacarta.com> On Wed, Sep 12, 2007 at 09:14:12AM -0500, John Cole wrote: > -1 > > And my reason for this is because of printing. We have to put a copyright > notice for our HUD site, and we do it with a DIV tag similar to the scale > control and I assume the new attribution control. > > But, when we print maps, we merge all of the layers into a single one for > printing to work, and I have MapServer put the copyright notice at the > bottom of the map (normally we do not want a layer just for copyright notice > and a separate WMS call, so the div tag works great for the interactive > map). I'm confused, I guess. 1. When you print maps, are you using OpenLayers? 2. When you print maps, do you have multiple layers turned on? If you're going to print a map, and you create a new base layer, and use no other layers -- then you simply don't have an attribution property set on your layer. If the control is there, it will, *by default* do nothing -- it only does something if you explicitly set the 'attribution' property on the layer to something that is not null. So, on your draggable maps, you have the attribution property set -- and on the printable maps, you don't. Right? Regards, -- Christopher Schmidt MetaCarta From john.cole at uai.com Wed Sep 12 11:03:07 2007 From: john.cole at uai.com (John Cole) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add att ribution control to map by default Message-ID: <76758090F8686C47A44B6FF52514A1D307909E74@hermes.uai.int> Christopher, When we print maps, we are using OpenLayers, as it's still a WMS layer, but there is only one base layer. When we create the OL map, we specify no controls at all, because these can have issues with different browsers print engines (sometimes the top control covers up the entire map, for whatever reason). It would be nice if all the browsers behaved the similar when it came to printing, but to reduce the problems we strip the map down to just the un-tiled image and nothing else. I'd like to make sure that whenever I print, no other controls exist, even if they are disabled. I'm worried about an empty div section blocking the map during printing. If the control has it's outer div set to display:none, then I doubt it would interfere, but just an empty one may cause problems. John -----Original Message----- From: Christopher Schmidt [mailto:crschmidt@metacarta.com] Sent: Wednesday, September 12, 2007 9:37 AM To: John Cole Cc: dev@openlayers.org Subject: Re: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add att ribution control to map by default On Wed, Sep 12, 2007 at 09:14:12AM -0500, John Cole wrote: > -1 > > And my reason for this is because of printing. We have to put a copyright > notice for our HUD site, and we do it with a DIV tag similar to the scale > control and I assume the new attribution control. > > But, when we print maps, we merge all of the layers into a single one for > printing to work, and I have MapServer put the copyright notice at the > bottom of the map (normally we do not want a layer just for copyright notice > and a separate WMS call, so the div tag works great for the interactive > map). I'm confused, I guess. 1. When you print maps, are you using OpenLayers? 2. When you print maps, do you have multiple layers turned on? If you're going to print a map, and you create a new base layer, and use no other layers -- then you simply don't have an attribution property set on your layer. If the control is there, it will, *by default* do nothing -- it only does something if you explicitly set the 'attribution' property on the layer to something that is not null. So, on your draggable maps, you have the attribution property set -- and on the printable maps, you don't. Right? Regards, -- Christopher Schmidt MetaCarta No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.15/1003 - Release Date: 9/12/2007 10:56 AM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.15/1003 - Release Date: 9/12/2007 10:56 AM This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. From crschmidt at metacarta.com Wed Sep 12 11:10:50 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add att ribution control to map by default In-Reply-To: <76758090F8686C47A44B6FF52514A1D307909E74@hermes.uai.int> References: <76758090F8686C47A44B6FF52514A1D307909E74@hermes.uai.int> Message-ID: <20070912151050.GA8723@metacarta.com> On Wed, Sep 12, 2007 at 10:03:07AM -0500, John Cole wrote: > Christopher, > When we print maps, we are using OpenLayers, as it's still a WMS layer, > but there is only one base layer. When we create the OL map, we specify no > controls at all, because these can have issues with different browsers print > engines (sometimes the top control covers up the entire map, for whatever > reason). It would be nice if all the browsers behaved the similar when it > came to printing, but to reduce the problems we strip the map down to just > the un-tiled image and nothing else. > > I'd like to make sure that whenever I print, no other controls exist, even > if they are disabled. I'm worried about an empty div section blocking the > map during printing. If the control has it's outer div set to display:none, > then I doubt it would interfere, but just an empty one may cause problems. Ah, then your'e fine with this: this only adds it to the map by *default* -- that is, if no controls:[] option is specified on the map. If you specify controls: [], then the control isn't added -- I think this was Paul's question as well, which I hope I adequately responded to there. This is *only* for the 'standard' default OL map -- if you want to customize your map, we're not going to force you into a specific direction. With that in mind, do you forsee a problem? or was your concern just that it would be added to the map regardless of what was specified in the map intializer control list? Regards, -- Christopher Schmidt MetaCarta From john.cole at uai.com Wed Sep 12 11:31:00 2007 From: john.cole at uai.com (John Cole) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add att ribution control to map by default Message-ID: <76758090F8686C47A44B6FF52514A1D307909E75@hermes.uai.int> Christopher, Yea, I was concerned that it would always be there :-) Right now, printing is a PITA, but I'm hoping to have time to work on a solution I *think* might work. This involves making sure all controls and layers have an additional 'noprint' css class on their containers. Then if a style sheet with a media option for print is available, it can set the 'noprint' class display: none, and that should remove all layers and controls. The trick of course is to have a base layer with the opposite true, it only gets turned on for the printing style sheet. I'm hoping that this scheme will allow users to simply hit 'print' from their browsers and have the maps print out correctly with the rest of the page, instead of having a separate page for printing. John -----Original Message----- From: Christopher Schmidt [mailto:crschmidt@metacarta.com] Sent: Wednesday, September 12, 2007 10:11 AM To: John Cole Cc: dev@openlayers.org Subject: Re: [OpenLayers-Dev] [OpenLayers-Trac] [OpenLayers] #966: Add att ribution control to map by default On Wed, Sep 12, 2007 at 10:03:07AM -0500, John Cole wrote: > Christopher, > When we print maps, we are using OpenLayers, as it's still a WMS layer, > but there is only one base layer. When we create the OL map, we specify no > controls at all, because these can have issues with different browsers print > engines (sometimes the top control covers up the entire map, for whatever > reason). It would be nice if all the browsers behaved the similar when it > came to printing, but to reduce the problems we strip the map down to just > the un-tiled image and nothing else. > > I'd like to make sure that whenever I print, no other controls exist, even > if they are disabled. I'm worried about an empty div section blocking the > map during printing. If the control has it's outer div set to display:none, > then I doubt it would interfere, but just an empty one may cause problems. Ah, then your'e fine with this: this only adds it to the map by *default* -- that is, if no controls:[] option is specified on the map. If you specify controls: [], then the control isn't added -- I think this was Paul's question as well, which I hope I adequately responded to there. This is *only* for the 'standard' default OL map -- if you want to customize your map, we're not going to force you into a specific direction. With that in mind, do you forsee a problem? or was your concern just that it would be added to the map regardless of what was specified in the map intializer control list? Regards, -- Christopher Schmidt MetaCarta No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.15/1003 - Release Date: 9/12/2007 10:56 AM No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.485 / Virus Database: 269.13.15/1003 - Release Date: 9/12/2007 10:56 AM This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. From crschmidt at metacarta.com Wed Sep 12 14:31:37 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Users] Handler problems In-Reply-To: <4fe6dd700709040139i3f90a2a4qf55372f5894a0b18@mail.gmail.com> References: <4fe6dd700708310720n6675d01ala33af447d304499b@mail.gmail.com> <4fe6dd700709010247g25028b77vcbedee637084f77d@mail.gmail.com> <4fe6dd700709040139i3f90a2a4qf55372f5894a0b18@mail.gmail.com> Message-ID: <20070912183137.GA12752@alta.metacarta.com> On Tue, Sep 04, 2007 at 09:39:08AM +0100, Tom (JDi Solutions) wrote: > In this example there is one further change from the example above. The > handler has been changed from Box to Point. Now if you shift click the map > the co-ords are displayed below the map as before, if you then shift click > outside the map div the co-ords are recalculated and displayed. This should > not happen! Further clicks outside the map do not trigger the handler. > http://demo.jdi-consult.net/oltest/custom-control-point.html > > Can someone please confirm this, is there a quick fix? Shall I add it to > JIRA? I could reproduce before, iirc, but I can't anymore. can you try checking out trunk and seeing if this is still happening for you? I can reproduce it on your page above, but not against http://openlayers.org/dev/examples/custom-control-point.html which is the same thing, but against trunk, afaik. Regards, -- Christopher Schmidt MetaCarta From john.frank at metacarta.com Thu Sep 13 06:32:03 2007 From: john.frank at metacarta.com (John R. Frank) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] improvements in the OpenLayers project's licenses Message-ID: Dear OpenLayers Community, We intend to make these changes in a few days. If you have any questions or comments, please direct them to users@openlayers.org Over the past few months, the OpenLayers PSC has discussed a couple issues in project licensing. One issue that motivated this is an inconsistency in the way we were treating sandboxes. We intend for sandboxes to be easy places for people to drop code before it has been groomed for distribution, which could be before a CLA has been signed. Currently, the repository-license.txt implies that a CLA has been signed. In fact, currently, the sandboxes are *un*licensed. The changes below fix this and improve the overall repository licensing setup. One of the foss4g discussion topics can be how to make sandboxes licensable -- CRS is carrying this on his list of things to discuss. The PSC has voted to adopt the following specific improvements, which serve to clarify ownership and move OpenLayers closer to OSGEO graduation. 1) Reorganize the directories and license files in SVN as follows: /sandbox/ /trunk/ /branches/ /project/website/ * moved from /trunk /tags/ /sandbox-license.txt * see below /repository-license.txt * also copied into /trunk/openlayers/. /release-license.txt 2) The current repository-license.txt has a preamble sentence that says that it covers the sandboxes. This is not the intent. The attached sandbox-license.txt says what we intend. 3) The current repository-license.txt explicitly references MetaCarta. We intend to replace it with the Clear BSD [1], which is better. In addition to replacing the old repository-license with the Clear BSD, we intend to change the first sentence to say "This license applies to all code and content in the 'branches', 'trunk', and 'project' directories of the Openlayers code repository at svn.openlayers.org" 4) As described on the page about the Clear BSD [1], the current CLAs are not as explicit about patent rights as one might like, so we intend to replace the current CLAs with those. In case you're curious, MetaCarta is now using the Clear BSD and these CLAs on FeatureServer and TileCache. 5) Similarly, we intend to change the release-license.txt sentence to say "This license applies to official code releases of the OpenLayers project, which are stored in svn.openlayers.org/tags/ and provided in archive form from www.openlayers.org" We intend to make these changes in a few days. If you have any questions or comments, please direct them to users@openlayers.org Yours, John Frank on behalf of the OpenLayers PSC [1] http://labs.metacarta.com/license-explanation.html -------------- next part -------------- These statements apply to all code and content in the sandbox directories inside the OpenLayers code repository in the subdirectories below svn.openlayers.org/sandbox/ Each sandbox directory contains content owned or licensed by the submitter. The submitter may be able to grant you rights to use or redistribute material from these directories. You must obtain such permissions directly from them. Neither the OpenLayers project nor its maintainer (MetaCarta, Inc.) maintain or own the material in the sandboxes. Nobody grants you any rights nor makes any express or implied warranties of any kind regarding this material. Before material from a sandbox can be moved into another part of this SVN repository or become part of an OpenLayers release, the owner must sign a Contributor License Agreement and announce the contribution on the dev@openlayers.org list. After that, the project maintainers will arrange to move the material out of the sandbox to an appropriate location from which others may use or redistribute the material in accordance with OpenLayers project licensing. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. From jachym.cepicky at gmail.com Thu Sep 13 10:11:14 2007 From: jachym.cepicky at gmail.com (Jachym Cepicky) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] can not focuse input text fields Message-ID: <1189692674.7823.15.camel@mellon> Hi, I try to setup basic WPS [1][2] client in OpenLayers. I used OpenLayers.Control.LayerSwitcher as base for the code. The working demo (at least in Firefox) can be seen at [3]. Only one problem: It is not possible, to focus input text fields by mouse (), so you can not write new values per keyboard (for example the server name or later the process Input values). Could anybody give me advice, how to get this working? The source, used in the demo [3] is new file, called WPS.py [4]. Thanks Jachym [1] http://www.opengeospatial.org/standards/requests/28 [2] http://pywps.wald.intevation.org [3] http://www.bnhelp.cz/mapserv/pokusy/OpenLayers/jachym/openlayers/examples/wps.html [4] http://dev.openlayers.org/sandbox/jachym/openlayers/lib/OpenLayers/Control/WPS.js -- Jachym Cepicky e-mail: jachym.cepicky@gmail.com URL: http://les-ejk.cz GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070913/fbfe49b5/attachment.bin From crschmidt at metacarta.com Thu Sep 13 21:06:25 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] 2.5 status update Message-ID: <20070914010625.GB13872@metacarta.com> 2.5 status update: * #928 -- Finally reproduced this. Checked in as 'buffer.html' in examples: switch to 1-buffer in the layerswitcher, drag map until center lat is ~80N. Watch the bottom row of tiles dissappear. There was a second issue in that ticket, but it was entirely related to ka-Map and nothing else. That one is more complex, more specified, and missing a patch. With that in mind, I'm encouraging anyone who cares about ka-Map to work on that as a ticket for 2.6. I have confirmed that the proposed fix for #928 works... but it worries me that we need to do it, and I'm not convinced I understand why it is happening. The mintiles stuff feels a bit weird to me, so I'm going to see if I can figure out something else that could be the underlying problem before putting the patch in. * #966 -- Barring any further argument against turning this on by default, I'm going to put it in tomorrow * #969 -- memory management patch which tim says he'll put together tomorrow morning. I think that will clear the road for a 2.5 RC: If you have any *behaviors which have changed/regressed since 2.4*, now is a great time to report them. Regards, -- Christopher Schmidt MetaCarta From volpicelli at oato.inaf.it Fri Sep 14 06:20:58 2007 From: volpicelli at oato.inaf.it (Antonio Volpicelli) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Problem with Firefox on Navtoolbar Message-ID: <46EA608A.1080700@oato.inaf.it> Hi devs, I am trying to use NavToolbar Control but seems that it doesn't work fine on Firefox and Opera It seems that the active area when I click is not on the arrow images. For the UP arrow the active area is some pixels at bottom right of the arrow image. For the DOWN arrow it is at top right of the arrow image The LEFT arrows doesn't work at all The RIGHT arrow works fine. So I tried the live example http://www.openlayers.org/dev/examples/navtoolbar.html and this has the same problem. It works fine with IE. Are there someone that know why? Thanks Antonio From jachym.cepicky at gmail.com Fri Sep 14 06:40:03 2007 From: jachym.cepicky at gmail.com (Jachym Cepicky) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] can not focuse input text fields In-Reply-To: <1189692674.7823.15.camel@mellon> References: <1189692674.7823.15.camel@mellon> Message-ID: <1189766403.8543.27.camel@mellon> hi, OpenLayers.Event.observe(myTextInput, "click", this.focusInputField); focusInputField: function(evt) { evt.target.focus(); }, j Jachym Cepicky p??e v ?t 13. 09. 2007 v 16:11 +0200: > Hi, > > I try to setup basic WPS [1][2] client in OpenLayers. I used > OpenLayers.Control.LayerSwitcher as base for the code. The working demo > (at least in Firefox) can be seen at [3]. > > Only one problem: It is not possible, to focus input text fields by > mouse (), so you can not write new values per > keyboard (for example the server name or later the process Input > values). Could anybody give me advice, how to get this working? > > The source, used in the demo [3] is new file, called WPS.py [4]. > > Thanks > > Jachym > > [1] http://www.opengeospatial.org/standards/requests/28 > [2] http://pywps.wald.intevation.org > [3] > http://www.bnhelp.cz/mapserv/pokusy/OpenLayers/jachym/openlayers/examples/wps.html > [4] > http://dev.openlayers.org/sandbox/jachym/openlayers/lib/OpenLayers/Control/WPS.js > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev -- Jachym Cepicky e-mail: jachym.cepicky@gmail.com URL: http://les-ejk.cz GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070914/dc11da79/attachment.bin From crschmidt at metacarta.com Fri Sep 14 07:05:39 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Problem with Firefox on Navtoolbar In-Reply-To: <46EA608A.1080700@oato.inaf.it> References: <46EA608A.1080700@oato.inaf.it> Message-ID: <20070914110539.GC11408@metacarta.com> On Fri, Sep 14, 2007 at 12:20:58PM +0200, Antonio Volpicelli wrote: > Hi devs, > I am trying to use NavToolbar Control but seems that it doesn't work > fine on Firefox and Opera > It seems that the active area when I click is not on the arrow images. > For the UP arrow the active area is some pixels at bottom right of the > arrow image. > For the DOWN arrow it is at top right of the arrow image > The LEFT arrows doesn't work at all > The RIGHT arrow works fine. > So I tried the live example > http://www.openlayers.org/dev/examples/navtoolbar.html and this has the > same problem. That's a weird-ass bug. Don't know why it's happening. Adding the following to your style.css or your page will fix it in FF ( don't have IE handy, please test and report back!): .olControlNavToolbar { width:0px; height:0px; } I'll file this as a ticket and make sure it goes in for 2.5, or some other similar fix. Thanks for the report! -- Christopher Schmidt MetaCarta From jonathan.zaid at mediolanum.it Fri Sep 14 08:05:25 2007 From: jonathan.zaid at mediolanum.it (jonz) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] NavToolbar control In-Reply-To: <20070522163605.GA11566@metacarta.com> References: <465304BE.5070401@where2getit.com> <20070522163605.GA11566@metacarta.com> Message-ID: <12673789.post@talk.nabble.com> Hi Christopher, I was running into the same sort of thing, and basically it's sort of impossibile to deactivate the zoombox without causing a zoom seeing as the mouseup goes thru to the map.. Ok as far as your response. I set up a simple "workaround" that seems to do the trick. after I activate the zoombox I set up my own priority handler on the mouseup so I get it before the map gets it. control_ZoomBox.activate(); map.events.registerPriority("mouseup", this, this.mouseup); then the event handler checks to see if we were dragging, via the dragHandler. If so then we let the mouseup bubble back up, otherwise we let the mouseup die here. Works great for me. Don't know if there are any side effects that I haven't found yet. function mouseup(evt) { if (this.control_ZoomBox.handler.dragHandler.dragging) { return(true); } else return (false); } --------------------- Jon Christopher Schmidt-4 wrote: > > On Tue, May 22, 2007 at 09:57:02AM -0500, Les Szklanny wrote: >> When clicking the NavToolbar toggle, the map's mouseup event fires... >> I believe this is a bug. I'm using OL '$Revision: 3113 $' on FF 2.0. > > This is expected behavior. In order to allow the 'zoombox' to be > released while the mouse is over a control, the controls are designed to > pass mouseup through to the map. > > Regards, > -- > Christopher Schmidt > MetaCarta > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > -- View this message in context: http://www.nabble.com/NavToolbar-control-tf3796903.html#a12673789 Sent from the OpenLayers Dev mailing list archive at Nabble.com. From volpicelli at oato.inaf.it Fri Sep 14 08:48:39 2007 From: volpicelli at oato.inaf.it (Antonio) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Problem with Firefox on Navtoolbar In-Reply-To: <20070914110539.GC11408@metacarta.com> References: <46EA608A.1080700@oato.inaf.it> <20070914110539.GC11408@metacarta.com> Message-ID: <46EA8327.1010909@oato.inaf.it> Hi Chris, FF is about the same , probably 1 or 2 px more left for UP and DOWN arrows. LEFT is not working yet. Opera now works fine and IE7 too. I don't know if this might be useful for you but if I use the navtoolbar-outsidemap.html all works fine. Thanks Ciao Antonio Christopher Schmidt wrote: > On Fri, Sep 14, 2007 at 12:20:58PM +0200, Antonio Volpicelli wrote: > >> Hi devs, >> I am trying to use NavToolbar Control but seems that it doesn't work >> fine on Firefox and Opera >> It seems that the active area when I click is not on the arrow images. >> For the UP arrow the active area is some pixels at bottom right of the >> arrow image. >> For the DOWN arrow it is at top right of the arrow image >> The LEFT arrows doesn't work at all >> The RIGHT arrow works fine. >> So I tried the live example >> http://www.openlayers.org/dev/examples/navtoolbar.html and this has the >> same problem. >> > > That's a weird-ass bug. Don't know why it's happening. > > Adding the following to your style.css or your page will fix it in FF ( > don't have IE handy, please test and report back!): > > .olControlNavToolbar { > width:0px; > height:0px; > } > > I'll file this as a ticket and make sure it goes in for 2.5, or some > other similar fix. > > Thanks for the report! > > > -- /-------------------------------------------------------\ PLEASE WARNING: E-mail is CHANGED volpicelli@oato.inaf.it /-------------------------------------------------------\ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070914/67d76b1d/attachment.html From crschmidt at metacarta.com Fri Sep 14 09:18:26 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Problem with Firefox on Navtoolbar In-Reply-To: <46EA8327.1010909@oato.inaf.it> References: <46EA608A.1080700@oato.inaf.it> <20070914110539.GC11408@metacarta.com> <46EA8327.1010909@oato.inaf.it> Message-ID: <20070914131826.GA10401@alta.metacarta.com> On Fri, Sep 14, 2007 at 02:48:39PM +0200, Antonio wrote: > Hi Chris, > FF is about the same , probably 1 or 2 px more left for UP and DOWN > arrows. LEFT is not working yet. > Opera now works fine and IE7 too. I'm perhaps confused. http://openlayers.org/~crschmidt/972/navtoolbar.html implements the solution I suggested: When you click in the middle of the arrow, does it work? (It does for me.) Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Fri Sep 14 09:22:51 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] NavToolbar control In-Reply-To: <12673789.post@talk.nabble.com> References: <465304BE.5070401@where2getit.com> <20070522163605.GA11566@metacarta.com> <12673789.post@talk.nabble.com> Message-ID: <20070914132251.GB10401@alta.metacarta.com> On Fri, Sep 14, 2007 at 05:05:25AM -0700, jonz wrote: > > Hi Christopher, > > I was running into the same sort of thing, and basically it's sort of > impossibile to deactivate the zoombox without causing a zoom seeing as the > mouseup goes thru to the map.. So, I look at: http://openlayers.org/dev/examples/navtoolbar.html I click the second tool, to activate it. No Zoom. I click the tool again. No zoom. I drag a box around spain. Zoom. I drag a box such that my mouse is over the navcontrol, and let go. Zoom. This is the behavior I expect. It sounds like you're doing something differently than I am: I'm not sure what it is. If the behavior described above is not what you get, then we have a different problem we should discuss -- but if the above is the behavior you get, then the only thing to discuss is why it isn't what you want :) Regards, -- Christopher Schmidt MetaCarta From jonathan.zaid at mediolanum.it Fri Sep 14 09:45:22 2007 From: jonathan.zaid at mediolanum.it (jonz) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] NavToolbar control In-Reply-To: <20070914132251.GB10401@alta.metacarta.com> References: <465304BE.5070401@where2getit.com> <20070522163605.GA11566@metacarta.com> <12673789.post@talk.nabble.com> <20070914132251.GB10401@alta.metacarta.com> Message-ID: <12675692.post@talk.nabble.com> Yes, I had seen the navtoolbar example and the behaviour is as I would like. Unfortunately, and I couldn't figure out why, that's not exactly what happens with my map. click on dragZoom click again on dragZoom Zooms in one level I debugged it, and caught the "mouseup" event coming from drag.js was causing the zoom. This same type of thing does NOT occur with navtoolbar example. To answer your question briefly, yes, I am doing something different (in the implementation) than you are, and surely that is the source of the problems. I created the toolbar by hand myself. I've been commissioned to "use" a toolbar which is made with a series of div's and images, and so instead of using the toolbar from OpenLayers, I just threw the toolbar into the map div and added links to the controls. so.. I have something like this as far as html goes.
    dragON.jpg dragZoomChange is: function dragZoomChange(img) { var name = img.src.replace(/.*\//,'').replace(/.jpg/,''); var newsrc = img.src.replace(/(.*\/)(.*$)/,'$1'); if (name == 'dragON') { control_ZoomBox.activate(); map.events.registerPriority("mouseup", this, this.mouseup); newsrc = newsrc + "drag.jpg"; } else { control_ZoomBox.deactivate(); map.events.unregister("mouseup", this, this.mouseup); newsrc = newsrc + "dragON.jpg"; } img.src = newsrc; } P.S: Thanks so much for being so active in the forum. Jon Christopher Schmidt-4 wrote: > > On Fri, Sep 14, 2007 at 05:05:25AM -0700, jonz wrote: >> >> Hi Christopher, >> >> I was running into the same sort of thing, and basically it's sort of >> impossibile to deactivate the zoombox without causing a zoom seeing as >> the >> mouseup goes thru to the map.. > > So, I look at: > > http://openlayers.org/dev/examples/navtoolbar.html > > I click the second tool, to activate it. No Zoom. > > I click the tool again. No zoom. > > I drag a box around spain. Zoom. > > I drag a box such that my mouse is over the navcontrol, and let go. > Zoom. > > This is the behavior I expect. > > It sounds like you're doing something differently than I am: I'm not > sure what it is. If the behavior described above is not what you get, > then we have a different problem we should discuss -- but if the above > is the behavior you get, then the only thing to discuss is why it isn't > what you want :) > > Regards, > -- > Christopher Schmidt > MetaCarta > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > -- View this message in context: http://www.nabble.com/NavToolbar-control-tf3796903.html#a12675692 Sent from the OpenLayers Dev mailing list archive at Nabble.com. From volpicelli at oato.inaf.it Fri Sep 14 09:52:33 2007 From: volpicelli at oato.inaf.it (Antonio) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Problem with Firefox on Navtoolbar In-Reply-To: <20070914131826.GA10401@alta.metacarta.com> References: <46EA608A.1080700@oato.inaf.it> <20070914110539.GC11408@metacarta.com> <46EA8327.1010909@oato.inaf.it> <20070914131826.GA10401@alta.metacarta.com> Message-ID: <46EA9221.2030506@oato.inaf.it> Sorry Chris , you have right. I was using another css , I inserted the new style on my html page and it works. Thanks a lot Antonio Christopher Schmidt wrote: > On Fri, Sep 14, 2007 at 02:48:39PM +0200, Antonio wrote: > >> Hi Chris, >> FF is about the same , probably 1 or 2 px more left for UP and DOWN >> arrows. LEFT is not working yet. >> Opera now works fine and IE7 too. >> > > I'm perhaps confused. > http://openlayers.org/~crschmidt/972/navtoolbar.html implements the > solution I suggested: When you click in the middle of the arrow, does it > work? (It does for me.) > > Regards, > -- /-------------------------------------------------------\ PLEASE WARNING: E-mail is CHANGED volpicelli@oato.inaf.it /-------------------------------------------------------\ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070914/54f89826/attachment.html From crschmidt at metacarta.com Fri Sep 14 10:51:43 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Problem with Firefox on Navtoolbar In-Reply-To: <46EA9221.2030506@oato.inaf.it> References: <46EA608A.1080700@oato.inaf.it> <20070914110539.GC11408@metacarta.com> <46EA8327.1010909@oato.inaf.it> <20070914131826.GA10401@alta.metacarta.com> <46EA9221.2030506@oato.inaf.it> Message-ID: <20070914145143.GB7946@metacarta.com> On Fri, Sep 14, 2007 at 03:52:33PM +0200, Antonio wrote: > Sorry Chris , you have right. > I was using another css , I inserted the new style on my html page and > it works. No problem, I was just worried :) #972 filed with patch, will get it reviewed before 2.5. Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Fri Sep 14 10:53:05 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] NavToolbar control In-Reply-To: <12675692.post@talk.nabble.com> References: <465304BE.5070401@where2getit.com> <20070522163605.GA11566@metacarta.com> <12673789.post@talk.nabble.com> <20070914132251.GB10401@alta.metacarta.com> <12675692.post@talk.nabble.com> Message-ID: <20070914145305.GC7946@metacarta.com> On Fri, Sep 14, 2007 at 06:45:22AM -0700, jonz wrote: > > Yes, I had seen the navtoolbar example and the behaviour is as I would like. > Unfortunately, and I couldn't figure out why, that's not exactly what > happens with my map. > > click on dragZoom > click again on dragZoom > Zooms in one level It sounds like you're not stopping mousedown when the user clicks. OpenLayers.Event.observe(controls[i].panel_div, "mousedown", OpenLayers.Event.stop.bindAsEventListener()); is from Control.Panel and should fix it. Regards, -- Christopher Schmidt MetaCarta From jachym.cepicky at gmail.com Fri Sep 14 13:10:09 2007 From: jachym.cepicky at gmail.com (Jachym Cepicky) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] possible bug in GML parser Message-ID: <1189789809.8543.63.camel@mellon> Hi, maybe, I found a bug in OpenLayers.Format.GML I wrote small application for OGC WPS. User can run some process on the server and as response, the server sends XML document with embed GML. The GML node can be extracted like: var outputGML = response.responseXML.getElementsByTagName("ComplexValue")[0].firstChild; // than would like to store it to OpenLayers.Layer.Vector: var g = new OpenLayers.Format.GML(); var s = new XMLSerializer(); var features = g.read(s.serializeToString(outputGML)); myVectorLayer.addFeatures(features); myVectorLayer.redraw(); New vector features are displayed in map window, but the result is a mess. I setup example at http://www.bnhelp.cz/mapserv/pokusy/OpenLayers/jachym/openlayers/examples/wps.html To reproduce the possible bug, please do following: 1 - digitize point 2 - unminize WPS tab (under LayerSwitcher) 3 - confirm server 4 - select "Buffer" process 5 - set buffer width (0.1 - 1) 6 - "Execute" the process Server output will be displayed with GML before and after it was imported to OpenLayers. The critical part of the code can be found at http://trac.openlayers.org/browser/sandbox/jachym/openlayers/lib/OpenLayers/Control/WPS.js lines 805 - 845 method parseExecuteResponse. What are the limitations of the GML parser in OL? Thanks Jachym -- Jachym Cepicky e-mail: jachym.cepicky@gmail.com URL: http://les-ejk.cz GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070914/1072d98f/attachment.bin From crschmidt at metacarta.com Fri Sep 14 13:21:06 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] possible bug in GML parser In-Reply-To: <1189789809.8543.63.camel@mellon> References: <1189789809.8543.63.camel@mellon> Message-ID: <20070914172106.GC19623@metacarta.com> On Fri, Sep 14, 2007 at 05:10:09PM +0000, Jachym Cepicky wrote: > Hi, > > maybe, I found a bug in OpenLayers.Format.GML > > I wrote small application for OGC WPS. User can run some process on the > server and as response, the server sends XML document with embed GML. > > The GML node can be extracted like: > > var outputGML = > response.responseXML.getElementsByTagName("ComplexValue")[0].firstChild; > > // than would like to store it to OpenLayers.Layer.Vector: > > var g = new OpenLayers.Format.GML(); > var s = new XMLSerializer(); > var features = g.read(s.serializeToString(outputGML)); ^^ these two lines are unneccesary -- you can just work with the outputGML object instead of serializing it first. > myVectorLayer.addFeatures(features); > myVectorLayer.redraw(); > What are the limitations of the GML parser in OL? Much less now than in the version you are using :) Looks like your code doens't have the changes we made in http://trac.openlayers.org/ticket/938 / r4206, which fix parsing of 3dpoints, which your service is returning. So, if you merge trunk into your sandbox, it should all be working just fine -- but your'e right that it was a bug :) Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Mon Sep 17 00:46:47 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OpenLayers 2.5 RC1 Available! Message-ID: <20070917044647.GA3068@metacarta.com> OpenLayers 2.5 Release Candidate Announcement The OpenLayers Development Team is proud to announce the first release candidate of OpenLayers 2.5. This release features a number of major developments, including: * Date Line Wrapping: Tiles wrap around the earth (#487) * New/Improved Formats: * KML (#927) * GeoRSS Simple (#973) * GeoJSON (#915) * New/Improved Feature Digitization: * Control to Drag Features (#638) * Control to Modify Features (#941) * RegularPolygon drawing/creation Support (#828) * SphericalMercator support on commercial layers (#686) * Tons and tons of bug fixes! We have also begun to move towards deprecating some of our outdated functionality. For information on that, and other important changes to the library before updating your applications, please refer to the Release Notes, at http://trac.openlayers.org/wiki/Release/2.5/Notes. As of 2.5-RC1, the OpenLayers 2.5 release closes 164 outstanding tickets, more than any other OpenLayers release to date! For this we are indebted to the many members of the community, and especially the hard work of organizations like The Open Planning Project via Tim Schaub and a number of developers like Pierre Giraud, Eric Lemoine, and Fred Junrod of the Camptocamp team, as well as continued support from Chris Schmidt and Erik Uzureau of MetaCarta. We invite you to help us test the 2.5 release candidate! To test 2.5 in your applications, include the following tag in your !OpenLayers-powered page: As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in Trac, under the 2.5 version and milestone. We look forward to your feedback! Regards, The OpenLayers Team From michael.ostling at metagis.se Mon Sep 17 06:11:40 2007 From: michael.ostling at metagis.se (=?iso-8859-1?Q?Michael_=D6stling?=) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] ArcGIS server 9.2 support for OL Message-ID: <002501c7f913$249fdd60$c701a8c0@metaport3> Hi, I have problems using the AGS mapcache component. I'm getting problems fitting the map correctly. I have tried to calculate the mapextent but does not get correct results anyway. (se below) I have struggled with this in a couple of weeks now and would be very happy if someone just could veryfy my way of calculating the extent. Over the map I'm getting errors from 10-20 meter up to several 1000 meters. Also when I zoomin by doubleclicking the map is not centered where I clicked. Regards Michael ********************************************** Have I understood it correctly when I'm doing the following. I have a mapcache that have a origin (Upper Left) at 1 200 000, 7 700 000 In my most detalied level of the cache I have 384 rows and 170 columns. Pixelsize is 512x512. Resolution in this level is 8.46668360003387 (meter) My total extentsize is therefore East-West 512 * 170 * 8.46668360003387 = 736940,1405469480000 North-South 512 * 384 * 8.46668360003387 = 1664617,7292354600000 My extentborder in west is therefore 1 200 000 + 736940,1405469480000 = 1936940.1405469500000 My extentborder in south is 7 700 000 - 1664617,7292354600000 = 6035382,0088900200000 In my code I have written: var lon = 1600000; var lat = 6700000; var zoom = 6; var map, layer,layer2; function init(){ map = new OpenLayers.Map( 'map', { maxExtent: new OpenLayers.Bounds(1200000,6035382.00889002,1936940.14054695,7700000), maxResolution: 2116.67090000847,resolutions: new Array(2116.67090000847, 1058.33545000423, 529.167725002117, 264.583862501058, 132.291931250529, 66.1459656252646, 33.0729828126323, 16.9333672000677, 8.46668360003387), tileSize : new OpenLayers.Size(512,512), tileOrigin: new OpenLayers.LonLat(1200000,7700000),units: 'm'} ); layer = new OpenLayers.Layer.AGS( "AGS", "http://metaport3/OL_AGS/Layers", {layername: '_alllayers', type:'png', tileOrigin: new OpenLayers.LonLat(1200000,7700000) } ); map.addLayer(layer); map.addControl(new OpenLayers.Control.LayerSwitcher()); map.addControl(new OpenLayers.Control.MousePosition()); map.setCenter(new OpenLayers.LonLat(lon, lat), zoom); } function addAGS() { l = new OpenLayers.Layer.AGS( OpenLayers.Util.getElement('layer').value, OpenLayers.Util.getElement('url').value, { 'layername': OpenLayers.Util.getElement('layer').value, 'type': OpenLayers.Util.getElement('type').value }); map.addLayer(l); map.setBaseLayer(l); } mvh Michael ------------------------------------------------------------------ MetaGIS AB Michael ?stling Mob: 070-279 19 76 Tel: 023 - 702 20 10 ePost: michael.ostling@metagis.se Adress: Britsarvsv?gen 28a, 791 36 FALUN Org Nr: 556638-7170 ------------------------------------------------------------------ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070917/7355cf22/attachment.html From crschmidt at metacarta.com Mon Sep 17 07:28:33 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] ArcGIS server 9.2 support for OL In-Reply-To: <002501c7f913$249fdd60$c701a8c0@metaport3> References: <002501c7f913$249fdd60$c701a8c0@metaport3> Message-ID: <20070917112833.GD9194@metacarta.com> On Mon, Sep 17, 2007 at 12:11:40PM +0200, Michael ?stling wrote: > Hi, > I have problems using the AGS mapcache component. > I'm getting problems fitting the map correctly. The AGS MapCache support *does not work*. I'm sorry if this is not clear. Where did you find it mentioned, and where could I mark more clearly thati t does not work? Did you pull it from the sandboxes? Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Mon Sep 17 12:17:27 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [crschmidt@metacarta.com: Re: [OpenLayers-Users] click-event in openlayers 2.5] Message-ID: <20070917161727.GA8400@metacarta.com> This is #982. This is a regression against 2.4 -- and I feel like it's one we've had before, though presumably not in the same way. If anyone wants to investigate, I think that the right place to look might be: r3891: #774 - drag control only calls move callback with a change in pixel position - DragPan control simplified Otherwise, I *think* it's got to be somewhere in: http://trac.openlayers.org/log/trunk/openlayers/lib/OpenLayers/Handler/Drag.js?action=stop_on_copy&rev=4230&stop_rev=3198&mode=stop_on_copy&verbose=on -- Chris ----- Forwarded message from Christopher Schmidt ----- From: Christopher Schmidt To: nhelminger Cc: users@openlayers.org Date: Mon, 17 Sep 2007 11:47:04 -0400 Subject: Re: [OpenLayers-Users] click-event in openlayers 2.5 On Mon, Sep 17, 2007 at 07:41:28AM -0700, nhelminger wrote: > > I'm using OpenLayers 2.5. > When dragging the map an click event is fired. > You can try out the click.html example. Thanks. Filed as a blocker for 2.5. Regards, -- Christopher Schmidt MetaCarta _______________________________________________ Users mailing list Users@openlayers.org http://openlayers.org/mailman/listinfo/users ----- End forwarded message ----- -- Christopher Schmidt MetaCarta From erik.uzureau at metacarta.com Mon Sep 17 12:50:58 2007 From: erik.uzureau at metacarta.com (Erik Uzureau) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OpenLayers 2.5 RC1 Available! In-Reply-To: <20070917044647.GA3068@metacarta.com> References: <20070917044647.GA3068@metacarta.com> Message-ID: <6ae3fb590709170950o72de5a19pa97652d0143be6f9@mail.gmail.com> 2.5!! Three cheers to everyone involved in this release. Special high fives to Chris Schmidt for once again being the muscle behind the movement to get all the loose ends together these last few weeks and for a brilliant job as always getting the packaging, release notes, and announcements all together.... and all that on a sunday night! Now *that's* dedication :-) There are tons and tons of closed tickets for this release and lots of them thanks to great bug reports that come from the very people on these email lists. THANK YOU! OpenLayers is really coming into its own and we could never do it without such a careful and supportive community. Erik ps. Hopefully we'll see some of you in Victoria next week at the FOSS4G conference :-) On 9/17/07, Christopher Schmidt wrote: > OpenLayers 2.5 Release Candidate Announcement > > The OpenLayers Development Team is proud to announce the first release > candidate of OpenLayers 2.5. This release features a number of major > developments, including: > > * Date Line Wrapping: Tiles wrap around the earth (#487) > * New/Improved Formats: > * KML (#927) > * GeoRSS Simple (#973) > * GeoJSON (#915) > * New/Improved Feature Digitization: > * Control to Drag Features (#638) > * Control to Modify Features (#941) > * RegularPolygon drawing/creation Support (#828) > * SphericalMercator support on commercial layers (#686) > * Tons and tons of bug fixes! > > We have also begun to move towards deprecating some of our outdated > functionality. For information on that, and other important changes to > the library before updating your applications, please refer to the > Release Notes, at http://trac.openlayers.org/wiki/Release/2.5/Notes. > > As of 2.5-RC1, the OpenLayers 2.5 release closes 164 outstanding > tickets, more than any other OpenLayers release to date! For this we > are indebted to the many members of the community, and especially the > hard work of organizations like The Open Planning Project via Tim Schaub > and a number of developers like Pierre Giraud, Eric Lemoine, and Fred > Junrod of the Camptocamp team, as well as continued support from Chris > Schmidt and Erik Uzureau of MetaCarta. > > We invite you to help us test the 2.5 release candidate! To test 2.5 in > your applications, include the following tag in your !OpenLayers-powered > page: > > > > As always, the source is available at http://openlayers.org/download/. > Bug reports can be filed in Trac, under the 2.5 version and milestone. > > We look forward to your feedback! > > Regards, > > The OpenLayers Team > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > From crschmidt at metacarta.com Mon Sep 17 12:51:28 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [crschmidt@metacarta.com: Re: [OpenLayers-Users] click-event in openlayers 2.5] In-Reply-To: <20070917161727.GA8400@metacarta.com> References: <20070917161727.GA8400@metacarta.com> Message-ID: <20070917165128.GA12108@metacarta.com> On Mon, Sep 17, 2007 at 12:17:27PM -0400, Christopher Schmidt wrote: > This is #982. This is a regression against 2.4 -- and I feel like it's > one we've had before, though presumably not in the same way. If anyone > wants to investigate, I think that the right place to look might be: > > r3891: > #774 - drag control only calls move callback with a change in pixel > position - DragPan control simplified Confirmed that this is the case. r3890 works -- r3891 breaks. Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Tue Sep 18 07:43:20 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] [OpenLayers-Users] problem in getZoomForResolution In-Reply-To: <74be4d6652fde3cef8f8a83d5d814c0c@145.50.39.11> References: <74be4d6652fde3cef8f8a83d5d814c0c@145.50.39.11> Message-ID: <20070918114320.GD17284@metacarta.com> On Tue, Sep 18, 2007 at 01:26:01PM +0200, Bart van den Eijnden (OSGIS) wrote: > We are experiencing a problem in Layer.js's getZoomForResolution in that > it's return value is sometimes 1 off. This is similar to TileCache's seed > problems and deals with precision. > > This problem was also in previous OL versions, but is still present in > 2.5RC1 unfortunately. It happens to us when we switch baselayers, which are > both WMS Tiled layers. The scales are only set on the Map, so basically the > layers share the same set of resolutions. > > If we use a different approach (find the minimal difference) it works fine: > > getZoomForResolution: function(resolution) { > var lastDiff = null; > var zoom = null; > for(var i=1; i < this.resolutions.length; i++) { > diff = Math.abs(this.resolutions[i]-resolution); > if (lastDiff && (diff < lastDiff)) > { > zoom = i; > } > lastDiff = diff; > } > return zoom; > }, > This seems low cost and unlikely to break things, but I'd prefer to get more buyin -- I think Tim is in favor of this (I know he was for TileCache, which is why this is what it does these days). It's also high benefit, if it actually fixes the problem. I'm moving this one to the dev list, since I think it's more appropriate for there -- any time you're talking about changing internals of the library, it's generally best to send to the dev list (though I'll admit I haven't bothered to make the distinction particularly clear: my bad). Regards, -- Christopher Schmidt MetaCarta From jachym.cepicky at gmail.com Tue Sep 18 08:08:29 2007 From: jachym.cepicky at gmail.com (Jachym Cepicky) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] HTTP POST via proxy.cgi Message-ID: <1190117309.7888.10.camel@mellon> Hi, the OpenLayers proxy.cgi script is not able to handle requests send by HTTP POST method. I submited [1] patch [2], which adds this feature. Jachym [1] http://trac.openlayers.org/ticket/991 [2] http://trac.openlayers.org/attachment/ticket/991/proxy.cgi.diff -- Jachym Cepicky e-mail: jachym.cepicky@gmail.com URL: http://les-ejk.cz GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070918/bb28dbda/attachment.bin From sderle at metacarta.com Tue Sep 18 10:51:14 2007 From: sderle at metacarta.com (Schuyler Erle) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fwd: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? Message-ID: <20070918145114.GT3930@vishnu.tridity.org> Here's a reminder from the OSGeo-Discuss list re: preparing for the FOSS4G code sprint next Friday. What should we spend that time building? There's a few ideas on the OSGeo wiki page: http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers * OL Context/WMC+ - read/write support for and OWS Context style doc * SLD support - edit/read/write * Renderer Optimizations o consider attributing geometry components with a minResolution below which the renderer doesn't deal with them o clipping - svg supports clipping, we need to consider clipping or another method of dealing with geometries that extend beyond the renderer bounds o add renderer * integrate emanual's animated zooming stuff Anyone care to add to or amplify any of these ideas? SDE ----- Forwarded message from Jody Garnett ----- Date: Mon, 17 Sep 2007 12:28:40 -0700 From: Jody Garnett To: OSGeo Discussions Subject: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? Just a reminder, the code sprint is almost upon us, and I would like to make sure we get as much time with the code as possible. A couple of suggestions: - try and make sure you have your design discussions, bug hit list or whatever out of the way before the sprint - make sure developers know what they need to have ready before the sprint (perhaps a checkout out of the latest?) - have fun. Jody _______________________________________________ Discuss mailing list Discuss@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/discuss ----- End forwarded message ----- From madair at dmsolutions.ca Tue Sep 18 11:54:40 2007 From: madair at dmsolutions.ca (Mike Adair) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fwd: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? In-Reply-To: <20070918145114.GT3930@vishnu.tridity.org> References: <20070918145114.GT3930@vishnu.tridity.org> Message-ID: <46EFF4C0.7040206@dmsolutions.ca> How about: - add support for MapGuide OS layer type; this code is essentially ready to go, I just need to create a ticket and a patch. - add support forr coordinate trasnformations as described previously Mike Schuyler Erle wrote: > Here's a reminder from the OSGeo-Discuss list re: preparing for the > FOSS4G code sprint next Friday. What should we spend that time > building? There's a few ideas on the OSGeo wiki page: > > http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers > > * OL Context/WMC+ - read/write support for and OWS Context style > doc > * SLD support - edit/read/write > * Renderer Optimizations > o consider attributing geometry components with a > minResolution below which the renderer doesn't deal with them > o clipping - svg supports clipping, we need to consider > clipping or another method of dealing with geometries that extend > beyond the renderer bounds > o add renderer > * integrate emanual's animated zooming stuff > > Anyone care to add to or amplify any of these ideas? > > SDE > > ----- Forwarded message from Jody Garnett ----- > > Date: Mon, 17 Sep 2007 12:28:40 -0700 > From: Jody Garnett > To: OSGeo Discussions > Subject: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? > > Just a reminder, the code sprint is almost upon us, and I would like to > make sure we get as much time with the code as possible. > > A couple of suggestions: > - try and make sure you have your design discussions, bug hit list or > whatever out of the way before the sprint > - make sure developers know what they need to have ready before the > sprint (perhaps a checkout out of the latest?) > - have fun. > > Jody > > _______________________________________________ > Discuss mailing list > Discuss@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/discuss > > ----- End forwarded message ----- > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > > From crschmidt at metacarta.com Tue Sep 18 12:52:26 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fwd: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? In-Reply-To: <46EFF4C0.7040206@dmsolutions.ca> References: <20070918145114.GT3930@vishnu.tridity.org> <46EFF4C0.7040206@dmsolutions.ca> Message-ID: <20070918165226.GB17881@metacarta.com> On Tue, Sep 18, 2007 at 11:54:40AM -0400, Mike Adair wrote: > How about: > - add support for MapGuide OS layer type; this code is essentially ready > to go, I just need to create a ticket and a patch. Adding things like new layers is grunt work that is probably best done outside the confrence setting if the code is largely complete: Unless I'm mistaken, there are (for example) no tests for the code. Things like that are really easy for a single person to review outside the conference setting, where things which require multiple people are harder to hack through. > - add support forr coordinate trasnformations as described previously This is a much better target, and I'm in favor of it. I think that it may make sense to try and hack out some preemptive plans during something like the webmap BOF, as well. Regards, -- Christopher Schmidt MetaCarta From bartvde at osgis.nl Tue Sep 18 13:05:52 2007 From: bartvde at osgis.nl (Bart van den Eijnden (OSGIS)) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fwd: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? In-Reply-To: <20070918145114.GT3930@vishnu.tridity.org> References: <20070918145114.GT3930@vishnu.tridity.org> Message-ID: <46F00570.90707@osgis.nl> Although I am not there unfortunately, I would love to see OpenLayers support an optional map mode which has arbitrary scales/resolutions, so no predefined scales/resolutions. What the user defines in his zoombox, he will zoom to. I know this can be done outside of the library with a few hacks probably, but it would be so much better if it would be part of the OpenLayers core IMHO, especially for supporting traditional GIS applications. We do hear a lot of users asking for this. Best regards, Bart Schuyler Erle schreef: > Here's a reminder from the OSGeo-Discuss list re: preparing for the > FOSS4G code sprint next Friday. What should we spend that time > building? There's a few ideas on the OSGeo wiki page: > > http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers > > * OL Context/WMC+ - read/write support for and OWS Context style > doc > * SLD support - edit/read/write > * Renderer Optimizations > o consider attributing geometry components with a > minResolution below which the renderer doesn't deal with them > o clipping - svg supports clipping, we need to consider > clipping or another method of dealing with geometries that extend > beyond the renderer bounds > o add renderer > * integrate emanual's animated zooming stuff > > Anyone care to add to or amplify any of these ideas? > > SDE > > ----- Forwarded message from Jody Garnett ----- > > Date: Mon, 17 Sep 2007 12:28:40 -0700 > From: Jody Garnett > To: OSGeo Discussions > Subject: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? > > Just a reminder, the code sprint is almost upon us, and I would like to > make sure we get as much time with the code as possible. > > A couple of suggestions: > - try and make sure you have your design discussions, bug hit list or > whatever out of the way before the sprint > - make sure developers know what they need to have ready before the > sprint (perhaps a checkout out of the latest?) > - have fun. > > Jody > > _______________________________________________ > Discuss mailing list > Discuss@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/discuss > > ----- End forwarded message ----- > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > > -- Bart van den Eijnden OSGIS, Open Source GIS bartvde@osgis.nl http://www.osgis.nl From andreas.hocevar at gmail.com Tue Sep 18 14:45:19 2007 From: andreas.hocevar at gmail.com (Andreas Hocevar) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fwd: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? In-Reply-To: <20070918145114.GT3930@vishnu.tridity.org> References: <20070918145114.GT3930@vishnu.tridity.org> Message-ID: <5b021dd0709181145k613c558i68d49a4793ac530b@mail.gmail.com> On 9/18/07, Schuyler Erle wrote: > Here's a reminder from the OSGeo-Discuss list re: preparing for the > FOSS4G code sprint next Friday. What should we spend that time > building? There's a few ideas on the OSGeo wiki page: I am preparing some code in my sandbox for parsing SLD, creating style rules (with filters) from it, and applying it to vector layers. At the code sprint, after reviewing my partial implementation, it could be completed to handle all or at least the most common of SLD. Furthermore, SLD write support is something that could be thougt of. And there are people who would also like to see some API functions for SLD editing applications. Regards, Andreas. From crschmidt at metacarta.com Tue Sep 18 15:50:03 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fixing Google Layers, OL SVN + OL <= 2.4 Message-ID: <20070918195003.GB8868@metacarta.com> If you are using a Layer.Google class, please read this! Your application may be broken! (This content is also available online at http://trac.openlayers.org/wiki/GoogleMapsFailure .) OpenLayers has, for a long time, used an internal assumption about the Google Maps API structure due to a lack of functionality in the API. The behavior that OpenLayers depends on has changed, and is no longer the same. We have fixed this functionality in OpenLayers SVN, and it will be shortly released in OpenLayers 2.5 RC2. If you are using an earlier OpenLayers release, you can work around the issue by adding the following code: GMap2.prototype.fromLatLngToContainerPixel = function(gLatLng) { // first we translate into "DivPixel" var gPoint = this.fromLatLngToDivPixel(gLatLng); // locate the sliding "Div" div var div = this.getContainer().firstChild.firstChild; // adjust by the offset of "Div" and voila! gPoint.x += div.offsetLeft; gPoint.y += div.offsetTop; return gPoint; }; This code snippet should be added *after* your GMap script is loaded, but before any Google Layers are initialized. In general, this means it should be at the beginning of your initialization function which is called on loading of the page. There is also a patch available: http://trac.openlayers.org/attachment/ticket/994/google.patch This patch is for 2.5, but applies cleanly to all previous copied of OpenLayers affected by the bug. More information on this problem is available in #994, for interested parties. (This bug was first brought to the attention of the developers approximately 3 hours ago, and was fixed approximately 2 hours later in SVN. The power of Open Source. Thanks for the feedback, everyone.) Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Tue Sep 18 16:42:17 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fwd: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? In-Reply-To: <46EFF4C0.7040206@dmsolutions.ca> References: <20070918145114.GT3930@vishnu.tridity.org> <46EFF4C0.7040206@dmsolutions.ca> Message-ID: <20070918204217.GA30700@metacarta.com> On Tue, Sep 18, 2007 at 11:54:40AM -0400, Mike Adair wrote: > How about: > - add support for MapGuide OS layer type; this code is essentially ready > to go, I just need to create a ticket and a patch. Also, as pointed out by a conversation with someone else today, it would be nice to have this code checked into a sandbox, since others are already duplicating this effort, which is unfortunate. You should have sandbox access: if you don't, please let me know and we can resolve this offlist. Checking it in in a sandbox is a great way to get a number of eyes and users on it before taking the time to create tests and a patch. Regards, -- Christopher Schmidt MetaCarta From madair at dmsolutions.ca Tue Sep 18 17:04:24 2007 From: madair at dmsolutions.ca (Mike Adair) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Fwd: [OSGeo-Discuss] FOSS4G CodeSprint are you ready? In-Reply-To: <20070918204217.GA30700@metacarta.com> References: <20070918145114.GT3930@vishnu.tridity.org> <46EFF4C0.7040206@dmsolutions.ca> <20070918204217.GA30700@metacarta.com> Message-ID: <46F03D58.6060203@dmsolutions.ca> Sorry for dragging my heels on this, but I've created #995 and checked my code into http://svn.openlayers.org/sandbox/madair. There is a examples/mapguide.html but that may require setting some config options to point to a valid MGOS service and the data layers served. Mike Christopher Schmidt wrote: > On Tue, Sep 18, 2007 at 11:54:40AM -0400, Mike Adair wrote: > >> How about: >> - add support for MapGuide OS layer type; this code is essentially ready >> to go, I just need to create a ticket and a patch. >> > > Also, as pointed out by a conversation with someone else today, it would > be nice to have this code checked into a sandbox, since others are > already duplicating this effort, which is unfortunate. > > You should have sandbox access: if you don't, please let me know and we > can resolve this offlist. > > Checking it in in a sandbox is a great way to get a number of eyes and > users on it before taking the time to create tests and a patch. > > Regards, > From franz-josef.behr at hft-stuttgart.de Wed Sep 19 05:33:13 2007 From: franz-josef.behr at hft-stuttgart.de (Dr. Franz-Josef Behr) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Presentation about OpenLayers In-Reply-To: <20070918204217.GA30700@metacarta.com> References: <20070918145114.GT3930@vishnu.tridity.org> <46EFF4C0.7040206@dmsolutions.ca> <20070918204217.GA30700@metacarta.com> Message-ID: <46F0ECD9.6010308@hft-stuttgart.de> Dear list, last week I had the opportunity to give a presentation at a meeting of a "Automation in Cartography, Photogrammetry and GIS" (http://www.ikg.uni-hannover.de/aga/) about Openlayers. If you are interested you download the updated PPT (English) from http://www.gis-news.de/papers/fjb_openlayers_4e.ppt. A PDF version can be found at http://www.ikg.uni-hannover.de/aga/pdf-files_aga2007/pdf_files_aga_vortraege_2007/aga2007_behr.pdf. Sorry for cross-posting! Mit freundlichen Gr??en / Regards / Cordialement Franz-Josef Behr --------------------------------------------------------------- What does education often do? It makes a straight-cut ditch of a free, meandering brook. H.D. THOREAU --------------------------------------------------------------- Prof. Dr. Franz-Josef Behr - Home Office Author of: Strategisches GIS-Management - http://www.gis-management.de eMail: franz-josef.behr@hft-stuttgart.de http://www.gis-news.de Tel: +49 (0)721 / 453980-1 sowie 45 33 35 Fax: +49 (0)721 / 453980-7 sowie via web.de: +49 (0)1212-5-12048213 From paulad at rmi.net Wed Sep 19 08:08:52 2007 From: paulad at rmi.net (pdecker) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] How to change the overview control's location Message-ID: <12683408.post@talk.nabble.com> Hello, I want to change the overview control's location so that when it is expanded it does not cover up the coordinate readout. I can modify the OpenLayers code if need be. I may want to change the location of other controls as well. Thanks so much. -PD -- View this message in context: http://www.nabble.com/How-to-change-the-overview-control%27s-location-tf4445203.html#a12683408 Sent from the OpenLayers Dev mailing list archive at Nabble.com. From paulad at rmi.net Wed Sep 19 08:10:35 2007 From: paulad at rmi.net (pdecker) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] How to change the overview control's location Message-ID: <12683408.post@talk.nabble.com> Hello, I want to change the overview control's location so that when it is expanded it does not cover up the coordinate readout. I can modify the OpenLayers code if need be. I may want to change the location of other controls as well. Thanks so much. -PD -- View this message in context: http://www.nabble.com/How-to-change-the-overview-control%27s-location-tf4445203.html#a12683408 Sent from the OpenLayers Dev mailing list archive at Nabble.com. From crschmidt at metacarta.com Wed Sep 19 08:13:42 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] OpenLayers 2.5 RC2 Announcement Message-ID: <20070919121342.GA27873@metacarta.com> The OpenLayers Development Team is proud to announce the second release candidate of OpenLayers 2.5. This RC incorporates the following fixes. * Click event firing with Navigation Control cleaned up. * Fix to Google layer due to Google API change. * Fix to typo in Layer.Image.setUrl * Fix changeBaseLayer zoom level change * Fix to proxy.cgi to support POST requests. We invite you to help us test the 2.5 release candidate! To test 2.5 in your applications, include the following tag in your OpenLayers-powered page: As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in Trac, under the 2.5 version and milestone. We look forward to your feedback! Regards, The OpenLayers Team From penyaskito at gmail.com Wed Sep 19 08:31:59 2007 From: penyaskito at gmail.com (=?UTF-8?Q?Christian_L=C3=B3pez_Esp=C3=ADnola?=) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] How to change the overview control's location In-Reply-To: <12683408.post@talk.nabble.com> References: <12683408.post@talk.nabble.com> Message-ID: You can do it through the CSS style.css located at the themes/default folder. The classes are coded with the ol prefix and the name of the control. In this case, olControlOverviewMapContainer. Hope this helps. On 9/19/07, pdecker wrote: > > Hello, > I want to change the overview control's location so that when it is expanded > it does not cover up the coordinate readout. I can modify the OpenLayers > code if need be. > > I may want to change the location of other controls as well. > > Thanks so much. > > -PD > -- > View this message in context: http://www.nabble.com/How-to-change-the-overview-control%27s-location-tf4445203.html#a12683408 > Sent from the OpenLayers Dev mailing list archive at Nabble.com. > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -- Regards, Christian L?pez Esp?nola From Eric.Peterson at motorola.com Wed Sep 19 12:01:56 2007 From: Eric.Peterson at motorola.com (Peterson Eric-EEP002) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Need assistance with Image layer Message-ID: I was given an image of a city street map that I would like to use as a base map layer. I know the image extent and its the image size, but I don't know how to set the zoom levels or resolutions appropriately. I understand what the terms scale and resolution mean, but I don't understand how those concepts translate into numbers that can be loaded into the options for constructing a new Image layer. I've tried playing around with information from http://trac.openlayers.org/wiki/SettingZoomLevels but I think I've only ended up more confused than when I started. Can anyone give me some pointers on how to use my knowledge of my map image's size, scale, and extent to properly configure the image layer? -eP -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070919/a415a83b/attachment.html From paulad at rmi.net Wed Sep 19 14:03:46 2007 From: paulad at rmi.net (pdecker) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] How to change the overview control's location In-Reply-To: References: <12683408.post@talk.nabble.com> Message-ID: <12782867.post@talk.nabble.com> Hello, Thank you so much, Christian. That is a clean solution and works splendidly! -PD Christian L?pez Esp?nola wrote: > > You can do it through the CSS style.css located at the themes/default > folder. > > The classes are coded with the ol prefix and the name of the control. > In this case, > olControlOverviewMapContainer. > > Hope this helps. > > > On 9/19/07, pdecker wrote: >> >> Hello, >> I want to change the overview control's location so that when it is >> expanded >> it does not cover up the coordinate readout. I can modify the OpenLayers >> code if need be. >> >> I may want to change the location of other controls as well. >> >> Thanks so much. >> >> -PD >> -- >> View this message in context: >> http://www.nabble.com/How-to-change-the-overview-control%27s-location-tf4445203.html#a12683408 >> Sent from the OpenLayers Dev mailing list archive at Nabble.com. >> >> _______________________________________________ >> Dev mailing list >> Dev@openlayers.org >> http://openlayers.org/mailman/listinfo/dev >> > > > -- > Regards, > > Christian L?pez Esp?nola > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > -- View this message in context: http://www.nabble.com/How-to-change-the-overview-control%27s-location-tf4445203.html#a12782867 Sent from the OpenLayers Dev mailing list archive at Nabble.com. From ian at planetmayo.com Fri Sep 21 02:11:53 2007 From: ian at planetmayo.com (Ian Mayo) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Development toolset Message-ID: Hi, I'm getting up & running with OpenLayers development - starting with small steps. To stop me reinventing the wheel, I'd appreciate anybody's tips on their development environment. I've seen the "ATF" plugin for Eclipse that seems to offer code completion & interactive debugging (two live-savers...). Mailing list entries show a lot of support for FireBug, but I haven't seen any body mention their editors. thanks in advance for any advice, Ian. From erik.uzureau at metacarta.com Fri Sep 21 02:14:57 2007 From: erik.uzureau at metacarta.com (Erik Uzureau) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Development toolset In-Reply-To: References: Message-ID: <6ae3fb590709202314j7d8fdc95xcf33915aaa382c6e@mail.gmail.com> I use eclipse with JSEclipse plugin http://www.interaktonline.com/Products/Eclipse/JSEclipse/Overview/ Erik On 9/21/07, Ian Mayo wrote: > Hi, > I'm getting up & running with OpenLayers development - starting with small > steps. > > To stop me reinventing the wheel, I'd appreciate anybody's tips on > their development environment. > > I've seen the "ATF" plugin for Eclipse that seems to offer code > completion & interactive debugging (two live-savers...). > > Mailing list entries show a lot of support for FireBug, but I haven't > seen any body mention their editors. > > thanks in advance for any advice, > Ian. > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > From giannibarrotta at gmail.com Fri Sep 21 03:36:46 2007 From: giannibarrotta at gmail.com (Gianni Barrotta) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Development toolset In-Reply-To: <6ae3fb590709202314j7d8fdc95xcf33915aaa382c6e@mail.gmail.com> References: <6ae3fb590709202314j7d8fdc95xcf33915aaa382c6e@mail.gmail.com> Message-ID: <190430c0709210036n514f33bdtbe622b216bfc2710@mail.gmail.com> What about the 'outline' view with JSEclipse? With some objects I can't she this view and I can't check class methods... Erik, do I miss something? On 9/21/07, Erik Uzureau wrote: > > I use eclipse with JSEclipse plugin > http://www.interaktonline.com/Products/Eclipse/JSEclipse/Overview/ > > Erik > > On 9/21/07, Ian Mayo wrote: > > Hi, > > I'm getting up & running with OpenLayers development - starting with > small > > steps. > > > > To stop me reinventing the wheel, I'd appreciate anybody's tips on > > their development environment. > > > > I've seen the "ATF" plugin for Eclipse that seems to offer code > > completion & interactive debugging (two live-savers...). > > > > Mailing list entries show a lot of support for FireBug, but I haven't > > seen any body mention their editors. > > > > thanks in advance for any advice, > > Ian. > > _______________________________________________ > > Dev mailing list > > Dev@openlayers.org > > http://openlayers.org/mailman/listinfo/dev > > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070921/cbdd6be9/attachment.html From frederic.junod at camptocamp.com Fri Sep 21 05:37:30 2007 From: frederic.junod at camptocamp.com (=?UTF-8?B?RnLDqWTDqXJpYw==?= Junod) Date: Wed Sep 1 17:23:32 2010 Subject: [OpenLayers-Dev] Should control.destroy() call removeControl ? Message-ID: <20070921113730.082249b2@camptocamp.com> Hi list, In OpenLayers.Layer the destroy function call removeLayer() to remove itself from the map. Shouldn't OpenLayers.Control.destroy() do the same and call removeControl() ? New ticket ? fredj -- Fr?d?ric Junod Camptocamp SA From crschmidt at metacarta.com Fri Sep 21 07:45:17 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Should control.destroy() call removeControl ? In-Reply-To: <20070921113730.082249b2@camptocamp.com> References: <20070921113730.082249b2@camptocamp.com> Message-ID: <20070921114517.GD26166@metacarta.com> On Fri, Sep 21, 2007 at 11:37:30AM +0200, Fr??d??ric Junod wrote: > Hi list, > > In OpenLayers.Layer the destroy function call removeLayer() to remove itself > from the map. > > Shouldn't OpenLayers.Control.destroy() do the same and call removeControl() ? Yep. removeControl is newer than removeLayer, and never got added. > New ticket ? New ticket, 2.6 because I'm concerned about the side effects of making this the default behavior. Regards, -- Christopher Schmidt MetaCarta From louvy.joseph at gmail.com Fri Sep 21 09:32:33 2007 From: louvy.joseph at gmail.com (louvy.joseph@gmail.com) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Are there png8 wms tile problems with IE? Message-ID: <46F3C7F1.7000303@gmail.com> I am cross posting this on both geoserver & openlayers lists.. Recently I was enquiring if any of you have seen the exception issues with geoserver 1.5.3. I have further problems with 1.5.3, this time with PNG8. Is the png8 format rendered by geoserver-1.5.3 fully compliant with the PNG specs? Please ignore my lack of knowledge on PNG. Are there any limitations or certain features not being implemented for this png8 format? I am using Openalyers 2.4 on the client side. Everything is fine on firefox. But both IE6 & IE7 have problems with the png8 produced by geoserver. This manifests in couple of ways: 1) Most of the times, the IE gets redirected to some other page when I use png8 format for openlayers wms layer. (If I use png instead of png8, everything is fine). I am hypothesizing that IE is not able to process the geoserver png8 and gets confused. 2) Lot of times with png8, the openlayers lands in OpenLayers.Util.onImageLoadError() handler. Basically IE thinks that there is some problem with image URL; however the IE ends up drawing the WMS content of the png8 tile fine (but the tile soon gets replaced by a pink tile). Looks like IE thinks that there is something wrong with this tile even though it was able to render it fine. The problem does not consistently happen with one particular tile; the same tile on refresh comes out fine. The support for png8 is very very important for IE6 since IE6 can't handle PNG24 transparency. Any body has any ideas? Thanks in advance.. Louvy Joseph From ahhughes at gmail.com Fri Sep 21 10:07:50 2007 From: ahhughes at gmail.com (Andrew Hughes) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Are there png8 wms tile problems with IE? In-Reply-To: <46F3C7F1.7000303@gmail.com> References: <46F3C7F1.7000303@gmail.com> Message-ID: <5f528cf40709210707h57164356ie7fed9d170617e1a@mail.gmail.com> Hi Louvy, I've noticed that the png8's had a problem in several pieces of software... not just IE. I suspect (and I do stress suspect) that this may be caused not by a defective image or the inability of IE/Others to handle 8 bit png.. but I think it has something to do with the HTTP response type of the image from geoserver. Correct me if I am wrong... but "image/png8" is not an official mime-type, its likely IE is getting confused by this. PNG was designed as a wrapper to several compression formats... hence the name Portable Network Graphics. In IE, I noticed that I was getting black instead of transparency in the image inside IE. Perhaps this is the same for you? In the end, rather than use png (24) or png8 I switched to gif. --AH On 9/21/07, louvy.joseph@gmail.com wrote: > > I am cross posting this on both geoserver & openlayers lists.. > > Recently I was enquiring if any of you have seen the exception issues > with geoserver 1.5.3. I have further problems with 1.5.3, this time with > PNG8. > > Is the png8 format rendered by geoserver-1.5.3 fully compliant with the > PNG specs? Please ignore my lack of knowledge on PNG. Are there any > limitations or certain features not being implemented for this png8 > format? I am using Openalyers 2.4 on the client side. Everything is fine > on firefox. But both IE6 & IE7 have problems with the png8 produced by > geoserver. This manifests in couple of ways: > > 1) Most of the times, the IE gets redirected to some other page when I > use png8 format for openlayers wms layer. (If I use png instead of png8, > everything is fine). I am hypothesizing that IE is not able to process > the geoserver png8 and gets confused. > > 2) Lot of times with png8, the openlayers lands in > OpenLayers.Util.onImageLoadError() handler. Basically IE thinks that > there is some problem with image URL; however the IE ends up drawing the > WMS content of the png8 tile fine (but the tile soon gets replaced by a > pink tile). Looks like IE thinks that there is something wrong with this > tile even though it was able to render it fine. The problem does not > consistently happen with one particular tile; the same tile on refresh > comes out fine. > > The support for png8 is very very important for IE6 since IE6 can't > handle PNG24 transparency. > > Any body has any ideas? Thanks in advance.. > Louvy Joseph > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070921/ad349643/attachment.html From crschmidt at metacarta.com Fri Sep 21 10:21:54 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] OpenLayers 2.5-rc3 Message-ID: <20070921142154.GA16371@metacarta.com> The OpenLayers Development Team is proud to announce the third release candidate of OpenLayers 2.5. Fixes in this version include: * Drag handler doesn't reset properties on left or improperly modified mousedown * Text nodes limited to 4096 characters in length. * KML/GML CDATA Attribute parsing * Small KML Example cleanups. We invite you to help us test the 2.5 release candidate! To test 2.5 in your applications, include the following tag in your OpenLayers-powered page: As always, the source is available at http://openlayers.org/download/. Bug reports can be filed in Trac, under the 2.5 version and milestone. We look forward to your feedback! Regards, The OpenLayers Team -- Christopher Schmidt MetaCarta From aaime at openplans.org Fri Sep 21 10:26:45 2007 From: aaime at openplans.org (Andrea Aime) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Are there png8 wms tile problems with IE? In-Reply-To: <5f528cf40709210707h57164356ie7fed9d170617e1a@mail.gmail.com> References: <46F3C7F1.7000303@gmail.com> <5f528cf40709210707h57164356ie7fed9d170617e1a@mail.gmail.com> Message-ID: <46F3D4A5.6090008@openplans.org> Andrew Hughes ha scritto: > Hi Louvy, > > I've noticed that the png8's had a problem in several pieces of > software... not just IE. I suspect (and I do stress suspect) that this > may be caused not by a defective image or the inability of IE/Others to > handle 8 bit png.. but I think it has something to do with the HTTP > response type of the image from geoserver. Correct me if I am wrong... > but "image/png8" is not an official mime-type, its likely IE is getting > confused by this. PNG was designed as a wrapper to several compression > formats... hence the name Portable Network Graphics. The mime type returned by the png8 map producer is still "image/png". > In IE, I noticed that I was getting black instead of transparency in the > image inside IE. Perhaps this is the same for you? > > In the end, rather than use png (24) or png8 I switched to gif. Just tried the following request: http://localhost:8080/geoserver/wms?HEIGHT=550&WIDTH=429&LAYERS=tiger%3Apoly_landmarks&STYLES=&SRS=EPSG%3A4326&FORMAT=image%2Fpng8&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetMap&EXCEPTIONS=application%2Fvnd.ogc.se_inimage&BBOX=-74.07079%2C40.661263%2C-73.884215%2C40.900463&transparent=true in both firefox and ie7/win xp and ie7 Vista, works fine in both, no black areas here... I don't have access to and older IE unfortunately... Cheers Andrea From lorenzo at ominiverdi.com Fri Sep 21 10:29:36 2007 From: lorenzo at ominiverdi.com (Lorenzo Becchi) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] WebMap BOF Message-ID: <46F3D550.5010301@ominiverdi.com> Hi all, as confirmed [1] the WebMap BOF is in room Saanich - 1 (126) I'm cross-posting, sorry all, to ka-map, openlayers and geoserver dev lists. I would love to invite Mapbender, Mapbuilder and all other projects involved in WebMapping. the discussion could be oriented on OpenLayers Code Sprint goals [2]. Naturally we will define again the program once all together. comments can be added on the WebMap BOF paragraph [3]. ciao Lorenzo [1] http://wiki.osgeo.org/index.php/FOSS4G2007_BOF_Sessions [2] http://wiki.osgeo.org/index.php/FOSS4G2007_CodeSprint#OpenLayers [3] http://wiki.osgeo.org/index.php/FOSS4G2007_BOF_Sessions#WebMap From aaime at openplans.org Fri Sep 21 10:33:19 2007 From: aaime at openplans.org (Andrea Aime) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] [Geoserver-devel] Are there png8 wms tile problems with IE? In-Reply-To: <46F3C7F1.7000303@gmail.com> References: <46F3C7F1.7000303@gmail.com> Message-ID: <46F3D62F.1090902@openplans.org> louvy.joseph@gmail.com ha scritto: > I am cross posting this on both geoserver & openlayers lists.. > > Recently I was enquiring if any of you have seen the exception issues > with geoserver 1.5.3. I have further problems with 1.5.3, this time with > PNG8. > > Is the png8 format rendered by geoserver-1.5.3 fully compliant with the > PNG specs? Please ignore my lack of knowledge on PNG. Are there any > limitations or certain features not being implemented for this png8 > format? I am using Openalyers 2.4 on the client side. Everything is fine > on firefox. But both IE6 & IE7 have problems with the png8 produced by > geoserver. This manifests in couple of ways: > > 1) Most of the times, the IE gets redirected to some other page when I > use png8 format for openlayers wms layer. (If I use png instead of png8, > everything is fine). I am hypothesizing that IE is not able to process > the geoserver png8 and gets confused. > > 2) Lot of times with png8, the openlayers lands in > OpenLayers.Util.onImageLoadError() handler. Basically IE thinks that > there is some problem with image URL; however the IE ends up drawing the > WMS content of the png8 tile fine (but the tile soon gets replaced by a > pink tile). Looks like IE thinks that there is something wrong with this > tile even though it was able to render it fine. The problem does not > consistently happen with one particular tile; the same tile on refresh > comes out fine. I would be happy to investigate this, but I can't reproduce any of these problems with the geoserver standard data set. If you can give me a full set of data, requests and whatnot needed to reproduce these errors I'll be happy to have a look at it. Cheers Andrea From crschmidt at metacarta.com Fri Sep 21 11:16:25 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] OpenLayers 2.5-rc3 In-Reply-To: <46F3DFBB.8010700@swoodbridge.com> References: <20070921142154.GA16371@metacarta.com> <46F3DFBB.8010700@swoodbridge.com> Message-ID: <20070921151625.GB21740@metacarta.com> On Fri, Sep 21, 2007 at 11:14:03AM -0400, Stephen Woodbridge wrote: > Christopher Schmidt wrote: > >The OpenLayers Development Team is proud to announce the third release > >candidate of OpenLayers 2.5. Fixes in this version include: > > > > * Drag handler doesn't reset properties on left or improperly modified > > mousedown > > * Text nodes limited to 4096 characters in length. > > Chris, > > Can you expand on the 4K limit. We often get back xml documents that > have more than 4K of text in a single node, like coordinates for a > singel segment of a route? Will this break now? No. It won't break now. These are 'fixes' -- things which were fixed in this relase. This limitation has been in all versions of OpenLayers thus far and never reported until Thursday, but is fixed now. http://trac.openlayers.org/ticket/1006 Regards, -- Christopher Schmidt MetaCarta From crschmidt at metacarta.com Sun Sep 23 00:10:13 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] OL BOFs -- Tues. and Weds. Message-ID: <20070923041013.GA5458@metacarta.com> FOSS4G Attendees: So, there's a big WebMap BOF on Tuesday night, for anyone interested in web mapping. Great. Because there's going to be so many non-OL specific people at that, I'd like to have anyone who is planning to participate in the code sprint on Friday stop in at a BOF on Wednesday night as well. Right now, it's set up for: Saanich - 1 (126) OpenLayers pre-codesprint meetup Christopher Schmidt after presentations on Wednesday, at 4:45. The point is just to get everyone set up with the administrativa that committing to OpenLayers requires, like CLAs filled out, wiki/trac/svn usernames and passwords created, etc. We'll also review some of the basic rules of OL committing both for the sprint and afterwards, and figure out what we're going to do for keeping this development going forward and not making it impossible to integrate back into trunk (as some of our previous efforts have ended up). So, Tuesday is a big group, lots of discussion/round tableness, etc. and Wednesday is 'OL hackers looking to get in on the Friday action showing up and chatting/meeting face to face/getting set up.' We'll probably be done long before the hour that's currently scheduled is up, but if you want to hack with us on Friday, *please* come by. Check the BOFs board during the conference for more. (Also, I'm hoping that most of the core devs will be able to be there on Wednesday night, which means it might also be a chance to do smaller scale meet and greet if you're busy Tuesday night with one of the other BOFs.) Regards, -- Christopher Schmidt MetaCarta From paulad at rmi.net Mon Sep 24 11:05:02 2007 From: paulad at rmi.net (pdecker) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] BBOX values are out of range for EPSG:4326 Message-ID: <12861727.post@talk.nabble.com> Hello, I am running example: controls.html which is found in the examples directory of OpenLayers2.3. One of the tile requests has a BBOX of: -1260, 990, -900, 1350. The request also shows the SRS=EPSG:4326. I thought BBOX values for SRS=EPSG:4326 were in the range: latitude 90 to -90 and longitude 180 to -180. The reason I ask is because I am now getting out of range values with a map whose coordinates are: MinLat=32.58:59N, MaxLat=32:59:00N, MinLon=085:00:00E, MaxLon=085:00:01E. Can OpenLayers handle a map which is 1 second by 1 second? Thanks in advance. -PD -- View this message in context: http://www.nabble.com/BBOX-values-are-out-of-range-for-EPSG%3A4326-tf4509740.html#a12861727 Sent from the OpenLayers Dev mailing list archive at Nabble.com. From giannibarrotta at gmail.com Mon Sep 24 12:38:47 2007 From: giannibarrotta at gmail.com (Gianni Barrotta) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] can not focuse input text fields In-Reply-To: <1189766403.8543.27.camel@mellon> References: <1189692674.7823.15.camel@mellon> <1189766403.8543.27.camel@mellon> Message-ID: <190430c0709240938p6d739b8bn28f789163f2c2d26@mail.gmail.com> Hi, I've got a similar problem. I can't select the text inside the input field. I tried with the following code: OpenLayers.Event.observe(myTextInput, "click", this.focusInputField); focusInputField: function(evt) { evt.target.select(); }, but the text on the field in not selected. Any idea? THANKS On 9/14/07, Jachym Cepicky wrote: > > hi, > > OpenLayers.Event.observe(myTextInput, "click", > this.focusInputField); > focusInputField: function(evt) { > evt.target.focus(); > }, > > j > > Jachym Cepicky p??e v ?t 13. 09. 2007 v 16:11 +0200: > > Hi, > > > > I try to setup basic WPS [1][2] client in OpenLayers. I used > > OpenLayers.Control.LayerSwitcher as base for the code. The working demo > > (at least in Firefox) can be seen at [3]. > > > > Only one problem: It is not possible, to focus input text fields by > > mouse (), so you can not write new values per > > keyboard (for example the server name or later the process Input > > values). Could anybody give me advice, how to get this working? > > > > The source, used in the demo [3] is new file, called WPS.py [4]. > > > > Thanks > > > > Jachym > > > > [1] http://www.opengeospatial.org/standards/requests/28 > > [2] http://pywps.wald.intevation.org > > [3] > > > http://www.bnhelp.cz/mapserv/pokusy/OpenLayers/jachym/openlayers/examples/wps.html > > [4] > > > http://dev.openlayers.org/sandbox/jachym/openlayers/lib/OpenLayers/Control/WPS.js > > _______________________________________________ > > Dev mailing list > > Dev@openlayers.org > > http://openlayers.org/mailman/listinfo/dev > -- > Jachym Cepicky > e-mail: jachym.cepicky@gmail.com > URL: http://les-ejk.cz > GPG: http://www.les-ejk.cz/pgp/jachym_cepicky-gpg.pub > > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070924/9b236d06/attachment.html From crschmidt at metacarta.com Mon Sep 24 14:37:16 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] BBOX values are out of range for EPSG:4326 In-Reply-To: <12861727.post@talk.nabble.com> References: <12861727.post@talk.nabble.com> Message-ID: <20070924183716.GA19433@metacarta.com> On Mon, Sep 24, 2007 at 08:05:02AM -0700, pdecker wrote: > > Hello, > I am running example: controls.html which is found in the examples directory > of OpenLayers2.3. http://openlayers.org/dev/examples/controls.html should be fundamentally the same: I don't see any requests outside the bounds of the world. Do you? (Tryign to figure out what I'm missing.) Regards, -- Christopher Schmidt MetaCarta From volpicelli at oato.inaf.it Tue Sep 25 02:53:23 2007 From: volpicelli at oato.inaf.it (Antonio) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Tooltips on the controls in NavToolBar Message-ID: <46F8B063.3020000@oato.inaf.it> Hi, I moved the NavToolBar with some controls outside of the Map and I would like to enable tooltips on they . Is there some one what I could do? Thanks Antonio -- /-------------------------------------------------------\ PLEASE WARNING: E-mail is CHANGED volpicelli@oato.inaf.it /-------------------------------------------------------\ From bartvde at osgis.nl Tue Sep 25 07:11:30 2007 From: bartvde at osgis.nl (Bart van den Eijnden (OSGIS)) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] problem in OpenLayers.Util.pagePosition Message-ID: <80efecaf6bb882076151257f715325a1@145.50.39.11> Hi list, using 2.5RC3 I have a problem in the above mentioned function, whereas this works fine in version 2.4. The problem is only in IE. The error occurs in the following line of getStyle (style is null or not an object): var value = element.style[OpenLayers.String.camelize(style)]; If I change the following line (back to its 2.4 equivalent): if(element == document.body) { to: if(element.offsetParent == document.body) { it works fine again. Best regards, Bart -- Bart van den Eijnden OSGIS, Open Source GIS http://www.osgis.nl From kleptog at gmail.com Tue Sep 25 08:44:31 2007 From: kleptog at gmail.com (Martijn van Oosterhout) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Tiled WFS layer Message-ID: <2fc2c5f10709250544k6c710195mb02ed29e1de97b33@mail.gmail.com> For a POI layer for OSM I've been working on a tiled version of the WFS layer (apparently I'm not the only one). I have it working now. It's really only minor changes from the standard TMS layer. There are some minor changes to the Tile.WFS class, which you can see here: http://dev.openstreetmap.org/~kleptog/pois/Tile_WFS.js Really only the changes in the "destroyAllFeatures" and the "draw" functions are necessary, otherwise the markers keep getting created and never destroyed. The actual WFSGrid is here: http://dev.openstreetmap.org/~kleptog/pois/WFSGrid.js It's really a minor variation on the TMS, the diff is here: http://dev.openstreetmap.org/~kleptog/pois/wfsgrid.txt The most necessary bits were the add/removeMarker, needed by Tile.WFS to interact with the marker layer. There are a few remaing issues: - Due to the way Layer.Grid works you need aggressive caching on the server side or it'll keep requesting the same thing over and over again. - The Markers disappear while dragging - It feels slow somehow... - The marker layer currently needs to be created by the user, but I've just been told it's ok to inherit from Markers and Grid simultaneously. Anyway, this is just to let you guy know where I'm up to, in case anybody has ideas. Complete working demo is here: http://dev.openstreetmap.org/~kleptog/pois/pois2.html Thanks in advance, -- Martijn van Oosterhout http://svana.org/kleptog/ From lee.keel at uai.com Tue Sep 25 10:36:02 2007 From: lee.keel at uai.com (Lee Keel) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Tooltips on the controls in NavToolBar Message-ID: <76758090F8686C47A44B6FF52514A1D30904DA53@hermes.uai.int> > -----Original Message----- > From: dev-bounces@openlayers.org [mailto:dev-bounces@openlayers.org] On > Behalf Of Antonio > Sent: Tuesday, September 25, 2007 1:53 AM > To: openlayers dev > Subject: [OpenLayers-Dev] Tooltips on the controls in NavToolBar > > Hi, > I moved the NavToolBar with some controls outside of the Map and I would > like to enable tooltips on they . > Is there some one what I could do? > > Thanks > > Antonio > > -- > /-------------------------------------------------------\ > PLEASE WARNING: E-mail is CHANGED > volpicelli@oato.inaf.it > /-------------------------------------------------------\ > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev Antonio, This feature has been asked about several times in the last couple of weeks and the standard response has been "This functionality is slated for 2.6.... but patches are welcome." -LK This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. From penyaskito at gmail.com Tue Sep 25 10:44:45 2007 From: penyaskito at gmail.com (=?UTF-8?Q?Christian_L=C3=B3pez_Esp=C3=ADnola?=) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Tooltips on the controls in NavToolBar In-Reply-To: <46F8B063.3020000@oato.inaf.it> References: <46F8B063.3020000@oato.inaf.it> Message-ID: Hi Antonio, See if http://dev.openlayers.org/sandbox/penyaskito/openlayers/examples/panel.html does what you want. If it helps, see the patch at the ticket #822 http://trac.openlayers.org/ticket/822 Cheers On 9/25/07, Antonio wrote: > Hi, > I moved the NavToolBar with some controls outside of the Map and I would > like to enable tooltips on they . > Is there some one what I could do? > > Thanks > > Antonio > > -- > /-------------------------------------------------------\ > PLEASE WARNING: E-mail is CHANGED > volpicelli@oato.inaf.it > /-------------------------------------------------------\ > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -- Regards, Christian L?pez Esp?nola From paulad at rmi.net Tue Sep 25 11:03:55 2007 From: paulad at rmi.net (pdecker) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] BBOX values are out of range for EPSG:4326 In-Reply-To: <20070924183716.GA19433@metacarta.com> References: <12861727.post@talk.nabble.com> <20070924183716.GA19433@metacarta.com> Message-ID: <12881570.post@talk.nabble.com> My zoom level was not high enough. I adjusted that and now the correct bounding boxes are being requested from OpenLayers. Thanks. Christopher Schmidt-4 wrote: > > On Mon, Sep 24, 2007 at 08:05:02AM -0700, pdecker wrote: >> >> Hello, >> I am running example: controls.html which is found in the examples >> directory >> of OpenLayers2.3. > > http://openlayers.org/dev/examples/controls.html > should be fundamentally the same: I don't see any requests outside the > bounds of the world. Do you? (Tryign to figure out what I'm missing.) > > Regards, > -- > Christopher Schmidt > MetaCarta > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > > -- View this message in context: http://www.nabble.com/BBOX-values-are-out-of-range-for-EPSG%3A4326-tf4509740.html#a12881570 Sent from the OpenLayers Dev mailing list archive at Nabble.com. From fporcelli at taic.net Tue Sep 25 11:25:34 2007 From: fporcelli at taic.net (fporcelli@taic.net) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] VML Rendering of point data Message-ID: <44045.192.168.1.70.1190733934.webmail@192.168.1.70> Hello dev -- I was wondering if anyone is aware of an issue discovered regarding rendering of KML point data using IE6. It seems the point locations are not placed at the correct coordinates when using the VML renderer with IE6. After some research I noticed that there was a documented issue in ticket #517 (http://trac.openlayers.org/ticket/517) regarding the inability to use floating point numbers in VML. It appears that this is directly related to the above issue. While this ticket is closed, is anyone aware that VML point data still is not rendering correctly? If a patch is required, I would be happy to offer up some assistance, but don't have write access to the code base. Thanks, Frank From crschmidt at metacarta.com Tue Sep 25 11:37:36 2007 From: crschmidt at metacarta.com (Christopher Schmidt) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] pgRouting + OpenLayers Message-ID: <20070925153736.GA29302@metacarta.com> What I Learned Yesterday at FOSS4G A report by Christopher Schmidt http://boston.freemap.in/routing.html Click 'set start point' Click on the map Click on 'set end point' Click and drag across the map and watch the little red line follow you. Thanks to Camptocamp and orkney for their presentation yesterday on how to do this. I'm currently working on adding data for the full state of Massachusetts: Right now the data is only Cambridge, so it's easy to wander out of the data. Regards, -- Christopher Schmidt MetaCarta From eric.c2c at gmail.com Tue Sep 25 14:38:31 2007 From: eric.c2c at gmail.com (Eric Lemoine) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] VML Rendering of point data In-Reply-To: <44045.192.168.1.70.1190733934.webmail@192.168.1.70> References: <44045.192.168.1.70.1190733934.webmail@192.168.1.70> Message-ID: <5ec103de0709251138y48ca8d74s9fe7f8490445bb3e@mail.gmail.com> On 9/25/07, fporcelli@taic.net wrote: > Hello dev -- > > I was wondering if anyone is aware of an issue discovered regarding rendering of KML point data using IE6. It seems the point locations are not placed at the correct coordinates when using the VML renderer with IE6. After some research I noticed that there was a documented issue in ticket #517 (http://trac.openlayers.org/ticket/517) regarding the inability to use floating point numbers in VML. It appears that this is directly related to the above issue. While this ticket is closed, is anyone aware that VML point data still is not rendering correctly? If a patch is required, I would be happy to offer up some assistance, but don't have write access to the code base. Hi Frank, This isn't a known issue. Could you provide more details? And possibly post some code... -- Eric From cameron.shorter at gmail.com Tue Sep 25 16:02:39 2007 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Tiled WFS layer In-Reply-To: <2fc2c5f10709250544k6c710195mb02ed29e1de97b33@mail.gmail.com> References: <2fc2c5f10709250544k6c710195mb02ed29e1de97b33@mail.gmail.com> Message-ID: <46F9695F.5090601@gmail.com> Martijn, I don't have any fixes, but am interested to hear that you are using WFS code with Openstreetmap. Does this mean that OSM now has a WFS interface? Is it a query only interface, or is there transactional support as well? Martijn van Oosterhout wrote: > For a POI layer for OSM I've been working on a tiled version of the > WFS layer (apparently I'm not the only one). I have it working now. > It's really only minor changes from the standard TMS layer. > > There are some minor changes to the Tile.WFS class, which you can see here: > http://dev.openstreetmap.org/~kleptog/pois/Tile_WFS.js > Really only the changes in the "destroyAllFeatures" and the "draw" > functions are necessary, otherwise the markers keep getting created > and never destroyed. > > The actual WFSGrid is here: > http://dev.openstreetmap.org/~kleptog/pois/WFSGrid.js > It's really a minor variation on the TMS, the diff is here: > http://dev.openstreetmap.org/~kleptog/pois/wfsgrid.txt > The most necessary bits were the add/removeMarker, needed by Tile.WFS > to interact with the marker layer. > > There are a few remaing issues: > - Due to the way Layer.Grid works you need aggressive caching on the > server side or it'll keep requesting the same thing over and over > again. > - The Markers disappear while dragging > - It feels slow somehow... > - The marker layer currently needs to be created by the user, but I've > just been told it's ok to inherit from Markers and Grid > simultaneously. > > Anyway, this is just to let you guy know where I'm up to, in case > anybody has ideas. Complete working demo is here: > http://dev.openstreetmap.org/~kleptog/pois/pois2.html > > Thanks in advance, > -- Cameron Shorter Systems Architect, http://lisasoft.com.au Tel: +61 (0)2 8570 5050 Mob: +61 (0)419 142 254 From ahhughes at gmail.com Tue Sep 25 22:20:34 2007 From: ahhughes at gmail.com (Andrew Hughes) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Tiled WFS layer In-Reply-To: <46F9695F.5090601@gmail.com> References: <2fc2c5f10709250544k6c710195mb02ed29e1de97b33@mail.gmail.com> <46F9695F.5090601@gmail.com> Message-ID: <5f528cf40709251920o4be7c16dj31feda16c9bb343f@mail.gmail.com> Hi Guys, I know this is getting a little "Ahead"... this is more "server-side" work.. but if the client operates with this in mind it could be a good idea. WFS tiling + Query Caching would be an excellent idea! Similar to WMS-C (tilecache).. it would be possible to cache each WFS/Tile query. So what... in addition, server-side middle ware could optimize/downsample/simplify complex geometries so that it is composed of only useful data at the Tile's resolution. Good but not great... so.... because we are now dealing with a tile grid, the server-side could "seed" and cache the same query's complex geometry at different resolutions, optimizing the data at each resolution. This would address problems related to vector data sizes inside the browser., increase server response times and user experience. Not an issue if your data is not complex... but then again.. you probably wouldn't be tiling anyway. Example Implementation (server side): * Receive WFS query.... * Optimize/Downsample the raw vector data to only useful data at the requested Tile resolution. * Return WFS response with optimized data for current resolution (z).. but continue server side.... (client gets response) * Analyze the raw vector data... iterate/seed the Tiles above and below the current resolution (z), down sampling/optimizing the the and cache these tiles. Two big pluses, browser only receives quick, thin responses. --AH p.s. also, this server overhead is not as big as you might think... it can be done quite sensibly.... with each step in the seed/optimize process builds on the previous seed/optimize operation. p.s. martin keep this in mind for a bigger picture... you might want to store something other than a "BufferedImage" one day :), particular if you are providing a data for "brainless", "gutless", "low bandwidth" mobile phones. On 9/26/07, Cameron Shorter wrote: > > Martijn, > I don't have any fixes, but am interested to hear that you are using WFS > code with Openstreetmap. Does this mean that OSM now has a WFS interface? > Is it a query only interface, or is there transactional support as well? > > Martijn van Oosterhout wrote: > > For a POI layer for OSM I've been working on a tiled version of the > > WFS layer (apparently I'm not the only one). I have it working now. > > It's really only minor changes from the standard TMS layer. > > > > There are some minor changes to the Tile.WFS class, which you can see > here: > > http://dev.openstreetmap.org/~kleptog/pois/Tile_WFS.js > > Really only the changes in the "destroyAllFeatures" and the "draw" > > functions are necessary, otherwise the markers keep getting created > > and never destroyed. > > > > The actual WFSGrid is here: > > http://dev.openstreetmap.org/~kleptog/pois/WFSGrid.js > > It's really a minor variation on the TMS, the diff is here: > > http://dev.openstreetmap.org/~kleptog/pois/wfsgrid.txt > > The most necessary bits were the add/removeMarker, needed by Tile.WFS > > to interact with the marker layer. > > > > There are a few remaing issues: > > - Due to the way Layer.Grid works you need aggressive caching on the > > server side or it'll keep requesting the same thing over and over > > again. > > - The Markers disappear while dragging > > - It feels slow somehow... > > - The marker layer currently needs to be created by the user, but I've > > just been told it's ok to inherit from Markers and Grid > > simultaneously. > > > > Anyway, this is just to let you guy know where I'm up to, in case > > anybody has ideas. Complete working demo is here: > > http://dev.openstreetmap.org/~kleptog/pois/pois2.html > > > > Thanks in advance, > > > > > -- > Cameron Shorter > Systems Architect, http://lisasoft.com.au > Tel: +61 (0)2 8570 5050 > Mob: +61 (0)419 142 254 > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/openlayers-dev/attachments/20070926/c3a44fdc/attachment.html From steven at minst.net Wed Sep 26 04:42:17 2007 From: steven at minst.net (Steven M. Ottens) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] overviewmap and spherical mercator Message-ID: <46FA1B69.9060205@minst.net> Hi All, I'm trying to implement an overviewmap together with a google layer, using the spherical mercator code by Tim. However, it fails with an error: 'bounds has no properties' in the function zoomToExtent in Map.js This function is called from zoomToMaxExtent and it uses this.getMaxExtent() to get a bounds. However this last function returns null. this.maxExtent at this point is -180,-90,180,90 which I believe is the default maxExtent, since it's wrong, tims foss4g sandbox only shows North America and last time I checked that doesn't span the globe ;) If I go into getMaxExtent at this point it tells me that this.baseLayer = null. At this point I don't know what to do. There is a baseLayer so I don't understand why in the overviewMap it doesn't show. Or when that's correct behavior, why it fails on a lack of bounds. Anyone has an overviewmap working with the Spherical Mercator projection, if so could you please enlighten me? Regards, Steven From volpicelli at oato.inaf.it Wed Sep 26 06:51:13 2007 From: volpicelli at oato.inaf.it (Antonio) Date: Wed Sep 1 17:23:33 2010 Subject: [OpenLayers-Dev] Tooltips on the controls in NavToolBar In-Reply-To: References: <46F8B063.3020000@oato.inaf.it> Message-ID: <46FA39A1.2020805@oato.inaf.it> Christian, this seems to work only if you keep the controls on the map. If you move the controls outside the map it doesn't work. This are some line of my code: