RE: mapping

I think that is correct.  What I am building is a representation of the
network structure with references to the node information that you are
describing.  One use of the map is to display available hotspots.  For
that purpose the information you have is perfect.  However, I would also
like to be able to display the infrastructure, hopefully with the current
status of links and nodes.

What I may do is work with hotspot information for now and move to
infrastructure specific elements later.

I'll print out information about the various schemas involved to peruse
while I am gone and try to work out an swn.rdf file afterwards.

I have found that the GoogleMaps documentation is somewhat limited.  It
can draw lines in full color with alpha and it can display "markers" with
custom icons.  It is my suspicion that the capability is there to draw
polygons either through their API or at least assisted by it, but some
delving into their .js files will have to be done.  Most likely, a cgi
will be written to draw the polygons needed so an image can be overlaid on
the map.


> Well, it sounds like we are doing two different things here.
>
> You are more interested in documenting the *real* SWN, where I simply
> have an rdf full of hotspots.
>
> I don't know if the meshesWith property would be ideal, as these are
> point-to-point infrastructure links.  There should be one in wireless
> ontology that specifies a link.  I used to keep them within the hotspot
> rdf, but I gave up.
>
> We should probably maintain our network infrastructure in something like
> swn.rdf ... If you want to supply  this document's url, maybe we can
> work on getting it completed and up to spec.
>
> One last thing, can GoogleMaps draw lines or highlight polygons?
>
>
>> -----Original Message-----
>> From: [email protected]
>> [mailto:[email protected]] On Behalf Of J. Kyllo
>> Sent: Friday, July 15, 2005 10:01 AM
>> To: [email protected]
>> Subject: RE: mapping
>>
>> Wow, I'm not sure how I missed that.  That's some good
>> homework for namespaces.  Coordinates would be great, but
>> they should probably supplement the address location rather
>> than replace it.
>>
>> When I was writing my xml ditty, I went with a seperate
>> section to store link data that specifies what nodes (what
>> interfaces really) are being linked.  In the wireless network
>> nodes ontology, is the "meshesWith"
>> property to be used for specifying links to other nodes?
>>
>> Additionally I was hoping to go more general than just
>> wireless and describe network links.  This allows for the
>> specification of tunnels or other hardwired links (DSL, for example).
>>
>> That data is certainly useful.  Thanks for pointing it out.
>> I just have to learn a little more about rdf!
>>
>> -Jeff
>>
>> > You might want to check out the wispot.rdf file which is
>> featured on
>> > the node list.
>> > I could also make sure the addresses are resolved properly so you
>> > don't have to bang geocoder.us to hell and back.
>> >
>> >
>> >> -----Original Message-----
>> >> From: [email protected]
>> >> [mailto:[email protected]] On Behalf Of J. Kyllo
>> >> Sent: Thursday, July 14, 2005 12:30 PM
>> >> To: [email protected]
>> >> Subject: mapping
>> >>
>> >> I don't mean to reinvigorate the beating of a dead horse,
>> but I have
>> >> recently done some work towards using google maps for
>> displaying SWN
>> >> nodes.  I will be out of town for the next week and a half, but if
>> >> anyone wants to take a look here you go:
>> >>
>> >> http://jkyllo.echospiral.com/map.html
>> >>
>> >> It is written in JavaScript so you can view the page source to get
>> >> the code.  It is my first project in JavaScript, but it's
>> a fun one.
>> >> The data is currently just stored in an XML file and is grabbed by
>> >> the app.  The idea is to update the xml from the wiki
>> periodically.
>> >> This is the reason for my recent posts about wiki xml data.
>> >> Eventually, the app could just grab from the wiki directly, but I
>> >> think this would cause undue overhead.
>> >> There are currently issues with reading the wiki xml, but
>> that's for
>> >> later discussion.
>> >>
>> >> If anyone is interested in details we can email directly
>> or what not.
>> >> I will try to do a writeup for the wiki, but I don't know
>> that I can
>> >> do that before I leave.
>> >>
>> >> Cheers,
>> >> Jeff K.
>> >>
>> >> _______________________________________________
>> >> Talk mailing list
>> >> [email protected]
>> >> http://seattlewireless.net/mailman/listinfo/talk
>> >>
>> > _______________________________________________
>> > Talk mailing list
>> > [email protected]
>> > http://seattlewireless.net/mailman/listinfo/talk
>> >
>>
>>
>> _______________________________________________
>> Talk mailing list
>> [email protected]
>> http://seattlewireless.net/mailman/listinfo/talk
>>
> _______________________________________________
> Talk mailing list
> [email protected]
> http://seattlewireless.net/mailman/listinfo/talk
>


_______________________________________________
Talk mailing list
[email protected]
http://seattlewireless.net/mailman/listinfo/talk