search

DavidZtako / Octopus-Pathfinder

0 stars 0 forks source link

Some suggestions #3

Open FlyingFi opened 3 years ago

FlyingFi commented 3 years ago

This is a very logical tool!

A few suggestions:

  1. I would suggest changing the name of the tool you have. "Landscape mapping tool" is a bit general and does not offer the user a very straightforward idea about what the tool does. Same with the "ReadME" file, where the project description could be refined more - to write from a user's perspective.

  2. Probably thinking about using a simple diagram to tell this idea below. 134809513-3cfe97ab-c756-4fda-a2c3-e92ad8ac7fd9

  3. There are quite a few things that you try to achieve through this definition, e.g. "I. The Shortest Path Component", "II. Hazard Mapping (Flooding)", "III. Shared Subway Interchange", "IV. Approximate Boundary". - Probably just focus on one as the main focus.

  4. The idea of "The Impenetrable Boundaries" sounds quite interesting. However, it was hard for me to see how it comes together in your definition, e.g. extracting those layers of impenetrable Boundaries.

  5. Consider if you really need all these features? If the definition focus on public transport, major highways for cars may not be helpful... This might slow down the file, alternatively, you could ask the user to define which ones they need.

    Screen Shot 2021-10-02 at 2 42 50 PM

  6. Not sure why "tourism" is what the tourists are trying to avoid...

    Screen Shot 2021-10-02 at 2 50 16 PM

  7. I couldn't load the file for over 15mins, I had to give up. I tried with both the osm file and my own osm file (around 50MB). Probably speed up the file first before anything. I'm happy to have another go at it after you've sped up the file.

Overall very good work and a very thorough project!

Fiona

DavidZtako commented 3 years ago

Hi Fiona,

Thanks for the feedback on my component. I am revising my grasshopper definition and description file based on your comments. A more usable OSM file has been uploaded to Github for testing. You can also use your smaller-scale site for testing if you wish.

I would like to briefly answer some of your questions about the purpose of this component (a more detailed description is still in progress). The primary purpose of my component is first to establish the shortest path between two landscape elements and then add an impenetrable boundary to mapping the change in the shortest path when it is disturbed.

The tool generation is placed in a hypothetical scenario. The scenario first assumes that an accident occurs in landscape element A (Building) and that people need to reach landscape element B (Healthcare Centre) in the shortest possible time. It also assumes that this process needs to avoid sites with a high density of people, so the tourism-related elements are used as impenetrable boundaries. Your advice has reminded me I need to be more careful and consider narrative when writing my readme file, which is very valuable!

Thank you for your comments and suggestions, and I hope my answers have partially answered your questions. Cheers!

David