Category: Maps

Glasgow Regions Mapped – Progress Update 1

You can read the initial post at: Mapping Glasgow Districts

We have had some great progress on the mapping so far. There have been 367 regions mapped to date. However, as mentioned in the original post, there are a huge number of regions in Glasgow so even with over 300 responses many regions have only one response and others are still unmapped. But in the hopes of encouraging some more responses I felt it would be nice to show what progress has been made to date.

Statistics so far:
Unique region names so far: 241

Most mapped regions:
City Centre – 10
Finnieston – 9
Merchant City – 9
Dennistoun – 8
Partick – 7
West End – 7
Garnethill – 6
Hyndland – 6
Woodlands – 5
Hillhead – 5
Mount Florida – 5

Regions so far. Click for PDF version.
map_so_far

We can see that there are still quite a few regions that have had the same number of responses with multiple region names.

We can look at what these responses have been, in an interactive map:


Full Screen.

We can see that the West End in general has been the target of a large number of responses, so we can drill in a little further:

west_end1

Extent of the west end:

West End

Individual regions:

Anderston

Anniesland

Blairdardie

Broomhill

Charing Cross

Dowanhill

Drumchapel

Finnieston

Firhill

Garrioch

Hillhead

Hyndland

Jordanhill

Kelvingrove Park

Knightswood

Maryhill

Not Partick

Park Circus

Partick

Partickhill

Scotstoun

Thornwood

West Maryhill

Whiteinch

Woodlands

Yoker

Yorkhill

A final note, there have been some creative responses as well, as expected. But the flagging system on the mapping page has worked incredibly well.

A huge thanks if you have responded.

Mapping an Integer

So just before Christmas I received my own “hand-crafted”, “unique”, and “hella-beautiful” integer. From Brooklyn Integers: 404578811.

http://www.brooklynintegers.com/int/404578811/

I was not initially sure what to do with it. But I had some time while waiting on points to appear in polygons so I though I would map my integer.

So we have a few combinations for co-ordinates:

  • 0, 404578811
  • 4 , 04578811
  • 40 , 4578811
  • 404 , 578811
  • 4045 , 78811
  • 40457 , 8811
  • 404578 , 811
  • 4045788 , 11
  • 40457881 , 1
  • 404578811, 0

    • And of course:

  • 404578811, 404578811

    • I have to say these do not translate very well into my current de facto co-ordinate system of British National Grid (0, 404578811 and 404578811, 0 and 404578811, 404578811 not shown).

    BNG_no_good

    Luckily we can try some alternatives. Smathermather had a great post about mapping Null Island/Archipelago, so we can re-use some code. To map our integers to a selection of CRSs.

    CREATE OR REPLACE FUNCTION integer_mapping2(

    crs integer,

    x integer,

    y integer)

  RETURNS geometry AS

$BODY$

DECLARE

    BODY geometry;

BEGIN

SELECT ST_Transform(ST_SetSRID(ST_MakePoint(x,y),crs), 4326) INTO BODY;

RETURN BODY;

EXCEPTION

    WHEN SQLSTATE 'XX000' THEN

    RETURN NULL;

END

$BODY$

  LANGUAGE plpgsql;

    We use the EXCEPTION, because some of the more awkward co-ordinate combinations cannot be translated back to EPSG:4326 without causeing a SQL error.

    Then we can create our our tables.

    CREATE TABLE my_integer_ AS

SELECT srid, integer_mapping2(srid, 404578811,404578811) as geom FROM spatial_ref_sys

    WHERE srid > 2000 AND srid < 4904;

    Replacing 404578811_404578811 as needed.

    Mapped:

    by_co_ord

    By CRS:

    by_crs

    4,04578811:

    4_04578811

    Album of the rest.

    It really shows how fragmented the EPSG codes are for New Zealand, and to a lesser extent the US.