Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Your problem is with your XPath selector. When you write:</p> <pre><code>i.xpath('//xmlns:AltitudeMeters') </code></pre> <p>you start at the root of the document and find every <code>&lt;AltitudeMeters&gt;</code> element at any level, not just children of the track that you are currently looking at. The minimum change you can make is to alter your XPath selector to be <code>.//xmlns:AltitudeMeters</code> (note the leading period):</p> <pre><code>doc = Nokogiri::XML(xml) tracks = doc.xpath( '//xmlns:Track' ) # You don't need to specify the namespace node_values = tracks.map do |track| { 'AltitudeMeters' =&gt; track.xpath('.//xmlns:AltitudeMeters').text } end p node_values #=&gt; {"AltitudeMeters"=&gt;"298.6267090"}, {"AltitudeMeters"=&gt;"498.6267090"}] </code></pre> <p>Additionally, if there is only one <code>Trackpoint</code> per track, I would use <code>at_xpath</code> instead, which returns the first matching element. Indeed, unless your schema is volatile, I would also specify exactly where to find the Altitude I wanted:</p> <pre><code>node_values = tracks.map do |track| { 'AltitudeMeters' =&gt; track.at_xpath('./xmlns:Trackpoint/xmlns:AltitudeMeters').text } end </code></pre> <p>Finally, since you seem to be working with a document with a single namespace, note that you can ask Nokogiri to drop all namespaces to make your life simpler:</p> <pre><code>doc = Nokogiri::XML(xml) doc.remove_namespaces! node_values = doc.xpath( '//Track/Trackpoint' ).map do |track| { 'Altitude' =&gt; track.at_xpath('./AltitudeMeters').text.to_f, 'Latitude' =&gt; track.at_xpath('./Position/LatitudeDegrees').text.to_f, 'Longitude' =&gt; track.at_xpath('./Position/LongitudeDegrees').text.to_f } end require 'pp' pp node_values #=&gt; [{"Altitude"=&gt;298.626709, "Latitude"=&gt;52.4864997, "Longitude"=&gt;13.3531452}, #=&gt; {"Altitude"=&gt;498.626709, "Latitude"=&gt;52.4864997, "Longitude"=&gt;13.3531452}] </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POValues 'doubled up' selecting out of XML in Nokogiri
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPhrogz
    1. USPhrogz
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POValues 'doubled up' selecting out of XML in Nokogiri
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COcool! thank you
      singulars
      1. PO
      1. USjens freudenau
    2. CO@jens You're welcome! Note that if this answer solved your problem, you should 'accept' it (checkmark) so that it may help others. (And it gives you +2 rep ;)
      singulars
      1. PO
      1. USPhrogz
    3. COI use this because removing namespace gave me an segmentaion fault and after update nokogiri I got an Internal Server error `code` tracks = doc.xpath( '//xmlns:Trackpoint' ) node_values = tracks.map do |track| { 'AltitudeMeters' => track.xpath('.//xmlns:AltitudeMeters').text, 'DistanceMeters' => track.xpath('.//xmlns:DistanceMeters').text, 'LatitudeDegrees' => track.xpath('.//xmlns:LatitudeDegrees').text, 'LongitudeDegrees' => track.xpath('.//xmlns:LongitudeDegrees').text } end `code` And how can I format code in the comment field?
      singulars
      1. PO
      1. USjens freudenau
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload