Re: [Libosmscout-development] osmscout-server
Library for OpenStreetMap offline rendering and routing
Status: Beta
Brought to you by:
tteuling
|
From: Lukáš K. <luk...@ce...> - 2016-09-21 08:46:43
|
Ok, after one day, when I was thinking how it can be used, it makes sence to me :) There is a lot of libraries and apps that are using online tile maps. It can be simply patched to use local server for offline usage. I dont see reason why authors should not accept such patches. Did you try to send patches to Maep or Modrana authors? Lukas Dne středa 21. září 2016 9:58:07 CEST rinigus napsal(a): > Morning! > > this looks like a great todo list, which I had, partially, in my mind as > well. > > Re style sheets: Style sheets would have to be known to the server, true. > But its possible to extend URL syntax to include style sheet name (such as > dark and light, for example) leading to URL like > http://localhost:8080/light.oss/0/1/....png . Assuming that multiple > StyleConfig's can access the same database, it shouldn't be a problem. > There are issues related to efficient implementation of handling multiple > style sheets, but I sure they can be resolved. > > Re custom rendering: I don't know what you mean by that. Maybe we could > come back to it later when I get the code in better shape. > > Re search and routing: I was planning to implement something like mapzen > URL search scheme (example https://search.mapzen.com/v1/search?text=YMCA > ). For routing, it should be possible to construct something similar. As I > could see, your demo programs would offer an excellent starting point and I > would 'just' need to wrap them into the server and return results in the > form of JSON. > > * OS specific, no iOS & Android: True, my focus is on the platforms that I > use. As for iOS and Android, I don't know how simple or hard would be to > support it. It would require GUI application in addition that can be > interfaced. I don't know also how well QML/Qt is supported in Android/iOS > and what are restrictions imposed by the corresponding stores. I guess, if > it all works, then others can try to adapt the server to these platforms as > well. > > * Re overhead: no comment for now, let's see how good or bad it is :) > > * Re vector tiles: why not to serve them. As soon as libosmscout would be > able to dump them into a binary format and that's the format that the > client expects, the server should be able to forward it without any issues. > Again, URL scheme could support that when needed. > > I'll keep you folks updated on the progress and will let you know when its > ready for some testing. > > Best wishes, > > rinigus > > On Wed, Sep 21, 2016 at 8:03 AM, Tim Teulings <ti...@fr...> wrote: > > Hello everybody, > > > > I think this is a good idea that gives another options and solves some > > design problems the library has. A central services avoid the > > situation where multiple applications install the same offline data. > > It does though also comes with some negative side effect besides the > > one you mentioned: > > * Everybody is using the same style sheet > > * No custom rendering (refresh, ....) > > * Only map drawing - though the central service could be enhanced with > > further REST services to centralize routing calculation, search,...and > > map the XXXService APIs to REST calls. > > * The current implementation is very OS specific (targeting android or > > iOS could be helpful, too) > > * There is some overhead (which is the main reason I did not start > > something like this on my own) > > > > So why not... > > > > For me it would be interesting if we also could offer vector tiles? > > > > -- > > Gruß... > > > > Tim > > > > ------------------------------------------------------------ > > ------------------ > > _______________________________________________ > > Libosmscout-development mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libosmscout-development |