GeoRssFeed Format

GeoRssFeed Format


This chapter is aimed at content partners. Content partner refers to partners who deliver dynamic content to eT4.META (content syndication).

Structure


The exchange format for dynamic content is standardized GeoRSS feed. For more information and a general introduction to the specifications take a look at http://www.georss.org/. Why did we choose this kind of format is selected? GeoRSS feeds are based on the coom and widespread technology of RSS feeds. The advantage is that you do not have to worry about technical development of the interface. Only the content level, the necessary meta informations, have to be defined. Therefor the implementation can be kept simple and the cost of interface development and projects can stay low. The fact that it is an established standard the individual feeds can be used for other projects. Thus, the feeds are used for non-recurring engineering costs for a variety of projects and clients. Particularly interesting for content providers is likely to be the fact that there is here no central data storage. The contents remain with content partners and can be accessed in real time.

Definition

Each item-tag represents one item (one pindata object). 
You can find more information about the feed structure in these articles:

Take a look at the xsd-schema-documentation or the schema itself for the GeoRSS-Feeds.

1. RSS header description

RSS Header

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <rss version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:georss="http://www.georss.org/georss/11" xmlns:ec="urn:schemas-econtent:rss"></rss></rss></rss></rss>
  3.     [...]
  4. </rss>
The header should be adopted completely.

RSS Channel

  1. <channel>
  2.     [...]
  3. </channel>
Informations and description for the whole feed.

Title


  2. <channel>
  3.     [...]
  4.     <title>eContent.Maps(bayern) - POI (Quality: 100%)</title>
  5.     [...]
  6. </channel>
georss-feed-title
  1. <channel>
  2.     [...]
  3.     <link>http://maps.hubermedia.de/</link>
  4.     [...]
  5. </channel>
Link to the georss-feed provider.

Description

  1. <channel>
  2.     [...]
  3.     <description>GeoRSS-Feed für eContent.Maps(bayern) POI</description>
  4.     [...]
  5. </channel>
A short description of the feed itself

Language

  1. <channel>
  2.     [...]
  3.     <language>de-DE</language>
  4.     [...]
  5. </channel>
Defines the language of the feed an objects

  1. <channel>
  2.     [...]
  3.     <copyright>hubermedia</copyright>
  4.     [...]
  5. </channel>
Provide all needed copyright informations

managingEditor

  1. <channel>
  2.     [...]
  3.     <managingEditor>support@hubermedia.de</managingEditor>
  4.     [...]
  5. </channel>
Mail adress of the responsible person for the objects

Webmaster

  1. <channel>
  2.     [...]
  3.     <webMaster>support@hubermedia.de</webMaster>
  4.     [...]
  5. </channel>
Mail adress of the responsible webmaster for technical questions

Category

  1. <channel>
  2.     [...]
  3.     <category>POI</category>
  4.     [...]
  5. </channel>
See type

Generator

  1. <channel>
  2.     [...]
  3.     <generator>eContent.Maps</generator>
  4.     [...]
  5. </channel>
Name of the generator that generates the feed

Docs

  1. <channel>
  2.     [...]
  3.     <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  4.     [...]
  5. </channel>
Url to further information about the feed

Count

  1. <channel>
  2.     [...]
  3.     <count>1</count>
  4.     [...]
  5. </channel>
Item-count within feed (optional)

Overallcount

  1. <channel>
  2.     [...]
  3.     <overallcount>23758</overallcount>
  4.     [...]
  5. </channel>
Overall-item-count (optional)

2. Default elements


Each object has to be a item element. There can be as many items in the feed as needed.
  1. <rss [...]>
  2.     <channel>
  3.         [...]
  4.         <item>
  5.         [...]
  6.         </item>
  7.         [...]
  8.         <item>
  9.         [...]
  10.         </item>
  11.         [...]
  12.     </channel>
  13. </rss>

title

  1. <item>
  2.     [...]
  3.     <title>Hofkäserei Lang</title>
  4.     [...]
  5. </item>
Title is an obligatory element.
  1. <item>
  2.     [...]
  3.     <link>http://api.esuchwas.de/Details.ashx?Id=qowqOuYK</link>
  4.     [...]
  5. </item>
Hyperlink to detailpage of object.

description

  1. <item>
  2.     [...]
  3.     <description><![CDATA[Dies ist eine <b>Demo</b>-Beschreibung]]></description>
  4.     [...]
  5. </item>
Item-description in HTML. The HTML-text has to be correctly encoded.
Either encode the html entities ("<strong>boldtext</strong>" --> "&lt;strong&gt;boldtext&lt;/strong&gt;")
or use CDATA (<![CDATA[<strong>boldtext</strong>]]>)

shortdescription

  1. <item>
  2.     [...]
  3.     <shortdescription><![CDATA[Dies ist eine kurze <b>Demo</b>-Beschreibung]]></shortdescription>
  4.     [...]
  5. </item>
Item-shortdescription in HTML. The HTML-text has to be correctly encoded.
Either encode the html entities ("<strong>boldtext</strong>" --> "&lt;strong&gt;boldtext&lt;/strong&gt;")
or use CDATA (<![CDATA[<strong>boldtext</strong>]]>)

category

  1. <item>
  2.     [...]
  3.     <category>Direktvermarkter</category>
  4.     <category>Kategorie X</category>
  5.     <category>Kategorie Y</category>
  6.     [...]
  7. </item>
Category-element is obligatory. It has to be a valid category hat is supported by the category-tree of the experience.

  1. <item>
  2.     [...]
  3.      <ec:link rel="default" url="coverimage.jpg" type="image/jpeg">cover image</ec:link>
  4.      <ec:link rel="imagegallery" url="image1.jpg" type="image/jpeg">image 1</ec:link>
  5.      <ec:link rel="imagegallery" url="image2.jpg" type="image/jpeg">image 2</ec:link>
  6.      <ec:link
  7.          rel="imagegallery"
  8.          url="image3.jpg"
  9.          type="image/jpeg"        
  10.          author="email@author.de"
  11.          source="Quelle des Bildes als Text"
  12.          latitude="49.7591181049"
  13.          longitude="12.0774078369141">Bild 3</ec:link> <!-- Link(Bild) mit weiteren Details -->

  15.      <ec:link rel="download" type="application/xml" url="http://link/download_gpx.aspx?id=15">GPX</ec:link>
  16.      <ec:link rel="audio" type="audio/mpeg" url="http://www.seite-mit-audio/audio.mp3" type="autio/mpeg">MP3</ec:link>
  17.      <ec:link rel="print" type="application/pdf" url="http://www.seite-mit-ausdruck.de/print.aspx?id=15">Drucken</ec:link>
  18.     [...]
  19. </item>
You can use as many ec:link elements as you need to.

Obligatory parameters:


Parameter
Type
Description
Sample
rel
String
Defines the type of ec:link. Possible values are:

default (cover picture)
summer (summer image)
winter (winter image)
imagegallery (images)
logo
print (printpage/pdf)                                        
download (e.g. tour-gpx)
video
audio
qrcode
booking
ticket                                                            
socialmedia
rating
externimagegallery
esuchwas
other
rel="default"
url
String
url to file/homepage

String
mime-type of file
type="audio/mpeg"

Optional parameters:

Parameter
Type
Description
Sample
author
String
eMail adress of author
source
String
source
source="eSuchWasV4"
latitude
String
Latitude: WGS84 coordinate
latitude="49.4685"
longitude
String
Longitude: WGS84 coordinate
longitude="12.07740"

geo:lat / geo:long

  1. <item>
  2.     [...]
  3.     <geo:lat>49.7591181049</geo:lat>
  4.     <geo:long>12.0774078369141</geo:long>
  5.     [...]
  6. </item>
Latitude / Longitude are obligatory elements. You can let us geocode the object based on its adress, but please provide this data if you can.

georss:elevation

  1. <item>
  2.     [...]
  3.     <georss:elev>20</georss:elev>
  4.     [...]
  5. </item>
Elevation above sea level in meters.

Source

  1. <item>
  2.     [...]
  3.     <source url="http://www.et4.de/">eTourist V4</source>
  4.     <ec:source_image>http://api.esuchwas.de/logo.png/</ec:source_image>
  5.     <ec:source_id>15</ec:source_id>     [...]
  6. </item>
source > Name and hyperlink of the source of the object.
ec:source_image > Image of the source.
ec:source_id > Unique id of the object.

author

  1. <item>
  2.     [...]
  3.     <author>support@hubermedia.de</author>
  4.     [...]
  5. </item>
The eMail adress of the person who is responsible for this object.

Adress

  1. <item>
  2.     [...]
  3.     <ec:street>Oed 2</ec:street>
  4.     <ec:plz>92665</ec:plz>
  5.     <ec:city>Kirchendemenreuth</ec:city>
  6.     <ec:county>Neustadt an der Waldnaab</ec:county>
  7.     <ec:country>DE</ec:country>
  8.     [...]
  9. </item>
In these fields the complete address of the object is stored.
If no Latitude/Longitude is provided, these data will be used to geocode the object.

ec:area

  1. <item>
  2.     [...]
  3.     <ec:area>Oberbayern</ec:area>
  4.     <ec:area>Gebiet2</ec:area>
  5.     <ec:area>WeiteresGebiet</ec:area>
  6.     [...]
  7. </item>
An unlimited number of tourist areas that apply to the object.

ec:created

  1. <item>
  2.     [...]
  3.     <ec:created>2009-07-20T10:00:00</ec:created>
  4.     [...]
  5. </item>
Creation-date of the object.

ec:changed

  1. <item>
  2.     [...]
  3.     <ec:changed>2011-02-01T16:00:00</ec:changed>
  4.     [...]
  5. </item>
Date of the last change of the object.

ec:keywords

  1. <item>
  2.     [...]
  3.     <ec:keywords>
  4.         <ec:keyword>Test1</ec:keyword>
  5.         <ec:keyword>Test2</ec:keyword>
  6.     </ec:keywords>
  7.     [...]
  8. </item>
Use as many keywords/tags as possible. These are immanent important for searching.

ec:text

  1. <item>
  2.     [...]
  3.     <ec:text>Dies ist die detailierte Beschreibung des Objektes</ec:text>
  4.     <ec:text rel="openings">Die Öffnungszeiten sind von ... bis ...</ec:text>
  5.     <ec:text rel="directions">Anfahrtsbeschreibung: ...</ec:text>
  6.     [...]
  7. </item>
Detailed texts for the object. It's a plain-text field, so no html tags may be used.
The type of the text is defined by the attribute "rel". Possible values:
  1. openings
  2. date
  3. dayoff
  4. directions

ec:shorttext

  1. <item>
  2.     [...]
  3.     <ec:shorttext>Dies ist eine kurze Beschreibung des Objektes</ec:shorttext>
  4.     [...]
  5. </item>
Short text for the object. It's a plain-text field, so no html tags may be used.

ec:highlight

  1. <item>
  2.     [...]
  3.     <ec:highlight>true</ec:highlight>
  4.     [...]
  5. </item>
If the object shall be marked as highlight, its value has to be "true".

ec:tel

  1. <item>
  2.     [...]
  3.     <ec:tel>0815/815</ec:tel>
  4.     [...]
  5. </item>
Phonenumber of the object.

ec:email

  1. <item>
  2.     [...]
  3.     <ec:email>email.des.objektes@provider.xy</ec:email>
  4.     [...]
  5. </item>
Contact-email of the object.

ec:contact_*

  1. <item>
  2.     [...]
  3.     <ec:contact_name>Fam. Huber</ec:contact_name> 
  4.     <ec:contact_street>Oed 2</ec:contact_street> 
  5.     <ec:contact_plz>92665</ec:contact_plz> 
  6.     <ec:contact_city>Kirchendemenreuth</ec:contact_city> 
  7.     <ec:contact_tel>0815/815</ec:contact_tel> 
  8.     <ec:contact_email>email.des.objektes@provider.xy</ec:contact_email> 
  9.     <ec:contact_link>http://www.ansprechpartner-website.de/</ec:contact_link> 
  10.     [...]
  11. </item>
Contact-partner.

ec:author_*

  1. <item>
  2.     [...]
  3.     <ec:autor_name>Stefan Huber</ec:autor_name> 
  4.     <ec:autor_street>Gaberlplatz 5</ec:autor_street> 
  5.     <ec:autor_plz>93462</ec:autor_plz> 
  6.     <ec:autor_city>Lam</ec:autor_city> 
  7.     <ec:autor_tel>0815/815</ec:autor_tel> 
  8.     <ec:autor_email>stefan.huber@hubermedia.de</ec:autor_email> 
  9.     <ec:autor_link>http://www.hubermedia.de/</ec:autor_link>
  10.     [...]
  11. </item>
Author.

ec:organisation_*

  1. <item>
  2.     [...]
  3.     <ec:organisation_name>Chiemgau Tourismus</ec:organisation_name>
  4.     <ec:organisation_link>http://www.chiemgau-tourismus.de/</ec:organisation_link>
  5.     <ec:organisation_image>http://www.chiemgau-tourismus.de/logo.png</ec:organisation_image>
  6.     <ec:organisation_email>info@chiemgau-tourismus.de</ec:organisation_email>
  7.     [...]
  8. </item>
Organisation/Region/Area information.

ec:timeintervalsNew

  1. <item>
  2.     [...]
  3.     <ec:timeIntervalsNew>
  4.         [...]
  5.     </ec:timeIntervalsNew>
  6.     [...]
  7. </item>
Dates/Openinghours.

These TimeIntervals are rules based on daily, weekly, monthly, yearly or single frequencies. The rules can be mixed. Events shall not overlap. DateTimes have to be in IS= 8601 Format: yyyy-MM-DDThh:mm:ss+hh:mm + diff to UTC. StartTime is inclusive, EndTime exclusive. TimeZone has to be IANA Time Zone Database ID and is obligatory (for germany, use Europe/Berlin).

There are different types to transfer the information.

01.09.2015 - 15.09.2015 whole day event
  1. <item>
  2.     [...]
  3.     <ec:timeIntervalsNew>
  4.         <ec:timeInterval start="2015-09-01T00:00:00+02:00" end="2015-09-16T00:00:00+02:00" tz="Europe/Berlin" freq="single" />     </ec:timeIntervalsNew>
  5.     [...]
  6. </item>

01.09.2015 from 8 until 17
  1. <item>
  2.     [...]
  3.     <ec:timeIntervalsNew>
  4.         <ec:timeInterval start="2015-09-01T08:00:00+02:00" end="2015-09-01T17:00:00+02:00" tz="Europe/Berlin" freq="single" />
  5.     </ec:timeIntervalsNew>
  6.     [...]
  7. </item>

01.09.2015 - 05.09.2015: from 08-12 and 13-17
  1. <item>
  2.     [...]
  3.     <ec:timeIntervalsNew>
  4.         <ec:timeInterval start="2015-09-01T08:00:00+02:00" end="2015-09-01T12:00:00+02:00" tz="Europe/Berlin" freq="daily" repeatUntil="2015-09-06T00:00:00+02:00" />
  5.         <ec:timeInterval start="2015-09-01T13:00:00+02:00" end="2015-09-01T17:00:00+02:00" tz="Europe/Berlin" freq="daily" repeatUntil="2015-09-06T00:00:00+02:00" />
  6.     </ec:timeIntervalsNew>
  7.     [...]
  8. </item>

daily from 13 until 17 (opening hours gastro)
  1. <item>
  2.     [...]
  3.     <ec:timeIntervalsNew>
  4.         <ec:daily>
  5.         <ec:timeInterval start="2015-01-01T13:00:00+01:00" end="2015-01-01T17:00:00+01:00" tz="Europe/Berlin" freq="daily" repeatUntil="2020-01-01T00:00:00+01:00" />
  6.     </ec:timeIntervalsNew>
  7.     [...]
  8. </item>

monday - thursday, 8-12 and 13-18 and friday 8-12 (opening hours poi)
  1. <item>
  2.     [...]
  3.     <ec:timeIntervalsNew>
  4.         <ec:timeInterval start="2015-01-01T08:00:00+01:00" end="2015-01-01T12:00:00+01:00" tz="Europe/Berlin" freq="weekly" repeatUntil="2020-01-01T00:00:00+01:00">
  5.             <ec:weekdays>
  6.                 <ec:weekday>1</ec:weekday> <!.. monday -->
  7.                 <ec:weekday>2</ec:weekday> <!.. tuesday -->
  8.                 <ec:weekday>3</ec:weekday> <!.. wednesday -->
  9.                 <ec:weekday>4</ec:weekday> <!.. thursday -->
  10.                 <ec:weekday>5</ec:weekday> <!..f riday -->
  11.             </ec:weekdays>
  12.         </ec:timeInterval>
  13.         <ec:timeInterval start="2015-01-01T13:00:00+01:00" end="2015-01-01T18:00:00+T01:00" tz="Europe/Berlin" freq="weekly" repeatUntil="2020-01-01T00:00:00+01:00">
  14.             <ec:weekdays>
  15.                 <ec:weekday>1</ec:weekday> <!.. monday -->
  16.                 <ec:weekday>2</ec:weekday> <!.. tuesday -->
  17.                 <ec:weekday>3</ec:weekday> <!.. wednesday -->
  18.                 <ec:weekday>4</ec:weekday> <!.. thursday -->
  19.             ;</ec:weekdays>
  20.         ;</ec:timeInterval>     ;</ec:timeIntervalsNew>
  21.     [...]
  22. </item>
All parameters:
  1. <item>
  2.     [...]
  3.     <ec:timeIntervalsNew>
  4.             <ec:timeInterval ...>
  5.                 <!-- Attribute:
  6.                 start="2015-01-01T08:00:00+01:00" - startdate first date, obligatory
  7.                 end="2015-01-01T17:00:00+01:00" - enddate first date, obligatory
  8.                 tz="Europe/Berlin" - timezone, obligatory
  9.                 freq="single" - ruletype, obligaotry (single,daily,weekly,monthly,yearly)
  10.                 
  11.                 repeatUntil="2020-01-01T00:00:00+01:00" - enddate when repeated interval
  12.                 repeatCount="100" - max count repetition, use repeatUntil OR repeatCount, not both at once
  13.                 interval="1" - repetition-interval, default 1
  14.                 dayOrdinal="2" weekday="0" - only with freq=monthly/yearly: every 2. sunday of month
  15.                 dayOfMonth="5" - only with freq=monthly/yearly: every 5. day of month
  16.                 month="5" - only with freq=yearly: which month
  17.                 -->
  18.                 
  19.                 <ec:weekdays> <!-- only with freq=weekly -->
  20.                     <ec:weekday>0</ec:weekday> <!-- 0=sunday - 6=saturday-->
  21.                     ...
  22.                 </ec:weekdays>
  23.                 
  24.             </ec:timeInterval>
  25.             [...]
  26.     </ec:timeIntervalsNew>
  27. </item>

ec:rating

  1. <item>
  2.     [...]
  3.     <ec:rating type="Panorama">75</ec:rating>
  4.     <ec:rating type="Kondition">50</ec:rating>
  5.     <ec:rating type="Fahrtechnik">5</ec:rating>
  6.     [...]
  7. </item>
There can be many different ratings. Value has to be between 0 and 100. Values for attribute "type" can be set free
Samle for start-rating 1-5 into percentage values:
  1. 0 = no star
  2. 20 = 1 star
  3. 40 = 2 stars
  4. 60 = 3 stars
  5. 80 = 4 stars
  6. 100 = 5 stars

ec:season

  1. <item>
  2.     [...]
  3.     <ec:season month="1">qualified</ec:season> <!-- january qualified -->
  4.     <ec:season month="2">dependent</ec:season> <!-- february dependent on weather-->
  5.     [...]
  6. </item>
Primarily used in module tour, but can also be used in all other modules.
Month: 1-12 (1=january)
Value
  1. undefined
  2. unqualified
  3. dependent (on weather)
  4. qualified
Default-value if not set: undefined

3. Specific elements for hotels

DEHOGA

  1. <item>
  2.     [...]
  3.     <ec:class_dehoga>4</ec:class_dehoga>
  4.     [...]
  5. </item>
DEHOGA rating/classification.
Values:
  1. 0: no stars
  2. 1: 1 star
  3. 1.5: 1 star superior
  4. 2: 2 stars
  5. 2.5: 2 stars superior
  6. 3: 3 stars
  7. 3.5: 3 stars superior
  8. 4: 4 stars
  9. 4.5: 4 stars superior
  10. 5: 5 stars
  11. 5.5: 5 stars superior

DTV

  1. <item>
  2.     [...]
  3.     <ec:class_dtv>4</ec:class_dtv>
  4.     [...]
  5. </item>
DTV rating/classification.
Values:
  1. 0: no stars
  2. 1: 1 star
  3. 1.5: 1 star superior
  4. 2: 2 stars
  5. 2.5: 2 stars superior
  6. 3: 3 stars
  7. 3.5: 3 stars superior
  8. 4: 4 stars
  9. 4.5: 4 stars superior
  10. 5: 5 stars
  11. 5.5: 5 stars superior

Affiliate ID

  1. <item>
  2.     [...]
  3.     <ec:affiliate_id></ec:affiliate_id>
  4.     [...]
  5. </item>
Affiliate Id.

Price

  1. <item>
  2.     [...]
  3.     <ec:price>55.5</ec:price>
  4.     [...]
  5. </item>
Min price.

4. Specific elements for gastro

Kitchen

  1. <item>
  2.     [...]
  3.     <ec:kitchen>deutsch</ec:kitchen> 
  4.     <ec:kitchen>asiatisch</ec:kitchen>
  5.     [...]
  6. </item>
Kitchentype of gastro.

5. Specific elements for events

Premium

  1. <item>
  2.     [...]
  3.     <ec:premium>false</ec:premium>
  4.     [...]
  5. </item>
If event shall be marked as premium event, value of this element has to be true.

6. Specific elements for tours

Polygon

  1. <item>
  2.     [...]
  3.     <georss:polygon>49.7591181049 12.0774078369141 49.7591181049 12.0774078369141</georss:polygon>
  4.     [...]
  5. </item>
Polygon of tour. Each latitude/longitude has to be seperated by one blank. If this element is used, tour is a round tour (start = end).
Please use line if it is not a round tour

Difficulty

  1. <item>
  2.     [...]
  3.     <ec:difficulty>3</ec:difficulty>
  4.     [...]
  5. </item>
Diffuculty of tour. Possible values:
  1. 1: very easy
  2. 2: easy
  3. 3: medium
  4. 4: hard
  5. 5: very hard

Length

  1. <item>
  2.     [...]
  3.     <ec:length>2530</ec:length>
  4.     [...]
  5. </item>
Length of tour in meter.

Duration

  1. <item>
  2.     [...]
  3.     <ec:duration>120</ec:duration>
  4.     [...]
  5. </item>
Duration of tour in minutes.

Alt diff

  1. <item>
  2.     [...]
  3.     <ec:alt_diff>100</ec:alt_diff>
  4.     [...]
  5. </item>
Total altitude ascending.

Round tour

  1. <item>
  2.     [...]
  3.     <ec:round_tour>true</ec:round_tour>
  4.     [...]
  5. </item>
Round tour.

Rest stop

  1. <item>
  2.     [...]
  3.     <ec:rest_stop>true</ec:rest_stop>
  4.     [...]
  5. </item>
If there are rest stops on this tour, value has to be true.

Elev min

  1. <item>
  2.     [...]
  3.     <ec:elev_min>420</ec:elev_min>
  4.     [...]
  5. </item>
Minimal elevation above sea level in meters.

Elev max

  1. <item>
  2.     [...]
  3.     <ec:elev_max>53</ec:elev_max>
  4.     [...]
  5. </item>
Maximal elevation above sea level in meters.

Elev image

  1. <item>
  2.     [...]
  3.     <ec:elev_image url="http://link.zum.hoehenprofil/hoehenprofil.aspx?id=5" thumb="http://link.zum.hoehenprofil/hoehenprofil.aspx?id=5">Höhenprofil</ec:elev_image>
  4.     [...]
  5. </item>
Url to elevation image.

7. Specific elements for packages

Price

  1. <item>
  2.     [...]
  3.     <ec:price>55.5</ec:price>
  4.     [...]
  5. </item>
Min price.

8. Internal Elements

GUID

  1. <item>
  2.     [...]
  3.     <guid isPermaLink="false">09CD55BA4483F03DA6C695406F4236F6</guid>
  4.     [...]
  5. </item>
This element will be created automatically and is not needed to be filled.

Local Id

  1. <item>
  2.     [...]
  3.     <ec:local_id>10272</ec:local_id>
  4.     [...]
  5. </item>
Local eT4.META id that will be filled automatically.

Creator

  1. <item>
  2.     [...]
  3.     <ec:creator>eSuchWas Edition Ostbayern</ec:creator>
  4.     [...]
  5. </item>
Creator of thie item/feed. It will be filled automatically. Values that are set in GeoRssFeed will be overwritten with our value defined in the maps-config.

9. complete RSS feed sample

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="eSuchWasV4.xsd" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:georss="http://www.georss.org/georss/11" xmlns:ec="urn:schemas-econtent:rss">
    <channel>
        <title>eContent.Maps(bayern) - POI (Quality: 100%)</title>
        <link>http://maps.hubermedia.de/</link>
        <description>GeoRSS-Feed für eContent.Maps(bayern) POI</description>
        <language>de-DE</language>
        <copyright>hubermedia</copyright>
        <managingEditor>support@hubermedia.de</managingEditor>
        <webMaster>support@hubermedia.de</webMaster>
        <category>POI</category>
        <generator>eContent.Maps</generator>
        <docs>http://blogs.law.harvard.edu/tech/rss</docs>

        <!-- Qualität des Feeds. Falls keine 100%, dann muss der GeoRSS-Feed nochmals abgerufen werden -->
        <quality>100</quality>

        <!-- Anzahl der Elemente im GeoRSS-Feed (optional) -->
        <count>1</count>

        <!-- alle Serverseitig gefundenen Objekte(optional) -->
        <overallcount>23758</overallcount>

        <!-- Zeit in Minuten, bis der Channel(Feed) aktualisiert werden sollte. -->
        <ttl>120</ttl>

        <item>

            <!-- START Interne Felder -->
            <!-- Bei den folgenden Feldern handelt es dich um interne Felder: -->
            <!-- Felder müssen nicht angegeben werden, da sie automatisch gefüllt werden. -->
            <!-- Hier angegebene Werte werden automatisch überschrieben -->

            <!-- GUID
            <guid isPermaLink="false">09CD55BA4483F03DA6C695406F4236F6</guid> -->

            <!-- Lokale eSuchWas ID
            <ec:local_id>10272</ec:local_id> -->

            <!-- Interne eSuchWas Ersteller-Daten
            <ec:creator>eSuchWas Edition Ostbayern</ec:creator> -->

            <!-- ENDE Interne Felder -->


            <!-- TITLE zwingend erforderlich -->
            <title>Hofkäserei Lang</title>

            <!-- LINK zur Detailsseite -->

            <!-- DESCRIPTION Detailierte Beschreibung als HTML -->
            <description><img border='0' src='http://et.cdn.hmgp.de/services2/streaming.ashx/emedia91568t.jpg'/><br/>Kategorie:<br/>Direktvermarkter<br/><br/>Standort:<br/><br/>92665 Kirchendemenreuth<br/>Landkreis Neustadt a.d. Waldnaab <a target="_blank" href="http://www.hubermedia.de/">
            <img border="0" alt="eSuchWas" src="http://api.esuchwas.de/images/logos/eSuchWas.png" style="float: right" />

            </a>
            </description>

            <!-- SHORTDESCRIPTION Kurzbeschreibung(Teaser) als HTML -->
            <shortdescription> in Kirchendemenreuth <a target="_blank" href="http://www.hubermedia.de/">
            <img border="0" alt="eSuchWas" src="http://api.esuchwas.de/images/logos/eSuchWas.png" style="float: right" />
            </a>
            </shortdescription>

            <!-- CATEOGRY Mindestens eine Kategorie des Items notwendig -->
            <category>Direktvermarkter</category>
            <category>Kategorie X</category>
            <category>Kategorie Y</category>

            <!-- ENCLOSURE Logo/Titelbild! -->

            <!-- Weitere Mediendaten -->
            <ec:link rel="imagegallery" url="Bild1.jpg">Bild 1</ec:link>
            <ec:link rel="imagegallery" url="Bild2.jpg">Bild 2</ec:link>
            <ec:link
             rel="imagegallery"
             url="Bild3.jpg"
             author="email@author.de"
             source="Quelle des Bildes als Text"
             latitude="49.7591181049"
             longitude="12.0774078369141">Bild 3</ec:link> <!-- Link(Bild) mit weiteren Details -->

            <ec:link rel="download" url="http://link/download_gpx.aspx?id=15">GPX</ec:link>
            <ec:link rel="audio" url="http://www.seite-mit-audio/audio.mp3" type="autio/mpeg">MP3</ec:link>
            <ec:link rel="print" url="http://www.seite-mit-ausdruck.de/print.aspx?id=15">Drucken</ec:link>

            <!-- GEO:LAT und GEO:LONG Geographische Daten, damit der Punkt auf Karteneinbindungen angezeigt werden kann -->
            <geo:lat>49.7591181049</geo:lat>
            <geo:long>12.0774078369141</geo:long>

            <!-- Höhe über dem Meeresspiegel in Meter -->
            <georss:elev>20</georss:elev>

            <!-- Daten des technischen Dienstleisters -->
            <!-- Quelle des Datensatzes (Technischer Dienstleister) -->
            <source url="http://www.et4.de/">eTourist V4</source>
            <!-- Bild-URL der des technischen Dienstleisters -->
            <ec:source_image>http://www.et4.de/logo.png</ec:source_image>
            <!-- Eindeutige ID des technischen Dienstleisters -->
            <ec:source_id>15</ec:source_id>
            <!-- Optional: Angabe einer URI mit Webservices für genauere Abfragen -->
            <ec:entry_point>http://www.url-zum-soap-webservice.de/Service.asmx</ec:entry_point>

            <!-- Email des Erstellers des Objekts -->
            <author>support@hubermedia.de</author>

            <!-- Adress-Daten -->
            <ec:street>Oed 2</ec:street>
            <ec:plz>92665</ec:plz>
            <ec:city>Kirchendemenreuth</ec:city>
            <ec:county>Neustadt an der Waldnaab</ec:county>
            <ec:country>DE</ec:country>

            <!-- Gebiete (ein oder mehrere touristische Gebiete) -->
            <ec:area>Oberbayern</ec:area>
            <ec:area>Gebiet2</ec:area>
            <ec:area>WeiteresGebiet</ec:area>

            <!-- Erstellungsdatum + Zeit-->
            <ec:created>2009-07-20T10:00:00</ec:created>

            <!-- Änderungsdatum + Zeit -->
            <ec:changed>2011-02-01T16:00:00</ec:changed>

            <!-- KEYWORDS wichtiges Feld für Volltextsuchen -->
            <ec:keywords>
            <ec:keyword>Test1</ec:keyword>
            <ec:keyword>Test2</ec:keyword>
            </ec:keywords>

            <!-- EC:OPTIONS kann beliebig mit XML Daten befüllt werden, die dann z.B. nach der Suche benötigt werden für spezielle Funktionen oder Anzeigen -->
            <!-- Diese Daten stehen dann auch in der eContent.Maps-API als Javascript-Objekt zur Verfügung -->
            <!-- -->
            <ec:options><poi id="10272" /><gebiete>Waldnaab-Tal, Oberpfälzer Wald, Naturpark Nördlicher Oberpfälzer Wald, Neustadt a.d. Waldnaab</gebiete></ec:options>

            <!-- Detailierte Beschreibung (NUR TEXT) -->
            <ec:text>Dies ist die detailierte Beschreibung des Objektes</ec:text>

            <!-- Weitere Beschreibungen (NUR TEXT) -->
            <!-- Diese Beschreibung sind abhängig vom Kontext (rel) -->
            <ec:text rel="openings">Die Öffnungszeiten sind von ... bis ...</ec:text>
            <ec:text rel="directions">Anfahrtsbeschreibung: ...</ec:text>

            <!-- Kurzbeschreibung (NUR TEXT) -->
            <ec:shorttext>Dies ist eine kurze Beschreibung des Objektes</ec:shorttext>

            <!-- Das Objekt ist ein Highlight (Default NEIN) -->
            <ec:highlight>true</ec:highlight>

            <!-- Kontakt: Telefon -->
            <ec:tel>0815/815</ec:tel>

            <!-- Kontakt: E-Mail -->
            <ec:email>email.des.objektes@provider.xy</ec:email>

            <!-- Ansprechpartner -->
            <ec:contact_name>Fam. Huber</ec:contact_name>
            <ec:contact_street>Oed 2</ec:contact_street>
            <ec:contact_plz>92665</ec:contact_plz>
            <ec:contact_city>Kirchendemenreuth</ec:contact_city>
            <ec:contact_tel>0815/815</ec:contact_tel>
            <ec:contact_email>email.des.objektes@provider.xy</ec:contact_email>
            <ec:contact_link>http://www.ansprechpartner-website.de/</ec:contact_link>

            <!-- Autor / Redakteur des Eintrags -->
            <ec:autor_name>Stefan Huber</ec:autor_name>
            <ec:autor_street>Gaberlplatz 5</ec:autor_street>
            <ec:autor_plz>93462</ec:autor_plz>
            <ec:autor_city>Lam</ec:autor_city>
            <ec:autor_tel>0815/815</ec:autor_tel>
            <ec:autor_email>stefan.huber@hubermedia.de</ec:autor_email>
            <ec:autor_link>http://www.hubermedia.de/</ec:autor_link>

            <!-- Organisation / Gebiet / Region -->
            <ec:organisation_name>Chiemgau Tourismus</ec:organisation_name>
            <ec:organisation_link>http://www.chiemgau-tourismus.de/</ec:organisation_link>
            <ec:organisation_image>http://www.chiemgau-tourismus.de/logo.png</ec:organisation_image>
            <ec:organisation_email>info@chiemgau-tourismus.de</ec:organisation_email>

            <!-- Festlegen der Termine/Öffnungszeiten -->
            <!-- Die Anzahl der Intervalle ist unbegrenzt -->
            <ec:timeIntervalsNew>>
                 <ec:timeInterval start="2015-09-01T00:00:00+02:00" end="2015-09-16T00:00:00+02:00" tz="Europe/Berlin" freq="single" />
            </ec:timeIntervalsNew>

            <!-- Weitere Allgemeine Merkmale -->
            <ec:family_friendly>true</ec:family_friendly><!-- Familiengerecht, Kinder -->
            <ec:barrier_free_info>true</ec:barrier_free_info><!-- Information zur Barrierefreiheit vorhanden -->

            <!-- Weitere Bewertungen / Ratings in Prozent! -->
            <!-- Abbildung eines 5 Sterne Systems ohne Zwischenstufen z.B. anhand folgender Werte: 20, 40, 60, 80, 100 -->
            <ec:rating type="Panorama">75</ec:rating> <!-- gute Aussicht (z.B. 4 von 5 Sternen) -->
            <ec:rating type="Kondition">50</ec:rating> <!-- mittel (z.B. 3 von 5 Sternen) -->
            <ec:rating type="Fahrtechnik">5</ec:rating> <!-- sehr leicht (z.B. 1 von 5 Sternen) -->

            <!-- Beste Jahreszeit je Monat -->
            <!-- Mögliche Werte: undefined, unqualified, dependent, qualified -->
            <!-- Alle Monate, die nicht angegeben werden sind automatisch im Zustand undefined (undefiniert) -->
            <ec:season month="1">qualified</ec:season> <!-- Januar geeignet -->
            <ec:season month="2">dependent</ec:season> <!-- Februar witterungsbedingt -->

            <!-- Verknüpfungen zu anderen Items per Guid -->
            <!-- Es sind auch Feed-Übergreifende Verknüpfungen möglich -->
            <ec:relation guid="09CD55BA4483F03DA6C695406F4236F6" category="Poi" type="Entlang der Tour">Parkplatz 1</ec:relation>
            <ec:relation guid="AFCD55BA4483F03DA6C695406F4236C5" category="Hotel">Hotel am Berg</ec:relation>
            <ec:relation guid="B0CD55BA4483F03DA6C695406F423601" category="Hotel" type="Partnerhotel">Hotel vorm Berg</ec:relation>

            <!-- THEMEN-SPEZIFISCHE DATEN -->
            <!-- Die folgenden Elemente können zwar jederzeit mit angegeben werden, machen jedoch nur bei den entsprechenden Themen Sinn -->

            <!-- THEMA: Gastgeber -->
            <ec:class_dehoga>4</ec:class_dehoga> <!-- 4 Sterne bei DEHOGA -->
            <ec:class_dtv>3</ec:class_dtv> <!-- 3 Sterne bei DTV -->
            <ec:affiliate_id></ec:affiliate_id><!-- AffiliateID (optinal, falls vorhanden) -->
            <ec:price>55.5</ec:price><!-- Preis ab 55,50 Euro -->

            <!-- THEMA: Events -->
            <ec:premium>false</ec:premium><!-- Kostenpflichtig ja/nein -->

            <!-- THEMA: Gastro - Mehrfachangabe von Küchenarten -->
            <ec:kitchen>deutsch</ec:kitchen>
            <ec:kitchen>asiatisch</ec:kitchen>

            <!-- THEMA: Touren -->
            <!-- Bei Touren ist die Angabe von GEORSS:POLYGON oder GEORSS:LINE notwendig -->
            <!-- Daten müssen nicht im Gesamt-Feed vorhanden sein. Alternativ erst beim Nachladen einzelner Items verwenden. -->
            <!-- Beim Nachladen muss der Feed-Handler auf den Parameter ?ROUTEID= reagieren, dem dann die ec:local_id übermittelt wird. -->
            <georss:polygon>49.7591181049 12.0774078369141 49.7591181049 12.0774078369141</georss:polygon>
            <!-- oder -->
            <!-- <georss:line>49.7591181049 12.0774078369141 49.7591181049 12.0774078369141</georss:line> -->

            <ec:difficulty>3</ec:difficulty><!-- Schwierigkeit 1-5 (sehr leicht, leicht, medium, schwer, sehr schwer) -->
            <ec:length>2530</ec:length><!-- Länge in m -->
            <ec:duration>120</ec:duration><!-- Dauer in Minuten -->
            <ec:alt_diff>100</ec:alt_diff><!-- Höhenmeter auf und abstieg -->
            <ec:round_tour>true</ec:round_tour><!-- Roundtour ja/nein, notwendig, da u.U. erst die Unterscheidung zwischen Polygon und Line erst beim Nachladen getroffen wird-->
            <ec:rest_stop>true</ec:rest_stop><!-- Einkehrmöglichkeit ja/nein -->
            <ec:elev_min>420</ec:elev_min><!-- Minimale Höhe über dem Meeresspiegel in Meter -->
            <ec:elev_max>530</ec:elev_max><!-- Maximale Höhe über dem Meeresspiegel in Meter -->
            <ec:elev_image thumb="http://link.zum.hoehenprofil/hoehenprofil.aspx?id=5" url="http://link.zum.hoehenprofil/hoehenprofil.aspx?id=5">Höhenprofil</ec:elev_image>

            <!-- THEMA: Globale Pauschalen -->
            <ec:price>55.5</ec:price><!-- Preis ab 55,50 Euro -->

        </item>

    </channel>
</rss>

Feed-Checker

You can test your generated feed with our FeedChecker.
Therefore you need your experience-name, because every experience can have their very own categories an requirements for data quality.

Parameter-Description

Content partners have to support at least these parameters. There has to be a standalone feed for every type (Hotel, Event, Gastro, Tour, POI, City, Area, Package, Article)

Parameter
Type
Description
Sample
startdate
Date
Startdate
&startdate=01.10.2015
enddate
Date
Enddate
&enddate=31.10.2015
starttime
Time
Starttime
&starttime=08:00:00
endtime
Time
Endtime
&endtime=18:00:00
mkt
String
This parameter determines the language in which the content is to be returned.
&mkt=de-DE
bookable
Boolean
Only return items that are online bookable
&bookable=true
people
Integer
Search for bookable items for that many people (only represents adult-count without children information)
&people=2
childages
List of Integer
Search for bookable items for these children ages (childages only represents the childages without people)
&childages=3,5,12
template
String
It is possible for one feed to be integrated in different projects with some changes within the feed itself. Possible values: iphone, esuchwas, empty (Default: empty)
&template=iphone


Samples:
  1. Get all data for default (german) language:
    http://url_partnerfeed/FEED.ashx
  2. Get all data for english language:
    http://url_partnerfeed/FEED.ashx?mkt=en 

Automatical Georeference

If you can not provide latitude/longitude values for your objects, it is possible to use a geocoder to get these data based on the adress. To use this feature, you have to fill the item elements ec:street, ec:plz, ec:city and ec:country

  1. <ec:street>Metzengasse 2</ec:street>
  2. <ec:plz>82405</ec:plz>
  3. <ec:city>Wessobrunn</ec:city>
  4. <ec:country>DE</ec:country>




    • Related Articles

    • meta-service: feedchecker

      Entry Point http://meta.et4.de/feedcheck.aspx Responsetype HTML-Page Description Analyzes a GeoRssFeed and shows the contained errors and warnings. Parameters Parameter Type Description e String The experience specifies the name of the project data ...

    • meta-service: hypersearch

      Entry Point http://meta.et4.de/rest.ashx/hypersearch/ Responsetype TemplateBased-XML-Response TemplateBased-JSON-Response TemplateBased-Protobuff-Response Description The meta.destination.one hyper search is a meta-search based on meta-data. The ...

    • meta-service: routing

      Entry Point http://meta.et4.de/rest.ashx/routing Responsetype TemplateBased-XML-Response TemplateBased-JSON-Response TemplateBased-Protobuff-Response Description Calculates a route based on start and end latitude/longitude with turn-by-turn ...

    • GeoRssFeed Schema

      Schema http://developer.et4.de/reference/current/schemas/GeoRssFeedV4.xsd Html-Help http://developer.et4.de/reference/current/GeoRssFeed_V4_xsd.html Inline-XSD <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" ...

    • meta-Service: types

      Entry Point http://meta.et4.de/rest.ashx/types/ Responsetype JSON-Response Description The types service returns a list of available topics. Parameters none Samples Sample 1: http://meta.et4.de/rest.ashx/types/