This map tile engine was created using PHP and MySQL (with spatial data types) for use with the Google Maps API. Spatial data is loaded in via .shp and .dbf files.

This project is split into 2 sections, the tile engine and the example which uses the tile engine. The example is VERY simplistic and does not provide a proper interface for managing the layers. At the moment it illustrates how to import a .shp file and how this data can be viewed in Google Maps.

Here is a demo of the map tile engine in action. I have only drawn the world boundaries. Map Example

1. Polygon
2. Linestring
3. Point

1. Clone the repo onto your server
2. Import the /db/ddl.sql file into MySQL
3. Change the MySQL connection details in the config file src/Gis/Config/default.php
4. To get the example running you will also need to edit the 'basePath' var in the src/example/html/map

1. Navigate to the src/example/index.php file
2. You should see world_simple.dbf and world_simple.shp file displaying in a list (This is an example data set)
3. If you click the preview link next to the .shp file you can inspect the first 10 records in the .shp file
4. If you click the load link you will be taken to a form where you can name the layer, select the set name (which comes from the .dbf file) and then import the dataset.
5. If the data imported successfully (you can have a look in the layers, sets and polygons table to confirm) you should be able to click on the 'Map Example' link at the top.

Since there is no interface for managing layers properly there are some things you need to know how to do manually until such time as an interface is developed. The fields on the layers table are important for how and when a layer is shown on the map. Here are some of the fields and what they do:

more to come here...

The spatial tables (polygon, point and linestring) had to use the MyISAM storage engine in order to make use of MySQL's spatial indexes.

1. Replace the example with a proper admin section for managing the layers.
2. Cache the map tiles.
3. Support KML files.
4. Support Multilines