articles

After we moved the propane tank, we knew we wante to stop using the wood burning stove and the old fireplace was never utilized. So, we did a fireplace insert with gas and we've never regretted it. I've updated the thermostat to work with our home automation tools and we can heat the front room in 10-15 mins.  We used Woodstove and Sun and we'll use them again for the firepit supplies when that project gets scoped.

After the septic was replaced and hillsides graded and a lot of brush removed, Ken suggested we hydroseed to protect the open hillside. This gave ua a great bloom of wildflowers and grass.

What was surprising was that Morgan Karst of Superior Hydroseeding was someone I went to high school with.

We did a lot of work on grading the property with Ken Clausing of A+ Construction. He and his crew replaced our septic lines, removed a lot of brush, graded a swale, graded a place for the propane tank, removed stumps and gave us lots of good advice for mountain livin'.

These initial grading projects helped us get a handle on managing the rain and brush that grow relentlessly. We did later projects that used these basic grading projects to build out terraces and increase our firebreak.

As I continue to study the MEAN.JS framework, I wanted to develop an app that would help cement what I've learned, illustrate some of the points I got hung up on and try to define problems well enough that I can try to get some more help where needed.

The failed septic system in late May 2012, got us started on a number of projects. Ken Clausing of A+ Construction was nice enough to come up that day. This is the project that started it all...

One of my objectives with migrating data out of Drupal and into a MEAN stack app is for easier management of downstream requests for JSON data. We want to take advantage of the built in functionality of the MeanJS stack, and here's a simple exaple.

In this use case we wish to expose articles to some other app who will make a HTTP GET request for all the articles or just one.

In app/controllers/articles.server.routes.js, we need to add entries for the two functions we'll allow via GET.

app.route('/api/articles')

.get(articles.list);

Created a norcal.cities.geojson file via geojson.io site.

In this tutorial we will load a small data set into MongoDB and build a simple map that adds a marker to a map. There is some preparation for this tutorial, so you will need the following:

- a working MeanJS environment

- created an Article in your working environment

- be prepared to do some find / replace in the GeoJSON data file attached to this tutorial

- be able to run commands from the terminal to load data into MongoDB via mongoimport and install angular-leaflet-directive

Well, I'm no expert but here's a tip that might save you some time. I have a Drupal databae outputting valid GeoJSON data. Our data looks like this:

{

"type": "Feature",

"geometry": {

"type": "Point",

"coordinates": [

-122.0570486784,

36.99607280576

]

},

"properties": {

"name": "Dean of Students Office",

"description": null,

"Food Type": "",

I took some time to try MeanIO over the past few days. While I ended up coming back to MeanJS, I drew some conclusions that might be helpful.

Here's the use case. I wanted to take a GeoJSON file, load it into a boilerplate MEAN stack, generate CRUD files and get a basic app tested. Ideally, I'd want to tweak the layouts, menus, and boilerplate HTML as well as use bower to add js libs that add functionality.

Update 5/1/15 - On a different instance of Mongo, I had run the command noted below and got errors. However, this worked:

mongoimport --db mean-dev -c points --file "points.geojson" --jsonArray

Let me save you the hours lost in trying to figure out getting GeoJSON features into individual documents in a collection versus one document with nested features.

MongoDB 3.0.2. Valid GeoJSON file full of 809 features.

Using this code:

mongoimport --db test --type json --file ./'mobilemaps.geojson'