Can you give me more detail on the 311 lat/long issue?
-
-
Replying to @Pearic_Roche
.@KansasCityEric lat/lon are in "address with geocode" and need to be parsed out. These should be in separate fields https://data.kcmo.org/widgets/7at3-sxhp …
1 reply 0 retweets 0 likes -
Replying to @Datapolitan
.@KansasCityEric parsing these with
#Excel is actually challenging because of the embedded line returns that prevent a simple text to cols2 replies 0 retweets 1 like -
-
Replying to @jalbertbowdenii
.
@jalbertbowdenii @KansasCityEric not everyone can use#Python#R or#SQL.#opendata4all2 replies 0 retweets 1 like -
Replying to @Datapolitan @jalbertbowdenii
I hear ya. Let me see if there is an easy way to do this. *fingers crossed*
1 reply 0 retweets 1 like -
Replying to @Pearic_Roche
.@KansasCityEric
@jalbertbowdenii Hopefully it's a quick win. The data is there, it's just a matter of formatting it differently.1 reply 0 retweets 1 like -
Replying to @Datapolitan
.@KansasCityEric I'd be interested to know if this data model affects
@socrata#API bounding box queries. Can they be defined in Lat/Lon?1 reply 0 retweets 0 likes -
Replying to @Datapolitan @socrata
Not sure.
@socrata should know. The way the location column is formatted is actually how@socrata formats it.1 reply 0 retweets 0 likes -
Replying to @Pearic_Roche @Datapolitan
bounding box queries will work just fine - the lat/long in address_with_geocode are geocoded from address
1 reply 0 retweets 1 like
API docs are at https://dev.socrata.com/foundry/data.kcmo.org/cyqf-nban … — you can get it all in (geo)json and/or CSV if you want
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.