text:
<?xml version="1.0" encoding="ISO-8859-1"?>
<geo:GeodesyML xsi:schemaLocation="urn:xml-gov-au:icsm:egeodesy:0.3" xmlns:geo="urn:xml-gov-au:icsm:egeodesy:0.3" xmlns:gml="http://www.opengis.net/gml/3.2" xmlns:ns9="http://www.w3.org/1999/xlink" xmlns:gmd="http://www.isotc211.org/2005/gmd" xmlns:gmx="http://www.isotc211.org/2005/gmx" xmlns:om="http://www.opengis.net/om/2.0" xmlns:gco="http://www.isotc211.org/2005/gco" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" gml:id="GeodesyMLType_24">
   <geo:siteLog gml:id="SiteLogType_24">
      <geo:formInformation>
         <geo:preparedBy>Rudi Stoeger</geo:preparedBy>
         <geo:datePrepared>2010-02-14T13:00:00Z</geo:datePrepared>
         <geo:reportType>UPDATE</geo:reportType>
      </geo:formInformation>
      <geo:siteIdentification>
         <geo:siteName>Ankara / Turkey</geo:siteName>
         <geo:fourCharacterID>ANKR</geo:fourCharacterID>
         <geo:monumentInscription>Pillar</geo:monumentInscription>
         <geo:iersDOMESNumber>20805M002</geo:iersDOMESNumber>
         <geo:cdpNumber></geo:cdpNumber>
         <geo:monumentDescription>PILLAR</geo:monumentDescription>
         <geo:heightOfTheMonument>1.1</geo:heightOfTheMonument>
         <geo:monumentFoundation>CONCRETE BLOCK</geo:monumentFoundation>
         <geo:foundationDepth>1.0</geo:foundationDepth>
         <geo:markerDescription>STEEL REFERENCE POINT</geo:markerDescription>
         <geo:dateInstalled>1995-06-20T14:00:00Z</geo:dateInstalled>
         <geo:geologicCharacteristic>Upper layer = Alluvial</geo:geologicCharacteristic>
         <geo:bedrockCondition>WEATHERED</geo:bedrockCondition>
         <geo:notes>From 1995-06-21 until 2008-05-06 ROGUE SNR-8000 or AOA SNR-8000 ACT GPS receivers operated in the Ankara GPS Permanent Tracking Station. Previously, this site was occupied by a Minimac 2816AT between 1991-10-11 and 1994-12-16 and subsequently occupied by a TRIMBLE 4000 SSE between dates 1995-02-08 and 1995-06-21. Detailed info and historical data is available at the on-site contact point. Since 2008-05-06 a TPS E_GGD GPS+GLO receiver is operating.</geo:notes>
      </geo:siteIdentification>
      <geo:siteLocation>
         <geo:city>Ankara</geo:city>
         <geo:state></geo:state>
         <geo:countryCodeISO>TUR</geo:countryCodeISO>
         <geo:tectonicPlate codeSpace="">EURASIAN</geo:tectonicPlate>
         <geo:approximatePositionITRF>
            <geo:xCoordinateInMeters>4121934.26</geo:xCoordinateInMeters>
            <geo:yCoordinateInMeters>2652189.812</geo:yCoordinateInMeters>
            <geo:zCoordinateInMeters>4069034.911</geo:zCoordinateInMeters>
            <geo:latitude-North>39.88751111111110247975375386886298656463623046875</geo:latitude-North>
            <geo:longitude-East>32.75857777777778068184488802216947078704833984375</geo:longitude-East>
            <geo:elevation-m_ellips.>974.8</geo:elevation-m_ellips.>
         </geo:approximatePositionITRF>
      </geo:siteLocation>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_108">
            <geo:manufacturerSerialNumber>T344</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">ROGUE SNR-8000</geo:receiverType>
            <geo:satelliteSystem>GPS</geo:satelliteSystem>
            <geo:serialNumber>T344</geo:serialNumber>
            <geo:firmwareVersion>3.0</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>1995-06-21T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>1996-02-07T00:00:00Z</geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>1995-06-21T00:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_109">
            <geo:manufacturerSerialNumber>AFUY1RUPO1S</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">TPS E_GGD</geo:receiverType>
            <geo:satelliteSystem>GPS+GLO</geo:satelliteSystem>
            <geo:serialNumber>AFUY1RUPO1S</geo:serialNumber>
            <geo:firmwareVersion>2.6.1 Jan,10,2008</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>2008-05-06T11:00:00Z</geo:dateInstalled>
            <geo:dateRemoved></geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>2008-05-06T11:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_110">
            <geo:manufacturerSerialNumber>T-313U</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">AOA SNR-8000 ACT</geo:receiverType>
            <geo:satelliteSystem>GPS</geo:satelliteSystem>
            <geo:serialNumber>T-313U</geo:serialNumber>
            <geo:firmwareVersion>3.3.32.4</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>2000-11-24T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>2008-05-06T10:00:00Z</geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>2000-11-24T00:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_111">
            <geo:manufacturerSerialNumber>T344</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">ROGUE SNR-8000</geo:receiverType>
            <geo:satelliteSystem>GPS</geo:satelliteSystem>
            <geo:serialNumber>T344</geo:serialNumber>
            <geo:firmwareVersion>3.2</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>1996-02-07T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>1996-07-23T00:00:00Z</geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>1996-02-07T00:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_112">
            <geo:manufacturerSerialNumber>T-398U</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">AOA SNR-8000 ACT</geo:receiverType>
            <geo:satelliteSystem>GPS</geo:satelliteSystem>
            <geo:serialNumber>T-398U</geo:serialNumber>
            <geo:firmwareVersion>3.3.32.3</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>2000-07-04T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>2000-11-24T00:00:00Z</geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>2000-07-04T00:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_113">
            <geo:manufacturerSerialNumber>T318</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">ROGUE SNR-8000</geo:receiverType>
            <geo:satelliteSystem>GPS</geo:satelliteSystem>
            <geo:serialNumber>T318</geo:serialNumber>
            <geo:firmwareVersion>3.2</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>1996-07-23T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>1997-07-24T00:00:00Z</geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>1996-07-23T00:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_114">
            <geo:manufacturerSerialNumber>T319</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">ROGUE SNR-8000</geo:receiverType>
            <geo:satelliteSystem>GPS</geo:satelliteSystem>
            <geo:serialNumber>T319</geo:serialNumber>
            <geo:firmwareVersion>3.2.32.4</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>1997-07-24T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>1999-07-09T00:00:00Z</geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>1997-07-24T00:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssReceivers>
         <geo:gnssReceiver gml:id="GnssReceiverType_115">
            <geo:manufacturerSerialNumber>T394</geo:manufacturerSerialNumber>
            <geo:receiverType codeList="codelist" codeListValue="codeListValue" codeSpace="DummyCodeSpace">ROGUE SNR-8000</geo:receiverType>
            <geo:satelliteSystem>GPS</geo:satelliteSystem>
            <geo:serialNumber>T394</geo:serialNumber>
            <geo:firmwareVersion>3.2.32.9</geo:firmwareVersion>
            <geo:elevationCutoffSetting>0.0</geo:elevationCutoffSetting>
            <geo:dateInstalled>1999-07-09T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>2000-07-04T00:00:00Z</geo:dateRemoved>
         </geo:gnssReceiver>
         <geo:dateInserted>1999-07-09T00:00:00Z</geo:dateInserted>
      </geo:gnssReceivers>
      <geo:gnssAntennas>
         <geo:gnssAntenna gml:id="GnssAntennaType_43">
            <geo:manufacturerSerialNumber>391-U</geo:manufacturerSerialNumber>
            <geo:antennaType codeList="codelist" codeListValue="codeListValue" codeSpace="codespace">AOAD/M_T        NONE</geo:antennaType>
            <geo:serialNumber>391-U</geo:serialNumber>
            <geo:antennaReferencePoint codeSpace="">BPA</geo:antennaReferencePoint>
            <geo:marker-arpUpEcc.>0.06</geo:marker-arpUpEcc.>
            <geo:marker-arpNorthEcc.>0.0</geo:marker-arpNorthEcc.>
            <geo:marker-arpEastEcc.>0.0</geo:marker-arpEastEcc.>
            <geo:alignmentFromTrueNorth>0.0</geo:alignmentFromTrueNorth>
            <geo:antennaRadomeType codeSpace="CodeSpaceAttr">NONE</geo:antennaRadomeType>
            <geo:radomeSerialNumber></geo:radomeSerialNumber>
            <geo:antennaCableType>RG 214</geo:antennaCableType>
            <geo:antennaCableLength>30.0</geo:antennaCableLength>
            <geo:dateInstalled>2000-11-24T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>2008-05-06T10:00:00Z</geo:dateRemoved>
         </geo:gnssAntenna>
         <geo:dateInserted>2000-11-24T00:00:00Z</geo:dateInserted>
      </geo:gnssAntennas>
      <geo:gnssAntennas>
         <geo:gnssAntenna gml:id="GnssAntennaType_44">
            <geo:manufacturerSerialNumber>393</geo:manufacturerSerialNumber>
            <geo:antennaType codeList="codelist" codeListValue="codeListValue" codeSpace="codespace">AOAD/M_T        NONE</geo:antennaType>
            <geo:serialNumber>393</geo:serialNumber>
            <geo:antennaReferencePoint codeSpace="">BPA</geo:antennaReferencePoint>
            <geo:marker-arpUpEcc.>0.06</geo:marker-arpUpEcc.>
            <geo:marker-arpNorthEcc.>0.0</geo:marker-arpNorthEcc.>
            <geo:marker-arpEastEcc.>0.0</geo:marker-arpEastEcc.>
            <geo:alignmentFromTrueNorth>0.0</geo:alignmentFromTrueNorth>
            <geo:antennaRadomeType codeSpace="CodeSpaceAttr">NONE</geo:antennaRadomeType>
            <geo:radomeSerialNumber></geo:radomeSerialNumber>
            <geo:antennaCableType>RG 214</geo:antennaCableType>
            <geo:antennaCableLength>30.0</geo:antennaCableLength>
            <geo:dateInstalled>1995-06-21T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>1996-07-23T00:00:00Z</geo:dateRemoved>
         </geo:gnssAntenna>
         <geo:dateInserted>1995-06-21T00:00:00Z</geo:dateInserted>
      </geo:gnssAntennas>
      <geo:gnssAntennas>
         <geo:gnssAntenna gml:id="GnssAntennaType_45">
            <geo:manufacturerSerialNumber>391</geo:manufacturerSerialNumber>
            <geo:antennaType codeList="codelist" codeListValue="codeListValue" codeSpace="codespace">AOAD/M_T        NONE</geo:antennaType>
            <geo:serialNumber>391</geo:serialNumber>
            <geo:antennaReferencePoint codeSpace="">BPA</geo:antennaReferencePoint>
            <geo:marker-arpUpEcc.>0.06</geo:marker-arpUpEcc.>
            <geo:marker-arpNorthEcc.>0.0</geo:marker-arpNorthEcc.>
            <geo:marker-arpEastEcc.>0.0</geo:marker-arpEastEcc.>
            <geo:alignmentFromTrueNorth>0.0</geo:alignmentFromTrueNorth>
            <geo:antennaRadomeType codeSpace="CodeSpaceAttr">NONE</geo:antennaRadomeType>
            <geo:radomeSerialNumber></geo:radomeSerialNumber>
            <geo:antennaCableType>RG 214</geo:antennaCableType>
            <geo:antennaCableLength>30.0</geo:antennaCableLength>
            <geo:dateInstalled>1997-07-24T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>1998-09-16T00:00:00Z</geo:dateRemoved>
         </geo:gnssAntenna>
         <geo:dateInserted>1997-07-24T00:00:00Z</geo:dateInserted>
      </geo:gnssAntennas>
      <geo:gnssAntennas>
         <geo:gnssAntenna gml:id="GnssAntennaType_46">
            <geo:manufacturerSerialNumber>404</geo:manufacturerSerialNumber>
            <geo:antennaType codeList="codelist" codeListValue="codeListValue" codeSpace="codespace">AOAD/M_T        NONE</geo:antennaType>
            <geo:serialNumber>404</geo:serialNumber>
            <geo:antennaReferencePoint codeSpace="">BPA</geo:antennaReferencePoint>
            <geo:marker-arpUpEcc.>0.06</geo:marker-arpUpEcc.>
            <geo:marker-arpNorthEcc.>0.0</geo:marker-arpNorthEcc.>
            <geo:marker-arpEastEcc.>0.0</geo:marker-arpEastEcc.>
            <geo:alignmentFromTrueNorth>0.0</geo:alignmentFromTrueNorth>
            <geo:antennaRadomeType codeSpace="CodeSpaceAttr">NONE</geo:antennaRadomeType>
            <geo:radomeSerialNumber></geo:radomeSerialNumber>
            <geo:antennaCableType>RG 214</geo:antennaCableType>
            <geo:antennaCableLength>30.0</geo:antennaCableLength>
            <geo:dateInstalled>1996-07-23T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>1997-07-24T00:00:00Z</geo:dateRemoved>
         </geo:gnssAntenna>
         <geo:dateInserted>1996-07-23T00:00:00Z</geo:dateInserted>
      </geo:gnssAntennas>
      <geo:gnssAntennas>
         <geo:gnssAntenna gml:id="GnssAntennaType_47">
            <geo:manufacturerSerialNumber>290</geo:manufacturerSerialNumber>
            <geo:antennaType codeList="codelist" codeListValue="codeListValue" codeSpace="codespace">AOAD/M_T        NONE</geo:antennaType>
            <geo:serialNumber>290</geo:serialNumber>
            <geo:antennaReferencePoint codeSpace="">BPA</geo:antennaReferencePoint>
            <geo:marker-arpUpEcc.>0.06</geo:marker-arpUpEcc.>
            <geo:marker-arpNorthEcc.>0.0</geo:marker-arpNorthEcc.>
            <geo:marker-arpEastEcc.>0.0</geo:marker-arpEastEcc.>
            <geo:alignmentFromTrueNorth>0.0</geo:alignmentFromTrueNorth>
            <geo:antennaRadomeType codeSpace="CodeSpaceAttr">NONE</geo:antennaRadomeType>
            <geo:radomeSerialNumber></geo:radomeSerialNumber>
            <geo:antennaCableType>RG 214</geo:antennaCableType>
            <geo:antennaCableLength>30.0</geo:antennaCableLength>
            <geo:dateInstalled>1998-09-16T00:00:00Z</geo:dateInstalled>
            <geo:dateRemoved>2000-11-24T00:00:00Z</geo:dateRemoved>
         </geo:gnssAntenna>
         <geo:dateInserted>1998-09-16T00:00:00Z</geo:dateInserted>
      </geo:gnssAntennas>
      <geo:gnssAntennas>
         <geo:gnssAntenna gml:id="GnssAntennaType_48">
            <geo:manufacturerSerialNumber>217 0243</geo:manufacturerSerialNumber>
            <geo:antennaType codeList="codelist" codeListValue="codeListValue" codeSpace="codespace">TPSCR3_GGD      CONE</geo:antennaType>
            <geo:serialNumber>217 0243</geo:serialNumber>
            <geo:antennaReferencePoint codeSpace="">BPA</geo:antennaReferencePoint>
            <geo:marker-arpUpEcc.>0.07</geo:marker-arpUpEcc.>
            <geo:marker-arpNorthEcc.>0.0</geo:marker-arpNorthEcc.>
            <geo:marker-arpEastEcc.>0.0</geo:marker-arpEastEcc.>
            <geo:alignmentFromTrueNorth>0.0</geo:alignmentFromTrueNorth>
            <geo:antennaRadomeType codeSpace="CodeSpaceAttr">CONE</geo:antennaRadomeType>
            <geo:radomeSerialNumber></geo:radomeSerialNumber>
            <geo:antennaCableType>ECOFLEX 10</geo:antennaCableType>
            <geo:antennaCableLength>30.0</geo:antennaCableLength>
            <geo:dateInstalled>2008-05-06T11:00:00Z</geo:dateInstalled>
            <geo:dateRemoved></geo:dateRemoved>
            <geo:notes>Antenna / radome pair individual calibrated absolute at Geo++</geo:notes>
         </geo:gnssAntenna>
         <geo:dateInserted>2008-05-06T11:00:00Z</geo:dateInserted>
      </geo:gnssAntennas>
      <geo:surveyedLocalTies>
         <geo:surveyedLocalTies gml:id="SurveyedLocalTiesType_8">
            <geo:tiedMarkerName>SLR Ankara</geo:tiedMarkerName>
            <geo:tiedMarkerUsage>SLR</geo:tiedMarkerUsage>
            <geo:tiedMarkerCDPNumber>7589</geo:tiedMarkerCDPNumber>
            <geo:tiedMarkerDOMESNumber>20805M001</geo:tiedMarkerDOMESNumber>
            <geo:differentialComponentsGNSSMarkerToTiedMonumentITRS>
               <geo:dx>-14.2608</geo:dx>
               <geo:dy>2.0499</geo:dy>
               <geo:dz>11.4556</geo:dz>
            </geo:differentialComponentsGNSSMarkerToTiedMonumentITRS>
            <geo:localSiteTiesAccuracy>0.0075</geo:localSiteTiesAccuracy>
            <geo:surveyMethod>TRIANGULATION</geo:surveyMethod>
            <geo:dateMeasured>1992-08-26T14:00:00Z</geo:dateMeasured>
            <geo:notes>Other given values 0.0079, 0.0048</geo:notes>
         </geo:surveyedLocalTies>
         <geo:dateInserted>2016-04-14T00:03:06Z</geo:dateInserted>
      </geo:surveyedLocalTies>
      <geo:frequencyStandards>
         <geo:frequencyStandard gml:id="FrequencyStandardType_62">
            <geo:standardType codeSpace="">INTERNAL</geo:standardType>
            <geo:inputFrequency>0.0</geo:inputFrequency>
            <gml:validTime nilReason="">
               <gml:TimePeriod gml:id="TimePeriodType_87">
                  <gml:beginPosition>1995-06-21T00:00:00Z</gml:beginPosition>
                  <gml:endPosition></gml:endPosition>
               </gml:TimePeriod>
            </gml:validTime>
         </geo:frequencyStandard>
         <geo:dateInserted>2016-04-14T00:03:06Z</geo:dateInserted>
      </geo:frequencyStandards>
      <geo:collocationInformations>
         <geo:collocationInformation gml:id="CollocationInformationType_6">
            <geo:instrumentationType codeSpace=""></geo:instrumentationType>
            <geo:status codeSpace="">MOBILE</geo:status>
            <gml:validTime>
               <gml:TimeInstant gml:id="TimeInstantType_55">
                  <gml:timePosition>1970-01-22T13:00:00Z</gml:timePosition>
               </gml:TimeInstant>
            </gml:validTime>
            <geo:notes>SLR-site 7589</geo:notes>
         </geo:collocationInformation>
         <geo:dateInserted>2016-04-14T00:03:06Z</geo:dateInserted>
      </geo:collocationInformations>
      <geo:humiditySensors>
         <geo:humiditySensor gml:id="HumiditySensorType_10">
            <geo:type codeSpace="">MP408A-T4-W4W</geo:type>
            <geo:manufacturer>ROTRONIC</geo:manufacturer>
            <geo:serialNumber>21206 009</geo:serialNumber>
            <geo:heightDiffToAntenna>-4.5</geo:heightDiffToAntenna>
            <geo:calibrationDate></geo:calibrationDate>
            <gml:validTime nilReason="">
               <gml:TimePeriod gml:id="TimePeriodType_88">
                  <gml:beginPosition>2002-06-07T00:00:00Z</gml:beginPosition>
                  <gml:endPosition></gml:endPosition>
               </gml:TimePeriod>
            </gml:validTime>
            <geo:dataSamplingInterval>900.0</geo:dataSamplingInterval>
            <geo:accuracy-percentRelativeHumidity>1.5</geo:accuracy-percentRelativeHumidity>
            <geo:aspiration>CAPACITANCE PROBE</geo:aspiration>
            <geo:notes>Humidity Sensor is above the antenna</geo:notes>
         </geo:humiditySensor>
         <geo:dateInserted>2016-04-14T00:03:06Z</geo:dateInserted>
      </geo:humiditySensors>
      <geo:pressureSensors>
         <geo:pressureSensor gml:id="PressureSensorType_10">
            <geo:type codeSpace="">APS 9215</geo:type>
            <geo:manufacturer>L-TECH LEIBENGUTH</geo:manufacturer>
            <geo:serialNumber>0500 5099A</geo:serialNumber>
            <geo:heightDiffToAntenna>0.56</geo:heightDiffToAntenna>
            <geo:calibrationDate></geo:calibrationDate>
            <gml:validTime nilReason="">
               <gml:TimePeriod gml:id="TimePeriodType_89">
                  <gml:beginPosition>2002-06-07T00:00:00Z</gml:beginPosition>
                  <gml:endPosition></gml:endPosition>
               </gml:TimePeriod>
            </gml:validTime>
            <geo:dataSamplingInterval>900.0</geo:dataSamplingInterval>
            <geo:accuracy-hPa>0.1</geo:accuracy-hPa>
            <geo:notes>Pressure sensor is below the antenna</geo:notes>
         </geo:pressureSensor>
         <geo:dateInserted>2016-04-14T00:03:06Z</geo:dateInserted>
      </geo:pressureSensors>
      <geo:temperatureSensors>
         <geo:temperatureSensor gml:id="TemperatureSensorType_10">
            <geo:type codeSpace="">MP408A-T4-W4W</geo:type>
            <geo:manufacturer>ROTRONIC</geo:manufacturer>
            <geo:serialNumber>21206 009</geo:serialNumber>
            <geo:heightDiffToAntenna>-4.5</geo:heightDiffToAntenna>
            <geo:calibrationDate></geo:calibrationDate>
            <gml:validTime nilReason="">
               <gml:TimePeriod gml:id="TimePeriodType_90">
                  <gml:beginPosition>2002-06-07T00:00:00Z</gml:beginPosition>
                  <gml:endPosition></gml:endPosition>
               </gml:TimePeriod>
            </gml:validTime>
            <geo:dataSamplingInterval>900.0</geo:dataSamplingInterval>
            <geo:accuracy-degreesCelcius>0.3</geo:accuracy-degreesCelcius>
            <geo:aspiration>PLATINUM PROBE</geo:aspiration>
            <geo:notes>Temperatur sensor is above antenna</geo:notes>
         </geo:temperatureSensor>
         <geo:dateInserted>2016-04-14T00:03:06Z</geo:dateInserted>
      </geo:temperatureSensors>
      <geo:otherInstrumentations>
         <geo:otherInstrumentation gml:id="OtherInstrumentationType_6">
            <geo:instrumentation></geo:instrumentation>
            <gml:validTime>
               <gml:TimeInstant gml:id="TimeInstantType_56">
                  <gml:timePosition>1970-01-22T13:00:00Z</gml:timePosition>
               </gml:TimeInstant>
            </gml:validTime>
         </geo:otherInstrumentation>
         <geo:dateInserted>2016-04-14T00:03:06Z</geo:dateInserted>
      </geo:otherInstrumentations>
      <geo:siteContact gml:id="AgencyPropertyType_48">
         <gmd:MD_SecurityConstraints id="MDSecurityConstraintsType_48">
            <gmd:classification>
               <gmd:MD_ClassificationCode codeList="codelist" codeListValue="codeListValue"/>
            </gmd:classification>
         </gmd:MD_SecurityConstraints>
         <gmd:CI_ResponsibleParty id="CIResponsiblePartyType_48">
            <gmd:individualName>
               <gco:CharacterString>Ayhan Cingoz</gco:CharacterString>
            </gmd:individualName>
            <gmd:organisationName>
               <gco:CharacterString>Harita Genel Komutanligi</gco:CharacterString>
            </gmd:organisationName>
            <gmd:contactInfo>
               <gmd:CI_Contact id="CIContactType_48">
                  <gmd:phone>
                     <gmd:CI_Telephone id="CITelephoneType_16">
                        <gmd:voice>
                           <gco:CharacterString>++90-312-5952256</gco:CharacterString>
                        </gmd:voice>
                        <gmd:facsimile>
                           <gco:CharacterString>++90-312-3201495</gco:CharacterString>
                        </gmd:facsimile>
                     </gmd:CI_Telephone>
                  </gmd:phone>
                  <gmd:address>
                     <gmd:CI_Address id="CIAddressType_48">
                        <gmd:deliveryPoint>
                           <gco:CharacterString>Harita Genel Komutanligi</gco:CharacterString>
                        </gmd:deliveryPoint>
                        <gmd:electronicMailAddress>
                           <gco:CharacterString>ayhan.cingoz@hgk.mil.tr</gco:CharacterString>
                        </gmd:electronicMailAddress>
                     </gmd:CI_Address>
                  </gmd:address>
               </gmd:CI_Contact>
            </gmd:contactInfo>
            <gmd:role>
               <gmd:CI_RoleCode codeList="codelist" codeListValue="codeListValue"/>
            </gmd:role>
         </gmd:CI_ResponsibleParty>
      </geo:siteContact>
      <geo:siteMetadataCustodian gml:id="AgencyPropertyType_49">
         <gmd:MD_SecurityConstraints id="MDSecurityConstraintsType_49">
            <gmd:classification>
               <gmd:MD_ClassificationCode codeList="codelist" codeListValue="codeListValue"/>
            </gmd:classification>
         </gmd:MD_SecurityConstraints>
         <gmd:CI_ResponsibleParty id="CIResponsiblePartyType_49">
            <gmd:organisationName>
               <gco:CharacterString>Bundesamt fuer Kartographie</gco:CharacterString>
            </gmd:organisationName>
            <gmd:contactInfo>
               <gmd:CI_Contact id="CIContactType_49">
                  <gmd:address>
                     <gmd:CI_Address id="CIAddressType_49">
                        <gmd:deliveryPoint>
                           <gco:CharacterString>Bundesamt fuer Kartographie</gco:CharacterString>
                        </gmd:deliveryPoint>
                     </gmd:CI_Address>
                  </gmd:address>
               </gmd:CI_Contact>
            </gmd:contactInfo>
            <gmd:role>
               <gmd:CI_RoleCode codeList="codelist" codeListValue="codeListValue"/>
            </gmd:role>
         </gmd:CI_ResponsibleParty>
      </geo:siteMetadataCustodian>
      <geo:moreInformation>
         <geo:dataCenter>www.bkg.bund.de www.fs.wettzell.de</geo:dataCenter>
         <geo:dataCenter>www.bkg.bund.de www.fs.wettzell.de</geo:dataCenter>
         <geo:urlForMoreInformation>www.bkg.bund.de www.fs.wettzell.de</geo:urlForMoreInformation>
         <geo:siteMap></geo:siteMap>
         <geo:siteDiagram></geo:siteDiagram>
         <geo:horizonMask></geo:horizonMask>
         <geo:monumentDescription></geo:monumentDescription>
         <geo:sitePictures>Y</geo:sitePictures>
         <geo:antennaGraphicsWithDimensions></geo:antennaGraphicsWithDimensions>
         <geo:insertTextGraphicFromAntenna></geo:insertTextGraphicFromAntenna>
         <geo:DOI codeSpace="CodeSpaceTODO">CodeTypeTODO</geo:DOI>
      </geo:moreInformation>
   </geo:siteLog>
</geo:GeodesyML>

redpajama_set_name: RedPajamaGithub


text:
Sabres fall to Islanders 3-2 in OT
Eichel scoring streak reaches 16 games
WBEN Newsroom
USA Today Sports Images
(WGR550-Kyle Powell) - A hard-fought game didn't go the Buffalo Sabres' way, but they were able to salvage a point in a 3-2 overtime loss to the New York Islanders inside the Nassau Veterans Memorial Coliseum.
In defeat, Jack Eichel's point streak reached 16 games long, and his late, third-period heroics helped force the extra frame in hostile territory.
With 5:11 gone in the first period, the Islanders got on the scoreboard first. New York put together an extended offensive zone possession, and made the most of the opportunity.
A loose puck was corralled by Linus Ullmark, but the netminder tried to play the puck to a defenseman in hopes of escaping the attack. Instead, the puck was turned over to Islanders forward Anthony Beauvillier, who then fed teammate Michael Dal Colle for a one-time shot that beat Ullmark. The goal was Dal Colle's second of the season.
Then with about 90 seconds left in the opening frame, Marco Scandella delivered a clean hit on Islanders' forward Ross Johnston, who was felled after the collision. Teammate Josh Bailey came to Johnston's defense; receiving a double-minor penalty for roughing in the process.
That would essentially conclude matters in the first, with the scoring reading 1-0 New York. Another shutout period for Islanders goaltending against the Sabres meant the team's current shutout streak against Buffalo reached 86:32. The last Sabres goal against the Islanders was still back on March 30, 2019 - a third period, Victor Olofsson powerplay goal in a 5-1 loss on the road.
Fittingly it was Olofsson who finally got Buffalo on the board in the second period, ending the team's scoreless streak against New York at 92:43.
With Brock Nelson of the Islanders in the penalty box for a holding the stick minor, Olofsson wired a one-timer past goalie Semyon Varlamov to even the score at 1-1. It was Victor's 14th goal of the season, eighth on the man advantage, and also helped Jack Eichel extend his NHL-best active point streak to 16 games. The captain received a secondary assist on the tying tally.
In successfully registering a point in 16-straight games, Eichel now owns the longest streak of consecutive games with a point in the NHL this season. His assist helped him pass Buffalo, New York's own Patrick Kane of the Chicago Blackhawks, who put together a 15-game streak earlier this fall.
The captain also moved himself up the leaderboard for longest streaks by U.S.-born players. Eichel now trails only Kane (20 games in the 2018-19 season; 26 games in the 2015-16 season) all-time, and is now in a tie with former Buffalo Sabres forward Tim Connolly. Connolly's 16-game streak came during his 2009-10 campaign in western New York.
The Sabres got themselves into penalty trouble after tying the game, though. A string of three consecutive minors had the Buffalo penalty killing units working hard for the majority of the middle stanza, but they were able to weather the storm and go 3-for-3 against the Islanders' powerplay.
The Sabres' special teams efforts helped keep the game tied a goal apiece through 40 minutes of play.
New York seized their lead back with just 4:50 gone in the final period of regulation. Forward Jordan Eberle's shot from the point found its way through some net-front traffic and past Ullmark as the Islanders snagged the 2-1 advantage.
It was getting late early inside the Coliseum, but with 1:46 left in regulation, Eichel stepped into save the day on the powerplay.
As advertised, the Islanders were tough as could be on the penalty kill. Mathew Barzal sat in the box in the waning minutes for roughing. Buffalo went to work in the New York zone, and with around two-minutes left Ullmark vacated his net for the extra skater to give the Sabres a 6-on-4 advantage. After a scrum in the corner, Rasmus Ristolainen emerged with the puck and got it to Eichel, whose backhand seconds later beat Varlamov and tied things, 2-2 and force overtime.
The game would end 3:04 into the extra period. Already with a pair of assists in the contest, Islanders forward Anthony Beauvillier was sprung on a breakaway after New York forced a turnover to be freed out of their own end. Beauvillier's forehand shot beat Ullmark and dropped the curtain on Buffalo via a 3-2 final.

redpajama_set_name: RedPajamaCommonCrawl


Sometimes when I crave lentils, I make lentil curry. Sometimes it's veggie loaf. But when it's crummy and rainy outside, I want something both filling and warming. What fits the bill better than soup?
Hiding out in the soup section of 1,000 Vegan Recipes was this one for "lemony" lentil and rice soup. Chock full of veggies, lentils, and brown rice in tomato broth with a touch of lemon juice, how could I resist?
The recipe called for a 14.5 ounce can of crushed tomatoes and 2 cups of tomato juice as part of the broth, neither of which I had, so I improvised by using half a 28-ounce can of tomatoes and diluting the remainder to a juice-like consistency. It worked out just fine and saved me having to rush off and buy tomato juice! (And, come to think of it, probably wound up being a lot less salty than it might otherwise.) The result was one heck of a hearty soup that satisfied my lentil craving while simultaneously combating the dreariness of the weather.
As an accompaniment, I made the ridiculously easy drop biscuits from The Joy of Vegan Baking. It's a cookbook I keep forgetting I own and definitely need to use more often. The biscuits literally come together in a few minutes and bake up soft on the inside with just a bit of crispness on top. One of the variation suggestions is to use Earth Balance instead of oil for a buttery flavor…do it. It smells amazing and tastes even better. They're great biscuits to make when you have a pot of something long-simmering on the stove that needs bready accompaniment.
Question for the comments: Do you make soup in the summer? Or do you prefer to leave heartier dishes for cooler months?


BSM decided to build a significant boutique overdrive pedal in order to add a different and more modern way of receiving the signature Blackmore sound additionally to the classic BSM full power Booster line: the SUPREME! If combines the medium output of an overdrive pedal with the typical Blackmore sound, so as to achieve Ritchie's tone immediately with most amps bright channel independently from the SUPREMES' output adjustment. The drive-control is there to set perfectly Ritchie's gain-shadings over the last four decades of his rock-artistic development. The basic tone is very beefy with direct bass, punching mids and uncoloured treble.
BSM determined to deliver only one distinctive sound and therefore to do without a tone-control. Apart from that the unit features the well-known crunching overdrive charm with a little compression, just uncompromisingly tuned to Ritchie's tone. To achieve the typical sound historical correct low/medium output pickups incl. the Lace Sensor Golds are highly recommended. Each unit is a hand built unique with point-to-point wiring, premium quality parts and has a true bypass switching.
The magical tone of the Supreme overdrive is achieved by the interaction between guitar pickup, booster and amplifier. The Booster should be connected in the signal path directly behind the guitar. The Supreme is powered by a 9V battery or external 9V power supply with a current consumption of approximately 3mA.
Lace Sensor Gold is registered trademark, which BSM is not affiliated with!
If you have any questions concerning our products, especially the BSM SUPREME special overdrive, our tech-head and mastermind Mr. Bernd C. Meiser would be happy to talk to you. So don't hestitate any longer and send him an email to info@treblebooster.net or use the contact form to contact him.


text:
The Anna Scherlie Homestead Shack is a site on the National Register of Historic Places located in Turner, Montana, United States.  It was added to the Register on November 5, 1998.

A historic placard at the site reads:
The Enlarged Homestead Act of 1909 brought settlers to Montana and to this area called the Big Flat. Neil J. Scherlie was among the first to file a homestead claim and over the course of four years, three sisters and two brothers made claims nearby. Thirty-two-year-old Anna Scherlie arrived in 1913, becoming part of a long tradition of women homesteaders in Montana. In fact, in the four surrounding townships, women made up about one-fourth of the total homestead applicants. By 1916, Anna had forty acres planted in wheat, oats, and flax. Isolation on the Big Flat led many settlers to winter elsewhere and Anna followed suit. Legend has it that she went to St. Paul to work for the family of railroad magnate James J. Hill. Over the decades, Anna made few changes to her small wood frame shack, adding only a vestibule for use as a summer kitchen, a storage shed, and laundry. Droughts, depression, and two world wars passed. Anna remained here long after her neighbors had built modern homes, insisting that she was "too old for modern conveniences." The Spartan lifestyle seems to have been Anna's preference. When she died in 1973, an estate of more than $100,000 was divided among eighteen nieces and nephews; her ashes were scattered beneath a lilac bush on the property. Leon and Nellie Cederburg purchased the homestead when its seasoned resident moved to Havre in 1968. Rather than return the site to crop land, the Cederbergs maintain the homestead exactly as Anna left it.

The homestead building is a  woodframe building with a gable roof.

References

Houses in Blaine County, Montana
Houses on the National Register of Historic Places in Montana
National Register of Historic Places in Blaine County, Montana
Houses completed in 1913
History of women in Montana

redpajama_set_name: RedPajamaWikipedia


text:
VC Firm Lightspeed Venture Partners to Invest $1.8 Bln in New Funds, Including CryptoVC Firm Lightspeed Venture Partners to Invest $1.8 Bln in New Funds, Including Crypto – Altcoin Today
July 11, 2018 - by coineradmin
American venture capital firm Lightspeed Venture Partners has raised $1.8 billion, which it plans to invest in startups in various fields, including digital currency, Reuters reported July 10.
Lightspeed told Reuters that $1.05 billion of the new funding will be allocated to invest in more mature companies. The firm is planning an expansion to Southeast Asia by contributing to companies active in fields from cryptocurrency and biotechnology to the cosmetics industry.
Since startups rely on funding from venture capital rather than public markets, Lightspeed will invest in a company repeatedly over the course of several years in order to keep a significant ownership interest. Jeremy Liew, a Lightspeed partner, told Reuters that such a trend "has only been increasing over time, and as a result our funds have been getting bigger over time as well."
At the same time, another Lightspeed partner Ravi Mhatre argued that granting "$500 million or a billion dollars can be a king-making strategy. But it's not a substitute for building a lasting company."
The partners said that it will be a challenge for Lightspeed to meet performance expectations due to the success of their previous funds, which have returned $2.7 billion to investors since the beginning of 2017. According to Reuters, companies supported by Lightspeed have conducted 17 initial public offerings (IPO) during the last five years. Liew said:
"If you point to one moment in time for the firm it was probably the Snap IPO. But really, it's a decade of hard work and it all came to fruition at the same time."
Lightspeed Venture Partners has traditionally been an early-stage investment firm and the first third-party investor in Snap's messaging app Snapchat. In 2014 Blockchain.com, then Blockchain.info, raised $30.5 million in a funding round led by Lightspeed.
In 2017, Liew advocated for investment in Bitcoin (BTC), predicting that BTC will reach $500,000 by 2030. He said then that "BTC and the other digital currencies, they all really see a lot of benefit in times of political and economic instability."
–AltcoinToday.com
Photo via Shutterstock.
TaggedAmerican venturebillioncapitalfirmLightspeedpartnersplansraisedVenturewhich
Previous Article Regulators Are Slowly Starting to Get It: Utility Tokens Are Real – CoinDesk
Next Article How Crypto Saved My Life in September 2017 – Hacker Noon


My first time in Thailand definitely did not disappoint. I've always loved Thai food and whenever I don't know what to eat, my go-to is any type of Thai food so I knew I was going to love Thailand. Although I've only explored a small part of Thailand, specifically Phuket, I realized there is so much more to love than the food culture. The beaches, super kind people, music and the beautiful energy of this island is unforgettable. Since this was a trip sponsored by Revolve, I did a little bit of shopping on their site before I left to Thailand and some of the items I packed have easily become my favorites. I wore this gorgeous red Majorelle Deep V Dress on the first night I got to Phuket. I gravitated towards the bright color of the dress and it was perfect for an outdoor sunset dinner. The dress paired perfectly with my Raye Silver Metallic Sandal which were pretty much the only pair of sandals that I brought. They have a tiny tiny heel so they have a slight dressy feel. Can you guys tell I love the color red? Wearing this Lovers + Friends Red Ruffle Bikini Top and matching Lovers + Friends Red Ruffle Bikini Bottom. Power shoulders are in. How cool is this Self Portrait polka dot top? I paired it with these GRLFRND baggy denim shorts and Raye Silver Metallic Sandal to keep cool in the humidity. I could not believe how sticky it was! My sunglasses are from Saint Laurent.
At night we explored the Phuket night market and I got to wear this Privacy Please black long sleeve bodysuit and NBD silver pants. I thought I scored on a pair of sunglasses but turns out I overpaid! All of the colorful buildings and twinkling lights made it for an exciting night and we ended the night at one of the best Thai restaurants. One of the highlights of my trip was being able to see the elephant sanctuary. I was in awe of how beautiful these creatures are and humbled by the experience. I wore my Lovers +Friends Striped Bustier and Lovers +Friends Striped Cropped Pants for the excursion. It made me so happy to see these gentle giants treated humanely. I will never forget this moment and how it impacted me. Cooling off from the beach and sailing in this Tularosa Off The Shoulder Crop Top and Tularosa High Waister Bikini Bottoms was the best. I also wore this Tularosa Pheobe Crop Top to change up my look and leave my shoulders sun kissed! Are you even in Thailand if you don't swim in their beautiful infinity pools? The silhouette of this Lovewave Yellow Bikini Top is sick so I paired it with these killer YSL cat eye sunglasses. When ending my Revolve trip to Thailand, I ended on a high note on a beautiful yacht in the middle of the blue ocean. With my french braided hair by the one and only Jen Atkin, I wore a Nicholas polka dot dress for my last night there before leaving. Thailand was magical from the food to the shady palm trees surrounding the beaches, everywhere you could find beauty. I can't wait to come back!
Are Retro Polka Dot Prints making a comeback?


text:
Welcome To Shop Philomena Visit Philomena Family
Shop Philomena
Holy Pictures
Pictures & PostersPrayer Card
Medals with Relics
Sacred Items
Blessed OilChapletsCord
StatuesRelicsCrucifixRosariesPrayer cardsCD and DVDBOOKS
Promotional Packages
St. John Vianney & St. Philomena Devotion Set 3
Minimum donation $10.00
St. John Vianney, Cure of Ars, Patron Saint of Priests and a great devotee of St. Philomena. Many accounts of miracles within his church, he said, were through the intercession of St Philomena. The image used on the St John Vianney and St Philomena items is of a full size statue in the Sanctuary of Saint Philomena, Italy. It is a paper mache statue which was made in 1890 at a famous school of art in Lece, Southern Italy.
This small promotional packet contains:
10 x note cards (with no text inside) of St John Vianney & St Philomena
1 x Wall Picture on plastic wood size 14cm x 9cm
"To Saint Philomena God refuses nothing", St. John Vianney
You're reviewing: St. John Vianney & St. Philomena Devotion Set 3
Sign Up for Our Newsletter and get regular product updates
© 2014 Shop Philomena. All Rights Reserved.


text:
Books By Nikki Rajala
Treacherous Waters
Waters Like the Sky
Voyageur's Blog
Glossary of
French terms
French Glossary 2
Make $$ — become a voyageur! (How much did they earn?)
by Nikki Rajala | Jul 4, 2021 | Voyageur | 2 comments
Oops! They wouldn't have been able to read this recruiting sign.
In these post-pandemic days, wages and work are in our daily conversations. Both have changed, and bring up questions like: What work are people willing to do? What wages and benefits lure them to choose work?
In the French-Canadian fur trade, from the 16th to19th centuries, jobs didn't exist like we think of them. A person had two choices: One followed in the footsteps of his or her parents OR apprenticed at a new trade, a very strict 7-year unpaid internship. Some became voyageurs — temporarily as pork-eaters or more permanently as winterers. It was work at a low rung. For those without skills in writing and mathematics (most of the population), it was impossible to work their way up to a higher level.
What wages did voyageurs earn?
This is a typical voyageur contract.
Here's the hierarchy — and the money they brought home: Some of this information comes from the contracts of my ancestors 1801-1824, admittedly a small sample among the 34,000 contracts that can be searched!!
Voyageurs — Also called engagés, they were paid in "room and board," equipment, clothing and coins, though sometimes cash became "in kind."
Pork-eaters signed contracts (which were read to them!) for one 5-month trip to the rendezvous and back, and earned from 230 to 400 livres, plus a shirt and trousers, a 2 1/2 point blanket, tobacco and knives. With higher skills, their steersmen earned 600 to 1,000 livres for the same journey. However, in 1815, three milieux (middlemen were the worker bees, not in charge) on the same trip earned 1,000 each, which seems high. Were they friends of the guide? Had the competition changed?
Winterers were furnished with a double set of clothing and equipment. However, their pay didn't markedly increase.
In 1804, Charles Peloquin's 2-year contract provided him 2 covers (blankets), 2 shirts, two pairs of cotton breeches, a pair of Soullier (shoes) and a Necklace per year — a device to help portage, like a tumpline. Plus wages of 600 livres or chelins a year.
If voyageurs had had trading cards …
Advances — Up to a third of wages could be drawn beforehand — but my ancestors didn't always choose to take that opportunity. Perhaps they had enough to pay their seigneurial taxes or the loan to the doctor or blacksmith. Perhaps they were saving for a cow. In later years, more took advances.
In 1789. Jean-Baptiste Peltier, gouvernail, contracted for 230 livres and drew 20 livres beforehand.
Antoine Felix, a pork-eater in 1806, signed on as gouvernail, accepted 25 piasters of his 250 livres in advance.
Mathew Peloquin, a winterer in 1815, took 10 and then 20 piasters from his 700-livre payout early.
By the way, did you notice that livres and chelins (shillings) seem interchangeable? And that advances could be paid in piasters? A shilling was considered a day's wage, 12 pence. It was valued at one-twentieth of a pound sterling. But in Canada, they used the Halifax pound, which was valued at 90 percent of the British sterling pound.
FACTOID: In 1789, 1,120 men were hired as canoemen, 35 as guides, 71 as interpreter-clerks and 50 as clerks. The North West Company started with a dozen or so partners, which increased over time. But there wasn't great potential for upward mobility.
A handy reminder of the current values for trading.
Clerks — These men managed small fur posts, keeping records of the daily trade and events. They hoped to move up the ladder. These few did.
John Macdonell signed on as a clerk for £100 a year with the North West Company in 1793. He became a partner in 1798. He retired and became a judge and family "banker" who gave lavishly to churches and schools but became encumbered by debt.
George Nelson, at age 15, hired on as an apprentice clerk in 1802 for the XY Company, working in the St. Croix valley — for a salary of £5 Halifax "with the promise of a Share in the Company at the expiration of the indentures." At the end of 5 years, he was eligible for £100 a year and more as he also moved up after XY merged with NWC.
Daniel Harmon's first engagement as a NWC clerk was for 7 years, and renewed for a year. Then he was sent to Dunvegan for "at least three years" with a salary of £100 Halifax per annum. And he was furnished with "Cloathing and victuals, &c, &c"
FACTOID: Clerks and partners were furnished with much better food — spices, tea, sugar and flour — and liquor —like Madiera wine and shrub. To inspire greater respect from the First Americans, the higher-ups were encouraged to dress befitting their rank — lace-edged shirts. a swallow-tail coat, cocked hats. They were allowed 60 pounds of baggage to the voyageurs' 40.
Gentlemen Partners (Bourgeois) — Partners were part-owners in the company who lived year-round in the interior for five years. They supervised several trading posts in their district, divided all the profits, garnering huge sums and building great houses in Montreal. In the beginning, they also brought servants, and if they'd married an Aboriginal woman, brought her and their children to wherever he needed to be,
North West Company partners met every year to transact business at the rendezvous. Grand Portage National Monument, Grand Portage, Minnesota
Peter Pond began his independent trading career in 1765 in Detroit, eventually becoming an original member of the North West Company. However, after he was implicated in several murders, he sold back his NWC share after 1788. He died in poverty in 1807.
Owners — These Montreal men ordered trade goods from around the world, managed the fur sales in European markets and controlled the company. In 1799, the Hudson's Bay Company sold 84,922 pelts! They raked in a bundle, so to speak.
So that brings up the next question:
How much was a livre or a pound worth then? What did a shilling or a piaster buy?? Unfortunately it takes a lot to explain that. I'll write about money and what it was worth in the early 1800s in future post.
Read a novel to get the feel of the time — "Waters Like the Sky" or "Treacherous Waters." Or the ebook.
Request to be on the waiting list for Book 3.
Got a burning question? I'll research the answers for a future post.
Subscribe to this blog and read posts as soon as they're finished.
For fun discoveries and quirky info, visit me on Facebook: I love your comments.
Book me as a speaker — now that it's possible in these post-COVID days.
Ask your local gift shop or library to add "Waters Like the Sky" or "Treacherous Waters" to their collections.
"Five Fur Traders of the Northwest: Being the Narrative of Peter Pond and the Diaries of John Macdonell …" edited by Charles M Gates. Minnesota Historical Society Press (St. Paul, Minnesota, 1965)
"Harmon's Journal, 1800-1819M by Daniel Williams Harmon, a Partner in the North West Company" with a forward by Jennifer S.H. Brown. Touchwood Editions (Toronto, Ontario, Canada, 2006)
"My First Years in the Fur Trade: The Journals of 1802-1804 by George Nelson" edited by Laura Peers and Theresa Schenck. Minnesota Historical Society Press (St. Paul, Minnesota, 2002)
Subscribe ToNikki's Newsletter
Join Nikki's mailing list to receive the latest news and updates. It's free, and you can opt out anytime!
Richard Wing on August 7, 2021 at 12:35 pm
I am a volunteer interpreter at Fort Vancouver National Historic Site and just came across your site.
While founded by rival HBC, I look forward to catching up on your articles and expanding my stories to share with our visitors.
Nikki Rajala on August 7, 2021 at 7:37 pm
Thanks for the kudos! It's so much fun to find good information–and then pass it on to others. One of my ancestors was a fur trader on the west coast, and a group of fifth cousins still live there. Many of the early ones traded before either the North West Company or Hudson's Bay were such rivals. Then, it was all one group and HBC lasted. Amazing that it's the oldest company in North America, in business since the 1600s!
Meet Postmaster Gregoire
Is that cash or credit?
'Indian' is not the best word?
Eat like a voyageur — pemmican (and rubaboo)
Eat like a voyageur — pea soup (Yum?)
Subscribe To Nikki's Newsletter
Join Nikki's mailing list to receive the latest news and updates. It's free and you can opt out anytime!
Archives Select Month January 2023 (1) June 2022 (1) March 2022 (1) February 2022 (1) January 2022 (1) December 2021 (1) October 2021 (1) September 2021 (1) August 2021 (2) July 2021 (1) May 2021 (1) March 2021 (1) February 2021 (2) January 2021 (2) November 2020 (1) October 2020 (1) September 2020 (2) August 2020 (1) July 2020 (2) June 2020 (1) May 2020 (2) April 2020 (2) March 2020 (2) February 2020 (2) January 2020 (2) December 2019 (2) November 2019 (1) October 2019 (2) September 2019 (1) August 2019 (1) July 2019 (1) June 2019 (3) May 2019 (4) April 2019 (2) March 2019 (2) February 2019 (2) January 2019 (1) November 2018 (2) October 2018 (3) September 2018 (2) August 2018 (1) July 2018 (2) June 2018 (1) May 2018 (1) April 2018 (1) February 2018 (4) January 2018 (2) December 2017 (1) November 2017 (3) October 2017 (15) September 2017 (1) August 2017 (5) July 2017 (1) June 2017 (1) May 2017 (1) June 2016 (1) October 2015 (1) May 2015 (1) April 2015 (1) February 2015 (1) January 2015 (1) December 2014 (1) October 2014 (2) September 2014 (2) August 2014 (1) July 2014 (2) June 2014 (1) May 2014 (2) March 2014 (1)
Categories Select Category Featured (61) Voyageur (61)
© 2018 - 2023 ~ Nikki Rajala


text:
Woman arrested for leaving $5,000 tip on boyfriend's credit card after argument
CLEARWATER, Fla. (FOX 13) - A woman was arrested after leaving a $5,000 tip on her boyfriend's credit card at a Clearwater restaurant after they got into an argument, Pinellas County deputies say.
The incident happened June 27 around 9:30 p.m.
Deputies say Serina Wolfe and her boyfriend got into an argument at the Clear Sky Cafe because she wanted a flight home to New York and her boyfriend refused to buy her a ticket.
Deputies say he put a hold on his credit card, but when he removed it, the woman made a $5,055.37 purchase at the Clear Sky Cafe.
The cafe was notified about the fraudulent purchase but says the waitress had already been paid for the amount of the tip.
Wolfe was arrested July 1st on theft charges. Her bond was set at $2,000.
Fox News meteorologist attacked on subway train


text:
About Norris
Defective Consumer Products
Drug Injury and Defective Medical Devices
Antidepressant Birth Defects
Blood Thinner Injuries
DePuy ASR Hip Implants
Low Testosterone Treatment
Morcellator Cancer
Risperdal®
Zimmer Knee Implant
Zofran®
Environmental Injury
Fire Injury
Life Insurance Company Fraud
Longshore and Maritime Injury
Veterans Benefits FAQ
Wrongful Death Attorneys
Asbestos FAQ
Asbestos Lung Cancer
Find out if you
have a case
Blood Thinner Injury Lawsuits
Traditionally, anticoagulant drugs are prescribed to help reduce blood clots that can cause heart attacks, stroke, or cardiovascular death. Warfarin (marketed as Coumadin®) has been used for half a century. However, some next-generation anticoagulants—such as Pradaxa® and Xarelto®—have been approved in the last ten years by the U.S. Food and Drug Administration (FDA).
These newer drugs have been linked to an increased risk of severe bleeding, which may lead to severe injuries or even death.
If you or someone you love suffered severe bleeding or other injuries after taking Pradaxa or Xarelto, call our drug injury lawyers today. Our firm has years of experience fighting for the rights of injury victims, and we're ready to help you too. Complete our free initial consultation form to get started today.
Pradaxa® Bleeding Lawsuit Settlements
Pradaxa (dabigatran), a prescription blood-thinning drug, was approved by the FDA in 2010 and is used to reduce stroke risk in non-valvular atrial fibrillation (AFib) patients. Four years later, the FDA published a study that revealed patients age 65 and older taking Pradaxa faced a higher risk of gastrointestinal bleeding than patients taking warfarin.
Due to these significant risks, thousands of victims and their families have brought lawsuits against Pradaxa manufacturer Boehringer Ingelheim, leading to settlements totaling more than $650 million to date.
Xarelto® Bleeding Risks
Despite being approved for use by the FDA in 2011, Xarelto (rivaroxaban) has been known to:
Triple the risk of major bleeding among patients suffering from Acute Coronary Syndrome.
Nearly triple the risk of major bleeding among acutely ill patients taking blood thinners to reduce the risk of blood clots.
Double the risk of severe bleeding among patients undergoing hip surgery.
Increase the risk of developing blood clots or suffering a stroke.
If you or someone you love took a blood-thinning medication, such as Pradaxa or Xarelto and suffered from severe bleeding, stroke, or blood clots, we may be able to help. Don't take on the pharmaceutical companies alone. Let our drug injury lawyers fight to get the compensation you deserve. Contact our law firm today.
Coumadin® is a registered trademark of Bristol-Myers Squibb Company and is used here only for the purpose of identifying the product in question. Pradaxa® is a registered trademark of Boehringer Ingelheim and is used here only for the purpose of identifying the product in question. Xarelto® is a registered trademark of Bayer AG and is used here only for the purpose of identifying the product in question.
This law firm is not associated with, sponsored by, or affiliated with Bayer AG; Boehringer Ingelheim; Bristol-Myers Squibb Company; or the U.S. Food and Drug Administration.
No representation is made that the quality of legal services to be performed is greater than the quality of legal services performed by the lawyers. All elements of this website are copyrighted materials for Clixsy, LLC or Norris Injury Lawyers © 2019


text:
Q: How to pass java script variables into json format i want to pass variable values into json below is what i am trying.
In javascript i am getting values like this:
var f_name= document.getElementById("firstname").value;
var phone_number= document.getElementById("number").value;

And then in JSON  i want to pass these values:
"Site": {
   "Name": "+f_name+",
   "Phone": "+phone_number+"
 }

its not working. What is wrong with this?

A: Create an object, then stringify it as JSON
var f_name       = document.getElementById("firstname").value;
var phone_number = document.getElementById("number").value;

var obj = {
    Name  : f_name,
    Phone : phone_number
}

var json = JSON.stringify(obj);

Chances are however that you haven't understood the difference between an object and a JSON string, and that you don't really want JSON at all.

redpajama_set_name: RedPajamaStackExchange


We are currently on a break from Dinner Church!
Whats Happening at Jehu's Table This Month?
We are a dynamic community gathered in a new kind of church in the heart of the Brooklyn neighborhood. We are committed to justice, which is God's love in the public square. We are rooted in the belief that God's Grace is for everyone, no exceptions. We confess this Grace because God is most fully revealed on the Cross. We are Jesus followers and believe although community can get messy we are still committed to gathering as one. We ground ourselves in these truths by recounting the ancient story of God's people in scripture and experiencing it in worship.
We are centered as an African-descent community of believers rooted in the Christian tradition with a Lutheran perspective. We are a mission of the Evangelical Lutheran Church in America that is rooted in the worship styles and cultural traditions of African-descent or "Black Church experience" but are a community for all marginalized peoples. In particular, we honor God's special dispensation for our LGBTQ+ siblings in Christ.
The church has a lot to answer for. We are honored you are even considering us as a community. We know that this world begs questions about who God is? Why are God's followers sometimes so hateful? We are committed to walking with you as you explore those questions. We are not here to sell you anything, including faith. We will be authentically broken and hope that you can see the Christ that is present with us. If that is something you desire too, we hope you can join us.
Want to know more? So do we! We are just launching this new church and so this page is just getting started. Subscribe for updates as this community unfolds in front of us.
We would love for you to join us our journey.
Christ is already present in Brooklyn. God is already up to some amazing things in East New York. We just want to witness God's glory along side you, even if you would never use those words to describe it.
Worship Time: 11am every Sunday.
Also check our calendar page.


BrightStar Care® of North Seattle's mission is to improve the health and wellbeing of those entrusted to our care. And from our industry-leading employment standards to RN oversight on every Plan of Care, we are committed to the highest levels of quality and support.
BrightStar Care is ready to help. For more information or to schedule a complimentary in-home care assessment, contact our BrightStar Care of North Seattle office at (206) 777-1190.


Mr. Edward Tian (Tian Suning) is the founder and Chairman of China Broadband Capital Partners, L.P. (CBC). CBC is a TMT sector focused private equity fund and invests primarily in companies in the Telecom, Internet, Broadband, Media and Technology ("TMT") sector and companies serving the TMT sector in China.
Before Mr. Tian founded CBC Capital, he was the Vice Chairman and CEO of China Netcom Group from Nov. 2002 to May 2006. He was the CEO of China Netcom Company Ltd. from Aug. 1999 to May 2002. Prior to joining China Netcom, Mr. Tian was the co-founder and Chief Executive Officer of AsiaInfo Holding Inc., the first Internet technology provider in China. AsiaInfo successfully listed in NASDAQ in 2001 under Mr. Tian's leadership. Mr. Tian also used to be the Vice Chairman of PCCW Limited from 2005 to 2007. He's now the Independent Director of several multi-national companies, they are including MasterCard International, Lenovo Group Limited and Taiking Life Insurance Company Limited. He's also the Senior Advisor of Kohlberg Kravis Roberts & Co. (KKR).
Mr. Tian holds a Ph.D. in Natural Resource Management from Texas Tech University. He is also the member of Harvard Business School Asia Advisory Committee, Co-Chair of TNC China Board.


Some days ago I was rather surprised when one of the developers at the work reported that permission grants he was assigning to a database are being ignored. To be more precise, users without specified privileges were able to actually work on a MySQL database without being prior permission.
Of course, I was very sceptical about the report, so I tried creating a new database on the machine, and tried to access it as a user which wasn't granted any permissions. And, as I expected, it didn't work. The user's access to database was declined. I went back to work thinking the colleague had made a type or something.
In five minutes he called again, and it turned out to be a database called 'test'. Once again I tried the whole procedure, this time using that database, and what do you know - he was right.
To cut the thing short, I've found out in the end that the problem was that for some sick reason, by default, the MySQL creates the 'test' database, and grants everyone the right to do whatever they can with it. After some research I've found a nice article at SecurityFocus which helped me solve the issue at hand. What I was most baffled about is that I really haven't ever ran into articles describing this kind of behaviour (maybe I was just too lazy to read stuff in details?).
In the end, the good thing is that now I know what to look out for in the future.


Help Slenderman defeat the most dangerous Creepypastas of all time.
somewhat good, my computer is so glitchy its hard to enjoy the game and i cant get past micky because it wont let me do anything but just stand and wach me exsplode. I rember beating him once but now its just inposible even with low quality setting on.
I have no clue how to get the mouse out of the mouse trap.
I love this game! I like how all of the solutions made logical sense and weren't just random, that is my biggest problem with most Point and Click games.
A simple point and click game starring the Strawberry Owl from Caramel Marshmallow.
Captured by pirates, you almost lost hope. But you still have a chance to escape!


text:
Phaedropsis bipunctalis är en fjärilsart som beskrevs av Hans Georg Amsel 1956. Phaedropsis bipunctalis ingår i släktet Phaedropsis och familjen Crambidae. Inga underarter finns listade i Catalogue of Life.

Källor

Fjärilar
bipunctalis


text:
Камбург () — город в Германии, в земле Тюрингия.

Входит в состав района Заале-Хольцланд. Подчиняется управлению Дорнбург-Камбург.  Население составляет 2899 человек (на 31 декабря 2006 года). Занимает площадь 13,31 км². Официальный код  —  16 0 74 011.

Город подразделяется на 8 городских районов.

Примечания

Ссылки
 Официальная страница

Города Тюрингии


Multiple agencies and organizations have developed applications, websites, and text message/email notification services that can send local weather alerts to your smart phone or other handheld device. Mobile users are encouraged to contact their local governmental jurisdiction for notification services available. The links provided below are a sampling of these services.
NOTE: Delta County provides these links as a public service, and they do not constitute product endorsements. Charges from wireless carriers may apply.