Parveen,
Have a look at the first bit of the source code. I think the default
location is specified there.
I think my first reply was wrong - it is an environment variable, not a
command line parameter, but you will see that when you look at the top of
the file.
Graham
from my phone
On 15 Jul
On Fri, Jul 15, 2011 at 11:37 AM, Graham Jones grahamjones...@gmail.com wrote:
Parveen,
Have a look at the first bit of the source code. I think the default
location is specified there.
I think my first reply was wrong - it is an environment variable, not a
command line parameter, but you
Hi, currently I extract a piece of map data and store it. Later on I
want to apply a set of changes to it. Here are my commands:
osmosis --read-pbf britishisles.osm.pbf --buffer bufferCapacity=12000
--bb bottom=51 top=52 left=-1 right=1 --write-pbf london.osm.pbf
osmosis --read-xml-change
The problems with change files + bounding boxes is that the change
file only contains the NEW version of objects. So when you clip it to
a bounding box, nodes that started out inside of the bbox and were
moved outside will get eliminated from the change and you will keep
the old version of the
Thanks.
You mentioned that the change file only contains the new version of
objects. If a node is being deleted is the lat/lon in the change file
guaranteed to be identical to the lat/lon for that node an up-to-date
planet file?
Are there any options to getting the old location of a moved node
It's always nice to release something for SotM, even if you're not there. :)
https://github.com/systemed/halcyon_pdf
ActionScript 3 PDF renderer. Uses MapCSS (natch :) ).
Pre-pre-pre-pre-pre-pre-alpha. Really only half finished. Full of
FIXMEs. Requires AS3 knowledge and patience to
#3674: object Object instead of GPS data
+---
Reporter: Zverik | Owner: potlatch-dev@…
Type: defect | Status: reopened
Priority: major | Milestone:
#3674: object Object instead of GPS data
+---
Reporter: Zverik | Owner: potlatch-dev@…
Type: defect | Status: reopened
Priority: major | Milestone:
Not 100% sure. The API documentation in the wiki does state that
lat/lon are required parameters for a delete operation. It doesn't say
that they must be the same as they were for the previous version of
the object. So I'm not sure if you can count on the lat/long being
identical.
Regardless of
Are there any options to getting the old location of a moved node
without writing my own Osmosis patch (if that's even possible)?
I think this cannot be solved easily. But I like your Idea of creating a change
file extract. One could implement it like this:
Exclude all create and modify
On 7/15/2011 7:55 PM, mar...@gmx.eu wrote:
Are there any options to getting the old location of a moved node
without writing my own Osmosis patch (if that's even possible)?
I think this cannot be solved easily. But I like your Idea of creating a
change file extract. One could implement it
Le 13/07/2011 21:09, Thomas Petillon a écrit :
Ce patch s'applique à Name_Toponymie.py et permet de régler le problème
des (nombreux) noms de lieu bretons contenant « c'h », dont l'apostrophe
est détectée comme une coupure de mot, ce qui déclenche une erreur de
toponymie due à la majuscule
Bonjour vous tous,
Je suis en train de regarder en quelle mesure le fameux changement de
licence affectera les la Nouvelle-Calédonie, et je suis tombé sur ce
changeset, dont l'auteur n'est pas affiché:
http://www.openstreetmap.org/browse/changeset/15678
Comment savoir s'il va accepter le
2011/7/15 Frédéric Rodrigo fred.rodr...@gmail.com
Le 13/07/2011 21:09, Thomas Petillon a écrit :
Ce patch s'applique à Name_Toponymie.py et permet de régler le problème
des (nombreux) noms de lieu bretons contenant « c'h », dont l'apostrophe
est détectée comme une coupure de mot, ce qui
(Désolé pour le double envoi, j'ai fait une fausse manipulation.)
2011/7/15 Frédéric Rodrigo fred.rodr...@gmail.com
Le 13/07/2011 21:09, Thomas Petillon a écrit :
Ce patch s'applique à Name_Toponymie.py et permet de régler le problème
des (nombreux) noms de lieu bretons contenant « c'h »,
SELECT Y(ST_AsText(ST_Transform(way, 4326))),
X(ST_AsText(ST_Transform(way, 4326))),
Distance(way, (SELECT way FROM planet_osm_point WHERE
osm_id=582505865))::int,
amenity || ' ' || name, 'icon.png', '16,16', '0,0'
FROM planet_osm_point P WHERE (amenity ILIKE 'res%' OR amenity ILIKE
16 matches
Mail list logo
