Re: [OSM-dev-fr] OSMOSIS --derive-change à partir d'une db pgsnapshot et d'un fichier pbf
Tu tombes bien, je suis sur Osmosis àtester des trucs aussi, là. --derive-change doit prendre deux fichiers xml en entrée, ce serait (sans tester): osmosis --read-pgsql host=localhost database=X user=X password=X --write-xml --read-pbf file=X.pbf --derive-change --write-xml-change file=X.osc Yves On 04/16/2014 10:59 AM, Marc Ducobu wrote: Bonjour, Est-ce possible de créer un fichier osc à partir d'une db pgsnapshot et d'un fichier pbf ? Selon http://blog.gmane.org/gmane.comp.gis.openstreetmap.region.fr.devel/month=20130301, ça semble possible. J'ai tenté la commande : osmosis --read-pgsql host=localhost database=X user=X password=X --read-pbf file=X.pbf --derive-change --write-xml-change file=X.osc Qui déclanche l'erreur suivante : org.openstreetmap.osmosis.core.OsmosisRuntimeException: Task 3-derive-change does not support data provided by default pipe stored at level 1 in the default pipe stack. Est-ce possible à faire ? Si oui comment faut-il adapter la commande ? Bonne journée. Marc ___ dev-fr mailing list dev-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev-fr ___ dev-fr mailing list dev-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev-fr
Re: [OSM-dev-fr] OSMOSIS --derive-change à partir d'une db pgsnapshot et d'un fichier pbf
Euh, non, plutot passer d'un datatset à un entity stream: osmosis --read-pgsql host=localhost database=X user=X password=X --dataset-dump --read-pbf file=X.pbf--derive-change --write-xml-change file=X.osc On 04/16/2014 10:59 AM, Marc Ducobu wrote: Bonjour, Est-ce possible de créer un fichier osc à partir d'une db pgsnapshot et d'un fichier pbf ? Selon http://blog.gmane.org/gmane.comp.gis.openstreetmap.region.fr.devel/month=20130301, ça semble possible. J'ai tenté la commande : osmosis --read-pgsql host=localhost database=X user=X password=X --read-pbf file=X.pbf --derive-change --write-xml-change file=X.osc Qui déclanche l'erreur suivante : org.openstreetmap.osmosis.core.OsmosisRuntimeException: Task 3-derive-change does not support data provided by default pipe stored at level 1 in the default pipe stack. Est-ce possible à faire ? Si oui comment faut-il adapter la commande ? Bonne journée. Marc ___ dev-fr mailing list dev-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev-fr ___ dev-fr mailing list dev-fr@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev-fr
[OSM-dev] glitch in minutely replication stream
The minutely replication stream was blocked for 12 hours due to a server problem. The broken sequence number was 834038, with 038.state.txt and 038.osc.gz being zero length files. When the replication was restarted these files were replaced with real data. Unfortunately this has caused a problem for using osmosis to fetch these changes automatically. Once the replication resumed it appears that osmosis skipped the changes in the new '038 files and downloaded '039 onwards. This affected the OSM rendering servers (Yevaud Orm) and I have forced them back to process everything from '037+ again to ensure the changes in the 038 file are rendered. Anyone else running services using the minutely diffs might need to do the same. Jon ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] glitch in minutely replication stream
Can you provide cookbook instructions for those of us running OSM tile servers based on the switch2osm.org instructions? Specifically, what does one do to forced them back to process everything from '037+ again? Lynn (D) On 4/18/2014 12:50 PM, Jon Burgess wrote: The minutely replication stream was blocked for 12 hours due to a server problem. The broken sequence number was 834038, with 038.state.txt and 038.osc.gz being zero length files. When the replication was restarted these files were replaced with real data. Unfortunately this has caused a problem for using osmosis to fetch these changes automatically. Once the replication resumed it appears that osmosis skipped the changes in the new '038 files and downloaded '039 onwards. This affected the OSM rendering servers (Yevaud Orm) and I have forced them back to process everything from '037+ again to ensure the changes in the 038 file are rendered. Anyone else running services using the minutely diffs might need to do the same. Jon ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] glitch in minutely replication stream
From: Lynn W. Deffenbaugh (Mr) [mailto:ldeff...@homeside.to] Sent: Friday, April 18, 2014 3:13 PM To: dev@openstreetmap.org Subject: Re: [OSM-dev] glitch in minutely replication stream Can you provide cookbook instructions for those of us running OSM tile servers based on the switch2osm.org instructions? Specifically, what does one do to forced them back to process everything from '037+ again? 1. Edit crontab to stop updates. 2. Wait until all updates have stopped (i.e. osm2pgsql is no longer running) 3. Open /var/lib/mod_tile/.osmosis/state.txt in a text editor 4. Change the sequenceNumber line to read sequenceNumber=834037 5. Edit crontab to start updates Note: Untested, but should work. ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] glitch in minutely replication stream
Paul, how much diffs will be processed ? On 19 avril 2014 02:47:07 UTC+02:00, Paul Norman penor...@mac.com wrote: From: Lynn W. Deffenbaugh (Mr) [mailto:ldeff...@homeside.to] Sent: Friday, April 18, 2014 3:13 PM To: dev@openstreetmap.org Subject: Re: [OSM-dev] glitch in minutely replication stream Can you provide cookbook instructions for those of us running OSM tile servers based on the switch2osm.org instructions? Specifically, what does one do to forced them back to process everything from '037+ again? 1. Edit crontab to stop updates. 2. Wait until all updates have stopped (i.e. osm2pgsql is no longer running) 3. Open /var/lib/mod_tile/.osmosis/state.txt in a text editor 4. Change the sequenceNumber line to read sequenceNumber=834037 5. Edit crontab to start updates Note: Untested, but should work. ___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté.___ dev mailing list dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/dev
[josm-dev] New JOSM Maps database feature
Hi,
If you go to https://josm.openstreetmap.de/wiki/Maps and its subpages, you
may notice these {view} entries behind the names. These lead to a new
page using OpenLayers3 to show the content of an entry including icons,
attribution, bounding boxes and surrounding shapes.
In my eyes that's a good instrument to verify the data entries and fix
outdated or wrong information. Feel free to update entries when you find
defective ones (i.e. like unclosed polygons).
Some notes:
- Type wms is not yet supported. I need to write JavaScript code which is
able to use JOSM URL and Tiled-WMS method with OpenLayers.
- No coordinates or zoom level displayed ATM, have to find out how to do
this properly with OL3.
- min-zoom is not supported by OpenLayers3. The initial zoom level is set
to the min-zoom, but Openlayers allows you nevertheless to zoom out.
- Preview mode not yet supported.
Help to fix the first two of above issues welcome. If someone makes an
example in JavaScript, I'll implement it in the server code.
Suggestions:
a) Together with that I'd like to add a tested=2014-05-04 tag to entry
to state when such an entry has last been checked to exist.
b) And in https://josm.openstreetmap.de/ticket/9914 we have the proposal
to add a new id tag inside entry with an ID compatible to iD for
automatic update possibility in JOSM.
Comments welcome.
Ciao
--
http://www.dstoecker.eu/ (PGP key available)
___
josm-dev mailing list
josm-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/josm-dev
