+1<br><br>Tamas<br><br><br><br><div class="gmail_quote">2011/3/24 Lime, Steve D (DNR) <span dir="ltr"><<a href="mailto:steve.lime@state.mn.us">steve.lime@state.mn.us</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I suppose we should talk on mapserver-dev. ;-) I'm happy to nominate you for documentation<br>
commit access. We like to try to match commits with tickets if non-trivial. There is a documentation<br>
component in trac that Jeff owns that can be used for that.<br>
<br>
One thing to note is that Jeff and Mike Smith started or at least pondered staring an "examples"<br>
effort in Montreal. I could see some of your symbolization examples being very useful in that context<br>
too.<br>
<br>
I'll start with a +1 on granting Havard Tveite commit access for documentation.<br>
<br>
Steve<br>
<br>
-----Original Message-----<br>
From: Havard Tveite [mailto:<a href="mailto:havard.tveite@umb.no">havard.tveite@umb.no</a>]<br>
Sent: Thursday, March 24, 2011 11:25 AM<br>
To: Lime, Steve D (DNR)<br>
Cc: <a href="mailto:thomas.bonfort@gmail.com">thomas.bonfort@gmail.com</a><br>
Subject: Re: 6.0 release plan - RFC45 - Consistent units in CLASS-> STYLE<br>
<br>
Dear Steve,<br>
<br>
I would be happy to contribute on the documentation<br>
related to rendering for version 6. I will, of course,<br>
have to consult you and Thomas in order to get<br>
clarifications on what intended behaviour is in some<br>
cases...<br>
<br>
How do we proceed? My osgeo user name is havatv.<br>
<br>
I have no experience with committing (I have only<br>
used SVN to check out). Is there any documentation<br>
that can help me avoid making big mistakes when<br>
committing?<br>
I have found a book, that I hope can help:<br>
<a href="http://svnbook.red-bean.com/en/1.4/svn-book.pdf" target="_blank">http://svnbook.red-bean.com/en/1.4/svn-book.pdf</a><br>
<br>
Is it enough to issue the svn commit command with a<br>
descriptive message using --message?<br>
<br>
I have had a look at the documentation development<br>
guide (<a href="http://mapserver.org/development/documentation.html" target="_blank">http://mapserver.org/development/documentation.html</a>),<br>
which seems reasonably straight forward.<br>
I have also read RFC 7.1, and have no problems with that.<br>
<br>
Håvard<br>
<br>
On 3/24/2011 3:42 PM, Lime, Steve D (DNR) wrote:<br>
> We'd be happy to have more documentation committers...<br>
><br>
> -----Original Message-----<br>
> From: thomas bonfort [mailto:<a href="mailto:thomas.bonfort@gmail.com">thomas.bonfort@gmail.com</a>]<br>
> Sent: Thursday, March 24, 2011 4:46 AM<br>
> To: Havard Tveite<br>
> Cc: Lime, Steve D (DNR)<br>
> Subject: Re: 6.0 release plan - RFC45 - Consistent units in CLASS-> STYLE<br>
><br>
> Thanks Havard,<br>
> For the documentation changes, it would probably be easier if you<br>
> could commit directly into the mapserver documentation site. I seem to<br>
> recall that for docs commit access, it is sufficient to post a short<br>
> message to the -dev list stating which areas you want to work on, and<br>
> your osgeo userid.<br>
><br>
> ps: good news for rfc45, I've just been on the phone with a customer<br>
> here in france who will probably be funding the anchorpoint stuff :)<br>
><br>
> On Thu, Mar 24, 2011 at 10:22, Havard Tveite<<a href="mailto:havard.tveite@umb.no">havard.tveite@umb.no</a>> wrote:<br>
>> An updated examples.sym (just the explaining text has changed).<br>
>><br>
>> Håvard<br>
>><br>
>> On 3/24/2011 10:17 AM, Håvard Tveite wrote:<br>
>>><br>
>>> Very nice!<br>
>>><br>
>>> How can I help updating the documentation?<br>
>>><br>
>>> Another thing:<br>
>>> I looked at the 6beta distribution and found that there<br>
>>> was a symbol directory.<br>
>>> I have updated the files in that directory to use the<br>
>>> Mapserver 6 mechanisms. You will find the new files<br>
>>> attached. I have also included two PNG files that show<br>
>>> the images produced by the previous map and symbol files<br>
>>> using Mapserver 5.2 (example-org.png) and my updated<br>
>>> files using 6beta3 (example.png).<br>
>>> I have only updated the existing examples, but could<br>
>>> add other (more advanced) examples if you like.<br>
>>><br>
>>> Håvard<br>
>>><br>
>>> On 3/23/2011 4:07 PM, thomas bonfort wrote:<br>
>>>><br>
>>>> Havard,<br>
>>>> fixed in trunk, please confirm ;)<br>
>>>><br>
>>>> thanks for testing!<br>
>>>><br>
>>>> thomas<br>
>>>><br>
>>>> On Tue, Mar 22, 2011 at 15:27, Havard Tveite<<a href="mailto:havard.tveite@umb.no">havard.tveite@umb.no</a>><br>
>>>> wrote:<br>
>>>>><br>
>>>>> Dear Thomas and Steve,<br>
>>>>><br>
>>>>> I have now tested quite a bit on 6beta2.<br>
>>>>> Many improvements!<br>
>>>>><br>
>>>>> I have one big concern that I think needs to be addressed<br>
>>>>> for 6.0:<br>
>>>>><br>
>>>>> Units in LAYER-> CLASS-> STYLE<br>
>>>>> ------------------------------<br>
>>>>> The units used for the different elements of the STYLE now<br>
>>>>> vary, and I think that will be very confusing to the users.<br>
>>>>> * WIDTH and SIZE specifies the width/height of the line/symbol<br>
>>>>> as the number of pixels/map units at the scale<br>
>>>>> 1:SYMBOLSCALEDENOM. I like this!<br>
>>>>> * GAP uses the same units (that is the gap in pixels/map units<br>
>>>>> at the scale 1:SYMBOLSCALEDENOM). I like this!<br>
>>>>> * PATTERN uses the WIDTH of the line as the unit, so to get<br>
>>>>> the gap as the number of pixels/map units at the scale<br>
>>>>> 1:SYMBOLSCALEDENOM, you have to multiply the GAP value by<br>
>>>>> the value of WIDTH. I don't like this!<br>
>>>>> * OFFSET seems to use the same approach as PATTERN when<br>
>>>>> "displacing" lines (units relative to line WIDTH).<br>
>>>>> For point symbols, it seems to use the same approach as GAP<br>
>>>>> (pixels/map units at the scale 1:SYMBOLSCALEDENOM).<br>
>>>>><br>
>>>>> My opinion is that the unit used for all the length/width/size<br>
>>>>> measure elements (GAP, OFFSET, PATTERN, SIZE, WIDTH) of<br>
>>>>> CLASS-> STYLE should be the number of pixels/map units at the<br>
>>>>> scale 1:SYMBOLSCALEDENOM (as is currently the case for WIDTH,<br>
>>>>> SIZE and GAP). This would mean that the units used for<br>
>>>>> PATTERN and OFFSET (for lines) would have to be changed.<br>
>>>>><br>
>>>>><br>
>>>>> Håvard<br>
>>>>><br>
>>>>> On 11/18/2010 4:13 PM, thomas bonfort wrote:<br>
>>>>>><br>
>>>>>> Havard,<br>
>>>>>><br>
>>>>>> rfc45 isn't dead, but the priority now is getting 6.0 out of the door,<br>
>>>>>> so I wouldn't expect those features by then.<br>
>>>>>> Once 6.0 is out, getting those features in is a matter of time and/or<br>
>>>>>> will and/or funding.<br>
>>>>>><br>
>>>>>> cheers,<br>
>>>>>> thomas<br>
>>>>>><br>
>>>>>> On Tue, Nov 9, 2010 at 16:23, Havard Tveite<<a href="mailto:havard.tveite@umb.no">havard.tveite@umb.no</a>><br>
>>>>>> wrote:<br>
>>>>>>><br>
>>>>>>> Dear Steve and Thomas,<br>
>>>>>>><br>
>>>>>>> I have been extremely busy this summer and autumn, so I<br>
>>>>>>> have not been able to follow Mapserver developments very<br>
>>>>>>> closely. But when I heard about the release plan for 6.0,<br>
>>>>>>> I thought about RFC45. There has been some interest<br>
>>>>>>> during the last years for some of the suggestions there,<br>
>>>>>>> and I still think that it includes some very good ideas<br>
>>>>>>> for quality improvements of Mapserver symbol rendering.<br>
>>>>>>> I have kept track of the progress on Cairo, so I don't know<br>
>>>>>>> if anything of this has been addressed there.<br>
>>>>>>><br>
>>>>>>> Here are some examples:<br>
>>>>>>><br>
>>>>>>> Stable origin for tile generation + polygon fill symbols:<br>
>>>>>>> This would require that for instance the coordinate system<br>
>>>>>>> origo be used instead of a local origo when placing tiles<br>
>>>>>>><br>
>>>>>>> Angle options - there has been some demand for compass (the<br>
>>>>>>> current vector? default).<br>
>>>>>>><br>
>>>>>>> Possibility to specify symbol origin for precise placement<br>
>>>>>>> of symbols.<br>
>>>>>>><br>
>>>>>>> And more.<br>
>>>>>>><br>
>>>>>>> Someone more familiar with the Mapserver code should perhaps<br>
>>>>>>> go through RFC45 again and check what can be achieved for 6.0.<br>
>>>>>>> I may have the time in a few weeks to help with specifications.<br>
>>>>>>><br>
>>>>>>> Håvard Tveite<br>
>>>>>>><br>
>>>>>>> On 11/9/2010 8:59 AM, thomas bonfort wrote:<br>
>>>>>>>><br>
>>>>>>>> On Mon, Nov 8, 2010 at 18:07, Lime, Steve D (DNR)<br>
>>>>>>>> <<a href="mailto:Steve.Lime@state.mn.us">Steve.Lime@state.mn.us</a>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> RFC-50: I think this is out for 6.0 unless those authors are still<br>
>>>>>>>>> around.<br>
>>>>>>>><br>
>>>>>>>> yes definitely. I'd like to tackle that one some day, but haven't got<br>
>>>>>>>> the time in the near future<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> RFC-52: The changes I’d like to see are relatively minor (from a<br>
>>>>>>>>> coding<br>
>>>>>>>>> perspective) and are a return to a single getShape() method in<br>
>>>>>>>>> MapScript.<br>
>>>>>>>>> It<br>
>>>>>>>>> will break 5.6 scripts but is simpler in the long run. I don’t know<br>
>>>>>>>>> that<br>
>>>>>>>>> an<br>
>>>>>>>>> RFC is necessary but I will start a ticket and we can go from there.<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> RFC-54: I think Thomas just needs to merge?<br>
>>>>>>>><br>
>>>>>>>> I'm planning to do this before the end of the month. It might slip a<br>
>>>>>>>> bit from the planned 15th november<br>
>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> RFC-58 – RFC-63: Are all basically complete, perhaps need docs<br>
>>>>>>>>> though.<br>
>>>>>>>><br>
>>>>>>>> RFC58 (kml) still needs a bit of love before being ready<br>
>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> RFC-64: Needs feedback. This may push us back a week or two<br>
>>>>>>>>> depending<br>
>>>>>>>>> on<br>
>>>>>>>>> feedback. I think 6.0 is the right time to implement though given<br>
>>>>>>>>> the<br>
>>>>>>>>> types<br>
>>>>>>>>> of proposed changes. They are not candidates for minor releases.<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> Thanks for pushing on this…<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> Steve<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> From: <a href="mailto:mapserver-dev-bounces@lists.osgeo.org">mapserver-dev-bounces@lists.osgeo.org</a><br>
>>>>>>>>> [mailto:<a href="mailto:mapserver-dev-bounces@lists.osgeo.org">mapserver-dev-bounces@lists.osgeo.org</a>] On Behalf Of Tamas<br>
>>>>>>>>> Szekeres<br>
>>>>>>>>> Sent: Saturday, November 06, 2010 6:12 PM<br>
>>>>>>>>> To: <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>>>>>>>>> Subject: [mapserver-dev] 6.0 release plan<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> Hi All,<br>
>>>>>>>>><br>
>>>>>>>>> In search of my memory (and my mails) the recent plan of the 6.0<br>
>>>>>>>>> release<br>
>>>>>>>>> has<br>
>>>>>>>>> been scheduled as follows:<br>
>>>>>>>>><br>
>>>>>>>>> "Plan for a feature freeze on Nov 15th, with a little over 2 months<br>
>>>>>>>>> for<br>
>>>>>>>>> betas, aiming for final release between Jan 15th and 31st"<br>
>>>>>>>>><br>
>>>>>>>>> How do we stand with the upcoming activities in the light of this?<br>
>>>>>>>>><br>
>>>>>>>>> I can see the following RFCs may be affected or must be scheduled:<br>
>>>>>>>>><br>
>>>>>>>>> RFC-50 (OpenGL)<br>
>>>>>>>>> RFC-52 (One-pass query processing), we wanted to do some rework as<br>
>>>>>>>>> far<br>
>>>>>>>>> as<br>
>>>>>>>>> I<br>
>>>>>>>>> remember.<br>
>>>>>>>>> RFC-54 (Rendering overhaul)<br>
>>>>>>>>> RFC-58 (KML output)<br>
>>>>>>>>> RFC-62 (Additional WFS GetFeature Output Formats)<br>
>>>>>>>>> RFC-63 (OpenLayers viewer)<br>
>>>>>>>>> RFC-64 (Expression parser overhaul)<br>
>>>>>>>>><br>
>>>>>>>>> Do we have any other plan which will be covered with an RFC soon?<br>
>>>>>>>>> How<br>
>>>>>>>>> much<br>
>>>>>>>>> time the pending efforts will take to be implemented?<br>
>>>>>>>>> The 6.0 release plan document may also updated with some up to date<br>
>>>>>>>>> information if possible.<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> Best regards,<br>
>>>>>>>>><br>
>>>>>>>>> Tamas<br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>>> _______________________________________________<br>
>>>>>>>>> mapserver-dev mailing list<br>
>>>>>>>>> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>>>>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
>>>>>>>>><br>
>>>>>>>>><br>
>>>>>>>> _______________________________________________<br>
>>>>>>>> mapserver-dev mailing list<br>
>>>>>>>> <a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
>>>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
>>>>>>><br>
>>>>>>> --<br>
>>>>>>> Håvard Tveite<br>
>>>>>>> Department of Mathematical Sciences and Technology, UMB<br>
>>>>>>> Drøbakveien 31, POBox 5003, N-1432 Ås, NORWAY<br>
>>>>>>> Phone: +47 64965483 Fax: +47 64965401 <a href="http://www.umb.no/imt/" target="_blank">http://www.umb.no/imt/</a><br>
>>>>>>><br>
>>>>><br>
>>>>> --<br>
>>>>> Håvard Tveite<br>
>>>>> Department of Mathematical Sciences and Technology, UMB<br>
>>>>> Drøbakveien 31, POBox 5003, N-1432 Ås, NORWAY<br>
>>>>> Phone: +47 64965483 Fax: +47 64965401 <a href="http://www.umb.no/imt/" target="_blank">http://www.umb.no/imt/</a><br>
>>>>><br>
>>><br>
>><br>
>> --<br>
>> Håvard Tveite<br>
>> Department of Mathematical Sciences and Technology, UMB<br>
>> Drøbakveien 31, POBox 5003, N-1432 Ås, NORWAY<br>
>> Phone: +47 64965483 Fax: +47 64965401 <a href="http://www.umb.no/imt/" target="_blank">http://www.umb.no/imt/</a><br>
>><br>
><br>
<font color="#888888"><br>
--<br>
Håvard Tveite<br>
Department of Mathematical Sciences and Technology, UMB<br>
Drøbakveien 31, POBox 5003, N-1432 Ås, NORWAY<br>
Phone: +47 64965483 Fax: +47 64965401 <a href="http://www.umb.no/imt/" target="_blank">http://www.umb.no/imt/</a><br>
<br>
</font><br>_______________________________________________<br>
mapserver-dev mailing list<br>
<a href="mailto:mapserver-dev@lists.osgeo.org">mapserver-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-dev" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-dev</a><br>
<br></blockquote></div><br><div style="visibility: hidden; left: -5000px; position: absolute; z-index: 9999; padding: 0px; margin-left: 0px; margin-top: 0px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 130%;" id="avg_ls_inline_popup">
</div>