sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M. Le Bihan (JIRA)" <>
Subject [jira] [Commented] (SIS-305) Shapefile reader should be able to use .SHX (shapefile index)
Date Sat, 05 Dec 2015 18:06:10 GMT


M. Le Bihan commented on SIS-305:

{code:java}InputFeatureStream is = shp.find("SELECT * FROM ABRALicenseePt_4326_clipped WHERE
ADDRID = 1152");{code}
will return only the Feature having this id among all the features of the shapefile.

Shapefile index (.SHX) is mandatory to use WHERE conditions in the SQL Statement that queries
the relative DBase file of the shapefile.

Status of this issue : ok to commit, awaiting restoration of JDK8 branch in order to commit.

> Shapefile reader should be able to use .SHX (shapefile index)
> -------------------------------------------------------------
>                 Key: SIS-305
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: Shapefile
>    Affects Versions: 0.7
>            Reporter: M. Le Bihan
>            Assignee: M. Le Bihan
>            Priority: Minor
>              Labels: JDBC, Shapefile
> Being able to read .SHX (shapefile index) that often accompany a shapefile is useful
for two reasons :
> 1) Currently when the JDBC driver runs an SQL request with a condition it go through
the Shapefile and the DBase III file sequentially, from the start to the end. It costs a lot.
> Reading the shapefile index open a way to :
> - first read DBase III content for matching records,
> - then do direct access to the shapefile features and return them.
> 2) If a shapefile is provided with a .SHX file and that we become able to INSERT or DELETE
records on it, we are expected to update this index file.

This message was sent by Atlassian JIRA

View raw message