This blog is part of a series about my first steps in using Spatial Data in the Oracle database. I am using the GPS data from my cycling activities collected by Strava. All of my files are available on GitHub.
The next stage is to use my Strava data as a resource for ride planning. For example, I want to go for a ride in the Chilterns this weekend, I want to look at previous rides in the Chilterns to see where I have gone. This presents a number of challenges that I will cover over the next few blogs.
- I need a working definition of the Chilterns.
- I need to identify which activities entered the area defined as being the Chilterns.
More generically, I might be interested in any area in any country. I need to be able to search for areas by name, then identify the activities that passed through these areas.
Geographical Areas
The world is divided up into 206 sovereignties (including independent and leased areas), and those are then divided down. Let's take the United Kingdom as an example:
United Kingdom
.England
.Northern Ireland
.Scotland
.Wales
.Guernsey
..Alderney
..Guernsey
..Herm
..Sark
.Isle of Man
.Jersey
.Anguilla
.Bermuda
.Cayman Islands
.Dhekelia Sovereign Base Area
.Falkland Islands
.Gibraltar
.British Indian Ocean Territory
..Diego Garcia Naval Support Facility
.Montserrat
.Pitcairn Islands
.South Georgia and the Islands
..South Georgia
..South Sandwich Islands
.Saint Helena
..Ascension
..Saint Helena
..Tristan da Cunha
.Turks and Caicos Islands
.British Virgin Islands
Akrotiri Sovereign Base Area
- The United Kingdom consists of the 4 'home' countries.
- These are divided down into counties, authorities, districts, boroughs, wards and parishes.
- Guernsey, Jersey and the Isle of Man are "Crown Dependencies".
- There are 14 dependent territories
- Some of these are broken down further into separate islands.
I need enough areas to allow me to effectively search areas by name and then determine which activities are in which areas.
To return to the original question, the Chiltern Hills are not a government administrative area but are designated as an Area of Outstanding Natural Beauty (AONB). As, they are a useful shorthand to describe some areas where I regularly cycle, so I have included them in the heirarchy.
Loading Spatial Data from Esri Shapefile
Lots of geographical data is publically available from a variety of organisations and governments in the form of shapefiles. This is "Esri's somewhat open, hybrid vector data format using SHP, SHX and DBF files. Originally invented in the early 1990s, it is still commonly used as a widely supported interchange format". Oracle provides a java shapefile converter that transforms shapefiles into database tables.
See also:
- ESRI Shapefile Technical Description
- Wikipedia: Shapefile
- Oracle Database 19c Developers Guide: Loading ESRI Shapefiles into Spatial and Graph
Shapefiles are zip archives that contain a number of files, including but not limited to the following, but containing at least always the first three:
- .shp - the main file that contains the geometry itself,
- .shx - an index file,
- .dbf - a DBase file containing other attributes to describe the spatial data. When you load the shapefile, the DBF file is loaded into all the other columns in the table. This file can be opened with Microsoft Excel so you can see the data,
- .prj - contains the projection description of the data,
- .csv -the same data as in the .dbf file, but as a comma-separated data file,
- .cpg - the code page of the data in the .dbf file.
A little searching with Google turned up a number of useful sources of publically available spatial data (although most of it requires to be licenced for commercial use).
- Natural Earth: 1:10m cultural vectors - countries/sovereign states of the World
- DIVA-GIS - Administrative areas for various countries
- UK
- Ordnance Survey: Boundary-Line - administrative boundaries in Great Britain
- Spatial Hub: Scottish Community Council Boundaries
- Department for the Environment, Food & Rural Affairs: Natural England, Areas of Outstanding Natural Beauty (AONB)
Most of the shapefiles provide data in latitude/longitude in WGS84 that corresponds to SRID 4326. However, the data from the UK government and the Ordnance Survey uses the British National Grid (BNG) GCS_OSGB_1936. This corresponds to SRID 27700 (see Convert GPX Track to a Spatial Line Geometry).
By default, the shapefile converter creates geometries in the coordinate system provided by the shapefile. It is possible to specify a different coordinate system at load time, however, converting the data significantly slows the load process (my experience is that it increases load duration by about a factor of approximately 5).
The spatial data is loaded into a geometry column called geom by default. However, the column name can be specified.
Later when it comes to comparing spatial data, you can only compare geometries that have the same SRID. Therefore, it is important to know the coordinate system of the data with which you are dealing. My convention is to put WGS84 (SRID 4326) data into columns call geom, and to put British National Grid into columns called geom_27700. I load data in the coordinate system of the shapefile. Later on, I may add additional columns and copy and convert the data.
I have written a simple shell script (load_shapes.sh) to call the java shapefile converter, including controlling the SRID and the name of the table and the geometry column.
#load_shapes.sh
…
function shp_load {
echo $0:$*
…
cd $dir
pwd
export clpath=$ORACLE_HOME/suptools/tfa/release/tfa_home/jlib/ojdbc5.jar:$ORACLE_HOME/md/jlib/sdoutl.jar:$ORACLE_HOME/md/jlib/sdoapi.jar
echodo "java -cp $clpath oracle.spatial.util.SampleShapefileToJGeomFeature -h oracle-database.local -p 1521 -sn oracle_pdb -u strava -d strava -t $table -f $base -r $srid -g ${col}"
}
clear
#set -x
shp_load /tmp/strava/ne_10m_admin_0_sovereignty.shp
shp_load /tmp/strava/ne_10m_admin_0_map_units
shp_load /tmp/strava/ne_10m_admin_0_map_subunits
…
I can now load each shapefile into a separate table.
Merging Shapefile Data into a Single Set of Data
The various tables created by loading shapefiles will each have their own structures determined by what was put into the shapefile. Ultimately, I am going to load them all into a single table with which I will work.
Areas have a hierarchy and that is represented in this table by the linked list of area code and number to parent area code and number. Foreign key constraints ensure the parent values are valid. There are also check constraints to prevent an area from being its own parent.
REM my_areas_ddl.sql
…
CREATE TABLE my_areas
(area_Code varchar2(4) NOT NULL
,area_number integer NOT NULL
,uqid varchar2(20) NOT NULL
…
,area_level integer NOT NULL
,parent_area_code varchar2(4)
,parent_area_number integer
,parent_uqid varchar2(20)
,name varchar2(40)
,suffix varchar2(20)
,iso_code3 varchar2(3)
…
,num_children integer
,matchable integer default 1
…
,geom mdsys.sdo_geometry
,geom_27700 mdsys.sdo_geometry
,mbr mdsys.sdo_geometry
,constraint my_areas_pk primary key (area_code, area_number)
,constraint my_areas_uqid unique (uqid)
,constraint my_areas_rfk_area_code foreign key (parent_area_code, parent_area_number) references my_areas (area_code, area_number)
,constraint my_areas_rfk_uqid foreign key (parent_uqid) references my_areas (uqid)
,constraint my_areas_fk_area_code foreign key (area_code) references my_area_codes (area_code)
,constraint my_areas_check_parent_area_code CHECK (area_code != parent_area_code OR area_number != parent_area_number)
,constraint my_areas_check_parent_uqid CHECK (uqid != parent_uqid)
)
/
--alter table my_areas modify matchable default 1;
Alter table my_areas add constraint my_areas_uq_iso_code3 unique (iso_code3);
Create index my_areas_rfk_uqid on my_areas(parent_uqid);
Create index my_areas_rfk_area_code on my_areas (parent_area_code, parent_area_number);
I have created scripts to populate data in the my_areas table from the Natural Earth data, and from the data for each country. Different scripts are needed for each shapefile.
- load_countries.sql - to load Natural Earth data
- load_uk.sql - to load Ordnance Survey data of Great Britain. This includes some DML to work out which wards and parishes are in which districts and boroughs and update the hierarchy accordingly.
- load_XXX.sql, - load administrative areas for a country where XXX is the 3-letter ISO code for that country (eg. load_FRA.sql for France).
- fix_names.sql - to simplify names stripping common suffixes such as a county, district, authority, ward etc.
- fix_my_areas.sql - script to collect statistics, count children for each area, look for areas that children of another area with the same name, simplify areas with more than 10,000 points.
No comments :
Post a Comment