logo for rowmaps web site rowmaps

these web pages
are being produced by
Barry Cornelius

rowmaps@gmail.com
Follow me at http://twitter.com/rowmaps

home

maps
preferences

original data
missing data
KMLs
GPXs
CSVs
GeoJSONs

using Organic Maps
app on a phone 
and getting it to
display rights of way


problems
links
posters

tweets
blog
contact
privacy

2022-08-11-1251

GeoJSON files containing the public rights of way of Kent

The council of Kent has provided me with an ESRI shape file that has the details of their public rights of way. The ESRI shape file was created on 25th April 2023. I have bundled the files of the ESRI shape file into a zip file. The Council also provides information about public rights of way on its online map. It may be that their map uses more up-to-date information.

An authority's Definitive Map is the authoritative source of their rights of way. The details of the public rights of way network contained in an authority's data are for information only, and are an interpretation of the Definitive Map, not the Definitive Map itself, and should not be relied on for determining the position or alignment of any public right of way. For legal purposes, an authority's data does not replace their Definitive Map. And changes may have been made to the Definitive Map that are not included in their data. The authority's data contains Ordnance Survey data © Crown copyright and database right 2024. Attempting to view this data with more detail than 1:10000 may produce an inaccurate rendering of the route of a public right of way.

In their reply, the Council also provide a PDF file that says the data is made available under the Open Government Licence v3.0. It also says "We ask that the user of the data acknowledges that this information contains OS derived data using the attribution statement: 'Contains OS data © Crown copyright and database rights 2022'".

Elsewhere on this web site, there is a web page about how this web site provides the public rights of way of Kent in KML format. That web page explains how I've augmented the basic KML with additional information.

I've converted this augmented KML into GeoJSON. Besides giving the longitudes and latitudes of the route of a public right of way, each entry in the GeoJSON also has a name and a description.
The name will be something like:
KT|SR|666
There are three parts to the name: "KT" (meaning "Kent"), the id of the parish/community and the id of the path within the parish/community.
The description will be something like:
Fo|KT:2130|0.208|333|0.09310|51.14979|0.09312|51.14681|546491,141030|546502,140699
This gives other information about the public right of way. First, there is a two letter code giving its type which is one of Fo (meaning Footpath), Br (meaning Bridleway), Re (meaning Restricted byway) and BO (meaning Byway open to all traffic). Following this code, there are a unique name, the length in miles, any additional information obtained from the data supplied by the authority (or none), the longitude of its first point, the latitude of its first point, the longitude of its last point, the latitude of its last point, the eastings and northings of its first point and the eastings and northings of its last point.

The following GeoJSON files are available:
GeoJSON file for footpaths in Kent;
GeoJSON file for bridleways in Kent;
GeoJSON file for restricted byways in Kent;
GeoJSON file for byways open to all traffic in Kent.

Because some of these GeoJSON files are large, the GeoJSON is also available in a large number of smaller files. Each smaller file has information about public rights of way that are in a square that is 0.1 degrees longitude wide and 0.1 degrees latitude high. For example, the file 00E511Fo.json contains details about the Footpaths that are partly/wholly in the square that is east and north of 0.0 degrees longitude and 51.1 degrees latitude.
Here is a link to a zip file containing all the smaller GeoJSON files for Kent.

The latitude values for Kent range from 50.91 to 51.47. And the longitude values range from 0.03 to 1.44.