Hi All,
I've just released Osmosis 0.38.
http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.38.tgz
http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.38.zip
http://dev.openstreetmap.de:23457/hudson/job/osmosis-RELEASE-ant/38/
From changes.txt:
- Updated internal storage to
Hi Brett,
thanks for your elaborate answer! Now I am up to date. Some ideas regarding my
use case ...
Am 18.11.10 23:50, schrieb Brett Henderson:
Hi Andreas,
The change was made mostly for performance reasons. With a full planet imported into the
database, bounding box style queries are
M∡rtin Koppenhoefer dieterdre...@gmail.com wrote:
yes, I did this because I don't know how to get a proper package for
mapnik, thank you.
This should be as simple as apt-get install libmapnik-dev
Sven
--
Der normale Bürger ist nicht an der TU Dresden und schreibt auch
nicht mit mutt. (Ulli
Andreas Kalsch andreaskal...@gmx.de wrote:
I think it is not a good idea to use hstore because then we can drop SQL,
use NoSQL for storing data and use PostGIS/Postgres for Geometry only.
In the real world there is no black and white! Shure, hstore is comparable
to NoSQL aproaches, but why
One simple answer: The drivers do not work appropriately with complex SQL data types. In PHP or
node.js I will get a string that I have to parse, in MongoDB, I get a proper object or list. If I
used hstore in a consequent way (I like consequence and unification), I would have sets in sets, and
Hi,
Andreas Kalsch wrote:
One simple answer: The drivers do not work appropriately with complex
SQL data types. In PHP or node.js I will get a string that I have to
parse, in MongoDB, I get a proper object or list. If I used hstore in a
consequent way (I like consequence and unification), I
Am 19.11.10 10:06, schrieb Frederik Ramm:
Hi,
Andreas Kalsch wrote:
One simple answer: The drivers do not work appropriately with complex SQL data types. In PHP or
node.js I will get a string that I have to parse, in MongoDB, I get a proper object or list. If I
used hstore in a consequent way
Hi,
On 18.11.2010 22:24, Frederik Ramm wrote:
Martijn van Exel wrote:
Does the process of applying minutely updates only work when the
initial planet was a full planet, not an extract?
Is it possible to do this on extracts?
Yes (use the bounding box filter on osm2pgsql), but there will be
Ulf Lamping wrote:
Am 15.11.2010 23:48, schrieb Sebastian Klein:
No objections. Maybe we can switch the default value of
mappaint.zoomLevelDisplay from false to true afterwards. This way
authors of external style sets can create fancy scale dependent styles
and don't need to bother their users
Andreas Kalsch andreaskal...@gmx.de wrote:
Example for unnessessary complex schema design:
http://wiki.openstreetmap.org/wiki/DE:HowTo_minutely_hstore
You are welcome to design a better database scheme suitable for rendering :)
osm2pgsql output is evolution _not_ design.
Using a join in
I'm wanting to add a feature to Freemap (UK OSM-based hiking site) to allow
users to tag individual trails with route descriptions, interesting features
etc - with the eventual aim of allowing users to select a walking route and
have a ready-made route description (note these descriptions will
Hi,
On 11/19/10 10:25, Andreas Kalsch wrote:
I am sure there are some good uses for hstore, but as soon as you use
it, you are waiting for something like a document-oriented database. I
ask myself: Why do I need normal columns when there is hstore?
This is exactly what I was getting at. If
I agree - my approach is the playground approach: At first, keep it simple. For your purpose it is
correct to split the table. What about a partial index over 1 table? This is possible with Postgres.
Am 19.11.10 11:03, schrieb Sven Geggus:
Andreas Kalschandreaskal...@gmx.de wrote:
Example
On Fri, Nov 19, 2010 at 09:37:33AM +0100, Andreas Kalsch wrote:
If you're applying diffs to the database you can enhance the
osmosisUpdate() function (initially empty, but can be customised) to
keep your separate tags tables up to date during each diff
application. You will need to run
Nick,
I am sure that all routing programs must do something similar, but last year
Hermann Kraus produced
srtm2wayinfohttp://wiki.openstreetmap.org/wiki/Srtm2wayinfofor his
Google Summer of Code Project.
It does what you are talking about - looks for junctions between ways and
splits the ways into
Andy Allan kirjoitti:
On Thu, Nov 18, 2010 at 5:58 PM, Mâ¡rtin Koppenhoefer
dieterdre...@gmail.com wrote:
First I must admit that I don't know much about projections, reference
systems and geodetic datums.
I have recently experimented with homemade hillshading and contours,
and I found out
On Fri, Nov 19, 2010 at 7:37 PM, Andreas Kalsch andreaskal...@gmx.dewrote:
Hi Brett,
thanks for your elaborate answer! Now I am up to date. Some ideas regarding
my use case ...
Am 18.11.10 23:50, schrieb Brett Henderson:
Hi Andreas,
The change was made mostly for performance reasons.
On Fri, Nov 19, 2010 at 8:25 PM, Andreas Kalsch andreaskal...@gmx.dewrote:
Am 19.11.10 10:06, schrieb Frederik Ramm:
Hi,
Andreas Kalsch wrote:
One simple answer: The drivers do not work appropriately with complex SQL
data types. In PHP or node.js I will get a string that I have to parse,
On Fri, Nov 19, 2010 at 10:50 PM, Sarah Hoffmann lon...@denofr.de wrote:
On Fri, Nov 19, 2010 at 09:37:33AM +0100, Andreas Kalsch wrote:
If you're applying diffs to the database you can enhance the
osmosisUpdate() function (initially empty, but can be customised) to
keep your separate tags
Hmm, I've given all of this a bit more thought. Perhaps there is a need for
a simple schema that is easy for people to populate and utilise. I'm
quite happy with hstore, but it's not as simple for those familiar with
basic SQL.
The original reason I created the so-called simple schema was to
On Sat, Nov 20, 2010 at 12:09 PM, Brett Henderson br...@bretth.com wrote:
Hmm, I've given all of this a bit more thought. Perhaps there is a need
for a simple schema that is easy for people to populate and utilise. I'm
quite happy with hstore, but it's not as simple for those familiar with
Roman Byshko wrote:
Hi guys,
currently AddPrimitivesCommand does not have a constructor where OsmLayer
can be give as a parameter. I'm developing a plugin right now and need this
option.
May I ask what the plugin if for?
The patch in the attachment adds this functionality. Would you please
Olivier Croquette wrote:
Hi !
When I call this code from JOSM :
String[] formats = ImageIO.getReaderFormatNames();
for (String f:formats) {
System.out.println(f);
}
It outputs tiff (lowercase, other variants like tif, TIF and TIFF are
23 matches
Mail list logo
