Ignore:
Timestamp:
10/07/12 15:15:27 (7 years ago)
Author:
mnagni
Message:

Complete - # 22489: CEDA Observation Collection - phenomenonTime
 http://team.ceda.ac.uk/trac/ceda/ticket/22489
Complete - # 22518: The description is broken
 http://team.ceda.ac.uk/trac/ceda/ticket/22518
Complete - # 22488: CEDA Observation Collection - Geographical Extent
 http://team.ceda.ac.uk/trac/ceda/ticket/22488

Now the Moles3EPB explicitly call the "synchronise" method in the SQLAlchemy mapped classes to assure the persistence of the data
Uses the CedaMolesModel? v 0.1.5 which correct a major problem in synchronise the instances with database

File:
1 edited

Legend:

Unmodified
Added
Removed
  • mauRepo/MolesManager/trunk/src/libs/migration/processor/commons.py

    r8445 r8460  
    959959            tm_position = createTM_Position(date8601 = createDate(isoDateStringToTimeDate(doc_phenomenon_time))) 
    960960            pt = createTM_Instant(tm_position) 
    961     return pt 
     961        return pt 
    962962 
    963963def fromPhenomenonTimeToString(phenomenonTime): 
     
    988988    return str(datetime.date(int(idate.year), int(idate.month), int(idate.day))) 
    989989 
    990 def fromGeographicBoundingBoxToString(geographicBoundingBox): 
    991     if geographicBoundingBox is None: 
     990def fromGeographicBoundingBoxToString(gbb): 
     991    if gbb is None: 
    992992        return None 
    993     return ('%f %f,%f %f') % (geographicBoundingBox.eastBoundLongitude, geographicBoundingBox.northBoundLatitude, \ 
    994                               geographicBoundingBox.westBoundLongitude, geographicBoundingBox.southBoundLatitude) 
     993    return '{0} {1},{2} {3}'.format(gbb.eastBoundLongitude, gbb.northBoundLatitude, gbb.westBoundLongitude, gbb.southBoundLatitude) 
    995994     
    996995def compareGeographicBoundingBoxes(gb1, gb2): 
Note: See TracChangeset for help on using the changeset viewer.