Quick idea for keeping track of file name abbreviations

I like to keep my file names short for several reasons: to make it easier to see the whole name at a glance, to make saving new files simpler, to allow room for additional characters when exporting new versions from different applications, and to (yes, still) deal with applications that have a set limit on the number of characters they will read or write from a file name.  

This leads me to abbreviate, and since I often end up with a few dozen files in the same folder with a bunch of different abbreviation combinations, I’ve come up with this trick to make sure I don’t forget things: add a few empy folders (or files, if you wish) as a key at the top of your directory.  In OS X, you can put a space at the beginning of the file name to force it to the top; in Windows I think you need to use an underscore.  So finally, in an image that is worth more than all the words I’ve just put down, here is an example.

 

List of GPlates rotation files

My dissertation is on BIOgeography, I swear!  I’ve had a hard time finding plate tectonic reconstructions (rotation files, .rot or .grot) to use in GPlates (hopefully a post on that sometime soon), so I will try to add to this list as I learn more.

Global rotation files:

  • First, the main GPlates Download page.  Scroll down to the “Download GPlates-compatible data” section, which contains some of what is listed here.
  • GPlates official sample data was commented on here.
  • Earthbyte rotations go back to 140 Ma.
  • CalTech rotations (which may or may not be different from EarthByte) go back to 140 Ma. 
  • Seton et al. (2012) rotations go back to 200 Ma.
  • Golonka (2007) has global rotation data in the supporting online material for the Late Triassic-Early Jurassic.
  • Supporting data for Williams et al. (2012), available from an FTP link in the text, has a rotation file from 1100 Ma to 530 Ma based on “the model of all Rodinia described by Li et al. (2008)” (SupplementaryTutorial2.pdf, p. 5).

Regional rotation files:

  • Australia
    • A rotation file for Australia (~1100 Ma – 530 Ma) by Giles et al. (2003) is included in the Williams et al. (2012) supporting data, above. 
    • A rotation file for Australia (~1100 Ma – 530 Ma) by Henson et al. (2011) is included in the Williams et al. (2012) supporting data, above.
    • A rotation file for Australia (~1100 Ma – 530 Ma) by Li and Evans (2011) is included in the Williams et al. (2012) supporting data, above.

 

Discussion in Other Places: Expanding Grand Forks

Relating to one of the interchange ideas recently published in the Herald, there is an ongoing discussion in the comments section for that article that is fairly interesting.  A little bit of local history, a little bit of speculation, and at least a few people thinking about where the city is headed.

OUR OPINION: Which comes first, the exit or the mall? (comments)

UPDATE:  Minutes after I posted, this article came out that summarizes some more things: http://www.grandforksherald.com/event/article/id/240410/

Exporting from Panorama Sheets

I just started playing with Panorama Sheets, which is a cheaper (and lower-power) version of Panorama, but which does exactly what I want: combines a spreadsheet interface with database-querying capabilities. At the moment, I don’t need the other functions of the full version of Panorama, so I may purchase this software after my trial runs out. I’ve seen a few glitches so far, one of them being that while in the Export Wizard (File->Export Text…), clicking on the “Export Text” button results in an “Error resolving alias.” error. Luckily, this can be solved by selecting the Export->Export to Text File… menu item. An additional problem I ran into is that the encoding is weird when trying to open this file in OpenOffice Calc, so it was easiest to open the text file, copy the contents, and paste into Calc, which will bring up a dialog box you can use to select your delimiter, etc.

 

South Washington Street Corridor – Bicycles in the Updated Plan

A while back fellow streets enthusiast and cycling commuter A.K. forwarded me a link to the new South Washington Street Corridor draft plan (which is listed as “final” now).  This post will cover some of my thoughts on the cycling aspects of the plan.

Figure 7.28, from The Forks MPO

The plan as stated will set aside multiple sections of bicycle “route” (I am using “route” as an indeterminate word for “places designed for cyclists to be”).  They are (from south to north)

  1. The existing shared-use path on the west side of South Washington Street, from 55th Avenue South to a point even with Hammerling Avenue, with the hopeful widening or addition of a shared-use path from this point for one block north to 14th Avenue South (Figure 7.28, top pane).
  2. 14th Street South, from 14th Avenue South to DeMers Avenue (Figure 7.28, top and middle panes).
  3. A section that will cross DeMers Ave and the railyard (Figure 7.28, middle pane):
    1. A new shared-use path on the south side of DeMers Avenue, between 14th Street South and South Washington Street.
    2. The existing shared-use path on the west side of DeMers Avenue, between DeMers Avenue and 1st Avenue North.  This is the railyard underpass itself, and modifying this stretch of road is discussed elsewhere in the report.
    3. 1st Avenue North, between North Washington Street and 14th Street North.
  4. 14th Street North, from 1st Avenue North to 8th Avenue North (Figure 7.28, bottom pane).
    1. The push-button crossing at 15th Street North would be moved to 14th Street North to help kids cross.  This is a great idea.
  5. The existing shared-use path on the west side of North Washington Street, from 8th Avenue North to Gateway Drive.

Frankly, I’m excited about this plan.  It would create a for-sure, straightforward, north-south bicycle route along one of the busiest corridors in the city.  It would be around 4.6 miles long, probably the longest straight stretch of cycling “route” that we have outside of the Greenway (which, of course, is not straight).  There are a few details that remain to be worked out, however.

  • It is granted, in general, that routing cyclists through controlled crossings is desired, however it should be understood that regular commuters will be utilizing routes that do not force them to stop and wait to cross streets at controlled intersections.  This should be kept in mind by the planners.
  • Section 1, above, has half a block of traffic (from Hammerling Avenue to 14th Avenue South) to deal with in the form of curb cuts for the businesses along that stretch.  I think this is in order to move cyclists through the controlled crossing at 17th Avenue South, rather than force riders to wait for traffic to cross 17th Avenue South at at 14th Street South.  It would seem better to route people along 15th Street South instead of 14th Street South.  Even though this leaves a relict half-block section of shared-use path to the north, it would minimize the potential interactions with vehicles turning into businesses along that stretch.
    • Most riders who know what they are doing will probably cross 17th Avenue South at 14th Street South and not at the light.
  • Section 3.1, above, routes cyclists through an apparently new shared-use path where the Hertz rental store is now.  Are they going to go for this?  Is there space for such a route?  The DeMers crossing is long and dangerous, and it is hoped that pedestrian/cycle signals will be given greater priority.
    • Again, most regular commuters will probably cross DeMers Avenue at 15th or 17th Avenue South while heading to or coming from the shared-use path on the north side of Demers Avenue.
  • Section 3.3, above, routes cyclists (coming from the south) from the existing shared-use path onto 1st Avenue North.  This intersection is heavily used by motor vehicles and they are not used to looking for cyclists who are not in the street.  It is suggested that an engineering solution to the grade problems at Dyke Avenue or the alley between Dyke Avenue and 1st Avenue North would alleviate the congestion issue at this intersection, at least for cyclists who are continuing north rather than crossing North Washington Street at 1st Avenue North.
  • Finally, I hope these improvements utilize some good signage, and that the bicycle signage in general is improved.  Clear “Bicycle Route” signs would be especially beneficial along 14th Street South and where the route turns.  Sharrows (I am not certain whether they are explicitly planned) would be an excellent addition to 14th Street and, although it is outside the scope of this plan, 17th Street South and other roads that we would like to encourage bicycle commuting along.
    • One comment from A.K. on this: ”
      I think the best way to implement the shared road on 14th, is to bring this concept to others. Otherwise it just becomes another 1-time deal in the city making drivers (and bikers alot) more confused.  Whatever signage/markings they do to 14th should also be done to other N/S streets such as 34th, 20th, 17th, 14th, etc. “

So that’s what I think, what about you?  If any of this is confusing, I will do my best to make additional concept maps available so we can all be on the same page.  Like I said at the top: it’s exciting that Grand Forks is putting this much thought into cycling facilities.  If you want to get involved, the MPO has just release the “MPO Citizen’s Guide For Participating In The Transportation Planning Process,” which has information on how to be notified about upcoming meetings, how the process works, and how much of an expert you need to be (I’m kidding, they want everyone’s input).

Quickies: Another Interchange Idea and the Columbia Road Widening

We’ve already seen ideas about creating a south-end Grand Forks/East Grand Forks bypass by building an interchange at Merrifield Road, but now there is talk of one going in one mile to the north, at 47th Ave South–if developer/landowner Guy Useldinger has his way.  What do you think?  If the city is going to invest in more infrastructure (to expand housing and commercial opportunities for investors for example), where should it be focused?

In other news, the plan to widen Columbia Road for a few blocks might be more expensive than anticipated.  No word yet on how bicycle and pedestrian facilities fit into the project.