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 Medway

The council of Medway have provided me with a zip file that has MapInfo files that has the details of their public rights of way. The MapInfo files seem to have been created on 1st December 2021. When I requested an update both in December 2022 and in February 2024 I was informed that "the information that we would provide to you has not changed since we last provided it".

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.

The council of Medway have informed me that the MapInfo files are made available under Open Government Licence v3.0. So it's possible for you to use this data provided you give the attribution that the data has been provided by the council of Medway.

Elsewhere on this web site, there is a web page about how this web site provides the public rights of way of Medway 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:
ME||RR26
There are three parts to the name: "ME" (meaning "Medway"), the id of the parish/community and the id of the path within the parish/community.
The description will be something like:
Fo|ME:1|0.232|none|0.48376|51.37254|0.48094|51.37540|572974,166648|572767,166959
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 Medway;
GeoJSON file for bridleways in Medway;
GeoJSON file for restricted byways in Medway;
GeoJSON file for byways open to all traffic in Medway.

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 04E513Fo.json contains details about the Footpaths that are partly/wholly in the square that is east and north of 0.4 degrees longitude and 51.3 degrees latitude.
Here is a link to a zip file containing all the smaller GeoJSON files for Medway.

The latitude values for Medway range from 51.32 to 51.48. And the longitude values range from 0.39 to 0.72.