You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have export to Organic Maps. We don't have import from Organic Maps. I see two parts to figure out.
Ideally we could get bookmark sync working, but I don't want to count on that any time soon.
Two tasks
Parsing KML completely
The KML generated by Desert Atlas is very simple. There are tags we don't use. I think the files generated by Organic Maps uses more. I don't want to miss anything. Maybe we can find a library.
UI: Phone / Browser / App
The UI for exporting to the app is already not ideal. Download a kml file via browser, open it, maybe your OS suggests your map app.
The reverse seems inherently worse. Save the file in Organic Maps. Go to browser, click import, find the file. Better than nothing but we can't pass it off as a smooth experience like the other direction.
Is there some sort of "share from Organic Maps to browser"? I don't think that exists. And anyway that's probably up to Organic Maps, not us.
Simpler version
All this said, it occurs to me that it would be useful to export/import KML between grains. Supposing you want to back up a grain without the downloaded maps. We wouldn't have to worry about the UI issue, and we could just make sure we parse the files we create. Though, we'd have to warn that we're not (yet) parsing most KML files.
The text was updated successfully, but these errors were encountered:
We have export to Organic Maps. We don't have import from Organic Maps. I see two parts to figure out.
Ideally we could get bookmark sync working, but I don't want to count on that any time soon.
Two tasks
Parsing KML completely
The KML generated by Desert Atlas is very simple. There are tags we don't use. I think the files generated by Organic Maps uses more. I don't want to miss anything. Maybe we can find a library.
UI: Phone / Browser / App
The UI for exporting to the app is already not ideal. Download a kml file via browser, open it, maybe your OS suggests your map app.
The reverse seems inherently worse. Save the file in Organic Maps. Go to browser, click import, find the file. Better than nothing but we can't pass it off as a smooth experience like the other direction.
Is there some sort of "share from Organic Maps to browser"? I don't think that exists. And anyway that's probably up to Organic Maps, not us.
Simpler version
All this said, it occurs to me that it would be useful to export/import KML between grains. Supposing you want to back up a grain without the downloaded maps. We wouldn't have to worry about the UI issue, and we could just make sure we parse the files we create. Though, we'd have to warn that we're not (yet) parsing most KML files.
The text was updated successfully, but these errors were encountered: