| [21:02:39] | * southerndan[m] has quit (*.net *.split) |
| [21:02:39] | * leogaggl[m] has quit (*.net *.split) |
| [21:02:39] | * chriswilliams[m] has quit (*.net *.split) |
| [21:02:39] | * alekospantazis[m has quit (*.net *.split) |
| [21:10:03] | * leogaggl[m] has joined #farmos |
| [21:10:13] | * chriswilliams[m] has joined #farmos |
| [21:10:21] | * southerndan[m] has joined #farmos |
| [21:11:00] | * alekospantazis[m has joined #farmos |
| [22:29:13] | * JustTB has quit (Quit: Leaving.) |
| [06:01:34] | * JustTB has joined #farmos |
| [06:50:43] | * JustTB has quit (Ping timeout: 244 seconds) |
| [07:00:46] | * JustTB has joined #farmos |
| [10:34:26] | * ludwa6 has joined #farmos |
| [10:45:26] | * ludwa6 has quit (Quit: ludwa6) |
| [10:47:33] | * ludwa6 has joined #farmos |
| [11:36:39] | <ludwa6> | hello room: n00b here, just got installed on farmos.net today, and starting configuration now, Areas first. I see i can import .KML, which is great, because i have areas defined in Google Earth Pro. Question; if i modify in FarmOS and want to EXPORT a .KML, is that also possible? |
| [11:38:57] | <mstenta[m]> | ludwa6: yes! in the Areas page, you can click checkboxes next to the areas you want (or select all) and click the KML button at the bottom |
| [11:39:04] | <mstenta[m]> | this will create a single KML file with all the selected areas |
| [11:39:16] | <mstenta[m]> | you can also do the same thing with logs (which can have their own geometry) |
| [11:39:46] | <mstenta[m]> | Also also: there is a "beta" module for bulk-importing multiple areas from a single KML file |
| [11:39:56] | <mstenta[m]> | Which makes it easier to import from something like Google Earth |
| [11:40:08] | <mstenta[m]> | I can turn that on if you'd like to try it |
| [11:40:17] | <mstenta[m]> | (Would recommend experimenting with just a few areas to start to get a feel for it) |
| [11:40:54] | <ludwa6> | excellent news, [m]; please do activate, and i will go slow as you say. Thanks! |
| [11:45:27] | <mstenta[m]> | ludwa6: Oh i forgot, it's enabled by default now :-) |
| [11:45:50] | <ludwa6> | cool! |
| [11:45:58] | <mstenta[m]> | Go to Areas (in the top), then click the "Area importer" tab |
| [12:04:59] | <ludwa6> | hmm: i exported a .KML file that has 9 properties in it (grouped into subfolders), opened it in my text editor, copy/pasted the code into the farmos window, and then clicked parse. No joy: output says “Total geometries: 0” |
| [12:05:15] | <ludwa6> | guess i’ll try a simpler .KML |
| [12:06:01] | <mstenta[m]> | ludwa6: the KML processing in the importer is relatively simple... (hence the "beta")... maybe it can't handle the subfolders? |
| [12:06:26] | <ludwa6> | reasonable theory of cause. trying one simple polygon now. |
| [12:14:07] | <ludwa6> | that seems to have worked pretty well. Only thing: it asked me to define a parent area, and instead of giving me the one area that existed (which is whole farm), i put what i thought was name of that area, and it created a dupe. |
| [12:16:46] | <mstenta[m]> | Ah yea, that is optional - it just gives you that option so that all imported areas are grouped under a new one, so you can easily see what was create |
| [12:23:14] | <ludwa6> | ok, i can work with this. Only: now i have two top-level areas defined… the first, what came by default, is name of my farm plus full address, what i entered in initial account config panel... |
| [12:23:57] | <mstenta[m]> | you can rearrange the hierarchy |
| [12:24:03] | <ludwa6> | … and then another that is simply the farm name, without the address… Which is what i called the parent of first two properties i have entered. One should be eliminated -but does it matter which? |
| [12:24:03] | <mstenta[m]> | there's a link at the top of the areas page |
| [12:24:11] | <mstenta[m]> | and you can delete the dupe one |
| [12:24:21] | <mstenta[m]> | no doesn't matter |
| [12:24:23] | <mstenta[m]> | up to you |
| [12:24:39] | <ludwa6> | ok -then i will delete the long one from default config with full address. |
| [12:24:45] | <mstenta[m]> | but you'll need to move the child areas in the hierarchy before you can delete |
| [12:25:06] | <mstenta[m]> | it will prevent you from deleting an area that has any children, or if it has any logs associated with it already |
| [12:25:14] | <ludwa6> | they are where they belong, in the simpler name i defined as their parent. that’s fine. |
| [12:40:16] | <ludwa6> | finished importing the 10 properties that make up my farm. Not too difficult… But if i have to do every object in my GIS like this, that will be quite a pain in the drain! |
| [12:41:36] | <ludwa6> | So i must think about how to get fields/ plantations/ beds in there. |
| [12:44:15] | <ludwa6> | ACTION making tea |
| [12:49:43] | <mstenta[m]> | gotta run, but here's the user guide - take a look at the mapping section and the assets >plantings for some good info |
| [12:49:47] | <mstenta[m]> | https://farmos.org/guide |
| [13:46:38] | * JustTB has quit (Ping timeout: 244 seconds) |
| [16:29:53] | * JustTB has joined #farmos |
| [17:16:49] | <mstenta[m]> | farmOS 1.0 has been released! |
| [17:16:59] | <mstenta[m]> | Oops I mean 1.1! |
| [17:17:01] | <mstenta[m]> | :-) |
| [17:17:04] | <mstenta[m]> | https://www.drupal.org/project/farm/releases/7.x-1.1 |
| [19:55:32] | * JustTB has quit (Quit: Leaving.) |