shapes to MySQL

[Stephen Woodbridge]

Ker Nulov wrote:
> I guess the time is wasted on searching, not drawing
> (because small shapefiles are drown very fast) and I
> thought .shx is the Shapefile index, I have no .qix
> index at all and I have hunderds of shapefiles. This
> is what I have:
> -rwxr-xr-x  1 root root  1687086 Feb 17 08:27
> Cdmexm_region.dbf
> -rwxr-xr-x  1 root root      187 Feb 17 08:27
> Cdmexm_region.prj
> -rwxr-xr-x  1 root root 78934876 Feb 17 08:27
> Cdmexm_region.shp
> -rwxr-xr-x  1 root root  1124780 Feb 17 08:27
> Cdmexm_region.shx
> 
> Is there a open source utility to create .qix? Never
> heard of them, looks interesting.

shptree is the utility and it is part of the mapserver build

-Steve

>  --- Stephen Woodbridge <woodbri at swoodbridge.com>
> escribió:
> 
> 
>>Ker Nulov wrote:
>>
>>>Ohh, well, my shapefile 78 MB and it has 140,000
>>>polygons. displaying 1km of zoom taks 1 sec, this
>>
>>is
>>
>>>too much for our application. I bet a query in
>>
>>MySQL
>>
>>>will be faster.
>>
>>What makes you think that? Where IS the performance
>>going to? Search for 
>>the objects, reading them from disk, of rendering
>>the objects? If you 
>>don't know then you are probably trying to optimize
>>the wrong thing.
>>
>>Many of us have been working with mapserver for
>>years and we have looked 
>>into these questions and I can tell you (as Attila
>>did) that shapefile 
>>are the fastest. Do all you shapefiles have spatial
>>indexes *.qix files 
>>associated with them? Start there.
>>
>>To answer your question, NO, you can not put your
>>shapefiles in MySQL 
>>and render then via mapserver. You can put them in
>>postGIS, but they 
>>will be slower than shapefiles.
>>
>>-Steve W.
>>
>>
>>> --- Attila Csipa <plists at prometheus.org.yu>
>>
>>escribió:
>>
>>>
>>>>On Friday 03 March 2006 16:38, Ker Nulov wrote:
>>>>
>>>>
>>>>>draw layers using MySQL access?  I need it to
>>>>
>>>>improove
>>>>
>>>>
>>>>>speed. My application uses mapscript with php.
>>>>
>>>>Shapefiles are likely the fastest storage for
>>>>small/generic data, moving to 
>>>>mysql (or any other database for that matter) will
>>>>probably not speed up 
>>>>things on itself unless you're really using some
>>>>DBMS specific feature.
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>	
>>>	
>>>		
>>>
>>
> ___________________________________________________________
> 
>>>Do You Yahoo!? 
>>>La mejor conexión a Internet y <b >2GB</b> extra a
>>
>>tu correo por $100 al mes. http://net.yahoo.com.mx 
>>
>>
> 
> 
> 
> 	
> 	
> 		
> ___________________________________________________________ 
> Do You Yahoo!? 
> La mejor conexión a Internet y <b >2GB</b> extra a tu correo por $100 al mes. http://net.yahoo.com.mx 
> 
>