Incorporating Google Street View Imagery with the LLPG

Sam Tizzard, London Borough of Harrow

About Me

Studied: • Geography with Natural Hazards

(BSc) at Coventry University• Volcanology and Geological Hazards

(MSc) at Lancaster University

I am currently a GIS Analyst/Technician for the London Borough of Harrow (since January 2015).

I have been using FME for around 8 months now.

Sam Tizzard – just a little bit about me

The LLPG? The LLPG (local land and property gazetteer):• Is an address database of all land and property within an authority

• Forms part of the NLPG (national land and property gazetteer)

• Integrated with many systems at Harrow and used for property searches within our ‘Harrow Address Lookup’.

Current Address Look Up

Provides a 360 degree view of the world along mapped routes or spheres.Accessible via an API:https://developers.google.com/maps/documentation/streetview/

Free for under 25,000 hits a day!!!

Why not use FME?

LLGP Address Data from the LLPG

Integrator Process‘LLPG Features’

Street Data from OS Highways Data

‘Road Points’

Calculate:

Nearest ‘Road Point’ to each ‘LLPG Feature’

WGS84 Conversion of the ‘Road Points’ Co-ordinates stored as

attributes only

Angle between each ‘LLPG feature’ and nearest ‘Road Point’

Build Google

Street view API URL and

wrap in href’s

1. Takes OS Highways Data (currently BETA).

2. Removes unwanted records.

3. Merges street information and road network.

4. Tidies attributes.5. Divides streets into

points at every metre.

The Workspace (part 1)

1. Finds the closest street point to every address point

2. Creates an extra vertex per features using the road points .

3. Calculates the azimuth of the line between address point and road point

4. Calculates actual angle

5. Creates Streetview URL

The Workspace (part 2)

The Generated URLTemplate URL:https://maps.googleapis.com/maps/api/streetview?size=600x600&location=@Value(URL_LATITUDE),@Value(URL_LONGITUDE)&heading=@Value(AZIMUTH_ANGLE)8&pitch=0&key=[API KEY]

Working URL:https://maps.googleapis.com/maps/api/streetview?size=640x640&location=51.5702293,-0.3451858&heading=326.5473190230258&pitch=0&key=[API KEY]

Example 1In Inspector: URL And Image:

https://maps.googleapis.com/maps/api/streetview?size=600x600&location=51.5702293,-

0.3451858&heading=326.5473190230258&pitch= 0&key=[API KEY]

Example 2In Inspector: URL And Image:

https://maps.googleapis.com/maps/api/streetview?size=600x600&location=51.5873401,-

0.3426364&heading=153.9711372925798&pitch =0&key=[API KEY]

Concluding Points1. FME has a great capability

to use ‘templates’ (e.g. a URL)

2. FME can almost handle any task (even when processing nearly six million points!)

3. Workspaces can always be improved

Thank you!For not making me use the sprinklers.

Any questions? Feel free to contact me at:Sam.Tizzard@harrow.gov.uk