And have a look here:
https://bitbucket.org/maproom/qmapshack/wiki/DeveloperCommitCode
If you need help on that use IRC to contact us. My IRC client is usually
active on working hours. But I might need some time to check it.
Am 12.07.2016 um 13:04 schrieb Oliver Eichler:
> Have a look into the folder:
>
> src/gis/rte
>
> That's where you find all route related code. CGisItemRte is the route
> object itself. Inside the object there is a structure rte_t holding all
> primary data of a route. A route point rtept_t is derived from a
> waypoint wpt_t plus some additional data, like it's sub-points (the
> polyline to the next real route point). the wpt_t structure has a member
> "name". That's probably where other programs store that information. But
> I haven't checked.
>
>
> If you search the source for "CGisItemRte(" you will find all locations
> where a new route item is created. You have to analyze each one for
> necessary changes. Well and finally do the changes, constantly testing
> if something gets broken.
>
>
> Oliver
>
>
> Am 12.07.2016 um 12:49 schrieb Wolfgang Rosner:
>> Am Tue, 12 Jul 2016 09:08:12 +0200
>> schrieb Oliver Eichler <[email protected]>:
>>
>>> I wait for someone really interested
>>> in routes to pick-up the topic.
>> ... nacktijall, ick hör dir trapsen...
>> (sorry, I'm afraid this is not really correct english... ;-)
>>
>>
>>
>> can you provide me some pointers where to start looking in the source
>> code?
>>
>> I haven't done any serious work in C yet, just some minor changes
>> of existing code.
>> My GUI programming skills are age old "hello world" level in java.
>>
>> But this does not mean that it should not be possible....
>>
>> If I have some points where to start, I might try to work back and
>> forth to get an idea whether I think I am able to produce usable code
>> extensions.
>>
>>
>>
>> I think, somewhere (after finishing the "create route" dialog) you get
>> waypoints as input and feed them to the routino API, right?
>> routino (or a generic routing wrapper) will return you the route.
>> And you will instantiate some kind of route object, containing some
>> routepoints, I suppose?
>>
>> When I remember the command line interface of routino, there are
>> several output formats, one of them along with all addresse details for
>> every route point. Actually, I think you must retrieve them already
>> when you display the routing instructions.
>>
>> So the job would be to collect the labelling data in descending order,
>>
>> - optionally: editable by user
>> - inherited from waypoint (first priority to implement)
>> - routino routing information (second priority to implement)
>> - optionally: lookup address, maybe in routino
>>
>> and write it into the route point properties.
>>
>> Initially, when I thought of writing a workaround hack, I considered it
>> as a task of writing xml (see below).
>> However, I suppose that QMS internally
>> uses another data structure where to store object information.
>> Where is this defined for routepoints?
>> How flexible is it? can it easily expanded to carry labels?
>> Or would this break myriads of dependencies?
>>
>> Of course, when writing gpx, this internal information must be
>> transferred to xml format.
>>
>> To have a visible goal,
>> here is a snippet of gpx generated by gpsbabel which contains
>> both labelled waypoints and routepoints:
>>
>> --8<----------
>> <wpt lat="49.432260000" lon="11.091530000">
>> <name>Nürnberg Hermundurenstraße 17</name>
>> <cmt>Nürnberg Hermundurenstraße 17</cmt>
>> <desc>Nürnberg Hermundurenstraße 17</desc>
>> </wpt>
>> <rte>
>> <rtept lat="49.432260000" lon="11.091530000">
>> <name>Nürnberg Hermundurenstraße 17</name>
>> <cmt>Nürnberg Hermundurenstraße 17</cmt>
>> <desc>Nürnberg Hermundurenstraße 17</desc>
>> </rtept>
>> --8<----------
>>
>> This is from the example I used in the "import route points" doc
>> and for the device screen shots in the issue text. Details here
>> https://bitbucket.org/snippets/wrosner/n4oK5
>>
>>
>>
>> So there is nothing to reinvent, just to transfer from waypoint to
>> routepoints.
>>
>> At least, so I hope.....
>>
>
> ------------------------------------------------------------------------------
> What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
> patterns at an interface-level. Reveals which users, apps, and protocols are
> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
> J-Flow, sFlow and other flows. Make informed decisions using capacity planning
> reports.http://sdm.link/zohodev2dev
> _______________________________________________
> Qlandkartegt-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Qlandkartegt-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
