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 implem
Thanks Toby, this is a bit more involved than I realized!
Andy
On 7/15/2011 7:53 PM, Toby Murray wrote:
> 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 pre
> 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 and datasets of no
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 th
#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:
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 bu
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
wi
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 node
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 changes
10 matches
Mail list logo
