Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add seamark:notice:orientation #22

Open
PetersonGIS opened this issue Feb 20, 2018 · 3 comments
Open

Add seamark:notice:orientation #22

PetersonGIS opened this issue Feb 20, 2018 · 3 comments
Assignees

Comments

@PetersonGIS
Copy link
Collaborator

Eventually we will want to have seamark notice orientation data in the db. Note: not crucial for proof-of-concept.
orientation

@erictheise erictheise self-assigned this Feb 20, 2018
@erictheise
Copy link
Member

Should be fixed with 1468ad0. Data will be available after tonight's import.

@erictheise
Copy link
Member

I am missing something obvious.

@erictheise erictheise reopened this Feb 21, 2018
@erictheise
Copy link
Member

erictheise commented Feb 23, 2018

The problem has been that one of the attributes on a seamark:notice, function, is a reserved word in SQL. The unexpected result is that the value of function has been getting through and appearing in the popup inspector but the next field in the query, orientation, disappeared with the error.

At a bit of a loss as to what the best thing to do is but for now I am replacing function with the S100 name, fnctnm. In the case of the buildings and landmarks queries I'll use functn.

A similar problem arose with the use of the attribute name group, which I replaced with signal_group, and which I'll revisit and log somewhere.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants