JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for SPACESYNTAX Archives


SPACESYNTAX Archives

SPACESYNTAX Archives


SPACESYNTAX@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

SPACESYNTAX Home

SPACESYNTAX Home

SPACESYNTAX  October 2014

SPACESYNTAX October 2014

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: How to have a 'segment map' in Depth map

From:

Juan Alvaro Alayo <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 27 Oct 2014 15:22:14 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (39 lines)

Hi (…)

I realise you are asking for detailed and technical information about the mechanics of how to run an angular analysis and how to define the “elements” of the model (axial lines, centre line…). I’m afraid I can’t help you on that because I don’t use a variety of representations or software tools.

However, I would like to mention something that perhaps you, or other people on this thread, may find of interest: the potential for “Node” analysis. Something that I think is worth bearing in mind when deciding on the representation technique.

Disclaimer: since I’m not actively involved in the Space Syntax community, other than occasionally reading these messages, it may be an issue already well analysed, in which case my apologies. But since I’m not sure, I thought I would share some thoughts, in case anyone sees potential for further research or to engage in conversation.

When I started looking into segments back in 1989, my main concern with the “traditional” (at the time) Axial Line representation was that streets, particularly long ones with plenty of connections, could show very different pedestrian flow patterns (or other social behaviour) along their length. Another concern was that the “weight" of each line was the same in the analysis regardless of their length or number of segments. Each line was an element with the same weight regardless of it being Oxford Street or a tiny side street.

On the other hand, I was very impressed with “axiality”, as a way of connecting elements that were not adjacent, and the strong results that integration measures provided when mapped against pedestrian flows.

To try to improve on that, and gain finer detail on the analysis, my suggestion was to use “nodes” and “segments” as the elements for the model and axiality as the relational property.

What I found was that, as a first pass, integration values for segments on the same line would be the same (segments are rather “dumb”, since they only “see” along the line) but integration values for nodes (the intersections between two or more lines) could vary quite significantly along a line. Basically, it was in the nodes where “stuff” happened, where connections took place. 

I then started to draw the axial lines in profile (with length along the X axis and integration value for the nodes along the Y axis), like a mountain chain. Drawn this way, one could see that the real integration value of the segments should relate to the nodes it had either side, (not necessarily those immediately adjacent, they could be tiny cul-de-sacs, but the highest one either side). I then derived an integration measure for the segments based on the profile of the line an the nodes either side, that improved correlation with pedestrian flows significantly.

Sorry for the long text, but the objective was to highlight that, in my view, the analysis of nodes, as spatial elements in their own right (and where the syntactic connections take place in the system), can provide a fine grain, and fairly rich, picture of the cities we want to analyse. 

I’ll be curious to know if anyone else out there has followed this line of work. 

Kind regards,
Juan Alayo

Note: The definition of “node" would need quite a bit more space and probably further research, when it affects more than two lines. But an initial “ common sense” approach, for junctions with more than two lines, of unifying the intersection points in one node, if they are sufficiently close and within a “convex” space, seems to work fine.







> El 27/10/2014, a las 9:47, SUBSCRIBE SPACESYNTAX Anonymous <[log in to unmask]> escribió:
> 
> Thanks Professors Alen, Bin, Juan for your replies on this post. Sorry if I'm asking for bit of technical information on this post, but I would be appreciate if other people also could come on to the board, and mention the process through which they run an 'angular analysis'. For the purpose of this post, let's assume we decide to go with 'angular analysis;. So which steps you take (compared with those I mentioned below). Specially, what type of 'axial lines' map you use (traditional ones based on visibility drawing by HAND, Auto, or the one proposed based on natural roads'. I believe, this step would be important in kind of standardization and avoid arbitrary process in space syntax research (which many pick on this as an obvious weaknesses of our SS research).  
> 
> Thanks

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager