FLacombe

Yes, keep it open please

Targeted issue in the upside test on https://www.openstreetmap.org/node/1372343866 node didn't show up again so far. I give it a supplementary try on two nodes: * https://www.openstreetmap.org/node/1675479294 (https://osmose.openstreetmap.fr/fr/issue/48804168-c1a8-5c0c-3b36-0fbb4c6299a4) * No osm...

Understood and legit Can't you produce the points dataset only by using ST_Intersection postgis function? Something like INSERT INTO location_transitions (geom) SELECT ST_Intersection(line.geom,cable.geom) FROM rte_lines line INNER JOIN rte_cable cable...

Ok it's not so time consuming to produce data manually. I'll look for it shortly

Well... shortly meant 4 years! I've now a file with 20k rows matching with power=tower features. How can I make it available to osmose to create a new merge analysis?...

No script, it was made one shot in qgis. Can I put the data on data.gouv instead of github?

> I suggest anyway to describe what do you made, to be able to produce a update in the future. Methodology is described in #2004

Here we go: https://www.data.gouv.fr/fr/datasets/reseau-de-transport-delectricite-pylones-speciaux/ I'll make a PR for a dedicated merge analysis for that. Is item 8290 with class 2 or 10 suitable for that @frodrigo ?

Worrying. Can it be caused by X/Y swap or wrong decimal separator, maybe? However `Load_XY("X", "Y")` sounds correct.

I see this warning in particular that was caused by conflation more than ref (original OSM feature doesn't have ref:FR:RTE on it) https://osmose.openstreetmap.fr/fr/issue/4f07d9dc-27e1-ce8b-4651-354a277fb8a3 How Osmose was able to propose a...