Re: [mapserver-users] Label wrapping question
Here it is: https://github.com/mapserver/mapserver/pull/5033 regards, dejan On 6. stu. 2014., at 22:27, Lime, Steve D (MNIT) wrote: > Dejan: If you'd open a ticket with your patches or submit a pull request it > would be appreciated. --Steve > > -Original Message- > From: mapserver-users-boun...@lists.osgeo.org > [mailto:mapserver-users-boun...@lists.osgeo.org] On Behalf Of Dejan Gambin > Sent: Thursday, November 06, 2014 7:34 AM > To: Rahkonen Jukka > Cc: 'mapserver-users@lists.osgeo.org' > Subject: Re: [mapserver-users] Label wrapping question > > Hi Jukka, > > If you remember, I've sent the screen captures. I am just interested if this > change makes sense and do you plan to embed it in the future versions? > > Like I said, this is just the proof of concept. I didn't make change for > label->encoding part, and also, it currently crashes in certain situation if > I have a word in label text longer than maxlength. It should all be revised > and modified. > > Thanks very much > > regards, dejan > On 24. ruj. 2014., at 15:15, Rahkonen Jukka (Tike) wrote: > >> Hi, >> >> Send us some screen captures of wrapped labels before and after your >> change. I feel that your change would make sense. >> >> -Jukka Rahkonen- >> >> Dejan Gambin wrote: >> >>> In the meantime, I have slightly changed msWrapText() function in >>> maplabel.c to get what I wanted. If someone is interested I can share the >>> short piece of code. >>> >>> regards, dejan >>> >>> >>> On 23. ruj. 2014., at 12:32, Dejan Gambin wrote: >>> Hi, I have some users wishing to use long legend labels, but they don't fit well on >>> my site. As I can see, MapServer is doing this - if maxlength > 0 and wrap >>> = 'char' >>> (usually space), insert a new line at the FIRST wrap character found >>> AFTER maxlength character. This is leading to some bad results (label >>> not wrapped or wrapped too early). My question is - shouldn't it be better to wrap at the LAST wrap character >>> BEFORE maxlength character? Is this maybe implemented somewhere or >>> there are plans for this? Thanks very much regards, dejan ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users >>> >>> ___ >>> mapserver-users mailing list >>> mapserver-users@lists.osgeo.org >>> http://lists.osgeo.org/mailman/listinfo/mapserver-users > > ___ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] WFS query slow on large postgis table (and small table disappointing as well)
Done, opened ticket: https://github.com/mapserver/mapserver/issues/5032 thomas bonfort wrote > Yes Marco, Please open a ticket for this. > > thanks, > thomas -- View this message in context: http://osgeo-org.1560.x6.nabble.com/WFS-query-slow-on-large-postgis-table-and-small-table-disappointing-as-well-tp5170988p5171815.html Sent from the Mapserver - User mailing list archive at Nabble.com. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] WFS query slow on large postgis table (and small table disappointing as well)
Yes Marco, Please open a ticket for this. thanks, thomas On 7 November 2014 09:34, deduikertjes wrote: > Ok, with all the help I came to the following results: > > Compile the current development version (6.5-dev) from GitHub & Install. > Results: > > Simple Spatial WFS queries require a non-empty > . > Setting it too foo proved to be > sufficient. > Query speed is indeed very fast now. > > Using WMS-dimensions as described on > http://mapserver.org/ogc/wms_dimension.html does work in > 6.4 but not in 6.5-dev. As I have need for them I recompiled mapserver > with a > -DCMAKE_INSTALL_PREFIX=/usr/local/bin switch so I can run mapserver 6.4 > en 6.5-dev next to each > other. GetMap requests are routed to mapserver 6.4 and GetFeature > requests are routed to 6.5-dev. > > Using the WMS-dimensons on 6.5-dev yields the following error: > > > msDrawMap(): Image handling error. Failed to draw layer named 'jan2014_low'. > msPostGISLayerWhichShapes(): Query error. Error executing query: ERROR: > operator does not exist: >= numeric > LINE 1: ...32.505600397 6790506.21879132))',900913) and >= 0.9... > ^ > HINT: No operator matches the given name and argument type(s). You might > need to add explicit type casts. > > > > Its seems that the dimension parameter is not inserted in the layer filter > expression. > Should I create a bug report for this? > > MArco > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/WFS-query-slow-on-large-postgis-table-and-small-table-disappointing-as-well-tp5170988p5171806.html > Sent from the Mapserver - User mailing list archive at Nabble.com. > ___ > mapserver-users mailing list > mapserver-users@lists.osgeo.org > http://lists.osgeo.org/mailman/listinfo/mapserver-users ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
Re: [mapserver-users] WFS query slow on large postgis table (and small table disappointing as well)
Ok, with all the help I came to the following results: Compile the current development version (6.5-dev) from GitHub & Install. Results: Simple Spatial WFS queries require a non-empty . Setting it too foo proved to be sufficient. Query speed is indeed very fast now. Using WMS-dimensions as described on http://mapserver.org/ogc/wms_dimension.html does work in 6.4 but not in 6.5-dev. As I have need for them I recompiled mapserver with a -DCMAKE_INSTALL_PREFIX=/usr/local/bin switch so I can run mapserver 6.4 en 6.5-dev next to each other. GetMap requests are routed to mapserver 6.4 and GetFeature requests are routed to 6.5-dev. Using the WMS-dimensons on 6.5-dev yields the following error: msDrawMap(): Image handling error. Failed to draw layer named 'jan2014_low'. msPostGISLayerWhichShapes(): Query error. Error executing query: ERROR: operator does not exist: >= numeric LINE 1: ...32.505600397 6790506.21879132))',900913) and >= 0.9... ^ HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. Its seems that the dimension parameter is not inserted in the layer filter expression. Should I create a bug report for this? MArco -- View this message in context: http://osgeo-org.1560.x6.nabble.com/WFS-query-slow-on-large-postgis-table-and-small-table-disappointing-as-well-tp5170988p5171806.html Sent from the Mapserver - User mailing list archive at Nabble.com. ___ mapserver-users mailing list mapserver-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapserver-users
