initial `cityseer` thoughts

[jGaboardi]

This PR kicks off the cityseer explorations. Please provide any thoughts/feedback/recommendations. See here for gist version of the notebook in this PR.

xref:

• 1

• 2

• (maybe) closes #2

[jGaboardi]

my next question for cityseer here is: what if we only have a geodataframe of linestrings (no OSM attributes etc), is that still a valid input for the simplification functions

Good point.

[jGaboardi]

@anastassiavybornova Should I move this notebook into the code/ directory (like yours)? Or should we move yours into this notebooks/ repo?

cc @martinfleis

[martinfleis]

I'd vote for code as @anastassiavybornova did it.

[jGaboardi]

I'd vote for code as @anastassiavybornova did it.

Sounds good. I'll update the location in this PR, as well as test with the standard data.

[jGaboardi]

Cityseer redeaux

• next attempt at understanding cityseer somewhat based on @anastassiavybornova's stuff
• very much a work in progress... just wanted to give an update
• will need much love and care
• initial thoughts from yall are very welcome

[jGaboardi]

Cityseer threedeaux

• @anastassiavybornova & @martinfleis – I made some pretty big updates & streamlines to the directory and infrastructure here. Please let me know if it's too much at once.
• Basically, added a dedicated 311 and 312 envs files, we should be able to use 312 now. CitySeer updated since I started using it. Also, worked out the opencv / `condaforge stuff.
• CItySeer is still a monster. The notebook I added to go through simplification step by step to demonstrate the graph elements at each stage. And I provide some PNGs in usecases/809/cityseer/ to visualize (not as cool as @anastassiavybornova's fancy gifs).
• LOTS can be done in terms of parameterizes within cityseer. Let me know if there is something specific to hone in on.