You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This server distributes maps to desktop, web, and mobile applications from
8
-
a standard Apache+PHP web hosting.
7
+
This server distributes maps to desktop, web, and mobile applications from a standard Apache+PHP web hosting.
9
8
10
-
Try a live demo at: http://tileserver.maptiler.com/
9
+
It is a free and open-source project implementing the OGC WMTS standard for pre-rendered map tiles made with any [map tiling software](https://www.maptiler.com/desktop/) like MapTiler Desktop, GDAL2Tiles, or any other MBTiles file.
11
10
12
-
It is a free and open-source project implementing OGC WMTS standard for
13
-
pre-rendered map tiles made with [MapTiler](http://www.maptiler.com/), GDAL2Tiles,
14
-
or available as MBTiles files.
11
+
It is the easiest and cheapest way how to serve zoomable maps in a standardized way - practically from any ordinary web hosting.
15
12
16
-
It is the easiest and cheapest way how to serve zoomable maps in a
17
-
standardized way - practically from any ordinary web hosting.
13
+
It is easy to install - copy the project files to a PHP-enabled directory along with your map data.
18
14
19
-
It is easy to install - just copy the project files to a PHP-enabled
20
-
directory along with your map data.
21
-
22
-
It comes with an online interface showing the list of the maps and step-by-step guides for online mapping libraries (Google Maps API, Leaflet, OpenLayers, OL3, MapBox JS, ArcGIS JS) and various desktop GIS software:
15
+
It comes with an online interface showing the list of the maps and step-by-step guides for online mapping libraries (Google Maps API, Leaflet, OpenLayers, OL3, MapLibre GL JS, ArcGIS JS) and various desktop GIS software:
This project is developed in PHP, not because it is the best language for
27
-
development of web applications, but because it maximally simplify the
28
-
deployment on large number of web hosting providers including various free
29
-
web hostings.
19
+
This project is developed in PHP, not because it is the best language for the development of web applications, but because it maximally simplifies the deployment on a large number of web hostings, including various free web hostings providers.
30
20
31
-
Tiles are served directly by Apache with mod_rewrite rules as static files
32
-
and therefore are very fast and with correct HTTP caching headers.
33
-
Only XML metadata are delivered via PHP.
34
-
MBTiles are served via PHP, and are therfore slower, unless they are unpacked with mbutil.
21
+
Tiles are served directly by Apache with mod_rewrite rules as static files and therefore are very fast and with correct HTTP caching headers. Only XML metadata is delivered via PHP. MBTiles are served via PHP and are therefore slower unless they are unpacked with mbutil.
35
22
36
-
[MapTiler](http://www.maptiler.com/) can render GeoTIFF, ECW, MrSID, GeoPDF into compatible map tiles. JPEG, PNG, GIF and TIFF with scanned maps or images without geolocation can be turned into standard map layers with the visual georeferencing functionality (http://youtu.be/eJxdCe9CNYg).
23
+
[MapTiler](http://www.maptiler.com/) can render GeoTIFF, ECW, MrSID, GeoPDF into compatible map tiles. JPEG, PNG, GIF, and TIFF with scanned maps or images without geolocation can be turned into standard map layers with the visual georeferencing functionality (http://youtu.be/eJxdCe9CNYg).
Download the project files as a [zip archive](https://github.com/klokantech/tileserver-php/archive/master.zip) or source code from GitHub and unpack it into a web-hosting of your choice.
52
39
53
-
If you access the web address relevant to the installation directory,
54
-
the TileServer.php Server should display you a welcome message and further
55
-
instructions.
40
+
If you access the web address relevant to the installation directory, the TileServer.php Server should display you a welcome message and further instructions.
56
41
57
-
Then you can upload to the web hosting your mapping data - a directory with
58
-
tiles rendered with [MapTiler](http://www.maptiler.com/).
42
+
Then you can upload to the web hosting your mapping data - a directory with tiles rendered with [MapTiler](http://www.maptiler.com/).
59
43
60
-
Tiles produced by open-source GDAL2Tiles or MapTiler and tiles in .mbtiles
61
-
files can be easily converted to required structure (XYZ with top-left origin
62
-
and metadata.json file). The open-source utility [mbutil](https://github.com/mapbox/mbutil) produces
63
-
exactly the required format.
44
+
Tiles produced by open-source GDAL2Tiles or MapTiler Desktop and tiles in .mbtiles format can be easily converted to the required structure (XYZ with top-left origin and metadata.json file). The open-source utility [mbutil](https://github.com/mapbox/mbutil) produces exactly the required format.
64
45
65
-
Direct reading of .mbtiles files is supported, but with decreased performance
66
-
compared to the static files in a directory. The advantage is easier data management,
67
-
especially upload over FTP or similar protocols.
46
+
Direct reading of .mbtiles files is supported but with decreased performance compared to the static files in a directory. The advantage is easier data management, especially upload over FTP or similar protocols.
68
47
69
48
Supported protocols:
70
49
--------------------
@@ -123,8 +102,7 @@ Supported protocols:
123
102
- Retina / HighDPI routing with 512 tiles
124
103
Use @2x suffix in url for JSONs and tiles. For example http://tileserver.maptiler.com/[email protected]
125
104
126
-
To use the OGC WMTS standard point your client (desktop or web) to the URL
127
-
of 'directory' where you installed tileserver.php project with suffix "wmts".
105
+
To use the OGC WMTS standard, point your client (desktop or web) to the URL of 'directory' where you installed tileserver.php project with suffix "wmts".
128
106
For example: http://www.example.com/directory/wmts
129
107
130
108
If you have installed the project into a root directory of a domain, then the address is: http://www.example.com/wmts
@@ -143,43 +121,35 @@ GetTile RESTful/KVP:
143
121
144
122
Other example requests are mentioned in the .htaccess.
145
123
146
-
TileServer-PHP supports all coordinates system. You have to define it with tilejson with specification on https://github.com/klokantech/tilejson-spec/tree/custom-projection/2.2.0
124
+
TileServer-PHP supports all coordinates systems. You have to define it with tilejson with specification on https://github.com/klokantech/tilejson-spec/tree/custom-projection/2.2.0
147
125
Or use MapTiler to produce datasets with this specification.
148
126
149
127
Performance from the web clients
150
128
--------------------------------
151
129
152
130
It is highly recommended to map several domain names to the service, such as:
This can be done with DNS CNAME records pointing to your hosting.
155
-
The reason for this is that traditionally browsers will not send more then two
156
-
simultaneous http request to the same domain - with multiple domains for the
157
-
same server you can better saturate the network and receive the maps faster.
133
+
134
+
This can be done with DNS CNAME records pointing to your hosting. The reason for this is that traditionally browsers will not send more than two simultaneous HTTP requests to the same domain - with multiple domains for the same server, you can better saturate the network and receive the maps faster.
158
135
159
136
Performance
160
137
-----------
161
138
162
-
In case the data are available in a form of directory with XYZ tiles, then
163
-
Apache webserver is serving these files directly as WMTS RESTful or KVP.
139
+
In case the data are available in the form of a directory with XYZ tiles, then the Apache webserver is serving these files directly as WMTS RESTful or KVP.
164
140
165
-
This means performance is excellent, maps are delivered very fast and large
166
-
number of concurrent visitors can be handled even with quite a low-end
167
-
hardware or cheap/free web hosting providers.
141
+
This means performance is excellent, maps are delivered very fast, and a large number of concurrent visitors can be handled even with quite low-end hardware or cheap/free web hosting providers.
168
142
169
-
Mod_rewrite rules are utilized to ensure the HTTP requests defined in the OCG
170
-
WMTS standard are served, and Apache preserve standard caching headers & eTag.
143
+
Mod_rewrite rules are utilized to ensure the HTTP requests defined in the OCG WMTS standard are served, and Apache preserves standard caching headers & eTag.
171
144
172
-
The performance should be significantly better then performance of any other
173
-
tile caching project (such as TileCache.org or GeoWebCache).
145
+
The performance should be significantly better than any other tile caching project (such as TileCache.org or GeoWebCache).
174
146
175
-
Performance graph for "apache static" comparing other tile caching projects
Performance graph for "apache static" comparing other tile caching projects is available online at http://code.google.com/p/mod-geocache/wiki/PreliminaryBenchmark
178
148
179
149
Limits of actual implementation
180
150
-------------------------------
181
151
182
-
With intention, in this moment the project supports only:
152
+
With intention, at this moment, the project supports only:
183
153
- We enforce and require XYZ (top-left origin) tiling schema (even for TMS).
184
154
185
155
Password protection
@@ -210,22 +180,19 @@ TileServer.php can run without any problems over HTTPS, if required.
210
180
Microsoft Windows web-hosting
211
181
-----------------------------
212
182
213
-
The TileServer.php should run on Windows-powered webservers with Apache
214
-
installation if PHP 5.2+ and mod_rewrite are available.
183
+
The TileServer.php should run on Windows-powered webservers with Apache installation if PHP 5.2+ and mod_rewrite are available.
215
184
216
-
With the IIS webserver hosting, you may need PHP and IIRF module
217
-
(http://iirf.codeplex.com/) and alter appropriately the rewrite rules.
185
+
With the IIS webserver hosting, you may need PHP and IIRF module (http://iirf.codeplex.com/) and alter appropriately the rewrite rules.
218
186
219
187
Credits / Contributors
220
188
----------------------
221
189
222
-
Project developed initially by Klokan Technologies GmbH, Switzerland in
223
-
cooperation with National Oceanic and Atmospheric Administration - NOAA, USA.
190
+
Project developed initially by Klokan Technologies GmbH, Switzerland, in cooperation with National Oceanic and Atmospheric Administration - NOAA, USA.
224
191
225
-
- Petr Pridal - Klokan Technologies GmbH <petr.pridal@klokantech.com>
192
+
- Petr Pridal - Klokan Technologies GmbH <petr.pridal@maptiler.com>
0 commit comments