Discussions on Boats
Start a New Discussion
-
-
A date designed to go along with the designer would be useful since they are normally specified together.
-
+1
-
Sounds like a good idea. This would be for the class right, or a specific ship?
-
For now I think it can just go on Ship Class since that's where the designer is. There's a more significant refactoring needed to allow things like Designer and Date Designed to be present on either the Ship Class or the Ship. Right now there's no way to handle designers of unique vessels which aren't part of a class.
-
I've added a Date Designed attribute to Ship Class. I think I've treated unique vessels as members of their own class (the topic takes both class and ship types).
-
Thanks for adding the new property. I'll give co-typing a try and see how it works. You might want to add a note to the description indicating that this is the intended usage (actually the whole schema is a little light on documentation).
-
-
-
-
Is there anyway for entering the shipping regions ? - its good for shipwrecks and other events where exact location is difficult to ascertain
-
i've entered Humber, Dogger, Foerties; Viking, Fair Isle, Faeroes, South East Iceland, Bailey, Rochall, Shannon, Sole; Fastnet; Lundy, Irish Sea, Plymouth, Portland, Wight, Dover, Fitzroy, Trafalgar, and some others but I am not sure they fit in
-
dsinclair,
I don't think there's one already available - I've cc'd in the Boats commons incase anyone there knows of something.
But you can always create your own Shipping region type if you wish.
-
I don't think there's anything like this currently, but I'm a little concerned about conflating a geographical region which is controlled by a single authority like the UK Met Office with a more general usage like locating shipwrecks since a) they can change them whenever they want and b) they don't need to align with common usage. If someone sank "off Fastnet," they're probably somewhere within a certain radius of Fastnet Rock, not necessarily in the rectangular with Fastnet Rock at one corner. Similarly, I'm sure the Irish don't consider the waters off Cork to be called "Fastnet."
I think it would be better to identify them as explicitly related to weather forecasting or the authority that defined them and have them dated for when they were created/changed. It would also be useful to annotate them with what they're named after to help tie them back to natural features. As an example, I've associated the UK Met "Dogger" with "Dogger Bank."
-
Thanks for this. I've been on holiday and away from the net which partially explains the delay in my reply. Maybe I was going to fast on this, and I began to expect a shaky reply to this, and thus understand your concern. I went to Iceland which is also affected by these demarcations. I have looked at a number of sites for other countries and so far have failed to find anything similar to the UK system. Ireland it apopears just designates the immediate coastal waters.
At first sight not even the US, Australia, New Zealand and other countries affected by UK methods appear to have similar designations.
Many are of course being replaced by oil blocks, which leaves other areas with no designation at all. Maybe I need time to research this more - probably Marine specialists such as scientists and geologists can suggest designations for the huge % of the world which is water !
-
Here's what the forecast zones look like for the waters near me http://www.nws.noaa.gov/om/marine/zone/wrdoffmz.htm. This is the offshore forecast map, so the white strip near the coast represents the coastal forecast zones (out to 25 nm).
The zones are often named by features on their boundaries and tend not to have simple names (e.g. "Baltimore Canyon to the Hague Line south of 1000 fathoms"), although a few have simple names which match up with geographic features like "Georges Banks." Coastal zones tend to have follow the longer boundary oriented naming e.g. "Merrimack River to Cape Cod out to 25 nm" Except for the ones which match up with a geographical feature, I've never heard anyone use them for anything other than weather forecasting.
-
Thanks.
I think I did catch a similar page on US waters briefly, and thought that anything so complex will sink my idea. You mentioned Irish waters. No doubt those areas (which appear to have no coastal waters) around some Carribean neighbours could raise some problems too. Can we just find a way of adding the regions to the weather forecasts of each country that uses such designations and leave it at that !
-
I've added the meteorology domain since this is much more about weather than about boats.
I don't think it really needs to be that complex. The names, even if they are long, are just names. I think the important defining characteristics are:
- Name
- Description (optional - could just use the aliases for a longer version of the name)
- Geographic bounds
- Meteorological service that defined the area (since multiple services may have different names for the same area)
The type should have an included type of Location, which will take care of most of this automatically. If it turned out to be necessary later, you could add dates valid or some other way of indicating changing areas over time (ie . change the included type to Dated Location).
For the UK Met, the marine forecasts include not only the shipping forecasts, but also the high seas forecasts http://www.metoffice.gov.uk/weather/marine/guide/highseas/key.html and the inshore waters forecast http://www.metoffice.gov.uk/weather/marine/guide/inshore/key.html
-
Seems like a good idea to me. I'd simplify it even further and only have the property for Meteorological Service, and just use the various Location properties for everything else. (Bounds can presumably be handled by adjacency or geometry files, assuming anyone has access to the latter and feels like loading them.)
-
Take a look at Forecast Zone and let me know what you think.
-
Looks good to me.
-
Thanks
Seems to work a treat !
-
Thanks! I should mention that United Kingdom is not a meteorological service, however. The UK's meteorological service is Met Office.
-
I've added some aliases for the Met Office which should make it easier to find if you type UK Met or United Kingdom Meteorolog...
-
-
-
-
Has anyone any comments on my draft ship passenger and ship crew types?
-
I gave them a superficial review and added some comments on the various types.
-
-
-
There is no help for the 'displacement' property. Are the units intended to be a long ton (imperial ton), short ton (2,000 lbs), or a tonne/metric ton (1,000 kg)?
Could we get the description updated with the correct answer as well as conversion factors from the other two measures for people doing data entry?
-
Also the unit for "length at waterline" isn't specified. The documentations says meters, but the property expects just a floating point.
-
I've updated the "length at waterline" unit, since that didn't involve any actual thought.
-
Kirrily pointed out to me that the displacement property on the Ship type is in metric tons, so the property on ship class should be the same.
-
-
-
Please may we add the following properties?
* hull material (eg. iron, wood, fiberglass)
* method of propulsion (wind, coal, diesel, nuclear power)
-
I'd also like to see these properties. Additionally, I'd love some size properties such as length and tonnage.
-
Agreed, though those can be a bit fiddly. Wikipedia infoboxes should give us some tips though. I did something similar for my Tall Ship type: length at waterline, sparred length, beam, sail area, etc. Not all work for non-sailing ships of course.
-
Yeah, your Tall Ship type has some very useful properties, but the commons Ship type seems more appropriate to use for my scuba diving domain. Once I finish up with my Marine Creature and Ecoregion types, I'm going to develop schema for Dive Site. One type of dive site are shipwrecks. I've begun schema for a Shipwreck type, which I'll ultimately use with my Dive Site type. I would love to inherit ship length for free, as you could make some fun queries (show me all shipwreck dive sites in Florida with a hull length greater than 100 feet).
-
Oh yeah, I would LOVE to co-type some of the tall ships as shipwrecks!
-
hey, ive made a more involved shiprwreck schema to seperate boat, shi[pwreck event and the underwater shipwreck
http://disaster2.freebase.com/type/schema/base/disaster2/wrecked_ship
tons of empty properties, but i think goodidea
-
-
-
-
The current types seem heavily biased towards motorized military vessels. Should the current ship_class be renamed something more appropriate to its set of properties like powered_military_vessel_class then have types defined for sailing_civilian_vessel_class, etc or can we get a broader set of properties added to the current ship_class/ship_type?
On a related note, the few sail related things that I spotted seemed to be miscategorized. I'd consider Shallop, Schooner, Brig to be ship_types, not ship_classes.
When defining types, it'd be great if a description, however brief, could be included to give a hint as to what the designer's intentions are.
-
Yeah, it's a real problem. Boats are one of the early models and I believe a lot of the work was done by someone who's no longer here. It's something I'm very interested in, though, and my recent work on Rail has given me some ideas about how to do it for boats. The problem is that "ship class" is so broad as to be almost meaningless, and some classes are particularly problematic -- like Frigate, which could be the modern kind of warship, or could be the Napoleonic era one, and how do you handle that?
In any case, I'll take a stab at it today and let you know. Thanks for prodding me/us!
-
I'd argue that those are two different classes, both with the name "Frigate," but I'm not sure how well Freebase (or its users) handles that type of thing. "Cutter" is probably another example.
-
-
-
-
How do we put in the Owner of a ship?
-
Noticable oversight. It must have been forgotten when we were merging the various private boat domains/types.
My proposal would be to add a boat_owner property to ship, pointing to a CVT of with a time span of ownership and an owner property (with an expected type of boat_owner.) That way various types of owners can be co-typed as boat_owners (racing syndicates, individuals, governments) and the transfer of ownership can be traced. Does that make sense? (I will add it to sandbox so we can play with it there.)
Ironically modeling boat ownership was a topic I brought up at one of the first user group meetings.
J
-
Sounds good to me.
-
-
-
I've made some big improvements to the existing boat schema. These changes are detailed here:
http://www.freebase.com/discuss/view?id=%2Fboats%2Fboat
I will be replacing the old schema with the new ones (currently ship and associated types) this week.
-
-