Sorry, I have some correction, it is right illustrations:
Result when order by asc:
http://s28.postimg.org/lqs8nxw31/asc.jpg
Result when order by desc:
http://s12.postimg.org/xondilekt/desc.jpg
___
mapserver-users mailing list
I would draw your attention to the source of this discussion.
http://osgeo-org.1560.x6.nabble.com/the-lines-one-above-other-td5187093.html
It seems I found how to display multilevel junction of highway with ORDER BY
in the case using a one layer. Adding order by id desc or order by id asc
in
It seems I found how to display multilevel junction of highway with ORDER
BY in the case using a one layer. Adding order by id desc or order by
id asc in subquery
$highwayLayer-set(data,geom from (select id, 'id = '||id as name, geom
from my_table
where ST_Intersects(geom, !BOX!) order by
You can do it in a single layer, provided that you have someway of
determining via attributes that a given road segment isn't connected
to other road segments below it (typically that would be something
saying it's a bridge rather than a regular road). The behavior is
undocumented and relies on
This is also not an issue in Oracle.
M
On 2/12/15, 8:55 AM, thomas bonfort thomas.bonf...@gmail.com wrote:
Actually there is an issue opened for this, as the order by inside the
subquery is not guaranteed to be maintained in the outer query:
https://github.com/mapserver/mapserver/issues/5008 .
No, MapServer respects the feature order. Using the ORDER BY with a
database connection, MapServer will draw features in that order.
Mike
--
Michael Smith
US Army Corps
Remote Sensing GIS/Center
On 2/12/15, 7:52 AM, Eichner, Andreas - SID
andreas.eich...@sid.sachsen.de wrote:
I'm not sure
Actually there is an issue opened for this, as the order by inside the
subquery is not guaranteed to be maintained in the outer query:
https://github.com/mapserver/mapserver/issues/5008 . For mssql there
has been a patch applied, for postgis it is not needed yet.
On 12 February 2015 at 08:48,
