[OpenLayers-Users] Experience using OpenLayers

[Jeff Yutzler]

responses inline...

Christopher Schmidt wrote:
> On Thu, May 17, 2007 at 06:39:56PM -0400, Jeff Yutzler wrote:
>   
>> ...tracking demonstration...
>>     
>
> Any possibility of a demo URL for this? Even if it's with faked data, it
> would be interesting to see how OpenLayers can be used 'for real' -- I'm
> much more a cartogrpaher than a 'GIS' person.
>
>   
The problem here is we don't currently have a convenient way leave all 
of the component pieces up and running perpetually.  However, if this 
changes, we will post it.  In the short term, it is more likely that we 
will generate a movie of the demonstration once I clean it up a little.  
Is that something you would want access to?
>> The biggest problem we have with OpenLayers is the way image updates
>> are handled.
> When you say 'update', I assume you mean 'mergeNewParams'. 
>
>   
Yes, 'mergeNewParams', in this case to update the TIME dimension of the 
WMS request.  I will open a ticket.
>> My next step in development is to support WFS-T.  We are reluctant to
>> try out 2.4RC3, but maybe it is time.  We are also interested in
>> multi-line, multi-polygon, and inner ring support.  We've implemented
>> this capability in other web clients so we know it can be done here.
>> I see this is on the road map for 2.5. Since we have full WFS-T
>> support via Red Spider Enterprise, this work should go quickly.
>>     
>
> 2.4RC3 is a relatively complete release. With the exception of a few
> minor bugs (georss serialization, for example), I expect very few
> differences between RC3 and RC4, and it seems possible that RC4 will be
> the final release. An OpenLayers release doesn't make it to RC stage
> without a significant amount of testing, both automated and
> non-automated, so the RCs are pretty low risk.
>   
OK, we'll take a look at 2.4RC3.
> Multi-line, multi-polygon, and inner ring support exists in the format
> parsers. The place where it doesn't exist yet is in the UI for feature
> creation, but if you have existing data, it can be displayed. This
> doesn't sound like it will solve all of your use cases, but it will at
> least allow you to visualize the content even if you can't do everything
> you want with it.
>
>   
We don't care about the format parsers because we handle all of that 
including rendering WFS layers as images through the Enterprise API.  
Well, that is not completely true, if the user selects a feature, we 
would want that rendered through OpenLayers.   For us though, the easy 
part is the actual WFS-T transaction and the hard part is the digitizing 
and editing.  Over the next few days, I will evaluate what OpenLayers 
does out of the box and figure out where to go from there.  I know Chris 
Holmes has some ideas so we might be able to collaborate.
>> The most annoying thing I had to do was provide something more capable
>> than the default Layer Switcher...Unfortunately, the YUI event model and the
>> Prototype-based event model are like oil and water.
>>     
>
> Hm, it's unfortunate to hear that there is a major problem here. I'd
> like to work to resolve what that problem is, though I'd also like to go
> on a 6 month sojourn through the Rocky Mountains, and given current time
> constaints in my daily life, it seems that both are equally likely :)
> Still, it seems that if there is a significant problem using OpenLayers
> with other event frameworks, we have a bug, and I'd like to see it
> fixed.
>
>   
Over the next week I will open a ticket and provide some sort of 
constrained use case.  This isn't a bug - it is working exactly as 
designed.  However, I was unable to come up with a design that would 
allow me to do what I wanted.  Maybe someone more clever from that 
standpoint can come up with the right technique.
>> Oh, and on the forum debate, I recommend not having a separate forum.
>> However, I do suggest you publicize the link to Nabble a little more.
>> I spent a lot of time blindly looking through the mail archives before
>> I spotted it.
>>     
>
> Any suggestions on where to put this? I know most things by URL, so an
> outsider point of view on this aspect of the project would be useful. 
>
>   
How about here:
http://openlayers.org/mailman/listinfo

If that is not possible, perhaps here under "Social":
http://trac.openlayers.org/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: jeff.yutzler.vcf
Type: text/x-vcard
Size: 331 bytes
Desc: not available
Url : http://lists.osgeo.org/pipermail/openlayers-users/attachments/20070518/84119690/jeff.yutzler.vcf