PageSourceSearch

https://www.geoplaner.com/

html geoplaner.com collected 2026-10-02 07:00:35 UTC 24,281 bytes, 429 lines download raw bytes

1<!DOCTYPE html>
2<html lang="en">
3<head>
4<meta content="text/html; charset=ISO-8859-1" http-equiv="content-type">
5<meta name="viewport" content="width=device-width, user-scalable=no, initial-scale=1.0, minimum-scale=1.0, maximum-scale=1.0">
6<meta name="apple-mobile-web-app-capable" content="yes">
7<meta name="format-detection" content="telephone=no">
8<meta content="Nathansen" name="author">
9<meta content="Free web-based application that provides several GIS and GPS utilies: coordinate finder, UTM-Lat/Lon converter, Geocoding, elevations, waypoint editor and route planner, gpx-file import and export." name="description">
10<meta content="Global Positioning System, GPS, UTM, route planner, Longitude, Latitude, GoogleMaps, Open Street Map, OSM, GoogleEarth, Geocoder, Geoplaner, GeoCaching" name="keywords">
11<meta content="index,follow" name="robots">
12<meta name="content-language" content="en">
13<link rel="alternate" hreflang="de" href="https://www.geoplaner.de/">
14<link rel="alternate" hreflang="en" href="https://www.geoplaner.com/">
15<link rel="apple-touch-icon-precomposed" href="zzpic/geoplaner-icon.png">
16<title>GPS Geoplaner - GeoConverter | Routeplanner online</title>
17<link media="screen" href="zzco/style1gp9.css" type="text/css" rel="stylesheet">
18<link media="screen" href="zzco/base64.css" type="text/css" rel="stylesheet">
19<link media="screen" href="zzco/leaflet.css" type="text/css" rel="stylesheet">
20<link media="screen" href="zzco/Control.FullScreen.css" type="text/css" rel="stylesheet">
21<!-- 
21<script type="text/javascript" src="https://maps.google.com/maps/api/js?key=AIzaSyAv5mn7wj5dgxkjq875dLkX6YU9N76gpfw&sensor=false"></script>
21 -->
22<script type="text/javascript" src="zzco/jscoord-1.1.1.js"></script>
vendor: 2 bytes, line 22
22
23<script type="text/javascript" src="zzco/leaflet.js"></script>
vendor: 2 bytes, line 23
23
24<script type="text/javascript" src="zzco/Control.Geocoder.min.js"></script>
vendor: 2 bytes, line 24
24
25<script type="text/javascript" src="zzco/Control.FullScreen.js"></script>
vendor: 2 bytes, line 25
25
26<script type="text/javascript" src="zzco/Leaflet.Icon.Glyph.js"></script>
vendor: 2 bytes, line 26
26
27<script type="text/javascript" src="zzco/gpso32.js"></script>
27
28</head>
29<body>
30<div id="geoplaner">
31<iframe id="upload_target" name="upload_target" src="zzco/blank.html"></iframe>
32<form name="gf" action="https://www.geoplaner.com/zzco/gpcom27.php" method="post" enctype="multipart/form-data" target="upload_target" onsubmit="0">
33<p id="lang">Geoplaner V3.2 - [ in English | <a href="https://www.geoplaner.de/" title="Geoplanner auf Deutsch">auf deutsch</a> ]</p>
34<div id="tleft">
35<div class="td50">
36<div class="geo1 td1">
37<div class="pline1"><b>dd.ddddd&deg;</b></div>
38<div class="pline1">
39<input class="etxt ell" size="8" maxlength="9" readonly="readonly" value="Latitude:" type="text">
40<input class="etxt e10" name="da1" size="10" maxlength="10" tabindex="8" onkeyup="gp.hkr(2)" type="text">&deg;N
41</div>
42<div class="pline1">
43<input class="etxt ell" size="8" maxlength="9" readonly="readonly" value="Longitude:" type="text">
44<input class="etxt e10" name="do1" size="10" maxlength="10" tabindex="9" onkeyup="gp.hkr(2)" type="text">&deg;E
45</div>
46<div class="pline1">
47<input class="butt" value="ok" title="Lat/Long - decimal degrees" onclick="gp.hhgeo(1)" tabindex="10" type="button">
48</div>
49</div>
50<div class="utm td1">
51<div class="pline1"><b>UTM</b> &nbsp; &nbsp;
52<select name="he" tabindex="3" title="northern or southern hemisphere">
53<option value="N">N</option>
54<option value="S">S</option>
55</select> Hemis.
56</div>
57<div class="pline1">
58<input class="etxt e2" name="zn" size="2" maxlength="2" tabindex="4" onkeyup="gp.hkr(1)" title="UTM zone number" type="text">
59<input class="etxt e1" name="zl" size="1" maxlength="1" readonly="readonly" type="text">
60<input class="etxt e8" name="ea" size="8" maxlength="10" tabindex="5" onkeyup="gp.hkr(1)" title="easting" type="text"> x-ea.
61</div>
62<div class="pline1">
63<input class="etxt e2h" size="2" maxlength="2" readonly="readonly" type="text">
64<input class="etxt e1" size="1" maxlength="1" readonly="readonly" type="text">
65<input class="etxt e8" name="no" size="8" maxlength="10" tabindex="6" onkeyup="gp.hkr(1)" title="northing" type="text"> y-no.
66</div>
67<div class="pline1">
68<input class="butt" value="ok" title="convert UTM to Latitude / Longitude" onclick="gp.hhutm()" tabindex="7" type="button">
69</div>
70</div>
71<div class="adr td2a">
72<div class="pline2">
73<b>postal address </b><i>or&nbsp;</i><b> point of interest (poi)</b> &nbsp;
74<input class="butt3" title="reverse geocoding - convert geographic position to address" onclick="gp.hrg()" value="--&gt;" tabindex="30" type="button">
75</div>
76<div class="pline2">
77<input class="e80adr" name="ad" size="45" maxlength="100" tabindex="31" onkeyup="gp.hkr(5)" type="text">&nbsp;
78<input class="butt3" value="ok" onclick="gp.hhadr()" tabindex="32" title="geocoding - convert address to geographic position" type="button">
79</div>
80</div>
81</div>
82<div class="td50">
83<div class="geo2 td1">
84<div class="pline1"><b>dd&deg; mm.mmm'</b></div>
85<div class="pline1">
86<input class="etxt e3" name="da2" size="3" maxlength="3" tabindex="11" onkeyup="gp.hkr(3)" type="text">&deg; 
87<input class="etxt e6" name="ma2" size="6" maxlength="6" tabindex="12" onkeyup="gp.hkr(3)" type="text">'
88<select name="la2" tabindex="13" title="northern or southern latitude">
89<option value="N">N</option>
90<option value="S">S</option>
91</select>
92</div>
93<div class="pline1">
94<input class="etxt e3" name="do2" size="3" maxlength="3" tabindex="14" onkeyup="gp.hkr(3)" type="text">&deg;
95<input class="etxt e6" name="mo2" size="6" maxlength="6" tabindex="15" onkeyup="gp.hkr(3)" type="text">'
96<select name="lo2" tabindex="16" title="eastern or western longitude">
97<option value="E">E</option>
98<option value="W">W</option>
99</select>
100</div>
101<div class="pline1">
102<input class="butt" value="ok" title="Lat/Long - degrees, decimal minutes" onclick="gp.hhdmm()" tabindex="17" type="button">
103</div>
104</div>
105<div class="geo3 td1">
106<div class="pline1"><b>dd&deg; mm' ss.s''</b></div>
107<div class="pline1">
108<input class="etxt e3" name="da3" size="3" maxlength="3" tabindex="18" onkeyup="gp.hkr(4)" type="text">&deg;
109<input class="etxt e2" name="ma3" size="2" maxlength="2" tabindex="19" onkeyup="gp.hkr(4)" type="text">'
110<input class="etxt e4" name="sa3" size="4" maxlength="4" tabindex="20" onkeyup="gp.hkr(4)" type="text">''
111<select name="la3" tabindex="21" title="northern or southern latitude">
112<option value="N">N</option>
113<option value="S">S</option>
114</select>
115</div>
116<div class="pline1">
117<input class="etxt e3" name="do3" size="3" maxlength="3" tabindex="22" onkeyup="gp.hkr(4)" type="text">&deg;
118<input class="etxt e2" name="mo3" size="2" maxlength="2" tabindex="23" onkeyup="gp.hkr(4)" type="text">'
119<input class="etxt e4" name="so3" size="4" maxlength="4" tabindex="24" onkeyup="gp.hkr(4)" type="text">''
120<select name="lo3" tabindex="25" title="eastern or western longitude">
121<option value="E">E</option>
122<option value="W">W</option>
123</select>
124</div>
125<div class="pline1">
126<input class="butt" value="ok" title="Lat/Long - degrees, minutes, seconds" onclick="gp.hhdms()" tabindex="26" type="button">
127</div>
128</div>
129<div class="ele td2b">
130<div class="pline2">
131<b class="pline2title">W3C/Browser -> Geolocation</b>
132</select>
133</div>
134<div class="pline2">
135<input class="buttlarge" value="my position" onclick="gp.hip()" tabindex="33" title="get my Geolocation" type="button">
136</div>
137</div>
138<div class="let td2b">
139<div class="pline2">
140<input class="e10edit" readonly="readonly" size="10" name="wn">
141<input class="butt3" value="edit" title="edit waypoint title/name" onclick="gp.hwe()" type="button">
142</div>
143<div class="pline2">
144<input class="butt2" value="&lt;&lt;" onclick="gp.hhfoc(-1000)" type="button"><input class="butt2" value="&lt;" onclick="gp.hhfoc(-1)" type="button">
145<input class="e4wpt" readonly="readonly" size="4" name="wl">
146<input class="butt2" value="&gt;" onclick="gp.hhfoc(1)" type="button"><input class="butt2" value="&gt;&gt;" onclick="gp.hhfoc(1000)" type="button">
147</div>
148</div>
149</div>
150<div id="map_canvas"> </div>
151<div id="map_copyright">Maps &copy; 2019 <a href="https://wiki.openstreetmap.org/wiki/Main_Page" target="_blank" onfocus="this.blur()"> OpenStreetMap</a>&nbsp;<a href="https://creativecommons.org/licenses/by-sa/2.0/" target="_blank" onfocus="this.blur()">CC-BY-SA</a> -
152</div>
153</div>
154<div id="tright">
155<div class="pline1"><b>POI / WPT / Waypoints</b></div>
156<div id="dt"> </div>
157<div id="btns">
158<a id="Linkage"></a>
159<input class="buttlarge" name="wb" title="remove single waypoint" value="remove WPT" onclick="gp.hcw()" type="button">
160<input class="buttlarge" title="remove all waypoints (RESET)" value="remove all WPTs" onclick="gp.hhcl()" type="button"><br>
161<input class="buttlarge" name="hwd" title="export waypoints as GPX-waypoint list" value="download WPTs" onclick="gp.hwd(this)" type="button">
162<input class="buttlarge" name="hrd" title="export waypoints as GPX-route" value="download Route" onclick="gp.hrd(this)" type="button"><br>
163<input class="buttfile" name="smf" accept="text/*" maxlength="1048576" title="select GPX-file for upload" type="file"><br>
164<input class="buttlarge" name="hwu" value="upload WPTs" title="import GPX-file with waypoints (routes and tracks will be ignored)" onclick="gp.hwu(this,1)" type="button">
165<input class="buttlarge" name="hru" value="upload Route" title="import GPX-file with route (waypoints and tracks will be ignored)" onclick="gp.hwu(this,2)" type="button"><br>
166<input name="sfb" type="hidden"><input name="swc" value="---" type="hidden"><input name="sfm" value="undef" type="hidden"><input name="sid" value="0" type="hidden"><input name="lng" value="en" type="hidden"><input name="elevation" value="disabled" type="hidden"><input class="e15ele" name="el" size="15" readonly="readonly" type="hidden">
167</div>
168</div>
169</form>
170</div>
171<div id="nav">
172<a href="#Linkage">Link Creator</a> | <a href="#GoogleMaps-OSM">GoogleMaps/OSM</a> | <a href="#Coordinate-Converter">Coordinate Converter</a> | <a href="#Geocoding">Geocoding</a> | <a href="#Route-Planner">Route Planner</a> | <a href="#Accuracy">Accuracy</a> | <a href="#Changelog">Changelog</a> | <a href="https://www.geoplaner.com/zzco/">Terms of Use</a>
173</div>
174<div id="content">
175<div class="linkbx">
176<p class="linkhl"><b>Link Creator &#8722;&gt; Geoplaner URL + waypoints (latitude, longitude, name (optionally))</b></p>
177<p class="linkp">1)&nbsp; With the help of the Geoplaner, add and edit the waypoints which should be included into the link.</p>
178<p class="linkp">2)&nbsp; Should the waypoint title/names also be included (increases the link length)? &nbsp; <input id="llcb"
179value="include WPT names" type="checkbox"> <b>yes</b></p>
180<p class="linkp">3)&nbsp; Click here <b>&#8722;&gt;</b> <input class="buttlarge linkbt" id="hpl" title="create link to geoplaner"
181value="create link" onclick="gp.hlc(this)" type="button"></p>
182<input id="llgp" onclick="this.select()" size="1000">
183<p id="llpv"> </p>
184<p class="linkp">4)&nbsp; Copy the link with "<b>Ctrl+C</b>" and paste it with "<b>Ctrl+V</b>" to the destination.</p>
185</div>
186<a class="ctop2" href="#"><i class="top"> </i></a>
187<h1>Geoplaner - Info / Help</h1>
188<p>The <b>Geoplaner</b> ( <b>Geo</b>Converter +
189Route<b>plan</b>[n]<b>er</b> ) provides several GIS and GPS
190utilities in a single web-based application:</p>
191<ul>
192<li><a href="#GoogleMaps-OSM">Coordinate Finder</a> - find
193locations worldwide with OpenStreetMap and Nominatim</li>
194<li><a href="#GoogleMaps-OSM">Altitude / Elevations</a>&nbsp; -
195retrieve SRTM elevations of any location</li>
196<li><a href="#Coordinate-Converter">UTM to Latitude / Longitude
197Converter</a> - and vice versa</li>
198<li><a href="#Coordinate-Converter">Latitude / Longitude
199Converter</a> - convert between three notations</li>
200<li><a href="#Geocoding">Geocoding</a> - address to Latitude /
201Longitude converter</li>
202<li><a href="#Geocoding">Reverse Geocoding</a> - Latitude /
203Longitude to address converter</li>
204<li><a href="#Route-Planner">GPS Waypoint &amp; Route Planner</a> -
205create GPS waypoints and routes</li>
206<li><a href="#Route-Planner">Import / Export GPS - Data</a> -
207upload and download *.gpx-Files</li>
208</ul>
209<a class="ctop" href="#"><i class="top"> </i></a>
210<h2><a id="GoogleMaps-OSM" name="GoogleMaps-OSM"></a>Coordinate
211Finder</h2>
212<p><b>Operating OpenStreetMap by mouse click:</b> Change the map
213type between<b>&nbsp;</b> <b><a href=
214"https://www.openstreetmap.org">OpenStreetMap</a></b>, <b><a href=
215"https://opentopomap.org/">OpenTopoMap</a></b>, <b><a href=
216"https://wiki.openstreetmap.org/wiki/Hike_%26_Bike_Map">HikeBike</a></b>,
217<b><a href="https://www.cyclosm.org/">CyclOSM</a></b> or
218<b><a href="https://wiki.openstreetmap.org/wiki/Esri">WorldImagery</a></b>;
219move the visible map section and zoom in and out the map.
220Furthermore there are buttons for browsing through the waypoint
221list, removing single or all waypoints and editing GPS waypoint
222titles/names.</p>
223<p><b>Coordinates or GPS waypoints can be created by:</b></p>
224<ul>
225<li><b>mouse click:</b> Create a new waypoint by clicking with the
226<i>left mouse button</i> on the desired position on map. Select an
227existing waypoint by clicking on it, or move the waypoint. Remove a
228waypoint by pressing the <i>"remove..."-button</i>.</li>
229<li><b>coordinate input:</b> Manually input of coordinates in UTM
230format: hemisphere, UTM zone, easting, northing; <i>or</i> Latitude
231and Longitude with three possible notations: decimal degrees:
232dd.ddddd&deg; degrees, decimal minutes: dd&deg; mm.mmm' degrees,
233minutes, seconds: dd&deg; mm' ss.s''</li>
234<li><b>address search (Geocoding):</b> Search for postal addresses:
235country, city, street no. <i>or</i>&nbsp; POI: hilltop, lake, town,
236island. Check the correctness of the location by reverse geocoding
237by pressing the <i>"--&gt;" - button</i>.</li>
238<li><b>gpx-file import:</b> Import coordinates as list of waypoints
239or GPS route by selecting a *.gpx file on your PC and uploading it.
240Press <i>"upload WPTs"-button</i> for importing GPS waypoints and
241<i>"upload Route"-button</i> for importing a GPS route.</li>
242</ul>
243<p><b>Elevation:</b> The Geoplaner automatically retrieves and
244includes the altitude or sea depth when creating a new waypoint.
245<s>The elevations are delivered by Google's elevation service.</s>
246The new Google-free elevation service is coming soon...</p>
247<a class="ctop" href="#"><i class="top"> </i></a>
248<h2><a id="Coordinate-Converter" name=
249"Coordinate-Converter"></a>UTM - Latitude / Longitude Converter
250(WGS84)</h2>
251<p>The Geoplaner converts <b><a href=
252"https://en.wikipedia.org/wiki/Universal_Transverse_Mercator_coordinate_system"
253target="_blank">UTM</a></b> (Universal Transverse Mercator) and
254<b>Latitude &amp; Longitude</b> coordinates. The coordinate
255converter is based on <b><a href="http://www.jstott.me.uk/jscoord/"
256target="_blank">JScoord V1.1.1.</a></b> The datum or reference
257ellipsoid is <b><a href=
258"https://en.wikipedia.org/wiki/World_Geodetic_System" target=
259"_blank">WGS 84</a></b> (World Geodetic System 1984). The input of
260UTM coordinates includes:</p>
261<ul>
262<li><b>hemisphere</b> (northern or southern),</li>
263<li><b>UTM zone</b> (zone number),</li>
264<li><b>easting</b> (x direction) <i>and</i></li>
265<li><b>northing</b> (y direction).</li>
266</ul>
267<p>Geographical coordinates: Longitude and Latitude can be entered
268in three different notations:</p>
269<ul>
270<li>decimal degrees: <b>dd.ddddd&deg;</b></li>
271<li>degrees, decimal minutes: <b>dd&deg; mm.mmm'</b></li>
272<li>degrees, minutes, seconds: <b>dd&deg; mm' ss.s''</b></li>
273</ul>
274<p>All formats or notations are converted into each other.</p>
275<a class="ctop" href="#"><i class="top"> </i></a>
276<h2><a id="Geocoding" name="Geocoding"></a>Geocoding - address
277search: postal address or POI</h2>
278<p><b>Geocoding:</b> The Geoplaner accepts <b>postal addresses</b>
279such as "state, city, street" or <b>POI</b> such as hilltops,
280lakes, cities and important places. However the returned geographic
281location are not always correct: Whereas the postal address lookup
282mostly returns correct locations, there are sometimes problems with
283the POI search, when the address string corresponds to several
284locations. So you should always check the search result on the map.
285If it is wrong, search for a more common POI or place nearby and
286then look for your POI on the map from there.</p>
287<p><b>Reverse Geocoding:</b> It might be also helpful to check the
288location by Reverse Geocoding (provided by
289OpenStreetMap/Nominatim). The reverse geocoder accepts geographic
290coordinates as input and returns a postal address. Just press the
291<b>"--&gt;"</b> - button to trigger reverse geocoding.</p>
292<a class="ctop" href="#"><i class="top"> </i></a>
293<h2><a id="Route-Planner" name="Route-Planner"></a>GPS route
294planner | tour planner</h2>
295<p>The Geoplaner / Route Planner provides basic route planner
296functions for creating GPS routes suitable for outdoor or street
297navigation with outdoor GPS receivers. Auto-routing is not
298supported, however you can map out GPS routes by mouse clicks
299manually. When creating a route for street navigation <i>GoogleMaps
300- "map</i>" is most suitable, whereas for walking tours or hiking
301<i>Open Street Map - "OSM"</i> is more convenient. Open Street Map
302contains many hiking trails and tracks, especially in touristic
303areas and mountains and is constantly being completed.</p>
304<p>The route planner internally buffers the coordinates as a list
305of single waypoints. However when downloading them you can
306optionally choose a waypoint download or a route download. This is
307important for transferring the waypoints or route to a GPS receiver
308afterwards. When uploading a GPX-File you can likewise choose
309whether you want to upload a route or a list of waypoints. The
310route planner converts GPS routes automatically into a GPS waypoint
311list. GPS track uploads are not supported yet. When uploading or
312downloading files no data or files are stored on the route planner
313server</p>
314<p><b>Export/Download:</b> After creating the route by setting
315several waypoints along the trail press the <i>"download Route"
316-button</i> and store the "route.gpx" - file on your PC. Then
317transfer "route.gpx" to your outdoor GPS receiver via Garmin
318MapSource or a GPS freeware, or directly save the file on the
319SD-Memorycard of your receiver.</p>
320<p><b>Import/Upload:</b> It is also possible to upload and edit
321existing GPS routes or to convert GPS routes into GPS waypoint
322lists and vice versa. When uploading waypoints or routes the route
323planner does not import elevations. However when scrolling or
324clicking through the waypoint list the Google elevation service
325will add the elevation values and the route planner automatically
326includes them for the gpx-file download.</p>
327<a class="ctop" href="#"><i class="top"> </i></a>
328<h2><a id="Accuracy" name="Accuracy"></a>Accuracy of coordinates
329and heights</h2>
330<h3>Accuracy of GoogleMaps</h3>
331<p>Most of the Google Maps are prepared from <a target="_blank"
332href="https://en.wikipedia.org/wiki/Landsat_7">Landsat-7 satellite
333images</a>. Landsat-7 was launched in April 1999 and is an Earth
334observation satellite of the U.S. National Aeronautics and Space
335Administration (NASA). <a target="_blank" href=
336"https://en.wikipedia.org/wiki/Google_Earth#Imagery_and_coordination">
337The accuracy of the derived Google Maps / Google Earth vector data
338varies from 0.1m in urban areas to 15m in the Antarctica.</a> The
339derived Coordinates are rounded by the Geoplaner to a precision of
3401m.</p>
341<h3>Accuracy of OpenStreetMap</h3>
342<p>The accuracy of OpenStreetMap is partially lower than of
343GoogleMaps. Especially OSM country roads and walking trails can
344have deviations of 10m or more. The reason for this is, that most
345of the OSM data is recorded by volunteers with their GPS receivers
346and afterwards uploaded to the OSM database. Depending on their GPS
347receivers and the reception conditions the accuracy of the recorded
348tracks varies between 3m and 30m. The accuracy of most OSM city
349maps, however is significantly higher and is comparable with the
350accuracy of Google Maps.</p>
351<h3>Elevation accuracy</h3>
352<p>The elevation values are provided by the <s>Google Elevation
353Service</s> Geoplaner elevation server (which is coming soon). The
354raw data for that were originally&nbsp; obtained during the
355<a target="_blank" href=
356"https://en.wikipedia.org/wiki/Shuttle_Radar_Topography_Mission">Shuttle
357Radar Topography Mission (SRTM)</a>: The freely available SRTM data
358consists of SIR-C data from NASA and X-SAR data of the German
359Aerospace Center (DLR). <a target="_blank" title=
360"https://de.wikipedia.org/wiki/SRTM-Daten#Erfassung_der_Daten:_SIR-C.2C_X-SAR"
361href=
362"https://de.wikipedia.org/wiki/SRTM-Daten#Erfassung_der_Daten:_SIR-C.2C_X-SAR">
363The SIR-C data have a height accuracy of about 6m on at a
364horizontal resolution of about 30m</a>. The X-SAR data should
365indeed have a higher accuracy up to 1m, but cover only 40% of the
366earth's surface.</p>
367<a class="ctop" href="#"><i class="top"> </i></a>
368<h2><a id="Changelog" name="Changelog"></a>Changelog</h2>
369<h3>2023/08/27 - GPS Geoplaner V3.2</h3>
370<p>Changing tile URLs from "https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png" to "https://tile.openstreetmap.org/{z}/{x}/{y}.png"</p>
371<h3>2020/10/18 - GPS Geoplaner V3.1</h3>
372<p>URL/link creator and HTML5 browsercache improvements: map type included and maximum number of waypoints increased to 100.</p>
373<h3>+++ Oct./Nov. 2019 - GPS Geoplaner V3.0 +++</h3>
374<p>+++ Replacing the overpriced GoogleMaps API with the free <a target=
375"_blank" href="https://leafletjs.com/">open-source JavaScript library Leaflet</a> +++</p>
376<h3>2017/08/26 - GPS Geoplaner V2.8</h3>
377<p>a) HTTPS enabled with <i>Let's Encrypt</i>. b) OpenStreetMap
378checkbox added to the link creator.</p>
379<h3>2014/12/06 - GPS Geoplaner V2.7</h3>
380<p>Maximum number of uploadable waypoints increased to 2000.</p>
381<h3>2014/02/05 - GPS Geoplaner V2.6</h3>
382<p>New feature added which allows to create links composed of the
383Geoplaner-<wbr>URL and up to 24 waypoints (latitude, longitude,
384name) as URL-<wbr>parameters.</p>
385<h3>2013/03/22 - GPS Geoplaner V2.5</h3>
386<p>a) Graphical user interface improved, better scaling due to the
387screen size. b) HTML5 Caching introduced.</p>
388<h3>2011/12/05 - GPS Geoplaner V2.4</h3>
389<p>a) Easier input of UTM coordinates with delimitors, e.g.:
390"5.865.883". b) Maximum number of uploadable waypoints increased to
391500.</p>
392<h3>2010/10/20 - Geoplaner V2.3</h3>
393<p>a) Google Street View enabled. b) Minor improvements: file
394upload, waypoint deletion, address input.</p>
395<h3>2010/08/18 - Geoplaner V2.2</h3>
396<p>a) Implementation of reverse geocoding, triggered by pressing
397the <b>"--&gt;"</b> - button. Reverse geocoder (Google) translates
398waypoints (coordinates) into postal addresses. b) Elevation output
399alternatively in "m" or "ft".</p>
400<h3>2010/07/01 - Geoplaner V2.1b</h3>
401<p>Performance improvements when uploading large gpx-files: The
402file upload or rather the data import into the browser is realised
403by javascript asynchronously.</p>
404<h3>2010/06/29 - GPS Geoplaner V2.1a - UTM-Lat/Lon converter &amp;
405route planner</h3>
406<p>Improvement of address and POI search: The address of the
407position delivered by Google-GeoCoder is displayed for
408verification. This is helpful when using the Geoplaner as route
409planner.</p>
410<h3>2010/06/22 - GPS Geoplaner V2.1 - UTM-Lat/Lon converter &amp;
411route planner</h3>
412<p>First version in English. The Geoplaner combines coordinate
413converter and route planner functions.</p>
414<a class="ctop" href="#"><i class="top"> </i></a>
415<p>&nbsp;</p>
416<p>&nbsp;</p>
417</div>
418<div id="footer">
419<p style="float:left;">&copy; 2009-2023 <a href=
420"https://nathansen.de/">Martin Nathansen</a></p>
421<p style="float:right;"><a rel="nofollow" href=
422"https://www.geoplaner.com/zzco/">Terms of Use &amp; Privacy
423Policy</a><br clear="all"></p>
424</div>
425<img src="https://xipa.de/co/pic/stat.php">
426<img id="iwpx" src="https://www.geoplaner.com/wpt.png" alt="wpt">
427</body>
428</html>
429

Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.