Hi,
This week I had a little blocker with deleting some subgraph nodes and
relations. For that I made a seperate test to identify the problem and
try to find a solution.
Apart from that I integrated a additonal spatial type function to get
the distance between geometry nodes and
updated the
Hi Andreas,
Sounds like good progress over all. It is only a week to the mid-terms, so
it would be good to do a general code overview and see if this can be
integrated with trunk. Shall we plan for a review and test integration in
the middle of next week?
Regards, Craig
On Sat, Jul 2, 2011 at
As far as I know there is no internal support for transparent traversals
across shards. Generally people are doing that in the application layer.
However, I think there might be a middle ground of sorts. I we modify the
relationship expander, I could imagine that relationships that are between
Hi Boris,
You do not need to read the property yourself from the node, rather use the
GeometryEncoder for this, it converts from the internal spatial storage to
the Geometry class, which you can work with. If you call geom.toString() you
will get a nice printable version (in WKT). Using the
Hi Boris,
Ah! You are using the REST API. That changes a lot, since Neo4j Spatial is
only recently exposed in REST and we do not expose most of the capabilities
I have discussed in this thread, or indeed in my other answer today.
I did recently add some REST methods that might work for you,
We are using node-id property references (the node id as a property), qualified
with a logical server reference, to provide this type of binding across
graphs. If you combine these with an index, you can actually get a lot of the
functionality of relationships cross graph, spanning physical
Wow that's great! I'll try it out asap. This leads to my next question: how
do I update the geometry in a layer, rather than add new? What I am thinking
of doing is having a multipoint geometery associated with each of my user
nodes which will represent their location history. My plan is to add
Actually,
Andreas Wilhelm is working right now on updating geometries.
Sent from my phone.
On Jul 2, 2011 5:00 PM, Boris Kizelshteyn bo...@popcha.com wrote:
Wow that's great! I'll try it out asap. This leads to my next question:
how
do I update the geometry in a layer, rather than add new? What
Everything written to the database with successful transactions is persisted
and will be accessible in any following sessions. Just _don't_ think of a
GraphDatabaseService instance as a short lived object (like a SQL
connection), but instead see it more as your database server which benefits
from
Hi fellow graphistas,
In testing our upcoming 1.4 GA release, we discovered a subtle bug in our 1.4
M05 release that can result in database corruption. Under certain circumstances
with clean shutdowns of the database it's possible that freed IDs will be
recycled more than once, meaning that on
Hi Jim,
thanks for reporting anyway. We run some structr instances on the latest
milestone, so I'd be interesed in some more details:
- Is 1.4 M04 safe?
- How can we detect whether corruption occured, and is there a way
recover from that?
- Is this bug contained in the current SNAPSHOT?
As I understand it, Andreas is working on the much more complex problem of
updating OSM geometries. That is more complex because it involves
restructuring the connected graph.
The case Boris has is much simpler, just modifying the WKT or WKB in the
editable layer. In the Java API this is simply
Is it possible to get distinct results in Cypher? Something like
START a=(1) MATCH (a)-[:FOOTYPE]-(b) RETURN DISTINCT b
I have a scenario where a single node may be connected multiple times
to another node, and I only want that other node to be returned once.
I'd hate to have to do this in my
Hi,
Recent builds of Neo4j-Spatial no longer like Peters new bounding box query.
Peter is on vacation, and I am not familiar with the code (nor cypher), so I
thought I would just dump the error message here for now in case someone can
give me a quick pointer.
The line of code is:
Query query =
Just pinged Andres on this. The r:TYPE is the culprit.
Sent from my phone.
On Jul 3, 2011 12:06 AM, Craig Taverner cr...@amanzi.com wrote:
Hi,
Recent builds of Neo4j-Spatial no longer like Peters new bounding box
query.
Peter is on vacation, and I am not familiar with the code (nor cypher),
We decided that we needed a meta-data character that wasn't :. Instead,
you now write: r~TYPE
Andrés
On Sun, Jul 3, 2011 at 12:44 AM, Peter Neubauer neubauer.pe...@gmail.comwrote:
Just pinged Andres on this. The r:TYPE is the culprit.
Sent from my phone.
On Jul 3, 2011 12:06 AM, Craig
16 matches
Mail list logo