Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Request #34

Open
jhelsel11 opened this issue Mar 6, 2020 · 9 comments
Open

File Request #34

jhelsel11 opened this issue Mar 6, 2020 · 9 comments
Assignees

Comments

@jhelsel11
Copy link
Contributor

Sijia, could network standard also contain a .shp file of the network with only the a and b nodes? I can't use the SSids to make true shapes in cube (and cube only takes a .shp file) so I'm using the a/b nodes from November, but those obviously aren't being updated. It'd be good to know that the shape I'm using is consistent with whatever the latest base network is.

As an aside, is there a process for updating geometries for when new links are added? Or will all projects involving new links just be straight lines?

@i-am-sijia
Copy link
Member

Shape file with A and B nodes: Yes, will update that.

Shapes for new links: Lasso does not do this, as CUBE log file does not pass along geometries. Maybe shapes will be created and added to geojson by Network Wrangler, and I would guess they will be straight lines. cc: @e-lo

@e-lo
Copy link

e-lo commented Mar 6, 2020

We don't have a way in our current MetCouncil workflow to add links using true shapes because Cube doesn't support it and that is our method for adding the links.

@jhelsel11
Copy link
Contributor Author

Ok. Just wanted to clarify.

@i-am-sijia
Copy link
Member

@jhelsel11

Added latest link shapefile with only A/B nodes to the oneDrive file.

@jhelsel11
Copy link
Contributor Author

jhelsel11 commented Mar 18, 2020

@i-am-sijia, I'll add this to the network_standard branch, but would you please add it there whenever you update the network_standard?

@jhelsel11
Copy link
Contributor Author

@i-am-sijia, I'm actually not sure how to upload the file since the zip is >100MB. Do you have the LFS? Does the whole repo?

@i-am-sijia
Copy link
Member

@jhelsel11, Yes, I have LFS and so does the repo. I'll upload the shapefile to network standard.

@i-am-sijia
Copy link
Member

@jhelsel11 I take it back, I think it's better to store the .shp file with CUBE fixed width files, as they are all for CUBE consumption. Do you have a location where you store the fixed width files?

@jhelsel11
Copy link
Contributor Author

My understanding of the work flow is that I will make the fixed width files from the network_standard json using lasso. So, I think it would make the most sense if all of your outputs (network_standard, shapes, etc) go into a single place that I can pull as a single update. Then the fixed width formats get written out by my (Rachel's) machine as part of my process.

And then we know that the shape was updated at the same time as network_standard. Does that work for you?

Maybe we should chat on the phone?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants