Embed Size (px)
Citation preview
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Translating Maps and Coordinates from the
Great War@muninn_project
Rob Warren1 David Evans2
[email protected] Doctoral Fellow
Big Data InstituteDalhousie University, Canada
[email protected] of Derby
Derby, UK
Terra Cognita Workshop at ISWC 2014Warren et al. Translating Map Coordinates 1/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Muninn Coverage
http://rdf.muninn-project.org/sparql
Warren et al. Translating Map Coordinates 2/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
LOD Cloud 2014 Muninn WW1
Warren et al. Translating Map Coordinates 3/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Problem definition
Figure : Circumstances of death of John Aaron
Warren et al. Translating Map Coordinates 4/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Table of Contents
1 The Great War in 10 slides
2 Results - The API
3 Ongoing Linked Geo Problems
Warren et al. Translating Map Coordinates 5/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Vimy Ridge
a
aFrom M001570, IWM
Warren et al. Translating Map Coordinates 6/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Imperial Grid On Metric Map
a
ahttp://www.westernfrontassociation.com/attachments/590_How%20to%20read%20read%
20a%20Trenchmap-rev5.pdf
Warren et al. Translating Map Coordinates 7/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Vimy Ridge
a
aFrom M 001570, IWM
Warren et al. Translating Map Coordinates 8/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Vimy Ridge
Warren et al. Translating Map Coordinates 9/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
New Projections
a
a??????, IWM
Warren et al. Translating Map Coordinates 10/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
German Army Systems
a
aFrom M 025838, IWMWarren et al. Translating Map Coordinates 11/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
German Army Systems
a
aFrom M 025838, IWM
Warren et al. Translating Map Coordinates 12/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
German Army Systems - 3 Systems and counting!
a
aFrom M 013420, M 020060, IWM
Warren et al. Translating Map Coordinates 13/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Where does the Belgian grid start?
Supposed to start at the Uccle Observatory in Brussels,
which moved.
50◦25′0.0006”, 4◦22′12.6978” ([4]), or 51◦10′06.895”,
4◦22′05.89” ([2]), 50◦24 , 4◦22′5.89” (NGI, [1]).
50◦23′57.2418”, 4◦22′10.0518” after exhaustive search,
thank you to Bill Frost and Pierre Voet.
Make it useful
Create an API; ideal integration point between systems.
Small app for human beings.
Warren et al. Translating Map Coordinates 14/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Linked Geo API
http://rdf.muninn-project.org/api/
TrenchCoordinates
Parameters q query, enrich ∈ {full, none, partial}.
Returns rdf/xml, n3, etc... (force with fmt=rdf)
Human being version: http://rdf.muninn-project.
org/TrenchCoordinates.html
Enriching (linking) on the fly
Link to geo-spatial objects in Muninn SPARQL server.
Link to French and German National Library geo-spatial
object.
National Library of Scotland and McMaster Map Library on
the way.
Latency is a problem.Warren et al. Translating Map Coordinates 15/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Linked Geo API - Design use cases
enrich=none, High volume batch coordinates translation.
Do it as fast as possible without any overhead or linkages.
enrich=partial (default), Human front-end support. Make it
fast, enrich if possible with anecdotal linkages but don’t
waste time doing it.
enrich=full, Send everything possible without regard to
speed or data volume. (eg: Get a working set of data)
Warren et al. Translating Map Coordinates 16/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Linked Geo API - Make the common case best
0
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1
0 300 600 900 1200
Fra
ctio
n
Compressed response body size (bytes)
Warren et al. Translating Map Coordinates 17/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Crafting response packets
1460 bytes for about 86% of IPv4 paths ([3])
70% of responses over a one month sample met this
requirement.
Linked Geo API - Answers allow for uncertainty
WGS84 query: btmaps:btmc ogc:contains geo:Point
British coordinates query: btmaps:btmc ogc:sfOverlaps
ogc:Geometry.
(Give ourselves some manoeuvring room)
20
ya
rds
50.3709, 2.7726
5 y
ard
s
Warren et al. Translating Map Coordinates 18/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
A point in space (and time)
About 50.3709, 2.7726
36c.s.28.a.3.9
Warren et al. Translating Map Coordinates 19/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
A point in space (and time)
20
ya
rds
50.3709, 2.7726
5 y
ard
s
Warren et al. Translating Map Coordinates 20/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
“Computer Science” and “Science” see decimals
differently.
Latitude 50.3709 is not the same as 50.370943, 50.36 or
50.36... or 50.360000.
Programmers just pass a data structure.
In the “real world”TM, this is where the measurement error
is created by operators.
My old chemistry lab instructor would be horrified at how
we do things.
Warren et al. Translating Map Coordinates 21/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
A point in space (and time)
50.3709, 2.7726
2.7725 2.7727
50.3710
50.3708
Warren et al. Translating Map Coordinates 22/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
A point in space (and time)
50.3709, 2.7726
2.7725 2.7727
50.3710
50.3708
BCDA
BCDAB
CDA
BCDA
2827
21 22
Warren et al. Translating Map Coordinates 23/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
What is the right thing to do?
Does the bbox:
ogc:sfOverlap 21.D, 22.C, 27.B and 28.A (or the largest
coordinate box with 100% cover?) ...
or ogc:sfOverlap 36C.s ...
or ogc:sfOverlap 36c.s.28.a.3.9?
Problem
No clear balance between the needs of a human, a
scientifically minded human and a machine answer.
The 80% solution currently involves a programmer parsing
the answer.
Warren et al. Translating Map Coordinates 24/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
The future
TrenchLabel TrenchLabel
"Military Trench"@en
Trench
rdf:typegeom:geometry
"Regina Trench"@en "Staufen Riegel"@de
skos-xl:Label
rdf:typerdf:type
skosxl:literalFormskosxl:literalForm
Organization
Organization
prov:Attributionprov:Attribution
"General Staff,
Geographical Section"@en
rdfs:label "Preußische Landesaufnahme (Deutsch Reich Generalstab)"@de
rdfs:label
skosxl:prefLabelskosxl:prefLabel
Warren et al. Translating Map Coordinates 25/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
The future
Warren et al. Translating Map Coordinates 26/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
From a visual perspective:
or http://sws.geonames.org/2987928/about.rdf
We need to:
Tackle precision and accuracy as both a problem and an
opportunity.
Warren et al. Translating Map Coordinates 27/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
Boring Conclusion frame
Implemented a coordinate converter using linked open
data principals.
Effective means of linking past locations (feature?) with
current locations.
How to communicate issues of precision, accuracy and
identity (!?) still an ongoing question.
Integration with other projects ongoing; need to get triples
to report accuracy (ssn ontology) on their own.
Questions!
Warren et al. Translating Map Coordinates 28/28
The Great War in 10 slides
Results - The API
Ongoing Linked Geo Problems
CARTOGRAPHIQUE MILITAIRE, I.
Triangulation du Royaume de Belgique.
No. v. 2-3 in Triangulation du Royaume de Belgique.
Cnophs, 1867.
JACK, E. M.
Report on survey on the Western Front 1914-1918.
His Majesty’s Stationery Office, London, 1920.
LUCKIE, M., AND STASIEWICZ, B.
Measuring path MTU discovery behaviour.
In 10th Conference on Internet Measurement (2010),
pp. 102–108.
MUGNIER, C. J.
The Kingdom of Belgium.
Photogrammetric Engineering & Remote Sensing (October
1998), 956–957.
Warren et al. Translating Map Coordinates 28/28
![Convergence of Wachspress coordinates: from polygons to ...jiri/papers/14KoBa.pdf · convex polygons are Wachspress coordinates [14], mean value coordinates [4], and harmonic coordinates](https://img.pdfslide.net/doc/110x75/5f6dfe23261f61015179236e/convergence-of-wachspress-coordinates-from-polygons-to-jiripapers-convex.jpg)
