[nmglug] Satellite imagery
Brian O'Keefe
okeefe at cybermesa.com
Sun Nov 11 08:45:34 PST 2018
Good ideas Jonathan. I'll check them out. Maybe something there.
On 11/10/18 10:26 PM, Jonathan Romero wrote:
> It also occurred to me that other train lines probably use the same
> track. Maybe see if Amtrak schedules were affected during that time?
>
> On Sun, Nov 11, 2018 at 12:24 AM Jonathan Romero <jonnyro at jonnyro.com
> <mailto:jonnyro at jonnyro.com>> wrote:
>
> I don’t think the resolution of your satellite photos has anything
> to do with your processor. The earth is huge and unless
> satellites are specifically tasked to do otherwise they take very
> low resolution images.
>
> Plus. Free offerings are likely to be lower resolution.
>
> Maybe you could find some historical data on taxes collected for
> delivered coal during that time period and see if there was any
> fluctuations? I mean if you really disrupted coal deliveries
> something should have been affected downstream.
>
> Also maybe see if there are any web forums for train conductors
> etc. maybe find a retired one that would point you in the right
> direction for finding the train schedule info you need.
>
> Seems like retirees love to talk. They are probably all on
> Facebook anyway
>
> On Sat, Nov 10, 2018 at 8:29 PM Brian O'Keefe
> <okeefe at cybermesa.com <mailto:okeefe at cybermesa.com>> wrote:
>
> And here's the image I'm trying to download and work with.
> Maybe a more powerful processor would help? Doubt that tho.
>
> On 11/10/18 5:25 PM, Jonathan Romero wrote:
>> You could also ask a company Called Vricon if they have
>> holdings for that date.
>>
>> Again the right timeline makes it unlikely but you might as
>> well ask.
>>
>> Check with planet.com <http://planet.com>. They have a pretty
>> big fleet up there and are capturing at a pretty high
>> frequency. Again. Probably expensive but perhaps worth it?
>>
>> Maybe bnsf doesn’t want to talk but delays at bnsf should
>> have affected other trains using that line.
>>
>> Traffic cams near train crossings?
>>
>> Google traffic data showing traffic delays indicative of
>> altered train flow?
>>
>> On Sat, Nov 10, 2018 at 7:16 PM Brian O'Keefe
>> <okeefe at cybermesa.com <mailto:okeefe at cybermesa.com>> wrote:
>>
>> There are many, many pix and video evidence collected by
>> the legal eagles that helped us up there but nothing that
>> shows the tracks beyond several hundred yards. I have
>> looked at images from GoogleEarth and there are two
>> sidings, one east and one west, of the conflict area. The
>> one to the west is 6 miles away and the one to the east
>> is 3. So I'm looking for images of those with trains, on
>> that day at that time. A tough one.
>>
>> Not sure why the smaller sized downloads are grayscale
>> but they are unreadable since they are so indistinct.
>> Weird there. There may be more pix from the state from
>> that day as they provided some for another case, same as
>> mine. The trains they show are in the Mandan yard,
>> pointing the wrong direct (according to testimony) and
>> are empty coal cars while state's testimony stated they
>> were two trains heading east loaded with coal. all I need
>> is a pic of the next mile or two to the west where the
>> "altercation" happened. No trains, no case.
>>
>> Thanks
>>
>> On 11/10/18 3:33 PM, Jonathan Romero wrote:
>>> Protesting good practices for the modern age will
>>> probably involve launching a drone to ensure good record
>>> keeping.
>>>
>>> Maybe fixed wing electric plus solar from the EFF?
>>>
>>> Or Good Samaritan private pilots?
>>>
>>> On Sat, Nov 10, 2018 at 5:26 PM Jonathan Romero
>>> <jonnyro at jonnyro.com <mailto:jonnyro at jonnyro.com>> wrote:
>>>
>>> Maybe have your lawyer request the info from BNSF.
>>>
>>> They probably know exactly where those trains were.
>>>
>>> I’d also see if flickr or any other image sharing
>>> site has images on that date or general location.
>>>
>>>
>>>
>>>
>>> On Sat, Nov 10, 2018 at 5:23 PM Arlo Barnes
>>> <arlo.barnes at gmail.com
>>> <mailto:arlo.barnes at gmail.com>> wrote:
>>>
>>> Yeah, a time so specific will be hard to find.
>>> https://www.openstreetmap.org/edit shows various
>>> freely-licensed imagery from that area, and the
>>> most recent one from Bing aerial there is from
>>> October 14th, 2016. Is there a bit of fuzz
>>> allowable on the time/date?
>>> —Arlo James Barnes
>>> _______________________________________________
>>> nmglug mailing list
>>> nmglug at lists.nmglug.org
>>> <mailto:nmglug at lists.nmglug.org>
>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>>>
>>> --
>>> Jonathan S. Romero
>>>
>>> --
>>> Jonathan S. Romero
>>>
>>> _______________________________________________
>>> nmglug mailing list
>>> nmglug at lists.nmglug.org <mailto:nmglug at lists.nmglug.org>
>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>> --
>> _______________________________________________
>> nmglug mailing list
>> nmglug at lists.nmglug.org <mailto:nmglug at lists.nmglug.org>
>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>>
>> --
>> Jonathan S. Romero
>>
>> _______________________________________________
>> nmglug mailing list
>> nmglug at lists.nmglug.org <mailto:nmglug at lists.nmglug.org>
>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
> --
> _______________________________________________
> nmglug mailing list
> nmglug at lists.nmglug.org <mailto:nmglug at lists.nmglug.org>
> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>
> --
> Jonathan S. Romero
>
> --
> Jonathan S. Romero
>
> _______________________________________________
> nmglug mailing list
> nmglug at lists.nmglug.org
> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nmglug.org/pipermail/nmglug-nmglug.org/attachments/20181111/d31821f8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.png
Type: image/png
Size: 3148 bytes
Desc: not available
URL: <http://lists.nmglug.org/pipermail/nmglug-nmglug.org/attachments/20181111/d31821f8/attachment-0001.png>
More information about the nmglug
mailing list