Well I looked at this tonight. It looks like postgis is perfectly
happy creating a linestring for a single node way. However it is not
considered valid. So doing a st_isvalid() on the resulting linestring
returns false. I am not sure what all the implications of this are
however it looks like it
On 11/09/2012 06:57 AM, Paul Norman wrote:
You should be able to create a linestring where the first and last point
are the same. This would be better than a phantom node.
No, because this is not a valid geometry (in ST_IsValid terms).
Paweł
___
Hi all,
On Friday I have implemented a simple validation in the OWL plugin that
checks whether given entity action (create/modify/delete) can be applied
to the current database state. See implementation: [1].
By invalid action I mean a situation when there is a delete action
in the pipeline
Hi All,
I'm keen to switch the Osmosis build over to using the Gradle build tool
instead of Ant. I've just checked in some new Gradle scripts. The current
Ant build works reasonably well, but I've lost many hours getting it to its
current point, and introducing new features is always a lot of
Hi Greg,
On 12 November 2012 03:24, Greg Troxel g...@ir.bbn.com wrote:
Does gradle require anything else (other than a JDK/JRE) in terms of
dependencies?
No. You just need a JDK 1.6 or higher. It has less dependencies than the
Ant build because it requires Ant to be installed along with a
On 11.11.2012 11:24, Paweł Paprota wrote:
By invalid action I mean a situation when there is a delete action
in the pipeline but there is no entity in the database to delete. Or
modify action with version X when there is no version X - 1 in the
database but some other version.
Do you have
Hi Stephan,
Do you have --simplify-change or --sort-change in your pipeline? I
have not fully thought about it, but it might introduce funny effects
if you rely on a special order of actions.
No. The exact pipeline is:
osmosis -v --rri --lpc --write-owldb-change authFile=~/authFile