Replies: 4 comments
-
Looks like at the moment you are just manually releasing user waypoints upon submission. Do you expect to use an API for user submission in the future? I think it would be a great feature to be able to submit waypoints to your API via share |
Beta Was this translation helpful? Give feedback.
-
Kml conversion looks simple, perhaps you could convert after pulling? I have too many features to add now but perhaps when I'm done. Could you explain further what you mean about the API? postMarker is my submission API |
Beta Was this translation helpful? Give feedback.
-
Yeah I definitely could convert what ever format you serve, though I'm not sure what that is. Perhaps you could update your README.md with information like that (url, format, etc)? Most mapping software supports kml, so it may make sense to add that. Also maybe include a developer guide on how to build, test, etc... This would be helpful for developers looking to contribute. Sorry I haven't looked deeply into your code, and might be making alot of assumptions, but I was thinking you had or was planning to have something like a REST API where other applications can get your data or even post directly to you. For example, OpenTrail DB --> OpenTrail API --> Mappoff (preset) Hope this makes sense. Definitely love your idea of sharing hiking data freely! |
Beta Was this translation helpful? Give feedback.
-
/api/getData returns a geoJSON, while /api/postMarker takes a custom JSON. Documentation is sparse to nonexistent but good idea, I'll wait until features are more stable because it may still change. |
Beta Was this translation helpful? Give feedback.
-
This sounds like a great project to be able share info freely among the hiking community! If you haven't already considered it, it would be great to have your API support export into kml/kmz. I think it would be a great addition to the presets of the Mappoff application.
Beta Was this translation helpful? Give feedback.
All reactions