Best of Craigslist 2014-07-24

I did not write this post, I promise.

To The Cyclists on University – 27 (University)
Keep calm. Fellow cyclist here; not here to run you off the road.

So, we got bike symbols painted on University. Sweet! Maybe less people will harass us now that it’s clear we actually belong in the street and not on the sidewalk.

Yeah, let me repeat that: now that we have bicycle arrows painted on the street, fellow cyclists, we need to be utilizing that resource. Not riding on the sidewalk anymore like a bunch of kids. I saw a mother out with her 5-year old daughter sharing the lane with cars today. If little girls can do it, you can do it.

We also need to be following the rules. Like adults. No one is going to support putting in more bicycle lanes if we keep blowing through intersections and acting like a bunch of arrogant, above-the-law, holier-than-thou assholes. And I’m as guilty as anyone of doing it, especially while riding in a pack.

Just because we finally got a little more space on the road doesn’t mean we have to hog the whole lane. Sure, it’s fun when we’re in a pack of 4 or 5 and can own it so we feel safe. But the guy stuck behind us is gonna take it out on me when I’m alone. This is how most of our road rage horror stories probably start. Ride single file when there’s a car back and just hold whatever it is you have to say until we get to where we’re going.

North Dakotans are known for being nice; let’s keep it that way.



Export from Petra, Import to Techlog

You can export selected wells from IHS Petra (v. 4.1.1) to a PPF file, and then import them into Schlumberger Techlog (v. 2013.2.0).  This will include all well information, location, zones, intervals, tops, variables, plug data, raster images, and perforations, according to Techlog help (“Importing from Petra”).

In Petra:

  1. Select your well list.  If you have a large number of wells (more than 500), I would suggest splitting up the well list into multiple exports.
  2. Project–>Export–>Petra Project File (*.ppf)…
  3. Choose settings.

    1. Remember to uncheck the “Encrypt well identifiers” box.

Locate your exported file in Windows Explorer.

In Techlog:

  1. If you have not set up a naming scheme for your project (or different than “STATE SAETZ 14-36” and variations), you can change a setting to name all the wells based on API or UWI.

    1. Open the project properties pane (your default bottom-left properties pane) with the convoluted Project–>Project utilities–>Edit the properties
    2. Select the “Project Properties” tab in the properties pane.
    3. Under “Import (LAS/DLIS/Geolog ASCII)” there is a “Well name” field.  
    4. Enter the field containing your well name.

      1. For me, importing a PPF, this is “UWI.”  
      2. If you are importing lose LAS files, you can open up the LAS file in a text editor and see what header field you should use.
  2. Open the Import pane.
  3. Drag your exported file from the Windows Explorer window to the Import pane in Techlog.

    1. This is the key step.  If you try to add the file as ASCII with the wizard (the only way I could get it to show up in the dialog), the wizard won’t identify it as a PPF file and won’t read the format correctly.

Grand Forks 311

You can now submit problems and requests directly to the city of Grand Forks with a 311 mobile app(lication) and online.  It looks like they are using the PublicStuff platform, which looks a great deal like SeeClickFix but the city apparently pays for.

Glancing through the Android app, it looks like they are keeping up with some of the requests and there has been a fair amount of activity since the app launched three days ago (but the list also includes requests from the testing phase before launch).

You do not need to log in or create an account to create an issue, but you do need to have an account to “support” (thumbs up) a concern.

I plan to keep the SeeClickFix sidebar up, at least for East Grand Forks.  [This was on the old Grand Forks Streets blog. 2014-09-10]

Submit issues or get the app here:


Petrel error: “unable to find first line of input data”

I ran into this today, and my best guess is that I was trying to use ASCII columnar data rather than Standard Keyword data.  

File that didn’t work:

2018 2018 0 0 0.57 63.8
2070 2070 0.42 0.33 0.57 49.74
2160 2160 1.37 0.69 0.88 66.9
2250 2249.98 2.9 1.4 1.19 68.68

File that did work:

*WELL 33xxxxxxxxxxxx    
0 0 0
2018 0.57 63.8
2070 0.57 49.74
2160 0.88 66.9
2250 1.19 68.68
2340 1.55 71.48

Petra exports in both formats for individual wells but not for bulk export.