Difference between revisions of "Location Configuration for Points"
From Earth Science Information Partners (ESIP)
(New page: {{WCS Glossary |TermDesc=From file [http://128.252.202.19:8080/static/point/point_config.py point_config.py] In it's simplest case, SQL views are used to create required location table, s...) |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{WCS Glossary | {{WCS Glossary | ||
| − | |TermDesc= | + | |Glossary Domain=WCS |
| + | |TermDesc=This is a [[Python_Dictionaries|python dictionary]] created by a human. It contains the name and columns of Location Table for Points. Used by Feature Processor for Points | ||
| + | |Links=[[Location_Table_for_Points|Location Table for Points]] [[Feature_Processor_for_Points|Feature Processor for Points]] [[Python_Dictionaries|python dictionary]] | ||
| + | }} | ||
| + | [http://128.252.202.19:8080/static/point/point_config.py point_config.py] | ||
In it's simplest case, SQL views are used to create required location table, so no aliasing is needed. | In it's simplest case, SQL views are used to create required location table, so no aliasing is needed. | ||
| Line 19: | Line 23: | ||
| − | In the CIRA/VIEWS case, table and fields are | + | [http://128.252.202.19:8080/static/CIRA/CIRA_config.py CIRA_config.py] |
| + | |||
| + | In the CIRA/VIEWS case, table and fields are aliased: | ||
VIEWS_location_info = { | VIEWS_location_info = { | ||
| Line 37: | Line 43: | ||
* "SiteCode", "Latitude" and "Longitude" are aliased to "loc_code", "lat" and "lon". | * "SiteCode", "Latitude" and "Longitude" are aliased to "loc_code", "lat" and "lon". | ||
| − | + | [[Category:StationPoint]][[Category:Server]] | |
Latest revision as of 13:20, September 6, 2010
< Back to Glossary | Edit with Form
Location_Configuration_for_Points Description: [[TermDesc::This is a python dictionary created by a human. It contains the name and columns of Location Table for Points. Used by Feature Processor for Points]]
Glossary Domain: WCS
Related Links
Links to this page
[[Links::Location Table for Points Feature Processor for Points python dictionary]]
Contributors
No Contributors
History
No History Available
Term Details
In it's simplest case, SQL views are used to create required location table, so no aliasing is needed.
location_info = {
'location':{
'service':'WFS',
'version':'1.0.0',
},
}
These are the standard names that datafed uses:
- The dimension name is "location".
- No aliasing is needed, since the DB table/view and column names are standard.
- The view/table name in the DB is "location".
- The columns are lat", "lon" and "loc_code" and loc_code is a text type, not an integer.
In the CIRA/VIEWS case, table and fields are aliased:
VIEWS_location_info = {
'location':{
'service':'WFS',
'version':'1.0.0',
'table_alias':'Site',
'columns':{
'loc_code':{'column_alias':'SiteCode'},
'lat':{'column_alias':'Latitude'},
'lon':{'column_alias':'Longitude'},
}
},
}
- The dimension name is still "location"
- The location table is called "Site"
- "SiteCode", "Latitude" and "Longitude" are aliased to "loc_code", "lat" and "lon".
