[OpenLayers-Dev] scale computation

2008-07-28 Thread bartvde
Hi list,

I am tracking down a difference in scale computation between OpenLayers
and Mapserver. I've given both the standard OGC resolution (dpi) of 90.71,
but still there is a difference. I.e. my MAP file says 25000, but in OL it
only becomes visible at 24998.

Could the difference be that Mapserver uses (width-1) is its scale
computation?

md = (width-1)/(resolution*msInchesPerUnit(units, center_y)); /*
remember, we use a pixel-center to pixel-center extent, hence the
width-1 */

Best regards,
Bart

___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


Re: [OpenLayers-Dev] SVG viewbox problem with minScale

2008-07-28 Thread Alexandre Dube
Hi Eric,

  I opened a ticket : #1631.

  Of what I understand, the bug comes from the resolution and inRange 
value of the layer.  While it's not inRange, our renderer doesn't change 
its left and top values, even if we zoom.  But, when inRange, it first 
checks the resolution.  If it changed, then new left-top values are 
created but in our case it didn't so the left-top values remain the 
sames and when each features is added, they are out of the 15000 pixel 
range and are not displayed.

  Best regards,

Alexandre


Eric Lemoine wrote:
 You indeed found a bug. Can you open a ticket and attach some code to
 help developpers reproduce it.

 Do you observe the same problem if you dont go beyond the 15000 px?
 I.e. go in range, pan w/o going beyond the limit, go out of range,
 pan, and go back in range. I'm trying to understand whether the
 problem comes from the code relating to the 15000px limit.

 Thanks. Eric

 2008/7/25, Alexandre Dube [EMAIL PROTECTED]:
   
 Hi everybody,

   I use Firefox ( big fan ).

   Of what I understand, each time I zoom in or out a map that has a
 vector layer, the left and top values of the rederer's viewbox are
 reseted to 0.

   I have a WFS layer with a minScale: 4 in my map.  So, the first
 time I get inRange of my layer, left and top are reset to 0.  If I pan,
 they change their value and if their value is 15000 pixels away from my
 original left-top, no feature will be drawn.

   The problem is if I zoom out of my minScale: 4, my layer becomes
 inactive.  Zooming out don't reset the left-top values.

   So, if I pan to somewhere else and then zoom in until I get inRange of
 my minScale, my WFS layer shows no features because it's as we didn't
 zoom at all ( the resolution is the same that the time we zoom out of
 range ) .  But, if I zoom in again once, then the features appear
 (because the resolution has changed, and left-top are reseted to 0).  If
 I zoom out once, the features are still there.

   I think the line 504 in SVG.js should be changed.  Instead of doing
 nothing if not inValidRange, it should check again by ignoring the
 resolution.  That would resolve the issue, I think...

 Any comments ?

 --
 Alexandre Dubé
 Mapgears
 www.mapgears.com

 ___
 Dev mailing list
 Dev@openlayers.org
 http://openlayers.org/mailman/listinfo/dev

 


-- 
Alexandre Dubé
Mapgears
www.mapgears.com

___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


[OpenLayers-Dev] Layer.Text popup getting bigger

2008-07-28 Thread Alexandre Dube
Hi,

I posted this message to the users list but got no reply.

I don't know if anybody noticed this yet : when you use a Layer.Text and 
you keep clicking on the same marker, the popup gets bigger and 
bigger.  Even the example it does that :

http://openlayers.org/dev/examples/markersTextLayer.html

Any comments ?  Is that a reported bug ?

-- 
Alexandre Dubé
Mapgears
www.mapgears.com

___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


Re: [OpenLayers-Dev] Layer.Text popup getting bigger

2008-07-28 Thread bartvde
See:

http://trac.openlayers.org/ticket/1586

Best regards,
Bart

 Hi,

 I posted this message to the users list but got no reply.

 I don't know if anybody noticed this yet : when you use a Layer.Text
 and you keep clicking on the same marker, the popup gets bigger and
 bigger.  Even the example it does that :

 http://openlayers.org/dev/examples/markersTextLayer.html

 Any comments ?  Is that a reported bug ?

 --
 Alexandre Dubé
 Mapgears
 www.mapgears.com

 ___
 Dev mailing list
 Dev@openlayers.org
 http://openlayers.org/mailman/listinfo/dev



___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


Re: [OpenLayers-Dev] SVG viewbox problem with minScale

2008-07-28 Thread Eric Lemoine
On Mon, Jul 28, 2008 at 3:35 PM, Alexandre Dube [EMAIL PROTECTED] wrote:
 Hi Eric,

  I opened a ticket : #1631.

  Of what I understand, the bug comes from the resolution and inRange value
 of the layer.  While it's not inRange, our renderer doesn't change its left
 and top values, even if we zoom.  But, when inRange, it first checks the
 resolution.  If it changed, then new left-top values are created but in our
 case it didn't so the left-top values remain the sames and when each
 features is added, they are out of the 15000 pixel range and are not
 displayed.

So it seems to me that the problem doesn't really related to the 15000
px limit. In this scenario:

- go out of range
- pan and zoom without going beyond the 15000 px limit
- go in range (the features should be visible as the limit was crossed)

is the location of features correct?

--
Eric
___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


[OpenLayers-Dev] ticket #1562

2008-07-28 Thread Eric Lemoine
Tim,

Could you take a look at http://trac.openlayers.org/ticket/1562?

It relates to one of your latest commits to vector-behavior. I think
it's better to call removeFeatures from destroyFeatures and let
removeFeatures trigger the featuresremoved event.

If you think my patch is ok, I'll commit it to trunk and revert yours
to vector-behavior.

Thanks,

--
Eric
___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


Re: [OpenLayers-Dev] Layer.Text popup getting bigger

2008-07-28 Thread Erik Uzureau
Yes, we are working on it.

On Mon, Jul 28, 2008 at 8:51 AM, [EMAIL PROTECTED] wrote:

 See:

 http://trac.openlayers.org/ticket/1586

 Best regards,
 Bart

  Hi,
 
  I posted this message to the users list but got no reply.
 
  I don't know if anybody noticed this yet : when you use a Layer.Text
  and you keep clicking on the same marker, the popup gets bigger and
  bigger.  Even the example it does that :
 
  http://openlayers.org/dev/examples/markersTextLayer.html
 
  Any comments ?  Is that a reported bug ?
 
  --
  Alexandre Dubé
  Mapgears
  www.mapgears.com
 
  ___
  Dev mailing list
  Dev@openlayers.org
  http://openlayers.org/mailman/listinfo/dev
 


 ___
 Dev mailing list
 Dev@openlayers.org
 http://openlayers.org/mailman/listinfo/dev

___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


Re: [OpenLayers-Dev] SVG viewbox problem with minScale

2008-07-28 Thread Alexandre Dube
Hi Eric,

  The location is correct.  It is ok to have a 15000px limit and that 
works perfectly. 

  To fix the bug, I think when the code checks the resolution, if it's 
the same than before, it should also check the location of one of our 
feature position...  If it's near our 15000px limit ( let's say more 
than 14000px for example ) it should change the left-top value of the 
renderer. 

  That way, even if we zoom out or pan, if we get out of our 15000px 
limit, features will continue to be displayed.

  What do you think ?

Alexandre

Eric Lemoine wrote:
 On Mon, Jul 28, 2008 at 3:35 PM, Alexandre Dube [EMAIL PROTECTED] wrote:
   

 So it seems to me that the problem doesn't really related to the 15000
 px limit. In this scenario:

 - go out of range
 - pan and zoom without going beyond the 15000 px limit
 - go in range (the features should be visible as the limit was crossed)

 is the location of features correct?

 --
 Eric
   


-- 
Alexandre Dubé
Mapgears
www.mapgears.com

___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


[OpenLayers-Dev] svn 1.5

2008-07-28 Thread Tim Schaub
Hey-

Wondering if others think a move to subversion 1.5 would be good.

A few features would be nice for OL development.  Particularly merge 
tracking.  From the release notes:


Merging changes from (say) trunk to a branch no longer requires that you 
specify the revision range. Instead, each time you want to sync up with 
trunk, you can just do:

$ cd BRANCH_WORKING_COPY
$ svn merge URL_TO_TRUNK

Subversion will figure out what changes from URL_TO_TRUNK have not yet 
been merged and pull in just those changes. When it's time to merge the 
branch back to trunk, do this:

$ cd TRUNK_WORKING_COPY
$ svn merge --reintegrate URL_TO_BRANCH


http://subversion.tigris.org/svn_1.5_releasenotes.html#merge-tracking

Pretty nice for sandbox users.  Not sure if there are constraints on 
doing this on the MC side.

Tim

PS - One (perhaps very minor) change that may affect some is that the 
repository basename is displayed in XML and HTML index views.  This 
breaks anything that previously relied on titles that were only revision 
numbers (zc.buildout recipes break).
___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev


Re: [OpenLayers-Dev] svn 1.5

2008-07-28 Thread Eric Lemoine
Hi Tim. So long that users need not upgrade their SVN clients, i see
no problem with having the repository going to 1.5. Talking about that
have people give SVK a try? SVK can check out code from SVN
repositories, and, IIRC, supports the same merge without out
indicating the previous merge revision feature. Eric

2008/7/29, Tim Schaub [EMAIL PROTECTED]:
 Hey-

 Wondering if others think a move to subversion 1.5 would be good.

 A few features would be nice for OL development.  Particularly merge
 tracking.  From the release notes:

 
 Merging changes from (say) trunk to a branch no longer requires that you
 specify the revision range. Instead, each time you want to sync up with
 trunk, you can just do:

 $ cd BRANCH_WORKING_COPY
 $ svn merge URL_TO_TRUNK

 Subversion will figure out what changes from URL_TO_TRUNK have not yet
 been merged and pull in just those changes. When it's time to merge the
 branch back to trunk, do this:

 $ cd TRUNK_WORKING_COPY
 $ svn merge --reintegrate URL_TO_BRANCH
 

 http://subversion.tigris.org/svn_1.5_releasenotes.html#merge-tracking

 Pretty nice for sandbox users.  Not sure if there are constraints on
 doing this on the MC side.

 Tim

 PS - One (perhaps very minor) change that may affect some is that the
 repository basename is displayed in XML and HTML index views.  This
 breaks anything that previously relied on titles that were only revision
 numbers (zc.buildout recipes break).
 ___
 Dev mailing list
 Dev@openlayers.org
 http://openlayers.org/mailman/listinfo/dev

___
Dev mailing list
Dev@openlayers.org
http://openlayers.org/mailman/listinfo/dev