[−][src]Struct reso_dd::Property
Fields
above_grade_finished_area: Option<f64>Finished area within the structure that is at or above the surface of the ground.
above_grade_finished_area_source: Option<AreaSource>The source of the measurements. This is a pick list of options showing the source of the measurement. i.e. Agent, Assessor, Estimate, etc.
above_grade_finished_area_units: Option<AreaUnits>A pick list of the unit of measurement for the area. i.e. Square Feet, Square Meters, Acres, etc.
access_code: Option<String>If the property is located behind an unmanned security gate such as in a Gated Community, what is the code to gain access through the secured gate.
accessibility_features: Option<Vec<AccessibilityFeatures>>A list or description of the accessibility features included in the sale/lease.
additional_parcels_description: Option<String>If additional parcels are included in the sale, a list of those parcel's IDs separated by commas. Do not include the first or primary parcel number, that should be located in the Parcel Number field.
additional_parcels_yn: Option<bool>Are there more than one parcel or lot included in the sale?
anchors_co_tenants: Option<String>The main or most notable tenants as well as other tenants of the shopping center or mall in which the commercial property is located.
appliances: Option<Vec<Appliances>>A list of the appliances that will be included in the sale/lease of the property.
architectural_style: Option<String>A list describing the style of the structure. For example, Victorian, Ranch, Craftsman, etc.
association_amenities: Option<Vec<AssociationAmenities>>Amenities provided by the Home Owners Association, Mobile Park or Complex. For example Pool, Clubhouse, etc.
association_fee: Option<f64>A fee paid by the homeowner to the Home Owners Association which is used for the upkeep of the common area, neighborhood or other association related benefits.
association_fee2: Option<f64>A fee paid by the homeowner to the second of two Home Owners Associations, which is used for the upkeep of the common area, neighborhood or other association related benefits.
association_fee2_frequency: Option<FeeFrequency>The frequency the association fee is paid. For example, Weekly, Monthly, Annually, Bi-Monthly, One Time, etc.
association_fee_frequency: Option<FeeFrequency>The frequency the association fee is paid. For example, Weekly, Monthly, Annually, Bi-Monthly, One Time, etc.
association_fee_includes: Option<Vec<AssociationFeeIncludes>>Services included with the association fee. For example Landscaping, Trash, Water, etc.
association_name: Option<String>The name of the Home Owners Association.
association_name2: Option<String>The name of the second of two Home Owners Association.
association_phone: Option<String>The phone number of the Home Owners Association. North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
association_phone2: Option<String>The phone number of the second of two Home Owners Association. North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
association_yn: Option<bool>Is there a Home Owners Association. A separate Y/N field is needed because not all associations have dues.
attached_garage_yn: Option<bool>A flag indicating that the garage attached to the dwelling.
availability_date: Option<NaiveDate>The date the property will be available for possession/occupation.
basement: Option<Vec<Basement>>A list of information and features about the basement. i.e. None/Slab, Finished, Partially Finished, Crawl Space, Dirt, Outside Entrance, Radon Mitigation
basement_yn: Option<bool>Does the property have a basement?
bathrooms_full: Option<f64>A room containing all 4 of the 4 elements constituting a bath, which are; Toilet, Sink, Bathtub or Shower Head. A Full Bath will typically contain four elements; Sink, Toilet, Tub and Shower Head (in tub or stall). However, some may considered a Sink, Toilet and Tub (without a shower) a Full Bath, others consider this to be a Three Quarter Bath. In the event that BathroomsThreeQuarter is not in use, this field may represent the sum of all Full and Three Quarter bathrooms.
bathrooms_half: Option<f64>A room containing 2 of the 4 elements constituting a bath, which are; Toilet, Sink, Bathtub or Shower Head. A Half Bath will typically contain a Sink and Toilet.
bathrooms_one_quarter: Option<f64>A room containing 1 of the 4 elements constituting a bath which are; Toilet, Sink, Bathtub or Shower Head. Examples are a vanity with a sink or a WC (Water Closet, which is a room with only a toilet).
bathrooms_partial: Option<f64>The number of partial bathrooms in the property being sold/leased. When used in combination with the BathroomsFull field, this replaces (or is the sum of) all Half and One Quarter bathrooms; and in the event BathroomsThreeQuarter is not used, BathroomsFull replaces (or is the sum of) all Full and Three Quarter baths. This field should not be used in combination with the BathroomsOneQuarter or the BathroomsHalf.
bathrooms_three_quarter: Option<f64>A room containing 3 of the 4 elements constituting a bath, which are; Toilet, Sink, Bathtub or Shower Head. A typical Three Quarter Bath will contain Sink, Toilet and Shower. Some may considered a Sink, Toilet and Tub (without a shower) a Three Quarter Bath, others consider this to be a Full Bath.
bathrooms_total_integer: Option<f64>The simple sum of the number of bathrooms. For example for a property with two Full Bathrooms and one Half Bathroom, the Bathrooms Total Integer will be 3. Expressing this example as 2.5, you will need to use a non-standard field name. Decimal based bathrooms are not recommended but possible via the Dictionary's extensibility.
bedrooms_possible: Option<f64>The sum of BedroomsTotal plus other rooms that may be used as a bedroom but are not defined as bedroom per local policy.
bedrooms_total: Option<f64>The total number of bedrooms in the dwelling.
below_grade_finished_area: Option<f64>Finished area within the structure that is below ground.
below_grade_finished_area_source: Option<AreaSource>The source of the measurements. This is a pick list of options showing the source of the measurement. i.e. Agent, Assessor, Estimate, etc.
below_grade_finished_area_units: Option<AreaUnits>A pick list of the unit of measurement for the area. i.e. Square Feet, Square Meters, Acres, etc.
body_type: Option<Vec<BodyType>>Type of mobile home.
builder_model: Option<String>The builders model name or number for the property.
builder_name: Option<String>Name of the builder of the property or builder's tract.
building_area_source: Option<AreaSource>The source of the measurements. This is a pick list of options showing the source of the measurement. i.e. Agent, Assessor, Estimate, etc.
building_area_total: Option<f64>Total area of the structure. Includes both finished and unfinished areas.
building_area_units: Option<AreaUnits>A pick list of the unit of measurement for the area. i.e. Square Feet, Square Meters, Acres, etc.
building_features: Option<String>Features or amenities of the building or business park.
building_name: Option<String>Name of the building or business park.
business_name: Option<String>Name of the business being sold.
business_type: Option<Vec<BusinessType>>The type of business being sold. Retail, Wholesale, Grocery, Food & Bev, etc.
buyer_agency_compensation: Option<String>The total commission to be paid for this sale, expressed as either a percentage or a constant currency amount.
buyer_agency_compensation_type: Option<CompensationType>A list of types to clarify the value entered in the BuyerAgencyCompensation field. For example $, % or some other clarification of the BuyerAgencyCompensation.
buyer_agent_aor: Option<String>The Buyer's Agent's Board or Association of REALTORS.
buyer_agent_designation: Option<Vec<BuyerAgentDesignation>>Designations and certifications acknowledging experience and expertise in various real estate sectors are awarded by NAR and each affiliated group upon completion of required courses.
buyer_agent_direct_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_email: Option<String>The email address of the Buyer's Agent.
buyer_agent_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_first_name: Option<String>The first name of the buyer's agent.
buyer_agent_full_name: Option<String>The full name of the buyer's agent. (First Middle Last)
buyer_agent_home_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Member resource's MemberKey.
buyer_agent_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Member resource's MemberKey. This is the numeric only key and used as an alternative to the BuyerAgentKey field.
buyer_agent_last_name: Option<String>The last name of the buyer's agent.
buyer_agent_middle_name: Option<String>The middle name of the buyer's agent.
buyer_agent_mls_id: Option<String>The local, well-known identifier. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
buyer_agent_mobile_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_name_prefix: Option<String>Prefix to the name (e.g. Dr. Mr. Ms. etc.)
buyer_agent_name_suffix: Option<String>Suffix to the BuyerAgentLastName (e.g. Esq., Jr., III etc.)
buyer_agent_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
buyer_agent_pager: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_preferred_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_preferred_phone_ext: Option<String>The extension of the given phone number (if applicable).
buyer_agent_state_license: Option<String>The license of the buyers agent. Separate multiple licenses with a comma and space.
buyer_agent_toll_free_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_url: Option<String>The website URI of the buyers agent.
buyer_agent_voice_mail: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_agent_voice_mail_ext: Option<String>The extension of the given phone number (if applicable).
buyer_financing: Option<Vec<BuyerFinancing>>A list of options that describe the type of financing used. This field is used when setting a listing to Closed. i.e. cash, FHA loan, etc.
buyer_office_aor: Option<String>The Buyer's Office's Board or Association of REALTORS.
buyer_office_email: Option<String>The email address of the Buyer's Office.
buyer_office_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_office_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey.
buyer_office_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey. This is the numeric only key and used as an alternative to the BuyerOfficeKey field.
buyer_office_mls_id: Option<String>The local, well-known identifier. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
buyer_office_name: Option<String>The legal name of the brokerage representing the buyer.
buyer_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
buyer_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
buyer_office_url: Option<String>The website URI for the buyers office.
buyer_team_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Teams resource's TeamKey.
buyer_team_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Teams resource's TeamKey. This is the numeric only key and used as an alternative to the BuyerTeamKey field.
buyer_team_name: Option<String>The name of the team representing the buyer.
cable_tv_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
cancellation_date: Option<NaiveDate>Date the listing contract between the seller and listing agent was cancelled. This is the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS.
cap_rate: Option<f64>Cap Rate is equivalent to the return on investment you would receive if you pay cash for a property. The ratio between the net operating income produced by an asset and its capital cost (the original price paid to buy the asset) or alternatively its current market value.
carport_spaces: Option<f64>The number of carport spaces included in the sale.
carport_yn: Option<bool>A flag indicating that the listing has a car port. This flag may be T/F, Y/N or other true, false or unknown indicator. As with all flags, the field may be null.
carrier_route: Option<String>The group of addresses to which the USPS assigns the same code to aid in mail delivery. For the USPS, these codes are 9 digits: 5 numbers for the ZIP Code, one letter for the carrier route type, and 3 numbers for the carrier route number.
city: Option<String>The city in listing address.
city_region: Option<String>A sub-section or area of a defined city. Examples would be SOHO in New York, NY, Ironbound in Newark, NJ or Inside the Beltway.
close_date: Option<NaiveDate>With for-sale listings, the date the purchase agreement was fulfilled. With lease listings, the date the requirements were fulfilled, such as contract and/or deposit. This is the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS.
close_price: Option<f64>The amount of money paid by the purchaser to the seller for the property under the agreement.
co_buyer_agent_aor: Option<String>The Co Buyer's Agent's Board or Association of REALTORS.
co_buyer_agent_designation: Option<Vec<CoBuyerAgentDesignation>>Designations and certifications acknowledging experience and expertise in various real estate sectors are awarded by NAR and each affiliated group upon completion of required courses.
co_buyer_agent_direct_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_email: Option<String>The email address of the Buyer's Co Agent.
co_buyer_agent_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_first_name: Option<String>The first name of the buyer's co-agent.
co_buyer_agent_full_name: Option<String>The full name of the buyer's co-agent. (First Middle Last)
co_buyer_agent_home_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Member resource's MemberKey.
co_buyer_agent_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Member resource's MemberKey. This is the numeric only key and used as an alternative to the CoBuyerAgentKey field.
co_buyer_agent_last_name: Option<String>The last name of the buyer's co-agent.
co_buyer_agent_middle_name: Option<String>The middle name of the buyer's co-agent.
co_buyer_agent_mls_id: Option<String>The local, well-known identifier. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
co_buyer_agent_mobile_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_name_prefix: Option<String>Prefix to the name (e.g. Dr. Mr. Ms. etc.)
co_buyer_agent_name_suffix: Option<String>Suffix to the CoBuyerAgentLastName (e.g. Esq., Jr., III etc.)
co_buyer_agent_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
co_buyer_agent_pager: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_preferred_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_preferred_phone_ext: Option<String>The extension of the given phone number (if applicable).
co_buyer_agent_state_license: Option<String>The license of the co-buyers agent. Separate multiple licenses with a comma and space.
co_buyer_agent_toll_free_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_url: Option<String>The website URI of the co-buyers agent.
co_buyer_agent_voice_mail: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_agent_voice_mail_ext: Option<String>The extension of the given phone number (if applicable).
co_buyer_office_aor: Option<String>The Co Buyer's Office's Board or Association of REALTORS.
co_buyer_office_email: Option<String>The email address of the Buyer's Co Office.
co_buyer_office_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_office_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey.
co_buyer_office_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey. This is the numeric only key and used as an alternative to the CoBuyerOfficeKey field.
co_buyer_office_mls_id: Option<String>The local, well-known identifier. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
co_buyer_office_name: Option<String>The legal name of the brokerage co-representing the buyer.
co_buyer_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_buyer_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
co_buyer_office_url: Option<String>The website URI for the co-buyers office.
co_list_agent_aor: Option<String>The Co Listing Agent's Board or Association of REALTORS.
co_list_agent_designation: Option<Vec<CoListAgentDesignation>>Designations and certifications acknowledging experience and expertise in various real estate sectors are awarded by NAR and each affiliated group upon completion of required courses.
co_list_agent_direct_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_email: Option<String>The email address of the Co Listing Agent.
co_list_agent_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_first_name: Option<String>The first name of the co-listing agent.
co_list_agent_full_name: Option<String>The full name of the co-listing agent. (First Middle Last)
co_list_agent_home_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Member resource's MemberKey.
co_list_agent_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Member resource's MemberKey. This is the numeric only key and used as an alternative to the CoListAgentKey field.
co_list_agent_last_name: Option<String>The last name of the co-listing agent.
co_list_agent_middle_name: Option<String>The middle name of the co-listing agent.
co_list_agent_mls_id: Option<String>The local, well-known identifier. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
co_list_agent_mobile_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_name_prefix: Option<String>Prefix to the name (e.g. Dr. Mr. Ms. etc.)
co_list_agent_name_suffix: Option<String>Suffix to the CoListAgentLastName (e.g. Esq., Jr., III etc.)
co_list_agent_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
co_list_agent_pager: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_preferred_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_preferred_phone_ext: Option<String>The extension of the given phone number (if applicable).
co_list_agent_state_license: Option<String>The license of the co-listing agent. Separate multiple licenses with a comma and space.
co_list_agent_toll_free_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_url: Option<String>The website URI of the co-listing agent.
co_list_agent_voice_mail: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_agent_voice_mail_ext: Option<String>The extension of the given phone number (if applicable).
co_list_office_aor: Option<String>The Co Listing Office's Board or Association of REALTORS.
co_list_office_email: Option<String>The email address of the Co Listing Office.
co_list_office_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_office_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey.
co_list_office_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey. This is the numeric only key and used as an alternative to the CoListOfficeKey field.
co_list_office_mls_id: Option<String>The local, well-known identifier. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
co_list_office_name: Option<String>The legal name of the brokerage co-representing the seller.
co_list_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
co_list_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
co_list_office_url: Option<String>The website URI for the co-listing office.
common_interest: Option<CommonInterest>Common Interest is a type of ownership in a property that is composed of an individual lot or unit and a share of the ownership or use of common areas. A Common Interest Development (CID) is usually governed by a recorded set of Covenants, Conditions & Restrictions (CC&Rs).
common_walls: Option<Vec<CommonWalls>>A multi select list with options like 1 Common Wall, 2 Common Walls, No Common Walls, No One Above, No One Below. Implementation should include rules preventing illogical selection combinations and to ensure consistency with the Property Attached Y/N field.
community_features: Option<Vec<CommunityFeatures>>A list of features related to, or available within, the community.
concessions: Option<Concessions>Are there concessions included in the sales agreement? Yes, No or Call Listing Agent
concessions_amount: Option<f64>The dollar amount of the concessions. If the concessions are made by the seller, some may subtract this value from the sales price as a means of calculating their own true price. If concessions are made by the buyer, some may add this amount to the sale price to create their own true price. Concessions made by both buyer and seller should be subtracted from each other providing a net value. Details of this calculation should be added to the Concessions Comments field.
concessions_comments: Option<String>Comments describing the concessions made by the buyer or the seller.
construction_materials: Option<Vec<ConstructionMaterials>>A list of the materials that were used in the construction of the property.
continent_region: Option<String>A sub-section or area of a continent. Examples would be Southern Europe or Scandinavia.
contingency: Option<String>A list of contingencies that must be satisfied in order to complete the transaction.
contingent_date: Option<NaiveDate>The date an offer was made with a contingency. The Listing remains On Market. This is the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS.
contract_status_change_date: Option<NaiveDate>The date of the listings contractual status change. This is not necessarily the time the agent made the change in the MLS system, but rather the date of the contractual change.
cooling: Option<Vec<Cooling>>A list describing the cooling or air conditioning features of the property.
cooling_yn: Option<bool>The property has cooling or Air Conditioning.
copyright_notice: Option<String>Notice of the legal rights of the owner of the information or data.
country: Option<Country>The country abbreviation in a postal address.
country_region: Option<String>A sub-section or area of a defined country. Examples would be Napa Valley in the US, or the Amalfi Coast in Italy.
county_or_parish: Option<String>The County, Parish or other regional authority
covered_spaces: Option<f64>The total number of garage and carport spaces.
crops_included_yn: Option<bool>Are crops included in the sale of the property.
cross_street: Option<String>Nearest cross streets to the property. This field is in addition to, and independent of, the driving directions field.
cultivated_area: Option<f64>Measurement or percentage of the property that has been cultivated.
cumulative_days_on_market: Option<f64>The number of days the property is on market, as defined by the MLS business rules.
current_financing: Option<Vec<CurrentFinancing>>A list of options that describe the type of financing that the seller currently has in place for the property being sold. i.e. cash, assumable, FHA loan, etc.
current_use: Option<Vec<CurrentUse>>A list of the type(s) of current use of the property. The current use of the property is an important factor in understanding the overall condition of the land and determining it's appropriateness for intended use.
doh1: Option<String>Department of Housing decal number for the mobile or manufactured home. For the first or only unit/section use DOH 1 over DOH 2 or 3.
doh2: Option<String>Department of Housing decal number for the mobile or manufactured home. For two units/sections use DOH 1 and 2 over DOH 3.
doh3: Option<String>Department of Housing decal number for the mobile or manufactured home. For two units/sections use DOH 1 and 2 over DOH 3.
days_on_market: Option<f64>The number of days the listing is on market, as defined by the MLS business rules.
development_status: Option<Vec<DevelopmentStatus>>A list of the Development Status of the property. The developmental status of land is an important factor in selling, purchasing and developing of land properties.
direction_faces: Option<DirectionFaces>The compass direction that the main entrance to the building faces. For example, North, South, East, West, South-West, etc. It may also be known as the building exposure.
directions: Option<String>Driving directions to the property.
disclaimer: Option<String>Text that serves as the negation or limitation of the rights under a warranty given by a seller to a buyer.
disclosures: Option<String>Legal or pertinent information that should be disclosed to potential buyer's agents.
distance_to_bus_comments: Option<String>A textual description of the distance to local bus stops.
distance_to_bus_numeric: Option<f64>Numeric distance from the property to the nearest bus stop.
distance_to_bus_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_electric_comments: Option<String>If the property does not currently have electrical utility, is service available and if so, what is the distance.
distance_to_electric_numeric: Option<f64>Numeric distance from the property to the electrical utility.
distance_to_electric_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_freeway_comments: Option<String>A textual description of the distance to freeways.
distance_to_freeway_numeric: Option<f64>Numeric distance from the property to the nearest freeway.
distance_to_freeway_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_gas_comments: Option<String>If the property does not currently have natural gas utility, is service available and if so, what is the distance.
distance_to_gas_numeric: Option<f64>Numeric distance from the property to the gas utility.
distance_to_gas_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_phone_service_comments: Option<String>If the property does not currently have phone service, is service available and if so, what is the distance.
distance_to_phone_service_numeric: Option<f64>Numeric distance from the property to the phone utility.
distance_to_phone_service_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feet, meters, yards, kilometers, miles, etc.
distance_to_placeof_worship_comments: Option<String>A textual description of the distance to local places of worship.
distance_to_placeof_worship_numeric: Option<f64>Numeric distance from the property to the nearest place of worship.
distance_to_placeof_worship_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_school_bus_comments: Option<String>Distance from the property to the nearest school bus pickup point.
distance_to_school_bus_numeric: Option<f64>Numeric distance from the property to the nearest school bus pickup point.
distance_to_school_bus_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_schools_comments: Option<String>A textual description of the distance to local schools.
distance_to_schools_numeric: Option<f64>Numeric distance from the property to the nearest school.
distance_to_schools_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_sewer_comments: Option<String>If the property does not currently have sewer or septic, is sewer service available and if so, what is the distance.
distance_to_sewer_numeric: Option<f64>Numeric distance from the property to the sewer utility.
distance_to_sewer_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_shopping_comments: Option<String>A description of the distance to primary shopping sources such as groceries, gasoline, clothing or department stores.
distance_to_shopping_numeric: Option<f64>Numeric distance from the property to the nearest shopping.
distance_to_shopping_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_street_comments: Option<String>If the property does not have a maintained road or street adjacent to the lot, what are the conditions of access and distance to a maintained road.
distance_to_street_numeric: Option<f64>Numeric distance from the property to the street.
distance_to_street_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
distance_to_water_comments: Option<String>If the property does not currently have water utility, is service available and if so, what is the distance.
distance_to_water_numeric: Option<f64>Numeric distance from the property to the water utility.
distance_to_water_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
documents_available: Option<String>A list of the Documents available for the property. Knowing what documents are available for the property is valuable information.
documents_change_timestamp: Option<DateTime<FixedOffset>>System generated timestamp of when the last update or change to the documents for this listing was made.
documents_count: Option<f64>The total number of documents or supplements included with the listings.
door_features: Option<Vec<DoorFeatures>>A list of features or description of the doors included in the sale/lease.
dual_variable_compensation_yn: Option<bool>A commission arrangement in which the seller agrees to pay a specified commission to the listing broker if the property is sold through the efforts of a cooperating broker, but the seller pays the Listing broker a different commission amount if the sale occurs if:1) there is no cooperating broker involved or 2) due to the efforts of the seller directly.
electric: Option<Vec<Electric>>A list of electric-service related features of the property (e.g. 110 Volt, 3 Phase, 220 Volt, RV Hookup). Note: the previous "Electric" field was renamed to DistanceToElectricComments
electric_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
electric_on_property_yn: Option<bool>Does the property currently have electrical utility available on the property.
elementary_school: Option<String>The name of the primary school having a catchment area that includes the associated property.
elementary_school_district: Option<String>The name of the elementary school district having a catchment area that includes the associated property.
elevation: Option<f64>The elevation of the property in relation to sea level. Use the Elevation Units field to communicate the unit of measurement. i.e. Feet or Meters.
elevation_units: Option<LinearUnits>A pick list of the unit of measurement used in the Elevation field. i.e. Feet, Meters.
entry_level: Option<f64>A numeric field that describes the level within the structure, SFR or a unit in a building, where the main entry to the dwelling is located. When a unit has one floor it is implicit that this is also the level of the unit itself.
entry_location: Option<String>A description of the main entry way to the property. i.e. Elevator, Ground Level w/ Steps, Ground Level w/o Steps, Mid Level, Top Level, etc.
exclusions: Option<String>Elements of the property that will not be included in the sale. i.e. Chandeliers will be removed prior to close.
existing_lease_type: Option<Vec<ExistingLeaseType>>Information about the status of the existing lease on the property. i.e. Net, NNN, NN, Gross, Absolute Net, Escalation Clause, Ground Lease, etc.
expiration_date: Option<NaiveDate>The date when the listing agreement will expire. This is the date entered by the agent reflecting when the change occurred, or will occur, contractually, not a timestamp of when the change was made in the MLS. The expiration date of listings, prior to their expiration, cancellation, sale or lease, is confidential information and should be restricted to the agent and their managers, partners or broker.
exterior_features: Option<Vec<ExteriorFeatures>>A list of features or description of the exterior of the property included in the sale/lease.
farm_credit_service_incl_yn: Option<bool>Specifies whether or not Farm Credit Service shares are included in the price of the property.
farm_land_area_source: Option<AreaSource>The source of the measurements. This may be a pick list of options showing the source of the measurement. i.e. Agent, Assessor, Estimate, etc. This field applies to all farm area fields (Cultivated, Pasture, Range, Wooded)
farm_land_area_units: Option<AreaUnits>A pick list of the unit of measurement for the area. i.e. Square Feet, Square Meters, Acres, etc. This field applies to all farm area fields (Cultivated, Pasture, Range, Wooded)
fencing: Option<Vec<Fencing>>A list of types of fencing found at the property being sold.
financial_data_source: Option<Vec<FinancialDataSource>>The source of the Rental information. For example Accountant, Owner, etc.
fireplace_features: Option<Vec<FireplaceFeatures>>A list of features or description of the fireplace(s) included in the sale/lease.
fireplace_yn: Option<bool>Does the property include a fireplace.
fireplaces_total: Option<f64>The total number of fireplaces included in the property.
flooring: Option<Vec<Flooring>>A list of the type(s) of flooring found within the property.
foundation_area: Option<f64>The area or dimensions of the footprint of the structure on the lot.
foundation_details: Option<Vec<FoundationDetails>>A list of the type(s) of foundation on which the property sits.
frontage_length: Option<String>Textual description of the length of the frontages selected in the Frontage Type field.
frontage_type: Option<Vec<FrontageType>>Pick list of types of frontage. i.e. Oceanfront, Lakefront, Golf course, etc. Information about roads or road frontage should be located in the Road Frontage Type and Road Surface Type fields.
fuel_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
furnished: Option<Furnished>The property being leased is furnished, unfurnished or partially furnished.
furniture_replacement_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
garage_spaces: Option<f64>The number of spaces in the garage(s).
garage_yn: Option<bool>A flag indicating that the listing has a garage. This flag may be T/F, Y/N or other true, false or unknown indicator. As with all flags, the field may be null.
gardener_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
grazing_permits_blm_yn: Option<bool>Specifies whether or not the property owner has grazing permits from the Bureau of Land Management.
grazing_permits_forest_service_yn: Option<bool>Specifies whether or not the property owner has grazing permits from the Forestry Service.
grazing_permits_private_yn: Option<bool>Specifies whether or not the property owner has private grazing permits.
green_building_verification: Option<String>A collection of verifications or certifications awarded to a new or pre-existing residential or commercial structure. For example: LEED, Energy Star, ICC-700. The collection includes information about the type, year, rating and other details about the awarded performance verification.
green_building_verification_type: Option<Vec<GreenBuildingVerificationType>>The name of the verification or certification awarded to a new or pre-existing residential or commercial structure. For example: LEED, Energy Star, ICC-700. In cases where more than one certification have been awarded, leverage multiple iterations of the green verification fields via the repeating element method.
green_energy_efficient: Option<Vec<GreenEnergyEfficient>>Pick list of general green attributes such as energy efficient doors, or appliances without naming specific elements with ratings that may wane over time.
green_energy_generation: Option<Vec<GreenEnergyGeneration>>Methods of generating power that are included in the sale or lease.
green_indoor_air_quality: Option<Vec<GreenIndoorAirQuality>>Pick list of indoor air quality measures without naming specific elements with ratings that may wane over time.
green_location: Option<String>Pick list describing efficiencies involved with the property's location such as walkability or transportation proximity without naming specific elements with ratings that may wane over time.
green_sustainability: Option<Vec<GreenSustainability>>Pick list of sustainable elements used in the construction of the structure without naming specific elements with ratings that may wane over time.
green_water_conservation: Option<Vec<GreenWaterConservation>>Pick list of general water conserving attributes of the property such as landscaping or reclamation without naming specific elements with ratings that may wane over time.
gross_income: Option<f64>The actual current income from rent and all other revenue generating sources.
gross_scheduled_income: Option<f64>The maximum amount of annual rent collected if the property were 100% occupied all year and all tenants paid their rent.
habitable_residence_yn: Option<bool>Does the property include a structure that can be lived in.
heating: Option<Vec<Heating>>A list describing the heating features of the property.
heating_yn: Option<bool>The property has heating.
high_school: Option<String>The name of the high school having a catchment area that includes the associated property.
high_school_district: Option<String>The name of the high school district having a catchment area that includes the associated property. When only one school district is used, this field should be used over the Junior or Elementary Districts.
home_warranty_yn: Option<bool>Is a home warranty included in the sale of the property? Single select.
horse_amenities: Option<Vec<HorseAmenities>>A list of horse amenities on the lot or in the community.
horse_yn: Option<bool>The Property is allowed to raise horses.
hours_days_of_operation: Option<Vec<HoursDaysOfOperation>>A simplified enumerated list of the days and hours of operation of the business being sold. i.e. Open 24 Hours or Open 7 Days. For more detailed descriptions use the HoursDaysofOperationDescription field.
hours_days_of_operation_description: Option<String>A detailed description of the hours and days the business being sold is open for business. For a specific list of simplified times the business is open, use the HoursDaysOfOperation Field (enumerated).
inclusions: Option<String>Portable elements of the property that will be included in the sale.
income_includes: Option<Vec<IncomeIncludes>>A list of income sources included in the GrossScheduledIncome and GrossIncome. i.e. Laundry, Parking, Recreation, Storage, etc.
insurance_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
interior_features: Option<Vec<InteriorOrRoomFeatures>>A list of features or description of the interior of the property included in the sale/lease.
internet_address_display_yn: Option<bool>A yes/no field that states the seller has allowed the listing address to be displayed on Internet sites.
internet_automated_valuation_display_yn: Option<bool>A yes/no field that states the seller allows the listing can be displayed with an AVM on Internet sites.
internet_consumer_comment_yn: Option<bool>A yes/no field that states the seller allows a comment or blog system to be attached to the listing on Internet sites.
internet_entire_listing_display_yn: Option<bool>A yes/no field that states the seller has allowed the listing to be displayed on Internet sites.
irrigation_source: Option<String>The source which the property receives its water for irrigation.
irrigation_water_rights_acres: Option<f64>The number of acres allowed under the property's water rights.
irrigation_water_rights_yn: Option<bool>Does the property include water rights for irrigation? A Boolean or Yes / No field.
labor_information: Option<Vec<LaborInformation>>Information about labor laws that are applicable to the business being sold. i.e. Union, Non-Union, Employee License Required.
land_lease_amount: Option<f64>When the land is not included in the sale, but is leased, the amount of the lease. This is the Space Rent for Mobile homes in a Park.
land_lease_amount_frequency: Option<FeeFrequency>When the land is not included in the sale, but is leased, the frequency the Land Lease Fee is paid.
land_lease_expiration_date: Option<NaiveDate>When the land is not included in the sale, but is leased, the expiration date of the Land Lease.
land_lease_yn: Option<bool>The land is not included in the sale and a lease exists.
latitude: Option<f64>The geographic latitude of some reference point on the property, specified in degrees and decimal parts. Positive numbers must not include the plus symbol.
laundry_features: Option<Vec<LaundryFeatures>>Add this pick list of features and locations where the laundry is located in the property being sold. i.e. Gas Dryer Hookup, In Kitchen, In Garage, etc.
leasable_area: Option<f64>The area that may be leased within the commercial property.
leasable_area_units: Option<AreaUnits>A pick list of the unit of measurement for the area. i.e. Square Feet, Square Meters, Acres, etc.
lease_amount: Option<f64>The amount of any lease the business pays for it's current location.
lease_amount_frequency: Option<FeeFrequency>The frequency of the LeaseAmount is paid. Monthly, weekly, annual, etc.
lease_assignable_yn: Option<bool>Can the lease at the business' current location be assigned to another party.
lease_considered_yn: Option<bool>Will the seller consider leasing the property instead of selling? Single select.
lease_expiration: Option<NaiveDate>The expiration date of the lease for the business' current location.
lease_renewal_compensation: Option<Vec<LeaseRenewalCompensation>>A list of compensations other than the original Selling Office Compensation. i.e. Compensation Paid on Renewal, Compensation Paid on Tennant Purchase, No Renewal Commission, Call Listing Office, etc.
lease_renewal_option_yn: Option<bool>Is there an option to renew the lease at the business' current location.
lease_term: Option<LeaseTerm>A pick list of lengths that represent the length of the lease. i.e. Weekly, Month to Month, 6 Month Lease, 12 Month Lease, 24 Month Lease.
levels: Option<Vec<Levels>>The number of levels in the property being sold. For example, One Level, Two Levels, Three or More Levels, Multi/Split, Loft. A discreet horizontal plane of interior living space (excluding basements).
license1: Option<String>License number of the mobile or manufactured home. Also known as the Department of Housing label/insignia number. For the first or only unit/section use License 1 over License 2 or 3.
license2: Option<String>License number of the mobile or manufactured home. Also known as the Department of Housing label/insignia number. For two units/sections use License 1 and 2 over License 3.
license3: Option<String>License number of the mobile or manufactured home. Also known as the Department of Housing label/insignia number. For two units/sections use License 1 and 2 over License 3.
licenses_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
list_aor: Option<String>The responsible Board or Association of REALTORS for this listing.
list_agent_aor: Option<String>The Listing Agent's Board or Association of REALTORS.
list_agent_designation: Option<Vec<ListAgentDesignation>>Designations and certifications acknowledging experience and expertise in various real estate sectors are awarded by NAR and each affiliated group upon completion of required courses.
list_agent_direct_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_email: Option<String>The email address of the Listing Agent.
list_agent_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_first_name: Option<String>The first name of the listing agent.
list_agent_full_name: Option<String>The full name of the listing agent. (First Middle Last)
list_agent_home_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the ListAgentKey is the system unique identifier from the system that the record was retrieved. This may be identical to the related xxxId. This is a foreign key relating to the Member resource's MemberKey.
list_agent_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the ListAgentKey is the system unique identifier from the system that the record was retrieved. This may be identical to the related xxxId. This is a foreign key relating to the Member resource's MemberKey. This is the numeric only key and used as an alternative to the ListAgentKey field.
list_agent_last_name: Option<String>The last name of the listing agent.
list_agent_middle_name: Option<String>The middle name of the listing agent.
list_agent_mls_id: Option<String>The local, well-known identifier for the member. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
list_agent_mobile_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_name_prefix: Option<String>Prefix to the name (e.g. Dr. Mr. Ms. etc.)
list_agent_name_suffix: Option<String>Suffix to the ListAgentLastName (e.g. Esq., Jr., III etc.)
list_agent_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
list_agent_pager: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_preferred_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_preferred_phone_ext: Option<String>The extension of the given phone number (if applicable).
list_agent_state_license: Option<String>The license of the listing agent. Separate multiple licenses with a comma and space.
list_agent_toll_free_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_url: Option<String>The website URI of the listing agent.
list_agent_voice_mail: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_agent_voice_mail_ext: Option<String>The extension of the given phone number (if applicable).
list_office_aor: Option<String>The Listing Office's Board or Association of REALTORS.
list_office_email: Option<String>The email address of the Listing Office.
list_office_fax: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_office_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey.
list_office_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Office resource's OfficeKey. This is the numeric only key and used as an alternative to the ListOfficeKey field.
list_office_mls_id: Option<String>The local, well-known identifier. This value may not be unique, specifically in the case of aggregation systems, this value should be the identifier from the original system.
list_office_name: Option<String>The legal name of the brokerage representing the seller.
list_office_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
list_office_phone_ext: Option<String>The extension of the given phone number (if applicable).
list_office_url: Option<String>The website URI for the listing office.
list_price: Option<f64>The current price of the property as determined by the seller and the seller's broker. For auctions this is the minimum or reserve price.
list_price_low: Option<f64>The lower price used for Value Range Pricing. The List Price must be greater than or equal to the ListPriceLow.
list_team_key: Option<String>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Teams resource's TeamKey.
list_team_key_numeric: Option<f64>A system unique identifier. Specifically, in aggregation systems, the Key is the system unique identifier from the system that the record was just retrieved. This may be identical to the related xxxId identifier, but the key is guaranteed unique for this record set. This is a foreign key relating to the Teams resource's TeamKey. This is the numeric only key and used as an alternative to the ListTeamKey field.
list_team_name: Option<String>The name of the team representing the seller.
listing_agreement: Option<ListingAgreement>The nature of the agreement between the seller and the listing agent. Examples are Exclusive Agency, Open Listing, etc.
listing_contract_date: Option<NaiveDate>The effective date of the agreement between the seller and the seller's broker. This is the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS.
listing_id: Option<String>The well known identifier for the listing. The value may be identical to that of the Listing Key, but the Listing ID is intended to be the value used by a human to retrieve the information about a specific listing. In a multiple originating system or a merged system, this value may not be unique and may require the use of the provider system to create a synthetic unique value.
listing_key: Option<String>A unique identifier for this record from the immediate source. This is a string that can include URI or other forms. Alternatively use the ListingKeyNumeric for a numeric only key field. This is the local key of the system. When records are received from other systems, a local key is commonly applied. If conveying the original keys from the source or originating systems, see SourceSystemKey and OriginatingSystemKey.
listing_key_numeric: Option<f64>A unique identifier for this record from the immediate source. This is the numeric only key and used as an alternative to the ListingKey fields. This is the local key of the system. When records are received from other systems, a local key is commonly applied. If conveying the original keys from the source or originating systems, see SourceSystemKey and OriginatingSystemKey.
listing_service: Option<ListingService>Defines the type or level of service the listing member will be providing to the selling home owner. This will typically be a single selection. Examples include Full Service, Limited Service or Entry Only.
listing_terms: Option<Vec<ListingTerms>>Terms of the listing such as Lien Release, Subject to Court Approval or Owner Will Carry. Also may include options that describe the financing terms that are acceptable to the seller, i.e. cash, assumable, FHA loan, etc.
living_area: Option<f64>The total livable area within the structure.
living_area_source: Option<AreaSource>The source of the measurements. This is a pick list of options showing the source of the measurement. i.e. Agent, Assessor, Estimate, etc.
living_area_units: Option<AreaUnits>A pick list of the unit of measurement for the area. i.e. Square Feet, Square Meters, Acres, etc.
lock_box_location: Option<String>A field describing the location of the lock box.
lock_box_serial_number: Option<String>The serial number of the lockbox placed on the property.
lock_box_type: Option<Vec<LockBoxType>>A field describing the type of lock box.
longitude: Option<f64>The geographic longitude of some reference point on the property, specified in degrees and decimal parts. Positive numbers must not include the plus symbol.
lot_dimensions_source: Option<LotDimensionsSource>The source of the measurements. This may be a pick list of options showing the source of the measurement. i.e. Agent, Assessor, Estimate, etc.
lot_features: Option<Vec<LotFeatures>>A list of features or description of the lot included in the sale/lease.
lot_size_acres: Option<f64>The total Acres of the lot. This field is related to the Lot Size Area and Lot Size Units and must be in sync with the values represented in those fields. Lot Size Source also applies to this field when used.
lot_size_area: Option<f64>The total area of the lot. See Lot Size Units for the units of measurement (Square Feet, Square Meters, Acres, etc.).
lot_size_dimensions: Option<String>The dimensions of the lot minimally represented as length and width (i.e. 250 x 180) or a measurement of all sides of the polygon representing the property lines of the property. i.e. 30 x 50 x 120 x 60 x 22.
lot_size_source: Option<LotSizeSource>The source of the measurements. This may be a pick list of options showing the source of the measurement. i.e. Agent, Assessor, Estimate, etc.
lot_size_square_feet: Option<f64>The total square footage of the lot. This field is related to the Lot Size Area and Lot Size Units and must be in sync with the values represented in those fields. Lot Size Source also applies to this field when used.
lot_size_units: Option<LotSizeUnits>A pick list of the unit of measurement for the area. i.e. Square Feet, Square Meters, Acres, etc.
mlsarea_major: Option<String>The major marketing area name, as defined by the MLS or other non-governmental organization. If there is only one MLS Area in use, it must be the MLSAreaMajor.
mlsarea_minor: Option<String>The minor/sub marketing area name, as defined by the MLS or other non-governmental organization. If there is only one MLS Area in use, it must be the MLSAreaMajor.
main_level_bathrooms: Option<f64>The number of bathrooms located on the main or entry level of the property.
main_level_bedrooms: Option<f64>The number of bedrooms located on the main or entry level of the property.
maintenance_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
major_change_timestamp: Option<DateTime<FixedOffset>>Timestamp of the last major change on the listing (see also MajorChangeType).
major_change_type: Option<ChangeType>Description of the last major change on the listing, i.e. “price reduction”, “back on market”, etc. May be used to display on a summary view of listing results to quickly identify listings that have had major changes recently.
make: Option<String>Make of the mobile or manufactured home.
manager_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations. This is for an individual manager. Use ProfessionalManagementExpense for a management company.
map_coordinate: Option<String>A map coordinate for the property, as determined by local custom. This is not necessarily the same as the geographic coordinate but may depend on the coordinate system used by whatever mapping service is customarily used by the listing service.
map_coordinate_source: Option<String>Name of the map or map book publisher.
map_url: Option<String>URI to a map of the property.
middle_or_junior_school: Option<String>The name of the junior or middle school having a catchment area that includes the associated property.
middle_or_junior_school_district: Option<String>The name of the junior or middle school district having a catchment area that includes the associated property.
mls_status: Option<String>Local or regional status that are well known by business users. Each MlsStatus must map to a single StandardStatus. Multiple MlsStatus may map to a single StandardStatus.
mobile_dim_units: Option<LinearUnits>A pick list of the unit linear measurement. i.e. feed, meters, yards, kilometers, miles, etc.
mobile_home_remains_yn: Option<bool>Is the mobile home to remain and be included in the sale of the property.
mobile_length: Option<f64>Length of the mobile/manufactured home.
mobile_width: Option<f64>Width of the mobile/manufactured home.
model: Option<String>Model of the mobile or manufactured home.
modification_timestamp: Option<DateTime<FixedOffset>>The transactional timestamp automatically recorded by the MLS system representing the date/time the listing was last modified.
net_operating_income: Option<f64>Net operating income is the revenue from a property after operating expenses have been deducted, but before deducting income taxes and financing expenses (interest and Principal Payments). For example, Gross Income - Operating Expenses = Net Operating Income (NOI).
new_construction_yn: Option<bool>Is the property newly constructed and has not been previously occupied?
new_taxes_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
number_of_buildings: Option<f64>Total number of separate buildings included in the income property.
number_of_full_time_employees: Option<f64>The current number of individuals employed by the business on a full-time basis.
number_of_lots: Option<f64>Total number of lots on the property or included in the sale. Land properties are often sold with multiple lots. It is important to be able to describe how many lots are in the property and not in all cases do lots have separate Parcel IDs.
number_of_pads: Option<f64>The number of pads or spaces in the mobile home park.
number_of_part_time_employees: Option<f64>The current number of individuals employed by the business on a part-time basis.
number_of_separate_electric_meters: Option<f64>Total number of separate meters on the property.
number_of_separate_gas_meters: Option<f64>Total number of separate meters on the property.
number_of_separate_water_meters: Option<f64>Total number of separate meters on the property.
number_of_units_in_community: Option<f64>The total number of units in the building, complex or community. This is not the number of units being sold, but rather the size of the community in which the dwelling being sold is located.
number_of_units_leased: Option<f64>Total number of units currently under a lease agreement.
number_of_units_mo_mo: Option<f64>The total number of units leasable month to month.
number_of_units_total: Option<f64>Total number of units included in the income property, occupied or unoccupied.
number_of_units_vacant: Option<f64>The number of units currently vacant.
occupant_name: Option<String>Name of the current occupant, if any, of the property being sold.
occupant_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
occupant_type: Option<OccupantType>A field that describes the type of occupant, i.e. Owner, Tenant, Vacant.
off_market_date: Option<NaiveDate>The date the listing was taken off market. Where possible, this date is reflective of the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS.
off_market_timestamp: Option<DateTime<FixedOffset>>The transactional timestamp automatically recorded by the MLS system representing the most recent date/time the listing's status was set to and off market status (not Active or Backup)
on_market_date: Option<NaiveDate>The date the listing was placed on market. Where possible, this date is reflective of the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS.
on_market_timestamp: Option<DateTime<FixedOffset>>The transactional timestamp automatically recorded by the MLS system representing the most recent date/time the listing's status was set to Active or Backup. This also includes initial input of the listing to Active/Backup or from a draft or approval status to Active/Backup.
open_parking_spaces: Option<f64>The number of open or uncovered parking spaces included in the sale.
open_parking_yn: Option<bool>A flag indicating that any parking spaces associated with the property are not covered by a roof.
operating_expense: Option<f64>The costs associated with the operation and maintenance of an income-producing property.
operating_expense_includes: Option<Vec<OperatingExpenseIncludes>>When individual expense fields are not used and only a total is entered, this lists the expenses that are included in the OperatingExpense field.
original_entry_timestamp: Option<DateTime<FixedOffset>>The transactional timestamp automatically recorded by the MLS system representing the date/time the listing was entered and made visible to members of the MLS.
original_list_price: Option<f64>The original price of the property on the initial agreement between the seller and the seller's broker.
originating_system_id: Option<String>The RESO OUID's OrganizationUniqueId of the Originating record provider. The Originating system is the system with authoritative control over the record. For example; the name of the MLS where the listing was input. In cases where the Originating system was not where the record originated (the authoritative system), see the Originating System fields.
originating_system_key: Option<String>The system key, a unique record identifier, from the Originating system. The Originating system is the system with authoritative control over the record. For example, the Multiple Listing Service where the listing was input. There may be cases where the Source System (how you received the record) is not the Originating System. See Source System Key for more information.
originating_system_name: Option<String>The name of the Originating record provider. Most commonly the name of the MLS. The place where the listing is originally input by the member. The legal name of the company.
other_equipment: Option<Vec<OtherEquipment>>A list of other equipment that will be included in the sale of the property.
other_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
other_parking: Option<String>Other types of parking available to, or part of, the property.
other_structures: Option<Vec<OtherStructures>>A list of structures other than the main dwelling. For example, Guest House, Barn, Shed, etc.
owner_name: Option<String>Name of the owner of the property being sold.
owner_pays: Option<Vec<OwnerPays>>A list of expenses for the property paid for by the owner as opposed to the tenant (e.g. Water, Trash, Electric).
owner_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
ownership: Option<String>A text description of the manner in which title to a property is held. Trust, Corporation, Joint Tennant, Individual.
ownership_type: Option<OwnershipType>Current type of ownership of the business being sold. i.e. Corporation, LLC, Sole P, Partnership, etc.,
parcel_number: Option<String>A number used to uniquely identify a parcel or lot. This number is typically issued by the county or county assessor. The AP number format varies from county to county. It is recommended that all Parcel Numbers be transmitted without dashes or hyphens.
park_manager_name: Option<String>Name of the manager of the mobile home park.
park_manager_phone: Option<String>North American 10 digit phone numbers should be in the format of ###-###-#### (separated by hyphens). Other conventions should use the common local standard. International numbers should be preceded by a plus symbol.
park_name: Option<String>Name of the mobile home park or corporate/commercial park.
parking_features: Option<Vec<ParkingFeatures>>A list of features or description of the parking included in the sale/lease.
parking_total: Option<f64>The total number of parking spaces included in the sale.
pasture_area: Option<f64>Measurement or percentage of the property that has been allocated as pasture or grazing area.
patio_and_porch_features: Option<Vec<PatioAndPorchFeatures>>A list of features or description of the patio or porch included in the sale/lease.
pending_timestamp: Option<DateTime<FixedOffset>>The transactional timestamp automatically recorded by the MLS system representing the most recent date/time the listing's status was set to Pending.
pest_control_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
pets_allowed: Option<Vec<PetsAllowed>>Are pets allowed at the property being leased? A list of yes, no and more detailed restrictions/allowances.
photos_change_timestamp: Option<DateTime<FixedOffset>>System generated timestamp of when the last update or change to the photos for this listing was made.
photos_count: Option<f64>The total number of pictures or photos included with the listing.
pool_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
pool_features: Option<Vec<PoolFeatures>>A list of features or description of the pool included in the sale/lease.
pool_private_yn: Option<bool>The property has a privately owned pool that is included in the sale/lease.
possession: Option<Vec<Possession>>A list defining when possession will occur. i.e. COE, COE+1, etc.
possible_use: Option<Vec<PossibleUse>>A list of the type(s) of possible or best uses of the property. Probable use gives a good indication of what the best use or potential use of the property could be. i.e. Primary, Vacation, Investment, Rental, Retirement
postal_city: Option<String>The official city per the USPS. May be different from the "City".
postal_code: Option<String>The postal code portion of a street or mailing address.
postal_code_plus4: Option<String>The postal code +4 portion of a street or mailing address.
power_production: Option<String>A collection of the types of power production system(s) available on the property. The collection includes the type of system and other details about the power produced and age of the system.
power_production_type: Option<Vec<PowerProductionType>>This field is a list of the types of power production system(s) available on the property. The key characteristics of the system are expected to appear as the "[type]" in the related power production fields in a flattened implementation (RETS 1.x only) of the power production fields. A relational implementation of power production must omit the type from the field name and use PowerProductionType to create a vertical representation of the various types of power production available. **Note that PV Solar is the only type of power production currently justified in multiple markets and thus shown. Up and coming renewables that could be added in the future depending on uptake: Wind, Geothermal, Thin Film Solar.
previous_list_price: Option<f64>The most recent previous ListPrice of the listing.
price_change_timestamp: Option<DateTime<FixedOffset>>The transactional timestamp automatically recorded by the MLS system representing the date/time the listing's price was last changed.
private_office_remarks: Option<String>A remarks field that is only visible to members of the same offices as the listing agent.
private_remarks: Option<String>Remarks that may contain security or proprietary information and should be restricted from public view.
professional_management_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations. This is for a management company. Use ManagerExpense for a individual manager.
property_attached_yn: Option<bool>A flag indicating that the primary structure is attached to another structure that is not included in the sale. i.e. one unit of a duplex. This flag may be T/F, Y/N or a list of attached or detached. As with all flags, the field may be null. In some systems this information may be part of the Property Sub Type.
property_condition: Option<Vec<PropertyCondition>>A list describing the condition of the property and any structures included in the sale.
property_sub_type: Option<PropertySubType>A list of types of residential and residential lease properties, i.e. SFR, Condo, etc. Or a list of Sub Types for Mobile, such as Expando, Manufactured, Modular, etc.
property_type: Option<PropertyType>A list of types of properties such as Residential, Lease, Income, Land, Mobile, Commercial Sale, etc...
public_remarks: Option<String>Text remarks that may be displayed to the public. In an MLS, it is the field where information is entered for the public. This information is intended to be visible on-line. This is typically information that describes the selling points of the building and/or land for sale. Local conditions and rules will determine what such content can contain. Generally, the following information is excluded: any information pertaining to entry to the property, the seller and/or tenant, listing member contact information. In other systems, these remarks will be determined by local business rules.
public_survey_range: Option<String>This field specifically identifies the Range identified by the Public Land Survey System (PLSS).
public_survey_section: Option<String>This field specifically identifies the Section identified by the Public Land Survey System (PLSS).
public_survey_township: Option<String>This field specifically identifies the Township identified by the Public Land Survey System (PLSS).
purchase_contract_date: Option<NaiveDate>With for-sale listings, the date an offer was accepted and the listing was no longer on market. This is the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS. With lease listings this may represent a meeting of the minds to lease, but some contractual requirements are yet to be fulfilled, such as contract signing or receipt of the deposit.
rvparking_dimensions: Option<String>The dimensions of the RV parking area minimally represented as length and width (i.e. 25 x 18) or a measurement of all sides of the polygon representing the usable RV parking space. i.e. 33 x 15 x 12 x 60.
range_area: Option<f64>Measurement or percentage of the property that has been allocated as range.
rent_control_yn: Option<bool>Is the property in a rent control area?
rent_includes: Option<Vec<RentIncludes>>A list of services or items that the tenant is not responsible to pay.
road_frontage_type: Option<Vec<RoadFrontageType>>Pick list of types of Road frontage. i.e. Freeway frontage, No Road Frontage, etc. The road frontage of the property is an important factor in determining value of the property and it’s appropriateness for intended use.
road_responsibility: Option<Vec<RoadResponsibility>>The person or entity responsible for road maintenance (e.g., City, County, Private).
road_surface_type: Option<Vec<RoadSurfaceType>>Pick list of types of surface of the Road to access the property. The surface of the road(s) for access to the property is an important factor in determining value of the property and it’s appropriateness for intended use.
roof: Option<Vec<Roof>>A list describing the type or style of roof. For example Spanish Tile, Composite, Shake, etc.
room_type: Option<Vec<RoomType>>This field is a list of the types used in the rooms repeating elements. The Type is a list of possible room types. i.e. Bedroom, Bathroom, Living Room, Workshop, etc. Each selected are expected to appear as the "[type]" in the related rooms fields in a flattened implementation (RETS 1.x only) of the room fields. A relational implementation of rooms must omit the type from the field name and use RoomType to create a vertical representation of the various rooms. **Note that Garage or Basement should not be added as a room type and are represented by the ParkingFeatures and Basement fields respectively.
rooms: Option<String>A collection of types of rooms and details/features about the given room.
rooms_total: Option<f64>The number of rooms in the dwelling.
seating_capacity: Option<f64>The seating capacity of the business being sold.
security_features: Option<Vec<SecurityFeatures>>A list describing the security features included in the sale/lease.
senior_community_yn: Option<bool>The community is a senior community.
serial_u: Option<String>Serial number of the mobile or manufactured home. For the first or only unit/section use Serial U over Serial X or Serial XX.
serial_x: Option<String>Serial number of the mobile or manufactured home. For two units/sections, Serial U should be used first, Serial X second over or Serial XX.
serial_xx: Option<String>Serial number of the mobile or manufactured home. For two units/sections, Serial U should be used first, Serial X second over or Serial XX.
sewer: Option<Vec<Sewer>>A list describing the sewer or septic features of the property.
showing_advance_notice: Option<f64>The hours of advance notice required to schedule a showing.
showing_attended_yn: Option<bool>Does this home require an attended showing? i.e. Yes = licensed agent representing the seller must be present during showing.
showing_contact_name: Option<String>The name of the contact for the showing of the listed property.
showing_contact_phone: Option<String>A telephone number that should be called to arrange showing the property.
showing_contact_phone_ext: Option<String>The extension of the given phone number (if applicable).
showing_contact_type: Option<Vec<ShowingContactType>>The type of contact for the showing. i.e. Agent, Broker, Seller.
showing_days: Option<String>The days of the week that the property is available for showing. i.e. Sundays, Mondays, Tuesdays, Wednesdays, Thursdays, Fridays, Saturdays
showing_end_time: Option<DateTime<FixedOffset>>From the days selected in the ShowingDays field, the end time that the property is available for showing.
showing_instructions: Option<String>Remarks that detail the seller's instructions for showing the subject property. Showing instructions may include: contact information, showing times, notice required or other information. These remarks are privileged and are not for public viewing.
showing_requirements: Option<Vec<ShowingRequirements>>A pick list of types of notice required to see the home. i.e. Appointment Required, Courtesy Call Only, Go Direct, etc.
showing_start_time: Option<DateTime<FixedOffset>>From the days selected in the ShowingDays field, the start time that the property is available for showing.
sign_on_property_yn: Option<bool>Is there a sign on the property.
skirt: Option<Vec<Skirt>>A list of types of mobile home skirting.
source_system_id: Option<String>The RESO OUID's OrganizationUniqueId of the Source record provider. The source system is the system from which the record was directly received. In cases where the source system was not where the record originated (the authoritative system), see the Originating System fields.
source_system_key: Option<String>The system key, a unique record identifier, from the Source System. The Source System is the system from which the record was directly received. In cases where the Source System was not where the record originated (the authoritative system), see the Originating System fields.
source_system_name: Option<String>The name of the immediate record provider. The system from which the record was directly received. The legal name of the company.
spa_features: Option<Vec<SpaFeatures>>A list of features or description of the spa included in the sale/lease.
spa_yn: Option<bool>The property has a spa.
special_licenses: Option<Vec<SpecialLicenses>>Special licenses required/used by the business being sold. i.e. Beer/Wine, Class H, Professional, Gambling, None.
special_listing_conditions: Option<Vec<SpecialListingConditions>>A list of options that describe the type of sale. i.e. Standard, REO, Short Sale, Probate, Auction, NOD, etc., at the time of listing.
standard_status: Option<StandardStatus>The status of the listing as it reflects the state of the contract between the listing agent and seller or an agreement with a buyer (Active, Active Under Contract, Canceled, Closed, Expired, Pending, Withdrawn). This is a Single Select field.
state_or_province: Option<StateOrProvince>Text field containing the accepted postal abbreviation for the state or province.
state_region: Option<String>A sub-section or area of a defined state or province. Examples would be the Keys in FL or Hudson Valley in NY.
status_change_timestamp: Option<DateTime<FixedOffset>>The transactional timestamp automatically recorded by the MLS system representing the date/time the listing's status was last changed.
stories: Option<f64>The number of floors in the property being sold.
stories_total: Option<f64>The total number of floors in the building. In the case of multi-dwelling structures, this is the entire structure and not the individual dwelling being sold.
street_additional_info: Option<String>Information other than a prefix or suffix for the street portion of a postal address.
street_dir_prefix: Option<StreetDirection>The direction indicator that precedes the listed property's street name.
street_dir_suffix: Option<StreetDirection>The direction indicator that follows a listed property's street address.
street_name: Option<String>The street name portion of a listed property's street address.
street_number: Option<String>The street number portion of a listed property's street address. In some areas the street number may contain non-numeric characters. This field can also contain extensions and modifiers to the street number, such as "1/2" or "-B". This street number field should not include Prefixes, Direction or Suffixes.
street_number_numeric: Option<f64>The integer portion of the street number.
street_suffix: Option<String>The suffix portion of a listed property's street address.
street_suffix_modifier: Option<String>The Street Suffix Modifier allows the member to enter a unique Street Suffix that was not found in the Street Suffix pick list or to extend or prefix the suffix.
structure_type: Option<Vec<StructureType>>The type of structure that the property completely or partially encompasses. For example, House or Cabin are the overall structure and typically sold or leased as a whole. Multi Family and Docks may be sold in whole, but are often sold or leased by unit/slip. This field is the type of structure as opposed to style, which is under the Architectural Style field.
sub_agency_compensation: Option<String>The total commission to be paid to the Sub Agency, expressed as either a percentage or a constant currency amount.
sub_agency_compensation_type: Option<CompensationType>A list of types to clarify the value entered in the SubAgencyCompensation field. For example $, % or some other clarification of the SubAgencyCompensation.
subdivision_name: Option<String>A neighborhood, community, complex or builder tract.
supplies_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
syndicate_to: Option<Vec<SyndicateTo>>When permitted by the broker, the options made by the agent on behalf of the seller, where they would like their listings syndicated. i.e. Zillow, Trulia, Homes.com, etc.
Becoming more common in the industry, MLS's are hosting a separate "Public Remarks" for syndication purposes. This field should be defaulted to containing the Public Remarks, but upon broker decision, modified to include contact and other information denied by IDX rules, but allowed under local and national regulations.
tax_annual_amount: Option<f64>The annual property tax amount as of the last assessment made by the taxing authority.
tax_assessed_value: Option<f64>The property value as of the last assessment made by the taxing authority.
tax_block: Option<String>A type of legal description for land in developed areas where streets or other rights-of-ways delineate large parcels of land referred to as divided into lots on which homes or other types of developments are built. An example would read "Lot 12 of Block 45 of Tract 3002 of the City of San Dunes, Desert County." Such a description would also reference an official plat filed with the clerk or recorder for that area which shows the location of the block and often the dimensions of the lots therein.
tax_book_number: Option<String>Some systems of parcel identification incorporate a method which utilizes a county identifier, a tax book number, a tax map number and a parcel identification number.
tax_legal_description: Option<String>A type of legal description for land in developed areas where streets or other rights-of-ways delineate large parcels of land referred to as divided into lots on which homes or other types of developments are built. An example would read "Lot 12 of Block 45 of Tract 3002 of the City of San Dunes, Desert County." Such a description would also reference an official plat filed with the clerk or recorder for that area which shows the location of the block and often the dimensions of the lots therein. The text here is also an index into the property as described by the County Recorder.
tax_lot: Option<String>A type of legal description for land in developed areas where streets or other rights-of-ways delineate large parcels of land referred to as divided into lots on which homes or other types of developments are built. An example would read "Lot 12 of Block 45 of Tract 3002 of the City of San Dunes, Desert County." Such a description would also reference an official plat filed with the clerk or recorder for that area which shows the location of the block and often the dimensions of the lots therein.
tax_map_number: Option<String>Some systems of parcel identification incorporate a method which utilizes a county identifier, a tax book number, a tax map number and a parcel identification number.
tax_other_annual_assessment_amount: Option<f64>Any other annual taxes, not including the tax reported in the TaxAmount field, as of the last assessment made by the taxing authority.
tax_parcel_letter: Option<String>Some systems of parcel identification incorporate a method which utilizes a county identifier, a tax book number, a tax map number and a parcel identification number.
tax_status_current: Option<Vec<TaxStatusCurrent>>The current tax status of the mobile home in cases where the land or space is included in the sale.
tax_tract: Option<String>A type of legal description for land in developed areas where streets or other rights-of-ways delineate large parcels of land referred to as divided into lots on which homes or other types of developments are built. An example would read "Lot 12 of Block 45 of Tract 3002 of the City of San Dunes, Desert County." Such a description would also reference an official plat filed with the clerk or recorder for that area which shows the location of the block and often the dimensions of the lots therein.
tax_year: Option<f64>The year in with the last assessment of the property value/tax was made.
tenant_pays: Option<Vec<TenantPays>>A list of services or items that the tenant is responsible to pay.
topography: Option<String>The state of the surface of the land included with the property. i.e. flat, rolling, etc.
total_actual_rent: Option<f64>Total actual rent currently being collected from tenants of the income property.
township: Option<String>A subdivision of the county.
transaction_broker_compensation: Option<String>The total commission to be paid to the transaction facilitator, expressed as either a percentage or a constant currency amount.
transaction_broker_compensation_type: Option<CompensationType>A list of types to clarify the value entered in the TransactionBrokerCompensation field. For example $, % or some other clarification of the TransactionBrokerCompensation.
trash_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
unit_number: Option<String>Text field containing the number or portion of a larger building or complex. Unit Number should appear following the street suffix or, if it exists, the street suffix direction, in the street address. Examples are: "APT G", "55", etc.
unit_type_type: Option<Vec<UnitTypeType>>This field is a list of the types used in the Unit Type repeating elements. The Type is a list of possible Unit Types. i.e. 1, 2, 3 or 2 Bed, Studio, Special Loft, etc. Each selected are expected to appear as the "[type]" in the related UnitType fields in a flattened implementation (RETS 1.x only) of the room fields. A relational implementation of UnitTypes must omit the type from the field name and use UnitTypeType to create a vertical representation of the various unit types. The fact that the field repeats the word "type" is intentional.
unit_types: Option<String>A collection of types of units included in the income (multi-family) property. The collection includes a type, beds, baths and other aspects of the type of unit behind described.
units_furnished: Option<UnitsFurnished>Are the units furnished? i.e. All Units, Varies By Unit, None.
universal_property_id: Option<String>The Universal Property Identifier is a unique identifier for all real property in the US and Canada. It is based on country and local identification methods and is limited to real property. For cases such as shares of real property, units, and other more granular cases, please utilize the UniversalPropertySubId.
universal_property_sub_id: Option<String>The Universal Property Sub Identifier is a unique identifier for all sub sets or shares of real property in the US and Canada. This may include Stock Cooperatives, Community Apartment, Units for Rent, etc. Informally abbreviated as "UPSI", It is based on country and local identification methods just as the UPI, but is limited to sub sets or shares of real property. For cases of complete real property, please utilize the UniversalPropertyId field.
unparsed_address: Option<String>The UnparsedAddress is a text representation of the address with the full civic location as a single entity. It may optionally include any of City, StateOrProvince, PostalCode and Country.
utilities: Option<Vec<Utilities>>A list of the utilities for the property being sold/leased.
vacancy_allowance: Option<f64>An estimate of the amount of rent that may be foregone because of unoccupied units.
vacancy_allowance_rate: Option<f64>An estimate of the percent of rent that may be foregone because of unoccupied units.
vegetation: Option<Vec<Vegetation>>A list of the type(s) of vegetation on the property. Note that this is not for farm crops, but more residential type vegetation.
videos_change_timestamp: Option<DateTime<FixedOffset>>System generated timestamp of when the last update or change to the videos for this listing was made.
videos_count: Option<f64>The total number of videos or virtual tours included with the listing.
view: Option<Vec<View>>A view as seen from the listed property.
view_yn: Option<bool>The property has a view.
virtual_tour_urlbranded: Option<String>A text field that holds the URL for a branded virtual tour of the property.
virtual_tour_urlunbranded: Option<String>A text field that holds the URL for an unbranded virtual tour of the property.
walk_score: Option<f64>A walkability index based on the time to walk from a property to near by essentials such as grocery stores, schools, churches, etc. See www.walkscore.com for more information and requirements for using WalkScore.
water_body_name: Option<String>The name, if known, of the body of water on which the property is located. (E.g., lake name, river name, ocean name, sea name, canal name).
water_sewer_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
water_source: Option<Vec<WaterSource>>A list of the source(s) of water for the property
waterfront_features: Option<Vec<WaterfrontFeatures>>Features of the waterfront on which the property is located.
waterfront_yn: Option<bool>The property is on the waterfront.
window_features: Option<Vec<WindowFeatures>>A list of features or description of the windows included in the sale/lease.
withdrawn_date: Option<NaiveDate>Date the listing was withdrawn from the market. This is not when a listing contact was cancelled or closed, but a withdrawal from the market while the contract between the seller and listing agent is still in effect and an offer has not been accepted. This is the date entered by the agent reflecting when the change occurred contractually, not a timestamp of when the change was made in the MLS.
wooded_area: Option<f64>Measurement or percentage of the property that is wooded or forest.
workmans_compensation_expense: Option<f64>The annual expense that is not paid directly by the tenant and is included in the Operating Expense calculations.
year_built: Option<f64>The year that an occupancy permit is first granted for the house or other local measure of initial habitability of the build. The type definition permits an empty value with an attribute noting that it is an unknown date or that the building is new construction. While constraints have not been applied, convention at the time of adoption has this as a four (4) digit year value.
year_built_details: Option<String>A description of the details behind the year the structure was built.
year_built_effective: Option<f64>The year a major rebuild/renovated of the structure occurred.
year_built_source: Option<YearBuiltSource>Add a list of sources of the year built. i.e. Appraiser, Assessor, Builder, Estimated, etc.,
year_established: Option<f64>The year the business being sold was established.
years_current_owner: Option<f64>The number of years the current owner has had possession of the business.
zoning: Option<String>A division of the city or county into areas of different permissible land uses. This Zone field should be used for the short code that is commonly used. For full textual descriptions please use the ZoningDescription field.
zoning_description: Option<String>A list of descriptions of the zoning of the property. The zoning codes are often non-descriptive and variant. Zoning Description is a more descriptive form of the zoning for the property, i.e. Agricultural, Residential, Rezone Possible, etc. Specific zone codes must be added to the Zoning field.
Trait Implementations
impl Clone for Property[src]
impl Debug for Property[src]
impl Default for Property[src]
impl<'de> Deserialize<'de> for Property[src]
fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error> where
__D: Deserializer<'de>, [src]
__D: Deserializer<'de>,
impl Serialize for Property[src]
Auto Trait Implementations
impl RefUnwindSafe for Property
impl Send for Property
impl Sync for Property
impl Unpin for Property
impl UnwindSafe for Property
Blanket Implementations
impl<T> Any for T where
T: 'static + ?Sized, [src]
T: 'static + ?Sized,
impl<T> Borrow<T> for T where
T: ?Sized, [src]
T: ?Sized,
impl<T> BorrowMut<T> for T where
T: ?Sized, [src]
T: ?Sized,
fn borrow_mut(&mut self) -> &mut T[src]
impl<T> DeserializeOwned for T where
T: Deserialize<'de>, [src]
T: Deserialize<'de>,
impl<T> From<T> for T[src]
impl<T, U> Into<U> for T where
U: From<T>, [src]
U: From<T>,
impl<T> ToOwned for T where
T: Clone, [src]
T: Clone,
type Owned = T
The resulting type after obtaining ownership.
fn to_owned(&self) -> T[src]
fn clone_into(&self, target: &mut T)[src]
impl<T, U> TryFrom<U> for T where
U: Into<T>, [src]
U: Into<T>,
type Error = Infallible
The type returned in the event of a conversion error.
fn try_from(value: U) -> Result<T, <T as TryFrom<U>>::Error>[src]
impl<T, U> TryInto<U> for T where
U: TryFrom<T>, [src]
U: TryFrom<T>,