Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Paul Wideman
    @pwideman
    FYI: A Feature object has a member with the name "geometry". The value
    of the geometry member SHALL be either a Geometry object as
    defined above or, in the case that the Feature is unlocated, a
    JSON null value.
    kasey
    @kasey
    We didn't talk about mixing feature schemas in a FeatureCollection. The exchange between Alex and Cholmes just now sounded like there was an assumption that all Features in a FeatureCollection would be of the same type.
    kasey
    @kasey
    @jeffnaus can you expand on what your DG colleague was describing? I think I need a concrete example
    Alex Kaminsky
    @alkamin
    Yeah, I think we should expect a mixture, otherwise it would be super weird. You wouldn't expect to get back several FeatureCollections with each of a certain type
    Paul Wideman
    @pwideman
    @joshfix have you generated new java classes from the updated spec?
    Josh Fix
    @joshfix
    i did last night but not yet today
    i just pushed an updated swagger yaml with all the core metadata stuff for features
    Josh Fix
    @joshfix
    here's my code that does nothing besides return all features
    requires mongo
    and here is my class that generates 20 features at a time. the code is a mess, so ignore it. it's invoked by hitting the /gen endpoint
    kasey
    @kasey
    Josh Fix
    @joshfix
    since geometry is just defined as an object now, it's missing the type parameter in my output. should we redefine this to to have a type property (string) and a geometry property (object) instead of making the entire definition just an object?
    Paul Wideman
    @pwideman
    it would be type and coordinates, but that doesn't cover the GeometryCollection case
    in which you just need an array named geometries
    kasey
    @kasey
    Push branch core-spec
    Josh Fix
    @joshfix
    You guys should ask Chris for permissions to the repo so you can push directly and not have to submit pull requests
    Alex Kaminsky
    @alkamin
    Yeap, I think we all have permissions now. PRs can be useful if we're looking for comments and discussion though.
    Sean Harkins
    @sharkinsspatial
    Here is a blog post describing some of our reasoning around our new postgres backed STAC API. https://medium.com/devseed/sat-api-pg-a-postgres-stac-api-af605cafd88d
    James Santucci
    @jisantuc
    it explains strategies we considered and why we picked what we did
    Grigory
    @pomadchin
    James Santucci
    @jisantuc
    i'm about done sprinting for the day -- i have a pr up to fix two particularly annoying franklin data import warts (azavea/franklin#319, https://github.com/azavea/franklin/issues/259). thursday afternoon i'm going to try to fix the last of the issues i mentioned in my intro (azavea/franklin#344). these should collectively make import significantly less frustrating. feel free to ping me though if there's something you think i can help with / should weigh in on