Hello!
I had taken an increasing interest in the data and software side of
OpenStreetMap over the last half year, quickly resulting in some hacking
on data analysis, map drawing and routing, leading to a C++ library
which is already usable (but still far form complete) and is designed to
handle
Hello!
For a Open Source project idea of mine I need vector data (with a good
enough resolution to display a country on screen, so no high resolution
stuff) for
* Continent borders (earth shape)
* Country borders (together with country name)
* Country capitals with position and name
* Big
Hello!
Because of you Gruß, I guess you are speaking german. Try:
Yes (Bonn) :-)
http://www.geofabrik.de/data/download.html
This as far as I know does not give me the required information. It contains
extras of the planet.osm by country (and partly smaller). So if I want the
position of
Hello!
(ah, another german :-)).
I have not yet found a more
convinient way than downloading a planet.osm
You may want to query the XAPI for the relevant data
http://wiki.openstreetmap.org/wiki/Xapi
Unlike the main API which restricts queries to 0.25 square degrees, XAPI
allows much
Hello!
in every country, in several counties, in certain towns, there are
properties characteristical for some object types of a certain kind.
Using boundary objects, one could create a geographical-bound css-like
object containing the tags to be used as defaults to overlay each such
Hello!
During my work on libosmscout I had the (obvious) idea to test the various
implementation aspect of my library against or (or multiple) defined *.osm
files.
This would have included testing for functionality like rendering things
like bridges, tunnels, layers and symbols but also routing
Hallo!
Why this mentality? It is trivial to implement a decompression
algorithm and some work better than others. Sounds like complaining
about stuff you don't have to care about.
I would not implement decompression myself, I have better things to
do. Thus I would a library for this. A
Hello!
However I'm wondering if there is any consensus on a standard OSM data
format optimised for vector rendering. There seems to be the OSM Mobile
No, as for the reason other people already have mentioned. For
libosmscout (clientside *offline* map rendering) the data format requires:
* As
Hello,
After days of efforts and workarounds, I decided to give up because this
mapsforge thing i loved is still too buggy. Also, the project has very little
activity since mid-2013 and it seems unlikely that these issues will ever be
fixed.
If you are still there… thanks for reading all
Hello,
I am looking for library that is processing OSM data into routing graph.
This graph will be later processed by my program so tight integration
with
existing routing engine is unneeded and unwanted.
libosmscout (libosmscout.sf.net) does generate a routing graph from a
parsed *.osm
to help me
getting started with it.
I'm Tim Teulings, the main author (but in recent times not the only
author) of libosmscout. I wrote the project idea and also likely would
be your mentor (though the rest of the libomscout community will likely
help, too).
Hello and welcome to Ope
Hello Christoph,
when it comes to read raw OSM dumps it's quite straightforward to parse
nodes: their geometry properties can be read alongside with their tags.
When it comes to linestrings and relations it is more complicated to access
their geometry: the geometry of referenced nodes needs to
Hello everybody,
Libosmium is not what you are looking for here. There are way too many
things you'd have to implement yourself on top of libosmium. Have a look
at https://github.com/Framstag/libosmscout , maybe that's something for
you.
Right. Libosmscout gives offers you most of the
Hello Kyle,
Yeah, I sent my reply to Jochen before I realized everything that libosmscout
implements, like Jochen says in the description of libosmium it's meant for
data manipulation, not for navigation. Libosmscout does everything that I need
for my application. You and Jochen are both
14 matches
Mail list logo
