From paul.neave at gmail.com Sun Oct 1 21:03:29 2006 From: paul.neave at gmail.com (Paul Neave) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] Re: Google Map projection and EPSG codes In-Reply-To: <451A5AA1.80401@gmail.com> References: <200609262038.k8QKclhB031617@tux.cubewerx.com> <451A5AA1.80401@gmail.com> Message-ID: I'd like to second this request - Mercator projection for WMS is something that I'm finding I desperately need for similar applications I'm developing that use imagery from different sources (that don't use plate carr?e). The hack that's currently available leaves large areas of the map distorted at zoomed-out levels. I don't know how difficult it would be to implement a new EPSG code on NASA's WMS server, but judging other examples around on the web it looks at though it is possible. Does anyone have any experience with this? Thanks, Paul. On 27/09/06, Cameron Shorter wrote: > One of the commonly requested features for a webmapping client is to > render WMS layers over Google Map basemaps. > > Unfortunately, this is tricky to implement because the projection used > by Google Maps doesn't have a corresponding EPSG code which means that > the projection cannot be selected using a standard WMS query. > > John Deck describes the problem, and a hack to get around it at: > http://johndeck.blogspot.com/2005/09/overlaying-mercator-projected-wms.html > John defines his own EPSG code in a mapserv config file. > > Questions: > ========== > 1. geoserver-devel, Is there a similar hack that can be used in Geoserver? > > 2. webmap-discuss, has anyone worked out a "less hacky" solution? > > 3. What is the process for defining a new EPSG code? Is this something > we can make happen? > > Proposal: > ========= > webmap-discuss, geoserver-devel, mapserver people, > If we cannot force a new EPSG code to be officially created, I suggest > that all the Open Source projects define a de-facto EPSG code for Google > Maps which Geoserv, Mapserv and the various webmapping clients all support. > > Craig Bruce wrote: > > "Kralidis,Tom [Burlington]" wrote: > > > > > >>Question: has there been any definition of an EPSG code as applied to > >>the way Google Maps displays their data (I'm not exactly sure what the > >>projection params, but I did find one def from the postgis-users mailing > >>list [see: > >>http://postgis.refractions.net/pipermail/postgis-users/2005-November/009 > >>920.html])? > >> > >>I'm not sure if CubeWerx has defined one in the 42xxx series of > >>'defacto' EPSG codes, or whether it's defined already, for that matter. > > > > > > The closest match we have found is a simple Mercator projection. One is > > defined in the OGC 41xxx space as: > > > > EPSG:41001: > > > > PROJCS["WGS84 / Simple Mercator", > > GEOGCS["WGS 84", > > DATUM["WGS_1984", > > SPHEROID["WGS_1984",6378137,298.257223563]], > > PRIMEM["Greenwich",0], > > UNIT["Decimal_Degree",0.0174532925199433]], > > PROJECTION["Mercator"], > > PARAMETER["latitude_of_origin",0], > > PARAMETER["central_meridian",0], > > PARAMETER["false_easting",0], > > PARAMETER["false_northing",0], > > UNIT["Meter",1]] > > > > This doesn't appear to be an exact match, however, as the mismatch grows > > from the equator from zero to a few kilometers. There might be a scale > > factor/secant involved. > > > > --------------------------+----------------------+-------------------------- > > Dr. Craig S. Bruce | Ph 819-771-8303 x205 | CubeWerx Inc. > > Senior Software Developer | Fax 819-771-8388 | Gatineau, Qu?bec, Canada > > csbruce@cubewerx.com | http://csbruce.com/ | http://www.cubewerx.com/ > > --------------------------+----------------------+-------------------------- > > "Q: How many of your previous romantic relationships were failures? > > A: All of them. > > Q: So, what are the chances for your present relationship? > > A: Well, let's check the statistics..." > > > > > -- > Cameron Shorter > http://cameron.shorter.net > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > > From cameron.shorter at gmail.com Thu Oct 12 07:08:51 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [Mapbuilder-users] How to show service exceptions from WMS? In-Reply-To: References: Message-ID: <452E2243.60808@gmail.com> webmap-discus, One of our uses wants to handle errors from WMS servers (which might be returned in XML format). Are other projects handling WMS errors? If so, how? Bart van den Eijnden (OSGIS) wrote: > I think most clients just implement inimage. > > But there are potential problems: > -inimage is optional in the WMS spec > -as you pointed out how will it look if multiple error images are stacked > > For Mapserver WMS client there is some discussion here: > > http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1246 > > You might also ask this to the OpenLayers (www.openlayers.org) guys, but I > don't think they support WMS XML error messages, but I don't know how hard > it would be to handle it in OpenLayers, maybe it's simpler there, and since > Mapbuilder plans to use OpenLayers as the rendering engine, it would be the > most logical place to handle it IMHO. > > Best regards, > Bart > > -- > Bart van den Eijnden > OSGIS, Open Source GIS > http://www.osgis.nl > > > --------- Oorspronkelijk bericht -------- > Van: Gertjan van Oosten > Naar: Cameron Shorter > Cc: mapbuilder-users@lists.sourceforge.net > Onderwerp: Re: [Mapbuilder-users] How to show service exceptions from WMS? > Datum: 12/10/06 06:59 > > >>Hi Cameron, >> >>As quoted from Cameron Shorter <cameron.shorter@gmail.com>: >>> One of the options you can send to the WMS allows you to specify that > > >>> exceptions are to be reported as an image. >>> Would that be acceptable? >> >>Since the WMS is written by me, that would be an option. However, as I >>understand it that would mean the error image is just another layer in >>the map stack. How this would look to the user is an open question, >>especially if the WMS returns errors for several layers... >> >>> If you want to handle an XML response instead of image, that will be >>> quite a bit harder and I'm not sure how we would do it. >>> Currently we simply create a HTML img tag <img > > src=http://wms?.../> > >>> >>> There would probably be a reasonable amount of work required to get >>> something workable. >> >>Should I open an RFE on Jira? I'm sure more people would find it useful >>if MapBuilder supported this. How do other mapping tools handle this >>(uDig etc.)? >> >>Kind regards, >>-- >>-- Gertjan van Oosten, gertjan@West.NL, West Consulting B.V., +31 15 2191 > > 600 > >>------------------------------------------------------------------------- >>Using Tomcat but need to do more? Need to support web services, security? >>Get stuff done quickly with pre-integrated technology to make your job > > easier > >>Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo >> > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > >>_______________________________________________ >>Mapbuilder-users mailing list >>Mapbuilder-users@lists.sourceforge.net >>https://lists.sourceforge.net/lists/listinfo/mapbuilder-users >> >> > > > > > -- Cameron Shorter http://cameron.shorter.net From cameron.shorter at gmail.com Fri Oct 13 08:32:21 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: VectorLayer design Message-ID: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> Following on from the discussion about Vector Rendering in browsers, I've put together my thoughts as to what the design should look like. (As a UML diagram) I've also included the raw UML (it was created on Umbrello using Linux). -- Cameron Shorter http://cameron.shorter.net -------------- next part -------------- A non-text attachment was scrubbed... Name: Layers.png Type: image/png Size: 24858 bytes Desc: not available Url : http://lists.osgeo.org/pipermail/mail_webmap-discuss/attachments/20061013/65edd792/Layers.png -------------- next part -------------- A non-text attachment was scrubbed... Name: Graphics.png Type: image/png Size: 18368 bytes Desc: not available Url : http://lists.osgeo.org/pipermail/mail_webmap-discuss/attachments/20061013/65edd792/Graphics.png -------------- next part -------------- A non-text attachment was scrubbed... Name: Controls.png Type: image/png Size: 12523 bytes Desc: not available Url : http://lists.osgeo.org/pipermail/mail_webmap-discuss/attachments/20061013/65edd792/Controls.png -------------- next part -------------- A non-text attachment was scrubbed... Name: graphics.xmi Type: text/x-xmi Size: 67500 bytes Desc: not available Url : http://lists.osgeo.org/pipermail/mail_webmap-discuss/attachments/20061013/65edd792/graphics.bin From greening at bigtribe.com Fri Oct 13 12:05:22 2006 From: greening at bigtribe.com (Dan R. Greening) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] VectorLayer design In-Reply-To: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> References: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> Message-ID: <0140108A-E0CB-4C3B-8195-21836AD29C99@bigtribe.com> Just some skimmed-it comments: Don't Polygon and Line each aggregate a List of Coord? I would use the diamond aggregate to denote this, because if you delete a Polygon you presumably want all the Coords deleted also. Pointer sort-of implies the Coords have a life of their own. Also maybe you want a 3..* on Polygon and a 2 on Line. Dan R. Greening, Ph.D., CEO BigTribe Corporation, http:// dan.greening.name/contact.htm On Oct 13, 2006, at 5:32 AM, Cameron Shorter wrote: > Following on from the discussion about Vector Rendering in browsers, > I've put together my thoughts as to what the design should look like. > (As a UML diagram) > > I've also included the raw UML (it was created on Umbrello using > Linux). > -- > Cameron Shorter > http://cameron.shorter.net > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/mail_webmap-discuss/attachments/20061013/933cb4ad/attachment.html From cameron.shorter at gmail.com Sat Oct 14 16:53:35 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] VectorLayer design In-Reply-To: <0140108A-E0CB-4C3B-8195-21836AD29C99@bigtribe.com> References: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> <0140108A-E0CB-4C3B-8195-21836AD29C99@bigtribe.com> Message-ID: <45314E4F.2050205@gmail.com> Thanks Dan, you are right. Now updated. Dan R. Greening wrote: > Just some skimmed-it comments: > > Don't Polygon and Line each aggregate a List of Coord? I would use the > diamond aggregate to denote this, because if you delete a Polygon you > presumably want all the Coords deleted also. Pointer sort-of implies > the Coords have a life of their own. Also maybe you want a 3..* on > Polygon and a 2 on Line. > > Dan R. Greening, Ph.D., CEO BigTribe Corporation, > http://dan.greening.name/contact.htm > > > > On Oct 13, 2006, at 5:32 AM, Cameron Shorter wrote: > >> Following on from the discussion about Vector Rendering in browsers, >> I've put together my thoughts as to what the design should look like. >> (As a UML diagram) >> >> I've also included the raw UML (it was created on Umbrello using Linux). >> -- >> Cameron Shorter >> http://cameron.shorter.net >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org >> >> For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org >> > > -- Cameron Shorter http://cameron.shorter.net From cameron.shorter at gmail.com Sat Oct 14 22:40:02 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] VectorLayer design In-Reply-To: <45314E4F.2050205@gmail.com> References: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> <0140108A-E0CB-4C3B-8195-21836AD29C99@bigtribe.com> <45314E4F.2050205@gmail.com> Message-ID: <8fd6e5470610141940u3f1261a9p3241f00eeb669a17@mail.gmail.com> Take 2 at the design: To avoid swamping the list with large images, I've copied the diagrams to my blog: http://cameronshorter2.blogspot.com/2006/10/ajax-vector-rendering-design.html On 10/15/06, Cameron Shorter wrote: > Thanks Dan, you are right. Now updated. > > Dan R. Greening wrote: > > Just some skimmed-it comments: > > > > Don't Polygon and Line each aggregate a List of Coord? I would use the > > diamond aggregate to denote this, because if you delete a Polygon you > > presumably want all the Coords deleted also. Pointer sort-of implies > > the Coords have a life of their own. Also maybe you want a 3..* on > > Polygon and a 2 on Line. > > > > Dan R. Greening, Ph.D., CEO BigTribe Corporation, > > http://dan.greening.name/contact.htm > > > > > > > > On Oct 13, 2006, at 5:32 AM, Cameron Shorter wrote: > > > >> Following on from the discussion about Vector Rendering in browsers, > >> I've put together my thoughts as to what the design should look like. > >> (As a UML diagram) > >> > >> I've also included the raw UML (it was created on Umbrello using Linux). > >> -- > >> Cameron Shorter > >> http://cameron.shorter.net > >> > >> > >> > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > >> > >> For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > >> > > > > > > > -- > Cameron Shorter > http://cameron.shorter.net > -- Cameron Shorter http://cameron.shorter.net From woodbri at swoodbridge.com Sun Oct 15 00:44:33 2006 From: woodbri at swoodbridge.com (Stephen Woodbridge) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] VectorLayer design In-Reply-To: <8fd6e5470610141940u3f1261a9p3241f00eeb669a17@mail.gmail.com> References: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> <0140108A-E0CB-4C3B-8195-21836AD29C99@bigtribe.com> <45314E4F.2050205@gmail.com> <8fd6e5470610141940u3f1261a9p3241f00eeb669a17@mail.gmail.com> Message-ID: <4531BCB1.9040906@swoodbridge.com> Cameron, I would like to add some additional use cases: TC has loaded some polygon data from different sources. He has some some adjacent polygons that he want to share a common edge. He needs to select each polygon and the start and end of the shared edge on each that needs to be snapped together. The first polygon can be the control and the second one gets manipulated. The edge of the second between the start and end gets removed and replaced by points from the first between its start and end marks. TC does not like some of the points on the shared edge, he would like to select the two polygons and move some of the points along the shared edge and some that are not shared. After looking at his handiwork and TC would like to undo the last few moves. TC thinks it is a bother to keep selecting both polygons to do the manipulation and would prefer to "link them together" along the common edge. To some extent this imply using topology, and planning for topology support could be very powerful, but this can also be done by maintaining some additional pointers and tracking and updating their children and avoiding circular references. -Steve W. Cameron Shorter wrote: > Take 2 at the design: > To avoid swamping the list with large images, I've copied the diagrams > to my blog: > http://cameronshorter2.blogspot.com/2006/10/ajax-vector-rendering-design.html > > > > On 10/15/06, Cameron Shorter wrote: >> Thanks Dan, you are right. Now updated. >> >> Dan R. Greening wrote: >> > Just some skimmed-it comments: >> > >> > Don't Polygon and Line each aggregate a List of Coord? I would use the >> > diamond aggregate to denote this, because if you delete a Polygon you >> > presumably want all the Coords deleted also. Pointer sort-of implies >> > the Coords have a life of their own. Also maybe you want a 3..* on >> > Polygon and a 2 on Line. >> > >> > Dan R. Greening, Ph.D., CEO BigTribe Corporation, >> > http://dan.greening.name/contact.htm >> > >> > >> > >> > On Oct 13, 2006, at 5:32 AM, Cameron Shorter wrote: >> > >> >> Following on from the discussion about Vector Rendering in browsers, >> >> I've put together my thoughts as to what the design should look like. >> >> (As a UML diagram) >> >> >> >> I've also included the raw UML (it was created on Umbrello using >> Linux). >> >> -- >> >> Cameron Shorter >> >> http://cameron.shorter.net >> >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org >> >> >> >> For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org >> >> >> > >> > >> >> >> -- >> Cameron Shorter >> http://cameron.shorter.net >> > > From cameron.shorter at gmail.com Mon Oct 16 17:17:21 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] VectorLayer design In-Reply-To: <4531BCB1.9040906@swoodbridge.com> References: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> <0140108A-E0CB-4C3B-8195-21836AD29C99@bigtribe.com> <45314E4F.2050205@gmail.com> <8fd6e5470610141940u3f1261a9p3241f00eeb669a17@mail.gmail.com> <4531BCB1.9040906@swoodbridge.com> Message-ID: <4533F6E1.7020204@gmail.com> Steven, Thanks for these use cases. Why don't you add them in the comments section of the blog: http://cameronshorter2.blogspot.com/2006/10/ajax-vector-rendering-design.html Stephen Woodbridge wrote: > Cameron, > > I would like to add some additional use cases: > > TC has loaded some polygon data from different sources. He has some some > adjacent polygons that he want to share a common edge. He needs to > select each polygon and the start and end of the shared edge on each > that needs to be snapped together. The first polygon can be the control > and the second one gets manipulated. The edge of the second between the > start and end gets removed and replaced by points from the first between > its start and end marks. > > TC does not like some of the points on the shared edge, he would like to > select the two polygons and move some of the points along the shared > edge and some that are not shared. After looking at his handiwork and TC > would like to undo the last few moves. > > TC thinks it is a bother to keep selecting both polygons to do the > manipulation and would prefer to "link them together" along the common > edge. > > To some extent this imply using topology, and planning for topology > support could be very powerful, but this can also be done by maintaining > some additional pointers and tracking and updating their children and > avoiding circular references. > > -Steve W. > > Cameron Shorter wrote: > >> Take 2 at the design: >> To avoid swamping the list with large images, I've copied the diagrams >> to my blog: >> http://cameronshorter2.blogspot.com/2006/10/ajax-vector-rendering-design.html >> >> >> >> On 10/15/06, Cameron Shorter wrote: >> >>> Thanks Dan, you are right. Now updated. >>> >>> Dan R. Greening wrote: >>> > Just some skimmed-it comments: >>> > >>> > Don't Polygon and Line each aggregate a List of Coord? I would use >>> the >>> > diamond aggregate to denote this, because if you delete a Polygon you >>> > presumably want all the Coords deleted also. Pointer sort-of implies >>> > the Coords have a life of their own. Also maybe you want a 3..* on >>> > Polygon and a 2 on Line. >>> > >>> > Dan R. Greening, Ph.D., CEO BigTribe Corporation, >>> > http://dan.greening.name/contact.htm >>> > >>> > >>> > >>> > On Oct 13, 2006, at 5:32 AM, Cameron Shorter wrote: >>> > >>> >> Following on from the discussion about Vector Rendering in browsers, >>> >> I've put together my thoughts as to what the design should look like. >>> >> (As a UML diagram) >>> >> >>> >> I've also included the raw UML (it was created on Umbrello using >>> Linux). >>> >> -- >>> >> Cameron Shorter >>> >> http://cameron.shorter.net >>> >> >>> >> >>> >> >>> >> >>> >> --------------------------------------------------------------------- >>> >> To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org >>> >> >>> >> For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org >>> >> >>> > >>> > >>> >>> >>> -- >>> Cameron Shorter >>> http://cameron.shorter.net >>> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > > -- Cameron Shorter http://cameron.shorter.net From bluecarto at gmail.com Tue Oct 17 04:16:02 2006 From: bluecarto at gmail.com (Pierre GIRAUD) Date: Fri Dec 22 15:49:42 2006 Subject: Fwd: [OpenLayers-Dev] Re: Vectors in OpenLayers? In-Reply-To: References: <20061011145303.GC31725@metacarta.com> <072D6D76-4C7B-4CA0-8254-336807BBA57E@dmsolutions.ca> <20061012235555.GK19482@crschmidt.net> <9903B6ED-F592-4307-9658-3349FBFDF51F@dmsolutions.ca> Message-ID: As said in the openlayers IRC topic, it is recommended to use the webmap list as possible. This message was sent to the openlayers-dev list last friday. For the rest of the discussion, I kept some interesting ideas shared by Paul and Cameron last night on the IRC chan. Is there already an OSGEO wiki page to contribute. Some people in camptocamp also gave a thought on UML diagrams. Regards Pierre GIRAUD ---------- Forwarded message ---------- From: Pierre GIRAUD Date: Oct 13, 2006 6:46 PM Subject: Re: [OpenLayers-Dev] Re: Vectors in OpenLayers? To: Cc: dev@openlayers.org I wanna propose you some peace of code for this. Hope you'll be able to have a quick look and check if I'm the good way. I tried to follow the "factory" pattern, but I'm not sure I implemented it right considering the rest of the architecture. Regards and nice week-end Pierre ps : this code might be useable in the current vector sandbox -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.osgeo.org/pipermail/mail_webmap-discuss/attachments/20061017/6bf1bf42/wkt.html -------------- next part -------------- A non-text attachment was scrubbed... Name: WKT.js Type: application/x-javascript Size: 2477 bytes Desc: not available Url : http://lists.osgeo.org/pipermail/mail_webmap-discuss/attachments/20061017/6bf1bf42/WKT.js From cameron.shorter at gmail.com Tue Oct 17 07:31:33 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] Fwd: [OpenLayers-Dev] Re: Vectors in OpenLayers? In-Reply-To: References: <20061011145303.GC31725@metacarta.com> <072D6D76-4C7B-4CA0-8254-336807BBA57E@dmsolutions.ca> <20061012235555.GK19482@crschmidt.net> <9903B6ED-F592-4307-9658-3349FBFDF51F@dmsolutions.ca> Message-ID: <4534BF15.1080604@gmail.com> I've moved the design to the wiki at http://wiki.osgeo.org/index.php/AJAX_WebMapping_Vector_Rendering_Design which should make it easier for others to contribute. Next, I plan to update the diagrams to include ideas from Paul Spensor and myself. Hopefully I'll get it done tonight - but it might have to wait until tomorrow. Please feel free to add a comment title underneath each diagram. Eg: ===Comments=== # Cameron Shorter: This design could be better if ... Pierre GIRAUD wrote: > As said in the openlayers IRC topic, it is recommended to use the > webmap list as possible. > This message was sent to the openlayers-dev list last friday. > > For the rest of the discussion, I kept some interesting ideas shared > by Paul and Cameron last night on the IRC chan. Is there already an > OSGEO wiki page to contribute. Some people in camptocamp also gave a > thought on UML diagrams. > > Regards > > Pierre GIRAUD > > > > ---------- Forwarded message ---------- > From: Pierre GIRAUD > Date: Oct 13, 2006 6:46 PM > Subject: Re: [OpenLayers-Dev] Re: Vectors in OpenLayers? > To: > Cc: dev@openlayers.org > > > I wanna propose you some peace of code for this. > Hope you'll be able to have a quick look and check if I'm the good way. > > I tried to follow the "factory" pattern, but I'm not sure I > implemented it right considering the rest of the architecture. > > Regards and nice week-end > > Pierre > > ps : this code might be useable in the current vector sandbox > > ------------------------------------------------------------------------ > > > ------------------------------------------------------------------------ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org -- Cameron Shorter http://cameron.shorter.net From woodbri at swoodbridge.com Wed Oct 18 10:41:04 2006 From: woodbri at swoodbridge.com (Stephen Woodbridge) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] VectorLayer design In-Reply-To: <4533F6E1.7020204@gmail.com> References: <8fd6e5470610130532q4fcd22e7ie0e564636e69a740@mail.gmail.com> <0140108A-E0CB-4C3B-8195-21836AD29C99@bigtribe.com> <45314E4F.2050205@gmail.com> <8fd6e5470610141940u3f1261a9p3241f00eeb669a17@mail.gmail.com> <4531BCB1.9040906@swoodbridge.com> <4533F6E1.7020204@gmail.com> Message-ID: <45363D00.20108@swoodbridge.com> Cameron, Added to your blog and to the wiki page. -Steve Cameron Shorter wrote: > Steven, > Thanks for these use cases. Why don't you add them in the comments > section of the blog: > http://cameronshorter2.blogspot.com/2006/10/ajax-vector-rendering-design.html > > > > Stephen Woodbridge wrote: >> Cameron, >> >> I would like to add some additional use cases: >> >> TC has loaded some polygon data from different sources. He has some >> some adjacent polygons that he want to share a common edge. He needs >> to select each polygon and the start and end of the shared edge on >> each that needs to be snapped together. The first polygon can be the >> control and the second one gets manipulated. The edge of the second >> between the start and end gets removed and replaced by points from the >> first between its start and end marks. >> >> TC does not like some of the points on the shared edge, he would like >> to select the two polygons and move some of the points along the >> shared edge and some that are not shared. After looking at his >> handiwork and TC would like to undo the last few moves. >> >> TC thinks it is a bother to keep selecting both polygons to do the >> manipulation and would prefer to "link them together" along the common >> edge. >> >> To some extent this imply using topology, and planning for topology >> support could be very powerful, but this can also be done by >> maintaining some additional pointers and tracking and updating their >> children and avoiding circular references. >> >> -Steve W. >> >> Cameron Shorter wrote: >> >>> Take 2 at the design: >>> To avoid swamping the list with large images, I've copied the diagrams >>> to my blog: >>> http://cameronshorter2.blogspot.com/2006/10/ajax-vector-rendering-design.html >>> >>> >>> >>> On 10/15/06, Cameron Shorter wrote: >>> >>>> Thanks Dan, you are right. Now updated. >>>> >>>> Dan R. Greening wrote: >>>> > Just some skimmed-it comments: >>>> > >>>> > Don't Polygon and Line each aggregate a List of Coord? I would >>>> use the >>>> > diamond aggregate to denote this, because if you delete a Polygon you >>>> > presumably want all the Coords deleted also. Pointer sort-of implies >>>> > the Coords have a life of their own. Also maybe you want a 3..* on >>>> > Polygon and a 2 on Line. >>>> > >>>> > Dan R. Greening, Ph.D., CEO BigTribe Corporation, >>>> > http://dan.greening.name/contact.htm >>>> > >>>> > >>>> > >>>> > On Oct 13, 2006, at 5:32 AM, Cameron Shorter wrote: >>>> > >>>> >> Following on from the discussion about Vector Rendering in browsers, >>>> >> I've put together my thoughts as to what the design should look >>>> like. >>>> >> (As a UML diagram) >>>> >> >>>> >> I've also included the raw UML (it was created on Umbrello using >>>> Linux). >>>> >> -- >>>> >> Cameron Shorter >>>> >> http://cameron.shorter.net >>>> >> >>>> >> >>>> >> >>>> >> >>>> >> >>>> --------------------------------------------------------------------- >>>> >> To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org >>>> >> >>>> >> For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org >>>> >> >>>> > >>>> > >>>> >>>> >>>> -- >>>> Cameron Shorter >>>> http://cameron.shorter.net >>>> >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org >> For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org >> >> > > From cameron.shorter at gmail.com Thu Oct 26 16:15:46 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [OpenLayers-Dev] [Dev] Re: Vectors in OpenLayers? In-Reply-To: References: <4CE9D61A-FDC9-436C-A6A5-1A5ED76960F1@dmsolutions.ca> <45385785.8020604@gmail.com> <4538AD5F.8070606@osgis.nl> <4538AFCA.7040809@gmail.com> <45392B02.5050103@gmail.com> Message-ID: <45411772.7090108@gmail.com> Pierre, From your email, it seems Bertil has a solid design, and not very different to what we have proposed. I'm busy for the next week or 2, but hope to have time to look at the code after that. Are you (or Pierre) still working on this, or interested in working on Vector Rendering further? Pierre GIRAUD wrote: > Hello all, > > This comes certainly a little late in the discussion but I'd like to > propose the architecture design a student (Bertil CHAPUIS) worked on > for camptocamp. This happened just before or while you also started > thinking about it, but we didn't have time to share it. > > It may go in a different way that the one proposed in the osgeo wiki > but here are summarized the pros and cons, or specific features of his > model. > > --- separated geometry model and rendering system --- > pros : > - Javascript geometry objects are clear and easier to instanciate > - those objects can be easily managed by new modules (WFS, etc...) > > cons : > - this implementation may be more difficult to maintain because it is > needed to alter the rendering engine or modules plugged on the model > when a geometry class is modified. But this should not happen often if > the classes follow the OGC norms at once. > > --- Editing events handlers --- > > The different rendering systems have the ability to send editing > events (requests). > > --- Vector Layer --- > > The model and geometry features management is handled in the vector > layer. It is sort of a features container. This helps to centralize > the actions on data so to make the integrity management easier. > > --- Editing controlers --- > The editing controlers manage the geometries modifications through the > vector layer and its methods. This allows to list the previous carried > actions and to propose cancel functionnalities. > > Constraint by a short period, he also already started to implement it > on top of openlayers librairy. > You can find a almost working demo at > http://dev.camptocamp.com/~bchapuis/openlayers/examples/vector.html > > I hope you can have a look and give back comments and/or additions. > Just note that the vml implementations isn't working completely for > the moment. > > Regards > > Pierre GIRAUD and Bertil CHAPUIS > -- Cameron Shorter http://cameron.shorter.net From bluecarto at gmail.com Thu Oct 26 16:33:38 2006 From: bluecarto at gmail.com (Pierre GIRAUD) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] Re: [OpenLayers-Dev] [Dev] Re: Vectors in OpenLayers? In-Reply-To: <45411772.7090108@gmail.com> References: <4CE9D61A-FDC9-436C-A6A5-1A5ED76960F1@dmsolutions.ca> <45385785.8020604@gmail.com> <4538AD5F.8070606@osgis.nl> <4538AFCA.7040809@gmail.com> <45392B02.5050103@gmail.com> <45411772.7090108@gmail.com> Message-ID: Sure, we will go further. We need something working soon. In any case, we currently spend much time on this. Pierre On 10/26/06, Cameron Shorter wrote: > Pierre, > From your email, it seems Bertil has a solid design, and not very > different to what we have proposed. > > I'm busy for the next week or 2, but hope to have time to look at the > code after that. > > Are you (or Pierre) still working on this, or interested in working on > Vector Rendering further? > > Pierre GIRAUD wrote: > > Hello all, > > > > This comes certainly a little late in the discussion but I'd like to > > propose the architecture design a student (Bertil CHAPUIS) worked on > > for camptocamp. This happened just before or while you also started > > thinking about it, but we didn't have time to share it. > > > > It may go in a different way that the one proposed in the osgeo wiki > > but here are summarized the pros and cons, or specific features of his > > model. > > > > --- separated geometry model and rendering system --- > > pros : > > - Javascript geometry objects are clear and easier to instanciate > > - those objects can be easily managed by new modules (WFS, etc...) > > > > cons : > > - this implementation may be more difficult to maintain because it is > > needed to alter the rendering engine or modules plugged on the model > > when a geometry class is modified. But this should not happen often if > > the classes follow the OGC norms at once. > > > > --- Editing events handlers --- > > > > The different rendering systems have the ability to send editing > > events (requests). > > > > --- Vector Layer --- > > > > The model and geometry features management is handled in the vector > > layer. It is sort of a features container. This helps to centralize > > the actions on data so to make the integrity management easier. > > > > --- Editing controlers --- > > The editing controlers manage the geometries modifications through the > > vector layer and its methods. This allows to list the previous carried > > actions and to propose cancel functionnalities. > > > > Constraint by a short period, he also already started to implement it > > on top of openlayers librairy. > > You can find a almost working demo at > > http://dev.camptocamp.com/~bchapuis/openlayers/examples/vector.html > > > > I hope you can have a look and give back comments and/or additions. > > Just note that the vml implementations isn't working completely for > > the moment. > > > > Regards > > > > Pierre GIRAUD and Bertil CHAPUIS > > > > > -- > Cameron Shorter > http://cameron.shorter.net > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > > From cameron.shorter at gmail.com Sat Oct 28 01:50:04 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [OpenLayers-Dev] Vector UI requirements In-Reply-To: <4FCA4ECFE787FB4CA8A7E1D47B2CBBA807DB5E@sbs.citysafe.local> References: <4FCA4ECFE787FB4CA8A7E1D47B2CBBA807DB5E@sbs.citysafe.local> Message-ID: <4542EF8C.2030608@gmail.com> Ed, There have been a few of us discussing Vector Rendering - some of the emails are on the webmap-discuss email list. You might want to check the archieves. The design we have come up with so far is at http://wiki.osgeo.org/index.php/AJAX_WebMapping_Vector_Rendering_Design (There are a few outstanding comments which I have not incorporated yet). Feel free to add your comments and/or suggestions. Ed Dowding wrote: > Folks ~ > > I'm just working up a UI for the vector work - just something so that we > have a first draft to look at, review, and have a think about. I'm > envisaging that this should be ok regardless of the drawing library > used. > > So let's start with a requirements list. Is there going to be more > functionality required than this? Eg GIS functionality that I've missed > off? > > Please update / comment to list or pref at > http://trac.openlayers.org/wiki/VectorDrawing > > > Have a great weekend, > > Ed > > > > > Shapes (create, update, destroy) > > * lines > * point > * polygon > * polygon with holes in them (does this have name?) > > Markers (create, update, destroy) > > * upload a marker > * group markers into directories > * drag markers onto the map > > Text labels (create, update, destroy) > > Import/Export > > * georss > * Export all / one > o Choose format.. > o geoRSS > o what others..? > * Import > o Browse... --> upload > > Other > > * Clear all > * Undo > > Item Styling > > Line > > * colour > * width > * opacity > > Fill > > * colour > * width > * opacity > > Text > > * color > * font size > * font weight > * font style > > Influences > > * photoshop > * fireworks > * www.quikmaps.com/new > > > > Ed > > > * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * > > IRIS - Integrated Risk Intelligence System > > Web based information and communication solutions > for emergency preparedness, response and recovery > > --------------------------------------------------------------------- > Ed Dowding ed@citysafe.org > [mob] +44 (0)7775 79 18 14 [sky] eddowding > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > Product Manager, CitySafe www.citysafe.org > ===================================================================== > > Helping keep Londoners safe and informed. > Join FREE at www.communitysafe.org > > ===================================================================== > Privileged or confidential information may be contained in this email > and is intended for the addressee. If you are not the addressee, or > the person responsible for delivering it to the person addressed, you > may not copy or deliver this to anyone else. If you receive this > email by mistake, please notify us immediately. > ===================================================================== > > > _______________________________________________ > Dev mailing list > Dev@openlayers.org > http://openlayers.org/mailman/listinfo/dev > -- Cameron Shorter http://cameron.shorter.net From cameron.shorter at gmail.com Sun Oct 29 19:26:50 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: Using OWS Context to describe GML/WFS layers which decimate Message-ID: <454546CA.4090109@gmail.com> Tom Kralidis, As part of OWS4, I'm using rendering GML layers in a web browser, and using OWS Context to describe the layers. The use case I'm having problem with is how to render large datasets when the user zooms out, which means you have to render a huge number of points. The usual solution is to decimate the features as you zoom out. Ie, reduce the number of points rendered. However, I don't think I can describe this using the current OWS Context. I assume the best solution would be to filter on the zoomLevel, and use a different data source for each zoomLevel or resolution, which I believe would require a change to the OWS Context spec. I'm open to suggestions here. -- Cameron Shorter http://cameron.shorter.net From cameron.shorter at gmail.com Mon Oct 30 02:00:54 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: AJAX vector rendering "gathering" Message-ID: <4545A326.9050801@gmail.com> There are a number of early implementations of AJAX GIS vector rendering that we are all involved in - and there seems to be a common desire to work together on this. I suggest we have an IRC meeting where we can agree on a common design (at a high level) then volunteer for components. that everyone who is interested join together in an IRC session in 12 hours at: http://timeanddate.com/worldclock/meetingdetails.html?year=2006&month=10&day=30&hour=19&min=0&sec=0&p1=240&p2=16&p3=179&p4=137 Sydney Tue 6:00:00 AM UTC+11 hours EST Amsterdam Mon 8:00:00 PM UTC+1 hour CET New York Mon 2:00:00 PM UTC-5 hours EST Los Angeles Mon 11:00:00 AM UTC-8 hours PST Corresponding UTC (GMT) Monday, 30 October 2006 at 19:00:00 Channel: irc://freenode.net#openlayers Agenda: 00 - 05: Roll Call. Confirm agenda. 05 - 10: Who is working on what, and what you plan to work on + questions. 10 - 50: Design discussion. 50 - 55: Coordinate efforts (who is working on what) 55 - 60: Arange next meeting. 60 --: Meeting close People who have shown an interest so far: ========================================= I'm writing vector rendering code for large GML datasets, currently using Mapbuilder but I'd like to move the logic into OpenLayers and use OpenLayers for the Mapbuilder rendering engine. With Paul Spencer, I've started putting together a design at: http://wiki.osgeo.org/index.php/AJAX_WebMapping_Vector_Rendering_Design#Graphics_Class_Diagram Paul Spencer has written vector rendering code for OpenLayers using IECanvas and has been discussing a new Vector rendering design with me. Pierre Giraud and Bertil Chapuis have implemented vector rendering in OpenLayers, including feature entry and editing at: http://dev.camptocamp.com/~bchapuis/openlayers/examples/vector.html Steven Ottens needs to edit features in a browser and I think he has plans for working on this soon. Ed Dowding has put together design ideas at: http://trac.openlayers.org/wiki/VectorDrawing Patrice Cappelaere has written SVG and VML support for GeoRSS and GML layers in Mapbuilder using elements of SLD for styling. Others on the CC list have contributed to discussions. Please add your name and come along if you are interested. -- Cameron Shorter http://cameron.shorter.net From cameron.shorter at gmail.com Mon Oct 30 04:39:19 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [Context.RWG] Using OWS Context to describe GML/WFS layers whichdecimate In-Reply-To: References: Message-ID: <4545C847.50708@gmail.com> zoomLevel is a term used by Google/Yahoo/MSN Maps. It is a measure of resolution. As you zoom out, the zoomLevel increases. Martin Daly wrote: >>I assume the best solution would be to filter on the >>zoomLevel, and use a different data source for each zoomLevel >>or resolution, which I believe would require a change to the >>OWS Context spec. > > > What is the definition of "zoomLevel", for all possible GML CRS-s? > > M > -- Cameron Shorter http://cameron.shorter.net From pat at cappelaere.com Mon Oct 30 05:07:45 2006 From: pat at cappelaere.com (Pat Cappelaere) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] AJAX vector rendering "gathering" In-Reply-To: <4545A326.9050801@gmail.com> Message-ID: I am interested but cannot attend. Sorry!. Pat. > From: Cameron Shorter > Reply-To: > Date: Mon, 30 Oct 2006 18:00:54 +1100 > To: Paul Spencer , Steven Ottens , > Christopher Schmidt , Ed Dowding , > Pierre GIRAUD , Patrice Cappelaere > , Bart van den Eijnden , Stephen > Woodbridge , 'Chris Holmes' > Cc: , > Subject: [webmap-discuss] AJAX vector rendering "gathering" > > There are a number of early implementations of AJAX GIS vector rendering > that we are all involved in - and there seems to be a common desire to > work together on this. > > I suggest we have an IRC meeting where we can agree on a common design > (at a high level) then volunteer for components. > > that everyone who is interested join together in an IRC session in 12 > hours at: > http://timeanddate.com/worldclock/meetingdetails.html?year=2006&month=10&day=3 > 0&hour=19&min=0&sec=0&p1=240&p2=16&p3=179&p4=137 > Sydney Tue 6:00:00 AM UTC+11 hours EST > Amsterdam Mon 8:00:00 PM UTC+1 hour CET > New York Mon 2:00:00 PM UTC-5 hours EST > Los Angeles Mon 11:00:00 AM UTC-8 hours PST > Corresponding UTC (GMT) Monday, 30 October 2006 at 19:00:00 > > Channel: > irc://freenode.net#openlayers > > Agenda: > 00 - 05: Roll Call. Confirm agenda. > 05 - 10: Who is working on what, and what you plan to work on + questions. > 10 - 50: Design discussion. > 50 - 55: Coordinate efforts (who is working on what) > 55 - 60: Arange next meeting. > 60 --: Meeting close > > People who have shown an interest so far: > ========================================= > I'm writing vector rendering code for large GML datasets, currently > using Mapbuilder but I'd like to move the logic into OpenLayers and use > OpenLayers for the Mapbuilder rendering engine. > With Paul Spencer, I've started putting together a design at: > http://wiki.osgeo.org/index.php/AJAX_WebMapping_Vector_Rendering_Design#Graphi > cs_Class_Diagram > > Paul Spencer has written vector rendering code for OpenLayers using > IECanvas and has been discussing a new Vector rendering design with me. > > Pierre Giraud and Bertil Chapuis have implemented vector rendering in > OpenLayers, including feature entry and editing at: > http://dev.camptocamp.com/~bchapuis/openlayers/examples/vector.html > > Steven Ottens needs to edit features in a browser and I think he has > plans for working on this soon. > > Ed Dowding has put together design ideas at: > http://trac.openlayers.org/wiki/VectorDrawing > > Patrice Cappelaere has written SVG and VML support for GeoRSS and GML > layers in Mapbuilder using elements of SLD for styling. > > Others on the CC list have contributed to discussions. Please add your > name and come along if you are interested. > > -- > Cameron Shorter > http://cameron.shorter.net > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > From cameron.shorter at gmail.com Mon Oct 30 19:28:34 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [Context.RWG] Using OWS Context to describe GML/WFS layers whichdecimate In-Reply-To: References: Message-ID: <454698B2.6020909@gmail.com> Martin, Point taken regarding G/Y/M maps. Replace zoomLevel with sld:Min/MaxScaleDenominator in my previous comment. I still need to reference different GML sources for each layer depending on scale, which doesn't seem to be covered by OWS Context yet. Martin Daly wrote: >>zoomLevel is a term used by Google/Yahoo/MSN Maps. >>It is a measure of resolution. As you zoom out, the zoomLevel >>increases. > > > That is not a definition that will wash in a standard that aims for > interoperability. > > In fact, OWS Context already uses sld:Min/MaxScaleDenominator in the > AbstractResourceType, so the capability already exists. > > As with the previous long e-mail trail re. GYM data, this spec. should > leverage de jure OGC standards, not de facto ones that large parts of > the target audience cannot use. > > M > > -- Cameron Shorter http://cameron.shorter.net From cameron.shorter at gmail.com Mon Oct 30 19:30:56 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [Context.RWG] Using OWS Context to describe GML/WFS layers whichdecimate In-Reply-To: <1082B4BE-7AF2-44F8-93B6-4901C32F9CAE@traversetechnologies.com> References: <40354295-649E-4F41-97CB-5CD67FB547E1@traversetechnologies.com> <23719.145.50.39.8.1162218693.squirrel@webmail.xs4all.nl> <1082B4BE-7AF2-44F8-93B6-4901C32F9CAE@traversetechnologies.com> Message-ID: <45469940.5020002@gmail.com> Yes, Joshua, You have done a better job describing my problem. Joshua Lieberman wrote: > Bart, > > There isn't really an option in WFS, though, to express what > "density" is appropriate for a given GetFeature request. Colleagues > of mine once introduced a random order function into WFS so that the > client could use maxFeatures for this purpose, requesting for example > maxFeatures=200 and expecting that these features would be randomly > (not necessarily evenly) distributed within the requested extent. > That doesn't give you scale-dependent generalization of polygon > features, though, and it would be a bit scary for a WFS to return > different polygon coordinate strings in response to maxFeatures > without a way to express that capability. > > Josh > > On Oct 30, 2006, at 9:31 AM, Bart van den Eijnden (OSGIS) wrote: > > >>Alternatively, you can also leave this at the server level. >> >>Like Geoserver does, with its kml_reflect script. If the extent is too >>large, it will produce an image for Google Earth, if you zoom in >>further, >>you will get actual vectors in KML. >> >>A similar thing could be done for this use case, where you would let a >>server-side script (acting as a WFS) decide how accurate and dense the >>point featurecollection returned would be. >> >>Best regards, >>Bart >> >> >>>It is probably worth looking at the Google Earth "super overlay" >>>definition (http://earth.google.com/kml/ >>>kml_21tutorial.html#superoverlays) to inform this discussion. It's a >>>pretty awkward way of defining a tile pyramid out of anything, >>>whether image files, cacheable WMS calls (their protestations against >>>WMS notwithstanding), or even WFS calls to features with different >>>levels of generality. It does, however, answer a need of working with >>>different zoom levels and tiles. >>> >>>We lack a few things, not just OWS Context capabilities, to do this >>>more elegantly. For example, it isn't immediately clear to me how to >>>define a GML feature which has different geometries at different >>>defined resolutions or scale ranges, or indicate that two feature >>>collections are the same features intended for different scales. >>>Without this sort of definition, there is something rather ad hoc >>>about expressing it in OWS Context. >>> >>>Josh >>> >>> >>>On Oct 30, 2006, at 5:07 AM, Martin Daly wrote: >>> >>> >>>>>zoomLevel is a term used by Google/Yahoo/MSN Maps. >>>>>It is a measure of resolution. As you zoom out, the zoomLevel >>>>>increases. >>>> >>>>That is not a definition that will wash in a standard that aims for >>>>interoperability. >>>> >>>>In fact, OWS Context already uses sld:Min/MaxScaleDenominator in the >>>>AbstractResourceType, so the capability already exists. >>>> >>>>As with the previous long e-mail trail re. GYM data, this spec. >>>>should >>>>leverage de jure OGC standards, not de facto ones that large >>>>parts of >>>>the target audience cannot use. >>>> >>>>M >>>> >>>> >>>>_______________________________________________ >>>>Context.rwg mailing list >>>>Context.rwg@opengeospatial.org >>>>https://mail.opengeospatial.org/mailman/listinfo/context.rwg >>> >>>_______________________________________________ >>>Context.rwg mailing list >>>Context.rwg@opengeospatial.org >>>https://mail.opengeospatial.org/mailman/listinfo/context.rwg >>> >> >> >>_______________________________________________ >>Context.rwg mailing list >>Context.rwg@opengeospatial.org >>https://mail.opengeospatial.org/mailman/listinfo/context.rwg > > > _______________________________________________ > Context.rwg mailing list > Context.rwg@opengeospatial.org > https://mail.opengeospatial.org/mailman/listinfo/context.rwg > -- Cameron Shorter http://cameron.shorter.net From woodbri at swoodbridge.com Mon Oct 30 21:27:53 2006 From: woodbri at swoodbridge.com (Stephen Woodbridge) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] AJAX vector rendering "gathering" In-Reply-To: <4545A326.9050801@gmail.com> References: <4545A326.9050801@gmail.com> Message-ID: <4546B4A9.4020209@swoodbridge.com> Cameron, I really wanted to attend, but had other commitments. Will someone post a summary of the discussion and any decisions/outcomes/etc. Thanks, -Steve Cameron Shorter wrote: > There are a number of early implementations of AJAX GIS vector rendering > that we are all involved in - and there seems to be a common desire to > work together on this. > > I suggest we have an IRC meeting where we can agree on a common design > (at a high level) then volunteer for components. > > that everyone who is interested join together in an IRC session in 12 > hours at: > http://timeanddate.com/worldclock/meetingdetails.html?year=2006&month=10&day=30&hour=19&min=0&sec=0&p1=240&p2=16&p3=179&p4=137 > > Sydney Tue 6:00:00 AM UTC+11 hours EST > Amsterdam Mon 8:00:00 PM UTC+1 hour CET > New York Mon 2:00:00 PM UTC-5 hours EST > Los Angeles Mon 11:00:00 AM UTC-8 hours PST > Corresponding UTC (GMT) Monday, 30 October 2006 at 19:00:00 > > Channel: > irc://freenode.net#openlayers > > Agenda: > 00 - 05: Roll Call. Confirm agenda. > 05 - 10: Who is working on what, and what you plan to work on + questions. > 10 - 50: Design discussion. > 50 - 55: Coordinate efforts (who is working on what) > 55 - 60: Arange next meeting. > 60 --: Meeting close > > People who have shown an interest so far: > ========================================= > I'm writing vector rendering code for large GML datasets, currently > using Mapbuilder but I'd like to move the logic into OpenLayers and use > OpenLayers for the Mapbuilder rendering engine. > With Paul Spencer, I've started putting together a design at: > http://wiki.osgeo.org/index.php/AJAX_WebMapping_Vector_Rendering_Design#Graphics_Class_Diagram > > > Paul Spencer has written vector rendering code for OpenLayers using > IECanvas and has been discussing a new Vector rendering design with me. > > Pierre Giraud and Bertil Chapuis have implemented vector rendering in > OpenLayers, including feature entry and editing at: > http://dev.camptocamp.com/~bchapuis/openlayers/examples/vector.html > > Steven Ottens needs to edit features in a browser and I think he has > plans for working on this soon. > > Ed Dowding has put together design ideas at: > http://trac.openlayers.org/wiki/VectorDrawing > > Patrice Cappelaere has written SVG and VML support for GeoRSS and GML > layers in Mapbuilder using elements of SLD for styling. > > Others on the CC list have contributed to discussions. Please add your > name and come along if you are interested. > From bartvde at osgis.nl Tue Oct 31 02:10:21 2006 From: bartvde at osgis.nl (Bart van den Eijnden (OSGIS)) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] AJAX vector rendering "gathering" Message-ID: <117e688acbe8839b27dd8c94f43a7125@145.50.39.8> Hi Steve, I can post a small summary. There was a discussion about using the DOJO Vector library, but generally OpenLayers is against introducing new dependencies (where they have just been removing others like Prototype). So it did not seem like the most appropriate option. Paul Spencer has been writing some code in OpenLayers for DMSG's MapGuide Fusion project, and this will be available roughly somewhere in the next month(s). It is based on Canvas and uses Google's IECanvas library. Paul and Christopher Schmidt claim this can do all they want to do for editing, even things like snapping should be possible. Cameron had some reservations when it comes to finding features on a map (performance e.g.), and attaching events to features. The server-side part of the Fusion project will likely not be open-sourced, but the vector part for OpenLayers will be. There will be a need for a redesign of the stuff after Cameron and Paul finish their general design. Cameron is working on SVG rendering in Mapbuilder for his OWS-4 project, and plans to integrate this into OpenLayers in the near future (maybe even next couple of weeks). The two options (Canvas and SVG) are probably complimentary. Please correct me if I noted something incorrectly :-) The IRC session was logged, but I don't have the URL unfortunately. Best regards, Bart -- Bart van den Eijnden OSGIS, Open Source GIS http://www.osgis.nl --------- Oorspronkelijk bericht -------- Van: webmap-discuss@mail.osgeo.org Naar: webmap-discuss@mail.osgeo.org Onderwerp: Re: [webmap-discuss] AJAX vector rendering "gathering" Datum: 31/10/06 00:27 > Cameron, > > I really wanted to attend, but had other commitments. Will someone post > a summary of the discussion and any decisions/outcomes/etc. > > Thanks, > -Steve > > Cameron Shorter wrote: > > There are a number of early implementations of AJAX GIS vector rendering > > that we are all involved in - and there seems to be a common desire to > > work together on this. > > > > I suggest we have an IRC meeting where we can agree on a common design > > (at a high level) then volunteer for components. > > > > that everyone who is interested join together in an IRC session in 12 > > hours at: > > http://timeanddate.com/worldclock/meetingdetails.html?year=2006&month=10&day=30&hour=19&min=0&sec=0&p1=240&p2=16&p3=179&p4=137 > > > > Sydney Tue 6:00:00 AM UTC+11 hours EST > > Amsterdam Mon 8:00:00 PM UTC+1 hour CET > > New York Mon 2:00:00 PM UTC-5 hours EST > > Los Angeles Mon 11:00:00 AM UTC-8 hours PST > > Corresponding UTC (GMT) Monday, 30 October 2006 at 19:00:00 > > > > Channel: > > irc://freenode.net#openlayers > > > > Agenda: > > 00 - 05: Roll Call. Confirm agenda. > > 05 - 10: Who is working on what, and what you plan to work on + questions. > > 10 - 50: Design discussion. > > 50 - 55: Coordinate efforts (who is working on what) > > 55 - 60: Arange next meeting. > > 60 --: Meeting close > > > > People who have shown an interest so far: > > ========================================= > > I'm writing vector rendering code for large GML datasets, currently > > using Mapbuilder but I'd like to move the logic into OpenLayers and use > > OpenLayers for the Mapbuilder rendering engine. > > With Paul Spencer, I've started putting together a design at: > > http://wiki.osgeo.org/index.php/AJAX_WebMapping_Vector_Rendering_Design#Graphics_Class_Diagram > > > > > > Paul Spencer has written vector rendering code for OpenLayers using > > IECanvas and has been discussing a new Vector rendering design with me. > > > > Pierre Giraud and Bertil Chapuis have implemented vector rendering in > > OpenLayers, including feature entry and editing at: > > http://dev.camptocamp.com/~bchapuis/openlayers/examples/vector.html > > > > Steven Ottens needs to edit features in a browser and I think he has > > plans for working on this soon. > > > > Ed Dowding has put together design ideas at: > > http://trac.openlayers.org/wiki/VectorDrawing > > > > Patrice Cappelaere has written SVG and VML support for GeoRSS and GML > > layers in Mapbuilder using elements of SLD for styling. > > > > Others on the CC list have contributed to discussions. Please add your > > name and come along if you are interested. > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > > > From cameron.shorter at gmail.com Tue Oct 31 04:18:27 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] AJAX vector rendering "gathering" In-Reply-To: <117e688acbe8839b27dd8c94f43a7125@145.50.39.8> References: <117e688acbe8839b27dd8c94f43a7125@145.50.39.8> Message-ID: <454714E3.2030708@gmail.com> Thanks Bart: Logs at: http://crschmidt.net/irc/openlayers/log.cgi/2006-10-30 Anselm Hook dropped in afterwards and plans to help out with the coding too. Bart van den Eijnden (OSGIS) wrote: > Hi Steve, > > I can post a small summary. > > There was a discussion about using the DOJO Vector library, but generally > OpenLayers is against introducing new dependencies (where they have just > been removing others like Prototype). So it did not seem like the most > appropriate option. > > Paul Spencer has been writing some code in OpenLayers for DMSG's MapGuide > Fusion project, and this will be available roughly somewhere in the next > month(s). It is based on Canvas and uses Google's IECanvas library. Paul and > Christopher Schmidt claim this can do all they want to do for editing, even > things like snapping should be possible. Cameron had some reservations when > it comes to finding features on a map (performance e.g.), and attaching > events to features. The server-side part of the Fusion project will likely > not be open-sourced, but the vector part for OpenLayers will be. There will > be a need for a redesign of the stuff after Cameron and Paul finish their > general design. > > Cameron is working on SVG rendering in Mapbuilder for his OWS-4 project, and > plans to integrate this into OpenLayers in the near future (maybe even next > couple of weeks). The two options (Canvas and SVG) are probably > complimentary. > > Please correct me if I noted something incorrectly :-) > > The IRC session was logged, but I don't have the URL unfortunately. > > Best regards, > Bart > > -- > Bart van den Eijnden > OSGIS, Open Source GIS > http://www.osgis.nl > > > --------- Oorspronkelijk bericht -------- > Van: webmap-discuss@mail.osgeo.org > Naar: webmap-discuss@mail.osgeo.org > Onderwerp: Re: [webmap-discuss] AJAX vector rendering "gathering" > Datum: 31/10/06 00:27 > > >>Cameron, >> >>I really wanted to attend, but had other commitments. Will someone post >>a summary of the discussion and any decisions/outcomes/etc. >> >>Thanks, >> -Steve >> >>Cameron Shorter wrote: >>> There are a number of early implementations of AJAX GIS vector > > rendering > >>> that we are all involved in - and there seems to be a common desire > > to > >>> work together on this. >>> >>> I suggest we have an IRC meeting where we can agree on a common > > design > >>> (at a high level) then volunteer for components. >>> >>> that everyone who is interested join together in an IRC session in 12 > > >>> hours at: >>> > > http://timeanddate.com/worldclock/meetingdetails.html?year=2006&month=10&day=30&hour=19&min=0&sec=0&p1=240&p2=16&p3=179&p4=137 > > >>> >>> Sydney Tue 6:00:00 AM UTC+11 hours EST >>> Amsterdam Mon 8:00:00 PM UTC+1 hour CET >>> New York Mon 2:00:00 PM UTC-5 hours EST >>> Los Angeles Mon 11:00:00 AM UTC-8 hours PST >>> Corresponding UTC (GMT) Monday, 30 October 2006 at 19:00:00 >>> >>> Channel: >>> irc://freenode.net#openlayers >>> >>> Agenda: >>> 00 - 05: Roll Call. Confirm agenda. >>> 05 - 10: Who is working on what, and what you plan to work on + > > questions. > >>> 10 - 50: Design discussion. >>> 50 - 55: Coordinate efforts (who is working on what) >>> 55 - 60: Arange next meeting. >>> 60 --: Meeting close >>> >>> People who have shown an interest so far: >>> ========================================= >>> I'm writing vector rendering code for large GML datasets, currently >>> using Mapbuilder but I'd like to move the logic into OpenLayers and > > use > >>> OpenLayers for the Mapbuilder rendering engine. >>> With Paul Spencer, I've started putting together a design at: >>> > > http://wiki.osgeo.org/index.php/AJAX_WebMapping_Vector_Rendering_Design#Graphics_Class_Diagram > > >>> >>> >>> Paul Spencer has written vector rendering code for OpenLayers using >>> IECanvas and has been discussing a new Vector rendering design with > > me. > >>> >>> Pierre Giraud and Bertil Chapuis have implemented vector rendering in > > >>> OpenLayers, including feature entry and editing at: >>> http://dev.camptocamp.com/~bchapuis/openlayers/examples/vector.html >>> >>> Steven Ottens needs to edit features in a browser and I think he has >>> plans for working on this soon. >>> >>> Ed Dowding has put together design ideas at: >>> http://trac.openlayers.org/wiki/VectorDrawing >>> >>> Patrice Cappelaere has written SVG and VML support for GeoRSS and GML > > >>> layers in Mapbuilder using elements of SLD for styling. >>> >>> Others on the CC list have contributed to discussions. Please add > > your > >>> name and come along if you are interested. >>> >> >> >>--------------------------------------------------------------------- >>To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org >>For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org >> >> >> > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > > -- Cameron Shorter http://cameron.shorter.net From Tom.Kralidis at ec.gc.ca Tue Oct 31 14:59:08 2006 From: Tom.Kralidis at ec.gc.ca (Kralidis,Tom [Burlington]) Date: Fri Dec 22 15:49:42 2006 Subject: [Context.RWG] Using OWS Context to describe GML/WFS layers whichdecimate Message-ID: <2576812186CDD411BF1500508B6DCE9510413F40@ecnwri1.ontario.int.ec.gc.ca> Cameron, So you want one OWSContext FeatureType to hold many GML documents? If yes, can you not define each GML doc as an OWSContext FeatureType, each with respective scale rules? > -----Original Message----- > From: Cameron Shorter [mailto:cameron.shorter@gmail.com] > Sent: 30 October, 2006 7:29 PM > To: Martin Daly > Cc: context.rwg@opengeospatial.org; Kralidis,Tom > [Burlington]; webmap-discuss@mail.osgeo.org; Raj Singh > Subject: Re: [Context.RWG] Using OWS Context to describe > GML/WFS layers whichdecimate > > Martin, > Point taken regarding G/Y/M maps. Replace zoomLevel with > sld:Min/MaxScaleDenominator in my previous comment. > > I still need to reference different GML sources for each > layer depending on scale, which doesn't seem to be covered by > OWS Context yet. > > > Martin Daly wrote: > >>zoomLevel is a term used by Google/Yahoo/MSN Maps. > >>It is a measure of resolution. As you zoom out, the zoomLevel > >>increases. > > > > > > That is not a definition that will wash in a standard that aims for > > interoperability. > > > > In fact, OWS Context already uses sld:Min/MaxScaleDenominator in the > > AbstractResourceType, so the capability already exists. > > > > As with the previous long e-mail trail re. GYM data, this > spec. should > > leverage de jure OGC standards, not de facto ones that > large parts of > > the target audience cannot use. > > > > M > > > > > > > -- > Cameron Shorter > http://cameron.shorter.net > From cameron.shorter at gmail.com Tue Oct 31 17:28:57 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: vector editing summary In-Reply-To: <2686af10610311244q7057d47by792a8c05301c449c@mail.gmail.com> References: <0128DD30-46B4-4B6A-98A2-4545330D2722@dmsolutions.ca> <454737A8.8070307@gmail.com> <2686af10610311244q7057d47by792a8c05301c449c@mail.gmail.com> Message-ID: <4547CE29.8020904@gmail.com> Yes Anselm, I suggest working in Paul's directory. (I assume that is OK with Paul?) And use the design from the UML diagrams as the master. At the moment, focus on the Graphics code. I'm struggling with how to handle Geometry at different scales. How do you describe a feature using a different FeatureCollection for each zoom level. I've raise the issue on the OWS Context email list and it seems that this problem has not been resolved properly in Context, WFS, and possibly even GML specs. Anselm Hook wrote: > I'd like to be able to play with some code a bit - should i use the > stuff here: > > http://svn.openlayers.org/sandbox/pagameba/vector/lib/OpenLayers/Vector.js > > Or should I use pauls stuff which may be elsewhere? > > I wouldn't mind roughing out some of camerons framework and then > playing with some canvas based implementations of the abstractions for > fun... > > - a > > On 10/31/06, Cameron Shorter wrote: > >> Paul, Anselm, >> I haven't updated as much of the design as I hoped. Other priorities got >> in the way. >> >> I've primarilly only updated the Graphics code. >> I've changed the names slightly to align with GO-1 naming convensions. >> (A Java standard API) >> >> I've re-introduced a Factory. >> >> The key API will be the Canvas object. >> >> I'll be back onto this tomorrow. (your afternoon) >> >> Paul Spencer wrote: >> > Cameron, here is my non-uml version of where I think we could go with >> > the design/architecture. I think this allows for a lot of flexibility >> > but is reasonably easy to understand. >> > >> > Lemme know what you think ... >> > >> > Cheers >> > >> > Paul >> > >> > -- >> > >> > Graphics >> > Graphics.Point >> > Graphics.Line >> > Graphics.LineSegment >> > Graphics.Polygon >> > Graphics.Circle >> > >> > Graphics represents graphic primitives. Graphic primitives deal >> > directly in pixel coordinates and know nothing about the spatial >> > objects they represent. >> > >> > Vector >> > Vector.Point >> > Vector.Line >> > Vector.Polygon >> > >> > Vector encapsulates a geo-spatial feature. Vector objects can create >> > Graphics primitives to use for rendering. A Vector object can also be >> > initialized from a Graphics object to aid in digitizing new features >> > and editing existing features. >> > >> > Style >> > Style.PointSymbolizer >> > Style.LineSymbolizer >> > Style.AreaSymbolizer >> > >> > Style is a general description of how to render a specific type of >> > Vector feature. Styles can be associated with a Layer or with >> > individual Vector objects. Style is used by the Renderer to create a >> > visual representation of a Vector >> > >> > Renderer >> > Renderer.Graphic >> > Renderer.Graphic.Canvas >> > Renderer.Graphic.SVG >> > Renderer.Graphic.VML >> > Renderer.WKT >> > Renderer.GML >> > >> > Renderer is a generic virtual vector rendering interface. Only >> > specific subclasses of Renderer can be instantiated. A vector layer >> > uses the renderer to render its Vector objects into some output. The >> > main use is to render a graphic representation of a Vector feature. >> > However, Renderers can also produce string representations such as WKT >> > and GML. >> > >> > Layer >> > Layer.Vector >> > Layer.Vector.GeoRSS >> > Layer.Vector.WFS >> > >> > A Layer.Vector is a generic vector rendering layer. It manages an >> > array of Vector objects. Sub-classes of Layer.Vector provide direct >> > access to vector data via a specific protocol like GeoRSS or WFS. >> > >> > >> > +-----------------------------------------------------------------+ >> > |Paul Spencer pspencer@dmsolutions.ca | >> > +-----------------------------------------------------------------+ >> > |Chief Technology Officer | >> > |DM Solutions Group Inc http://www.dmsolutions.ca/ | >> > +-----------------------------------------------------------------+ >> > >> > >> > >> > >> > >> >> >> -- >> Cameron Shorter >> http://cameron.shorter.net >> > -- Cameron Shorter http://cameron.shorter.net From cameron.shorter at gmail.com Tue Oct 31 19:17:11 2006 From: cameron.shorter at gmail.com (Cameron Shorter) Date: Fri Dec 22 15:49:42 2006 Subject: [Context.RWG] Using OWS Context to describe GML/WFS layers whichdecimate In-Reply-To: <2576812186CDD411BF1500508B6DCE9510413F40@ecnwri1.ontario.int.ec.gc.ca> References: <2576812186CDD411BF1500508B6DCE9510413F40@ecnwri1.ontario.int.ec.gc.ca> Message-ID: <4547E787.2030404@gmail.com> Kralidis,Tom [Burlington] wrote: > Cameron, > > So you want one OWSContext FeatureType to hold many GML documents? > > If yes, can you not define each GML doc as an OWSContext FeatureType, > each with respective scale rules? Tom, Using Style scale rules to make a layer visible or not would be one solution - but with a number of limitations: 1. If I were to build a LayerList (or Legend) from the Context, would I end up with a layer for each scale? 2. If my legend was smart, and layers were only visible at certain resolutions, how do I associate a HighResolutionLayer with a LowResolutionLayer so that the Layer attributes (like visibility) can be associated between layers. > > > >>-----Original Message----- >>From: Cameron Shorter [mailto:cameron.shorter@gmail.com] >>Sent: 30 October, 2006 7:29 PM >>To: Martin Daly >>Cc: context.rwg@opengeospatial.org; Kralidis,Tom >>[Burlington]; webmap-discuss@mail.osgeo.org; Raj Singh >>Subject: Re: [Context.RWG] Using OWS Context to describe >>GML/WFS layers whichdecimate >> >>Martin, >>Point taken regarding G/Y/M maps. Replace zoomLevel with >>sld:Min/MaxScaleDenominator in my previous comment. >> >>I still need to reference different GML sources for each >>layer depending on scale, which doesn't seem to be covered by >>OWS Context yet. >> >> >>Martin Daly wrote: >> >>>>zoomLevel is a term used by Google/Yahoo/MSN Maps. >>>>It is a measure of resolution. As you zoom out, the zoomLevel >>>>increases. >>> >>> >>>That is not a definition that will wash in a standard that aims for >>>interoperability. >>> >>>In fact, OWS Context already uses sld:Min/MaxScaleDenominator in the >>>AbstractResourceType, so the capability already exists. >>> >>>As with the previous long e-mail trail re. GYM data, this >> >>spec. should >> >>>leverage de jure OGC standards, not de facto ones that >> >>large parts of >> >>>the target audience cannot use. >>> >>>M >>> >>> >> >> >>-- >>Cameron Shorter >>http://cameron.shorter.net >> > > -- Cameron Shorter http://cameron.shorter.net From pspencer at dmsolutions.ca Tue Oct 31 21:17:31 2006 From: pspencer at dmsolutions.ca (Paul Spencer) Date: Fri Dec 22 15:49:42 2006 Subject: [webmap-discuss] Re: vector editing summary In-Reply-To: <4547CE29.8020904@gmail.com> References: <0128DD30-46B4-4B6A-98A2-4545330D2722@dmsolutions.ca> <454737A8.8070307@gmail.com> <2686af10610311244q7057d47by792a8c05301c449c@mail.gmail.com> <4547CE29.8020904@gmail.com> Message-ID: <33B39F1E-BA81-4673-B6BA-2D9EB725687C@dmsolutions.ca> http://svn.openlayers.org/sandbox/pagameba/vector is the current (not working) version that I am using to move code around in. I created a copy of the more-or-less working version in http:// svn.openlayers.org/sandbox/pagameba/vector-original The newer version is starting to look like the list below but a bunch of stuff is still not moved around and its not in a runnable state right now. Also, I did add the primative methods to the point and line segment code for basic picking functions, which are the building blocks for editing controls. Once the code is running again, I'll chat with Chris Schmidt about creating controls for digitizing and editing. Anselm ... not sure where you want to dig in, perhaps just dig around and look at the code ... I'll be working on it again tomorrow night for an hour or two I think, perhaps we could discuss how to split up the work if you see an area you want to work on. Cheers Paul On 31-Oct-06, at 5:28 PM, Cameron Shorter wrote: > Yes Anselm, I suggest working in Paul's directory. (I assume that > is OK with Paul?) > > And use the design from the UML diagrams as the master. > At the moment, focus on the Graphics code. > > I'm struggling with how to handle Geometry at different scales. > How do you describe a feature using a different FeatureCollection > for each zoom level. > > I've raise the issue on the OWS Context email list and it seems > that this problem has not been resolved properly in Context, WFS, > and possibly even GML specs. > > Anselm Hook wrote: >> I'd like to be able to play with some code a bit - should i use >> the stuff here: >> http://svn.openlayers.org/sandbox/pagameba/vector/lib/OpenLayers/ >> Vector.js >> Or should I use pauls stuff which may be elsewhere? >> I wouldn't mind roughing out some of camerons framework and then >> playing with some canvas based implementations of the abstractions >> for >> fun... >> - a >> On 10/31/06, Cameron Shorter wrote: >>> Paul, Anselm, >>> I haven't updated as much of the design as I hoped. Other >>> priorities got >>> in the way. >>> >>> I've primarilly only updated the Graphics code. >>> I've changed the names slightly to align with GO-1 naming >>> convensions. >>> (A Java standard API) >>> >>> I've re-introduced a Factory. >>> >>> The key API will be the Canvas object. >>> >>> I'll be back onto this tomorrow. (your afternoon) >>> >>> Paul Spencer wrote: >>> > Cameron, here is my non-uml version of where I think we could >>> go with >>> > the design/architecture. I think this allows for a lot of >>> flexibility >>> > but is reasonably easy to understand. >>> > >>> > Lemme know what you think ... >>> > >>> > Cheers >>> > >>> > Paul >>> > >>> > -- >>> > >>> > Graphics >>> > Graphics.Point >>> > Graphics.Line >>> > Graphics.LineSegment >>> > Graphics.Polygon >>> > Graphics.Circle >>> > >>> > Graphics represents graphic primitives. Graphic primitives deal >>> > directly in pixel coordinates and know nothing about the spatial >>> > objects they represent. >>> > >>> > Vector >>> > Vector.Point >>> > Vector.Line >>> > Vector.Polygon >>> > >>> > Vector encapsulates a geo-spatial feature. Vector objects can >>> create >>> > Graphics primitives to use for rendering. A Vector object can >>> also be >>> > initialized from a Graphics object to aid in digitizing new >>> features >>> > and editing existing features. >>> > >>> > Style >>> > Style.PointSymbolizer >>> > Style.LineSymbolizer >>> > Style.AreaSymbolizer >>> > >>> > Style is a general description of how to render a specific type of >>> > Vector feature. Styles can be associated with a Layer or with >>> > individual Vector objects. Style is used by the Renderer to >>> create a >>> > visual representation of a Vector >>> > >>> > Renderer >>> > Renderer.Graphic >>> > Renderer.Graphic.Canvas >>> > Renderer.Graphic.SVG >>> > Renderer.Graphic.VML >>> > Renderer.WKT >>> > Renderer.GML >>> > >>> > Renderer is a generic virtual vector rendering interface. Only >>> > specific subclasses of Renderer can be instantiated. A vector >>> layer >>> > uses the renderer to render its Vector objects into some >>> output. The >>> > main use is to render a graphic representation of a Vector >>> feature. >>> > However, Renderers can also produce string representations such >>> as WKT >>> > and GML. >>> > >>> > Layer >>> > Layer.Vector >>> > Layer.Vector.GeoRSS >>> > Layer.Vector.WFS >>> > >>> > A Layer.Vector is a generic vector rendering layer. It manages an >>> > array of Vector objects. Sub-classes of Layer.Vector provide >>> direct >>> > access to vector data via a specific protocol like GeoRSS or WFS. >>> > >>> > >>> > >>> +-----------------------------------------------------------------+ >>> > |Paul Spencer >>> pspencer@dmsolutions.ca | >>> > >>> +-----------------------------------------------------------------+ >>> > |Chief Technology >>> Officer | >>> > |DM Solutions Group Inc http:// >>> www.dmsolutions.ca/ | >>> > >>> +-----------------------------------------------------------------+ >>> > >>> > >>> > >>> > >>> > >>> >>> >>> -- >>> Cameron Shorter >>> http://cameron.shorter.net >>> > > > -- > Cameron Shorter > http://cameron.shorter.net > > --------------------------------------------------------------------- > To unsubscribe, e-mail: webmap-discuss-unsubscribe@mail.osgeo.org > For additional commands, e-mail: webmap-discuss-help@mail.osgeo.org > +-----------------------------------------------------------------+ |Paul Spencer pspencer@dmsolutions.ca | +-----------------------------------------------------------------+ |Chief Technology Officer | |DM Solutions Group Inc http://www.dmsolutions.ca/ | +-----------------------------------------------------------------+ From Tom.Kralidis at ec.gc.ca Tue Oct 31 21:50:20 2006 From: Tom.Kralidis at ec.gc.ca (Kralidis,Tom [Burlington]) Date: Fri Dec 22 15:49:43 2006 Subject: [Context.RWG] Using OWS Context to describe GML/WFS layers whichdecimate Message-ID: <2576812186CDD411BF1500508B6DCE950D17F88E@ecnwri1.ontario.int.ec.gc.ca> > -----Original Message----- > From: Cameron Shorter [mailto:cameron.shorter@gmail.com] > Sent: 31 October, 2006 7:17 PM > To: Kralidis,Tom [Burlington] > Cc: Martin Daly; context.rwg@opengeospatial.org; > webmap-discuss@mail.osgeo.org; Raj Singh > Subject: Re: [Context.RWG] Using OWS Context to describe > GML/WFS layers whichdecimate > > Kralidis,Tom [Burlington] wrote: > > Cameron, > > > > So you want one OWSContext FeatureType to hold many GML documents? > > > > If yes, can you not define each GML doc as an OWSContext > FeatureType, > > each with respective scale rules? > > Tom, > Using Style scale rules to make a layer visible or not would > be one solution - but with a number of limitations: > 1. If I were to build a LayerList (or Legend) from the > Context, would I end up with a layer for each scale? > Yes, however you could build your client Legend handler to show layers only if they're within the scale range of where the application scale is at. > 2. If my legend was smart, and layers were only visible at > certain resolutions, how do I associate a HighResolutionLayer > with a LowResolutionLayer so that the Layer attributes (like > visibility) can be associated between layers. > If OWSContext identified the notion of a @group attribute as part of the AbstractResourceType, this might be an option. There has been some mild discussion on this front. > > > > > > > > >>-----Original Message----- > >>From: Cameron Shorter [mailto:cameron.shorter@gmail.com] > >>Sent: 30 October, 2006 7:29 PM > >>To: Martin Daly > >>Cc: context.rwg@opengeospatial.org; Kralidis,Tom [Burlington]; > >>webmap-discuss@mail.osgeo.org; Raj Singh > >>Subject: Re: [Context.RWG] Using OWS Context to describe GML/WFS > >>layers whichdecimate > >> > >>Martin, > >>Point taken regarding G/Y/M maps. Replace zoomLevel with > >>sld:Min/MaxScaleDenominator in my previous comment. > >> > >>I still need to reference different GML sources for each layer > >>depending on scale, which doesn't seem to be covered by OWS Context > >>yet. > >> > >> > >>Martin Daly wrote: > >> > >>>>zoomLevel is a term used by Google/Yahoo/MSN Maps. > >>>>It is a measure of resolution. As you zoom out, the zoomLevel > >>>>increases. > >>> > >>> > >>>That is not a definition that will wash in a standard that > aims for > >>>interoperability. > >>> > >>>In fact, OWS Context already uses > sld:Min/MaxScaleDenominator in the > >>>AbstractResourceType, so the capability already exists. > >>> > >>>As with the previous long e-mail trail re. GYM data, this > >> > >>spec. should > >> > >>>leverage de jure OGC standards, not de facto ones that > >> > >>large parts of > >> > >>>the target audience cannot use. > >>> > >>>M > >>> > >>> > >> > >> > >>-- > >>Cameron Shorter > >>http://cameron.shorter.net > >> > > > > > > > -- > Cameron Shorter > http://cameron.shorter.net >