[mapserver-users] Ogrtileindex bug in Mapserver 7.0

[Rahkonen Jukka (MML)]

Hi,

I believe it did work with v. 6.4 but I noticed the issue now when I was building a new dataset which has bigger envelopes which makes it more common that BBOX fits totally inside an envelope.  We do not have any MS 6.x running any more so testing would mean some extra work. Last time vector tileindex system is probably touched because of this discussion: http://osgeo-org.1560.x6.nabble.com/GetFeatureInfo-error-with-native-vector-tileindex-td5155807.html


-Jukka Rahkonen-

thomas bonfort wrote:

did this work OK with previous mapserver versions ?

On 22 October 2015 at 10:39, Rahkonen Jukka (MML) <jukka.rahkonen at maanmittauslaitos.fi> wrote:
> Hi,
>
> I have loads of shapefiles on a disk and I have combined them into a single layer by creating an index shapefile with ogrtindex http://www.gdal.org/ogrtindex.html which is doing the same for the original vector datasets than gdaltindex for images by storing an envelope of each source dataset into the index file. "Vector tile" in my question means the envelope in the ogrtindex shapefile.
>
> The issue is that when I use CONNECTIONTYPE OGR and the BBOX of the GetMap request is totally inside of some envelope in the ogrtindex shapefile then Mapserver believes that BBOX contains no data. It only finds the envelopes (and finally the original vector data by following the file path that is stored into the LOCATION field)  if BBOX is intersecting the boundary of an envelope. See my trial with ASCII graphics below, when BBOX is totally inside the envelope then no data are found. The key is that data are not found when BBOX intersects with the envelope (the interior of the polygon) but not with the boundary of the polygon. With native TILEINDEX access to vector data this issue does not happen.
>
>
> -------------------
> |   ----- ----        |
> |  | BBOX |       |  <envelope of a vector dataset or "vector tile"
> |  ----------        |
> ------------------
>
> -Jukka Rahkonen
>
> thomas Bonfort wrote:
>
> It's not clear to me what your issue actually is....
>
>> reading data from the shapefiles which are behind the ogrtileindex 
>> file only if the BBOX of the WMS GetMap request intersects the 
>> boundary of the vector tile
>
> ->why is that not the expected behavior?
> -> what do you mean by "vector tile" ?
>
> On 21 October 2015 at 10:30, Rahkonen Jukka (MML) <jukka.rahkonen at maanmittauslaitos.fi> wrote:
>> Hi,
>>
>>
>>
>> I was wondering why my ogrtileindex layer sometimes works but sometimes not.
>> It appears that Mapserver is reading data from the shapefiles which 
>> are behind the ogrtileindex file only if the BBOX of the WMS GetMap 
>> request intersects the boundary of the vector tile.  Mapserver 
>> version is 7.0.0 on Linux and GDAL version is 2.0.1, released 
>> 2015/09/15. The ogrtindex file is shapefile and it is defined in the 
>> mapfile as
>>
>>
>>
>>   CONNECTIONTYPE OGR
>>
>>   TILEINDEX "/tindex/heigthidx.shp,0"
>>
>>
>>
>> Can anybody suggest a quick workaround?
>>
>>
>>
>>
>>
>> -Jukka Rahkonen-
>>
>>
>> _______________________________________________
>> mapserver-users mailing list
>> mapserver-users at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/mapserver-users