[OpenLayers-Dev] Dev Digest, Vol 43, Issue 8

Thu Apr 8 10:34:46 EDT 2010

I have a question regarding the 2.9_r10183 trunk rel. When implementing
this ver. the layerSwitcher appears in the upper left-corner as opposed
to the upper-right (v2.8). It is positioned beneath the Navigation
Control. When the LayerControl is expanded the panel appears opaque and
the close handle is attached to the bottom outside corner. Because of
the opaqueness the handle can not been seen. I have not found a way to
alter this behavior in the css.  
I'd appreciate any assistance. I am new to OpenLayers and hope this is
the appropriate forum to submit a question. If not please advise. Thnx.
-----Original Message-----
From: dev-bounces at openlayers.org [mailto:dev-bounces at openlayers.org] On
Behalf Of dev-request at openlayers.org
Sent: Thursday, April 08, 2010 3:04 AM
To: dev at openlayers.org
Subject: Dev Digest, Vol 43, Issue 8

Send Dev mailing list submissions to
	dev at openlayers.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://openlayers.org/mailman/listinfo/dev
or, via email, send a message with subject or body 'help' to
	dev-request at openlayers.org

You can reach the person managing the list at
	dev-owner at openlayers.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dev digest..."

Today's Topics:

   1. Re: Graticule control can't be deactivated (Xavier Mamano (jorix))
   2. Need ideas for VML feature text label rendering	speed
      improvement (Cliang)
   3. Re: Need ideas for VML feature text label rendering speed
      improvement (Cliang)
   4. Re: Get direction from route to route... draw route on	map
      (Like GPS) (Stephen Woodbridge)
   5. Re: Chrome issue with WMS (C?dric Moullet)
   6. VML optimization- node.style.cssText in IE	possible?
      (ashley_c_mort)
   7. Raster map shift - still no clues (Stefanie Weykam)
   8. call for vote on 2.9 RC2 (bartvde at osgis.nl)

----------------------------------------------------------------------

Message: 1
Date: Wed, 7 Apr 2010 09:44:48 -0800 (PST)
From: "Xavier Mamano (jorix)" <xavier.mamano at gmail.com>
Subject: Re: [OpenLayers-Dev] Graticule control can't be deactivated
To: dev at openlayers.org
Message-ID: <1270662288438-4866434.post at n2.nabble.com>
Content-Type: text/plain; charset=us-ascii

I think that usability is important, for this I open the ticket
http://trac.openlayers.org/ticket/2567 to add  the activation and
deactivation in Graticule control.
-- 
View this message in context:
http://n2.nabble.com/Graticule-control-can-t-be-deactivated-tp4836670p48
66434.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.

------------------------------

Message: 2
Date: Wed, 7 Apr 2010 11:01:11 -0800 (PST)
From: Cliang <thephatness.nabble at mailnull.com>
Subject: [OpenLayers-Dev] Need ideas for VML feature text label
	rendering	speed improvement
To: dev at openlayers.org
Message-ID: <1270666871800-4866820.post at n2.nabble.com>
Content-Type: text/plain; charset=us-ascii

Hi Devs,

First of all, great work! It has been a pleasure to use the framework.

My app contains a vector based drilldown style map. United States
(labels: 2
char state abbreviation) -> State (labels: 2 char county abbreviation)
->
County (labels: 5 digit Zip code). The target browser is IE 7/8. While
it
renders fine on non-IE browsers, IE itself spends a significant amount
of
time drawing text according to the built-in profiling tool. I've tweaked
the
geometries to have max 2000 vertices but some levels contain over 200
features (extreme cases: 254 Texas counties, 282 Los Angeles zip codes).

I was thinking of preventing the label from being drawn if it does not
fit
within the width of the geometry at the centroid for the current zoom.
It
seems like some time is spent rendering the VML textbox offline to
determine
the size. I would be fine with estimating the width from the number of
characters since the label text characters are relatively equal width.
VML
rendering is beyond what my brain can wrap around so any suggestions of
how
I can tweak VML.js to do this?

Thanks!
-=Cliff
-- 
View this message in context:
http://n2.nabble.com/Need-ideas-for-VML-feature-text-label-rendering-spe
ed-improvement-tp4866820p4866820.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.

------------------------------

Message: 3
Date: Wed, 7 Apr 2010 13:17:19 -0800 (PST)
From: Cliang <thephatness.nabble at mailnull.com>
Subject: Re: [OpenLayers-Dev] Need ideas for VML feature text label
	rendering speed improvement
To: dev at openlayers.org
Message-ID: <1270675039724-4867617.post at n2.nabble.com>
Content-Type: text/plain; charset=us-ascii

Digging deeper, as ugly as this is, it will work for me for now:

In OpenLayers.Renderer.drawFeature()

if ((bounds.getSize().w / this.getResolution()) > (style.label.length *
7))
{
    this.drawText(feature.id, style, location);
} else {
    this.removeText(feature.id);
}

-- 
View this message in context:
http://n2.nabble.com/Need-ideas-for-VML-feature-text-label-rendering-spe
ed-improvement-tp4866820p4867617.html
Sent from the OpenLayers Dev mailing list archive at Nabble.com.

------------------------------

Message: 4
Date: Wed, 07 Apr 2010 22:46:45 -0400
From: Stephen Woodbridge <woodbri at swoodbridge.com>
Subject: Re: [OpenLayers-Dev] Get direction from route to route...
	draw route on	map (Like GPS)
To: Alexandre Dube <adube at mapgears.com>
Cc: dev at openlayers.org
Message-ID: <4BBD4395.1070909 at swoodbridge.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

Alexandre Dube wrote:
> Hi,
> 
> CampToCamp worked on such a widget in GeoExt.ux. Currently in a
sandbox :
>
http://dev.geoext.org/sandbox/cmoullet/ux/RoutingPanel/examples/RoutingP
anelExample.html
> 
> See also :
> http://pgrouting.postlbs.org/

See also :

http://opengraphrouter.sourceforge.net/
http://imaptools.com:8080/maps/gsoc2009/?zoom=7&lat=52.6515&lon=-122.375
22&layers=BTTT&start=-122.546657%2053.327732&stop=-122.108537%2052.23878
1&method=GetDD&lang=eng

Here is a similar demo using pgRouting, albeit one that I have modified 
to some extent:

http://gis.imaptools.com/routing/leaddog/?zoom=10&lat=33.85674&lon=35.53
073&layers=B0TTTF&start=35.493266%2033.82595&stop=35.623749%2033.813568&
method=STS&lang=eng

-Steve

> Regards,
> 
> Alexandre
> 
> yellow wrote:
>> Hi,
>>
>> I would like to know if it is possible to create an application using
open
>> layers that gives users the shortest road to a particular destination
by
>> drawing the route on the map. And if possible avoiding one-way roads.
>>
>> Can anyone please suggest any resources, ideas or show me a simple
example.
>>
>> Thanks in advance. 
>>   
> 
> 

------------------------------

Message: 5
Date: Thu, 8 Apr 2010 07:21:58 +0200
From: C?dric Moullet <cedric.moullet at camptocamp.com>
Subject: Re: [OpenLayers-Dev] Chrome issue with WMS
To: Pierre Giraud <pierre.giraud at camptocamp.com>
Cc: OpenLayers dev mailing list <dev at openlayers.org>
Message-ID:
	<m2j156196721004072221raf6d35d0m1ce673922b05867c at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

I have created a ticket: http://trac.openlayers.org/ticket/2568
<http://trac.openlayers.org/ticket/2568>Unfortunately, I was not able to
create a patch.
C?dric

2010/4/1 Pierre Giraud <pierre.giraud at camptocamp.com>

> Yep, this is an important information.
> I succeeded in reproducing the issue in Chrome 4.x on Linux too.
> The problem doesn't seem to appear in Chrome 5.x.
>
> In fact, it seems like the transition.html example in OpenLayers
doesn't
> behave as expected in Chrome 4.x.
>
> Pierre
>
>
> 2010/4/1 C?dric Moullet <cedric.moullet at camptocamp.com>
>
>> Hi,
>> It seems that this use case is not always reproducible.
>>
>> OS: Windows Vista
>> Chrome Version: 4.1.249.1045 (42898)
>>
>> Here is more detailes use case.
>> 1. http://www.openaddresses.org/
>>  <http://www.openaddresses.org/>2. Search Lausanne in geonames search
and
>> recenter to Lausanne
>> 3. With Shift key, draw a small zoom rectangle in the middle of the
red
>> points.
>> 4. You should see the big points now.
>>
>> At least by me, I can reproduce the issue.
>> Can you reproduce this case ? If yes, any idea of the cause ?
>> Thanks a lot,
>> C?dric
>>
>> 2010/4/1 C?dric Moullet <cedric.moullet at camptocamp.com>
>>
>>> Hi,
>>> In OpenAddresses, we have the following problem with chrome:
>>> 1. Try to open with chrome
>>>
http://www.openaddresses.org/?northing=5863427.1119846&easting=738362.58
397773&zoom=12&overlayOpacity=0.7
>>>
<http://www.openaddresses.org/?northing=5863427.1119846&easting=738362.5
8397773&zoom=12&overlayOpacity=0.7>2.
>>> Make a zoom in
>>>
>>> Result: we see large red points. It seems that the WMS layer is not
>>> refresh and keep the resized image.
>>> If needed the code of the layer creation is here:
>>>
http://code.google.com/p/openaddresses/source/browse/trunk/openaddresses
/openaddresses/public/app/js/OpenAddressesLayout.js#257
>>>
>>> This affects only chrome: do you have an idea of the cause of the
problem
>>> ?
>>> Thanks in advance,
>>> C?dric
>>>
>>> --
>>> Geospatial Director Camptocamp SA
>>> C?dric Moullet
>>> PSE A
>>> CH-1015 Lausanne
>>> www.camptocamp.com  / www.mapfish.org / twitter.com/cedricmoullet /
>>> mapfishblog.blogspot.com/
>>>
>>> +41 79 759 69 83 (mobile)
>>> +41 21 619 10 21 (direct)
>>> +41 21 619 10 10 (centrale)
>>> +41 21 619 10 00 (fax)
>>>
>>
>>
>>
>> --
>> Geospatial Director Camptocamp SA
>> C?dric Moullet
>> PSE A
>> CH-1015 Lausanne
>> www.camptocamp.com  / www.mapfish.org / twitter.com/cedricmoullet /
>> mapfishblog.blogspot.com/
>>
>> +41 79 759 69 83 (mobile)
>> +41 21 619 10 21 (direct)
>> +41 21 619 10 10 (centrale)
>> +41 21 619 10 00 (fax)
>>
>> _______________________________________________
>> Dev mailing list
>> Dev at openlayers.org
>> http://openlayers.org/mailman/listinfo/dev
>>
>>
>
>
> --
> Pierre GIRAUD
> G?omaticien, Analyste
>
> Camptocamp France SAS
> Savoie Technolac, BP 352
> 73377 Le Bourget du Lac, Cedex
>
> Tel : 00 33 4 79 44 44 93
> Mail : pierre.giraud at camptocamp.com
> http://www.camptocamp.com
>

-- 
Geospatial Director Camptocamp SA
C?dric Moullet
PSE A
CH-1015 Lausanne
www.camptocamp.com  / www.mapfish.org / twitter.com/cedricmoullet /
mapfishblog.blogspot.com/

+41 79 759 69 83 (mobile)
+41 21 619 10 21 (direct)
+41 21 619 10 10 (centrale)
+41 21 619 10 00 (fax)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://openlayers.org/pipermail/dev/attachments/20100408/a61f4a3a/attach
ment-0001.htm 

------------------------------

Message: 6
Date: Thu, 8 Apr 2010 01:49:03 -0400
From: "ashley_c_mort" <ashley_c_mort at raytheon.com>
Subject: [OpenLayers-Dev] VML optimization- node.style.cssText in IE
	possible?
To: <users at openlayers.org>, <dev at openlayers.org>
Message-ID: <05e801cad6df$320993e0$22099195 at us.ray.com>
Content-Type: text/plain; charset="us-ascii"

    We are trying to optimize the performance of our app that uses
OpenLayers (IE 7&8).  It appears that the node.style calls in the VML.js
are
taking a lot of time in certain cases and we were trying to use cssText
to
get it done in one call.  Has anyone tried using one node.style.cssText
call
instead of multiple node.style calls?  
    Using node.style.cssText works one time when the data is first drawn
but
future changes to the node's cssText don't seem to take effect (ex: data
will be created in the correct location but the data never moves [top,
left]
when the user zooms).
    Any ideas are greatly appreciated?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://openlayers.org/pipermail/dev/attachments/20100408/b3226933/attach
ment-0001.htm 

------------------------------

Message: 7
Date: Thu, 08 Apr 2010 08:17:51 +0200
From: Stefanie Weykam <stefanie at weykam.net>
Subject: [OpenLayers-Dev] Raster map shift - still no clues
To: dev at openlayers.org
Message-ID: <4BBD750F.8070103 at weykam.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi list members,
I posted a message on 26 of March reporting a strange displacement that 
only effects raster maps. I am pretty sure the WMS are alright, since 
another client displays the maps correctly. Due to the pixel size, the 
difference is big enough to become quite obvious.
The fact that GetFeaturteInfo always returns the right (expected) values

even if the pixel is not the one that should be visible at the 
particular point, made me suggest that this could be a display artefact.

- ??
For more details and test code see my message on 26.3.2010

I received no hints so far. Should I file a bug?

Regards,
Stefanie

------------------------------

Message: 8
Date: Thu, 8 Apr 2010 09:04:08 +0200 (CEST)
From: bartvde at osgis.nl
Subject: [OpenLayers-Dev] call for vote on 2.9 RC2
To: dev at openlayers.org
Message-ID:

<15886.145.50.39.11.1270710248.squirrel at webmail.hostingdiscounter.nl>
Content-Type: text/plain;charset=iso-8859-1

Hi list,

I would like to call for a vote on a second release candidate (RC2) for
OpenLayers 2.9.

4 tickets have been pulled up (2561, 2562, 2563 and 2564), I've verified
all tests still pass in IE6 and FF 3.6.2, so all is in good shape.

Best regards,
Bart

------------------------------

_______________________________________________
Dev mailing list
Dev at openlayers.org
http://openlayers.org/mailman/listinfo/dev

End of Dev Digest, Vol 43, Issue 8
**********************************