Comments (7)
PS I'd suggest keeping style consistent with the source database to facilitate interoperability
from usdaplantsapi.
The .x
and .y
versions are definitely from a join, but since they were there already I didn't know how to rename the .y
versions. Do I just remove the .y
versions?
I can convert back to CamelCase
from usdaplantsapi.
Sorry didn't realize that was my work! Yes drop the .y versions.
The original USDA names have a few potholes, not pure CamelCase - the goal
is consistency rather than style.
On Tue, Jul 12, 2016 at 6:42 PM Scott Chamberlain [email protected]
wrote:
The .x and .y versions are definitely from a join, but since they were
there already I didn't know how to rename the .y versions. Do I just
remove the .y versions?I can convert back to CamelCase
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#7 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAcX5-ofBaHPy4puo-DcMQGWzOxVc8YJks5qVCZogaJpZM4JK62n
.
from usdaplantsapi.
But keep the joined columns to the right of the columns with .y
versions, correct?
from usdaplantsapi.
yep - keep joined columns to the right. They are sparse - only 3% of the rows have any information (from http://plants.usda.gov/charinfo.html) - "2000 conservation plant species and 500 additional cultivar".
If speed or optimization is an issue, you could reduce the size by either a) keeping the tables separate and joining on the fly or b) not returning values that are ""
.
from usdaplantsapi.
I might make a separate table for the other columns.
also, returning ""
isn't ideal, meaning to change all those to null
but haven't sorted out fastest way to do that yet
I might play with not returning fields with no data, though that makes merging records a bit more complicated
from usdaplantsapi.
@sckott regarding Syntax - I just checked and now see that they don't use camel case but white space. Seems reasonable that useability should trump consistency so go with the potholes.
from usdaplantsapi.
Related Issues (14)
- add robots.txt
- feedback HOT 6
- update to newer data HOT 2
- make status page HOT 1
- add api docs HOT 1
- Add citation & terms HOT 2
- log file rotation HOT 1
- API down HOT 3
- new dump perhaps HOT 2
- switch from Unicorn to Puma server
- support fuzzy match
- wetland indicator status feature HOT 1
- Retiring this API next week HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from usdaplantsapi.