Location Configuration for Points

< Back to Glossary | Edit with Form

Location_Configuration_for_Points Description: 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: {{{Glossary Domain}}}"{{{Glossary Domain}}}" is not in the list (WCS, HTAP, AQInfrastructure) of allowed values for the "Glossary Domain" property.

Related Links

Links to this page
[[Links::Location Table for Points Feature Processor for Points]]

Contributors

No Contributors

History

No History Available

Term Details

point_config.py

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.

http://128.252.202.19:8080/static/CIRA/CIRA_config.py CIRA_config.py]

In the CIRA/VIEWS case, table and fields are alised:

   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".