Cheetah, the CONFIGURBANIST

Comment

Comment by Pirouz Nourian on January 14, 2016 at 5:00am

Hi Tim, that component is indeed one of the trickiest in the toolkit. I have been working on alternative approaches intensively in the past year. I will share the new components for splitting the network from our kitchen tomorrow. The problem is the topological validity of the network as one connected graph. Many things that appear to be connected to bare eyes are unfortunately not cleanly connected in terms of their computational representation. There are many efforts in the fields of GIS in the direction of resolving such problems while requiring as little human intervention as possible. Not so easy; but the new tools could do much better I suppose. They are based on a much more systematic approach.

 

Comment by Tim on January 13, 2016 at 11:38pm

Hi Pirouz

I'm trying to get it working with a street network that I have here, but so far I can't, could you elaborate on the source of the problem?

1. Solution exception:Value was either too large or too small for an Int32.

According to Zuzanna:

I have tried the newest version and I have encountered an issue with Network Distance Calculator. When I connect Attraction Points the component reports an error. It says that "value is too big or too small for Int32 value". What does it mean? 

solved it. I had some lines which did not connect to the middle of other lines.

She managed to solve the problem, but I don't understand the nature of it. I know that all the lines must be split into segments and connect to each other's endpoints, but what's wrong?

(also, there is a flat mesh, I assume if you don't have terrain geometry, component won't work, is that correct?)

Comment by Tim on January 13, 2016 at 10:02pm

Get this weird pop up when loading my street network. There should be no nurbs there because I converted all of them into polylines prior to the analysis (I double checked with selection tools, no curves).

Comment by Tim on January 13, 2016 at 9:47pm

Found a typo

Comment by Pirouz Nourian on January 13, 2016 at 4:36am

Thanks! apparently the typos are "dsitbuted" everywhere :)

Comment by Tim on January 12, 2016 at 2:28am

Found a typo, peace.

Comment by Tim on January 11, 2016 at 8:19am

Great news indeed. I'll keep an eye for typos or weird stuff. Not a problem for me since I'm gonna use cheetah quite a lot for what I'm doing here.

Comment by Pirouz Nourian on January 11, 2016 at 8:16am

Hi Tim, thanks for point out :) ps. the new version is getting almost ready. It will be based on a dll that can be used in coding new projects. Can't promise a date yet because I am busy with writing my dissertation but sometime in the spring I hope we will publish it.  

Comment by Tim on January 11, 2016 at 7:58am

Found a typo.

Comment by Pirouz Nourian on October 23, 2015 at 4:32am

Hi all, it looks like nothing is going on with the development, but in fact we are continuously working on a new version. I tested a whole new version in a workshop for eCAADe conference at TU Wien recently. I also presented the new features in a paper and a talk:

Here are links to my presentation and the paper:

https://mh-engage.ltcc.tuwien.ac.at/engage/ui/watch.html?id=b1dffea...

More info on my website: 

https://sites.google.com/site/pirouznourian/configurbanist

 the paper on CONFIGURBANIST, to be made open access early in 2016. For the time being, you can find it on research gate.

• ‹ Previous
• 1
• …
• 8
• 9
• 10
• 11
• 12
• …
• 21
• Next ›
• Page