[OSM-dev] GSoC OpenSurveyor week report #7
Viesturs Zarins
viesturz at gmail.com
Sat Aug 3 16:58:48 UTC 2013
Also, can you expand on the idea of recoding just timestamps.
Nowdays every device has GPS. The only benefit I see is saving battery with
dedicated GPS logger...
You would need subsecond precision time on the device running OpenSurveyor
- can you read that off GPS sensor? Network based time sync?
How is the JOSM plugin going? I would like to do an end-to-end test.
Viesturs
On Sat, Aug 3, 2013 at 7:53 PM, Viesturs Zarins <viesturz at gmail.com> wrote:
> Cool, i really hope that we have a great app at the end of week #13.
> Meanwhile what is the most useful way I can help you along? Unfortunately
> I don't have the free time to do actual coding.
>
> Waiting for week 8 :)
>
> Viesturs
>
>
> On Sat, Aug 3, 2013 at 2:15 PM, Pavel Melnikov <positron96 at gmail.com>wrote:
>
>> Hello Viesturs and thank you for report!
>>
>> Yes, so far the app looks much like OsmTracker, though one fundamental
>> difference is data format for export - it is not an .osm file, but a data
>> that will be used in JOSM plugin to create an osm file manually there. A
>> plugin is being created by Ilya Zverev who is a mentor for this project.
>> One more fundamental difference is that OpenSurveyor can work without GPS
>> present on the device (and without map). It records marker timestamps that
>> could be used on desktop to assign position based on external GPS track
>> recorded by other navigator system (garmin, etc)
>>
>> And yes, most of the features related to map UI that you mentioned are on
>> the todo-list, including freehand drawing and manual placing predefined
>> markers on the map. Though I do not think WMS will be implemented
>> (Simplified TMS as used in web-based maps probably will)
>>
>> On Sat, Aug 3, 2013 at 3:47 AM, Viesturs Zarins <viesturz at gmail.com>wrote:
>>
>>> Hi Pavel,
>>>
>>> I have been following your OpenSurveyor updates and I'm excited on the
>>> "walking papers idea". I tried the built app and worked so far without
>>> crashes.
>>>
>>> So far you seem to be duplicating the OsmTracker functions. It would
>>> make sense to start with the hardest / most useful feature first (the map)
>>> - as it would impact the app design greatly. I would hate to see the SOC
>>> done without getting to the most valuable feature. Getting an OsmTracker
>>> clone is not of any use.
>>>
>>> Anyway, it's nice to see somebody picking up where OsmTracker stopped.
>>> Some stuff I really would like to see implemented (in no particular
>>> order):
>>> - recording for images heading (automatic or manual) (check out how
>>> Ingress is doing it with portal submission GUI).
>>> - ability to save POIs by manually placing a point in a map.
>>> - selectable map background (OSM render, Bing maps, other sources,
>>> preferably full WMS support)
>>> - drawing freehand shapes on the map, (select a preset and draw an
>>> outline).
>>> - deletion/editing of POIs (you already have this).
>>> - displaying existing POIs in a separate layer, because raster maps
>>> often omit POIs close to other map features.
>>>
>>> Keep in mind that there are two quite different use cases for a
>>> surveying app:
>>> - a fresh region with no precision data - the GPS track is the main
>>> reference. OsmTracker is already doing pretty good job here.
>>> - densely mapped region possibly with precision data import / high
>>> precision imagery tracing - main activity is adding features to existing
>>> map. Placing a point relative to existing lines is more precise than GPS.
>>>
>>> Also how can I use the export files? A plugin for JOSM?
>>>
>>> Cheers,
>>> Viesturs
>>>
>>>
>>> On Fri, Aug 2, 2013 at 9:49 PM, Pavel Melnikov <positron96 at gmail.com>wrote:
>>>
>>>> Hi everyone.
>>>> I am having problems with my Internet provider (and he is having
>>>> problems with hardware) and that limits my ability to code very much. So
>>>> "done" list for this week is not that impressing:
>>>>
>>>> *Done this week:*
>>>>
>>>> - "Take photo" action is implemented (Closes #2)
>>>> - Markers can be deleted from the list (if they contained external
>>>> files, those are also deleted)
>>>> - New version of XML preset file, with localization postfix applied
>>>> to titles. One preset can be used for several languages. See
>>>> https://github.com/positron96/opensurveyor/wiki/Preset-XML-format#localization
>>>> - Almost full localization into English and Russian.
>>>> - Reworked button layout. It handles various number of buttons
>>>> nicely, leaves no extra space on edges. With >9 buttons it reduces sizes of
>>>> buttons
>>>> - POIs can be edited after creation by clicking on the item in the
>>>> list
>>>> - A lot of fixes and small improvements
>>>>
>>>> *TODO: *
>>>>
>>>> - Start work on a map UI
>>>> - Make session persistent (autosave and continue unsaved session)
>>>>
>>>> *Problems:*
>>>> Damn internet provider!! Can't code anything without stackoverflow and
>>>> google.
>>>>
>>>> As the last week, binary package can be found here:
>>>> https://github.com/positron96/opensurveyor/releases/tag/soc-week7
>>>>
>>>>
>>>> _______________________________________________
>>>> dev mailing list
>>>> dev at openstreetmap.org
>>>> http://lists.openstreetmap.org/listinfo/dev
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20130803/ac08be1d/attachment.html>
More information about the dev
mailing list