I’m a bit embarrassed but I don’t have AgOpenGPS running on any computer or tractor just yet. Been a while since I was using it. Does it store kml files by default for each field? Are the boundary and ab line files separate?
So one kml file created per field? multiple entities in it? I’ll have to fire up AOG and get an example file created. Then I’m sure I can make a converter script using my existing isoxml code.
That looks really good! I’ll test your task data and see if my Fendt can process it.
If I understand you correctly, you took a field file from AOG, imported the KML file into QGIS, created a shapefile there, and then uploaded it to Geo-Bird. Is that correct?
Okay, that’s interesting. My last test’s with the AOG KML in GeoBird didn’t succeed. It could be possible that I have a layer for coverage and some AB and courve Lines. Maybe that is the issue, why I get an error.
I do have some AOG kml files here. I’ll make a python script to convert it to isoxml sometime tonight. Should be fairly straight forward to adapt the isoxml code I posted earlier.
On windows use py to invoke instead of python3. By default it creates a TASKDATA directory in the current directory. Passing -h to the script will give you a list of options including setting the operator, farm name, and full output path to write the ISOXML data.
Currently only does the AB Lines and Boundaries in a single Field.kml file.
This weekend I’ll put a simple Tk GUI on top of it and make it so you can point it at the AOG Fields folder and it will grab all the fields and put everything in a single TASKDATA bundle.
I am eager to see if this ISO XML option will work to import my lines into a Raven Viper 4! What is an estimated timeline on this release?
I want to input a bunch of lines manually using Lat/Lon and heading. While playing with the latest version 5.8.3, I notice that when entering values for an AB line, only the on-screen keyboard works for that. Can this be changed to allow input from a keyboard and accept copy/paste?
his would by far be the simplest and fastest solution.
Could you check before the release whether this also works in simulator mode on the home computer?
I don’t want to touch the version on my tractor anymore because the system is running very well at the moment (never change a running system…). I would perform the conversion at my desk by pulling copies of the field files from the tractor and then opening and saving them once in the simulator.
All of my fields and meadows are now converted and deposited for Fendt to read on its terminal.
At this point, I want to express my gratitude to everyone who participated in the discussion and shared their solutions. A special thanks to CommonRail, as I chose to follow his path.
I faced some initial challenges with QGIS and the Next Wayline Converter. Once those were overcome, I converted everything in just a few hours. Now my question to all of you: Is anyone currently in the same situation as I was a few days ago and doesn’t know how to proceed? If so, I would be willing to create a brief guide and publish it as a PDF or a forum post. I would only make the effort in the case of an urgent need, as in a few weeks (no, I don’t know the exact release date ), an updated version of AOG will be released, generating ISOXML files. This should make things much easier and more straightforward.
Important to note:
- I have only converted the outer boundary and ONE AB line.
- Inner boundaries (islands or other obstacles) are not considered.
- Manual tracing is required in QGIS.
- Only AB lines can be transferred.
- The use of both programs is not self-explanatory
Let me know, and I’ll see what I can do.
So now, Merry Christmas to all of you… or will have… or had!
P.S. Time zones can be headache-inducing